The Submit button is one of the most powerful features of the Quik! Forms Engine for enterprise customers. It is often leveraged in use cases when the customer needs users to send form data back to the customer's system for processing, archiving, or validating prior to e-signature. A submit event in the Quik! Forms Engine is very similar to a Save event, as both post form data to a specified location set by the customer. The primary difference between the two functions is that a Submit event always validates any Required Fields that may exist on the form (Required Fields are type of field rule, discussed here), and a Save event does not. This page explains how to implement some of the most common uses cases of the Submit button.

Above: Submit Button in the Quik! Form Viewer

Above: Error notification when attempting to submit a form without filling out Required Fields

Use Case #1: Submit form data for storage/archiving

The most basic use of the Submit button is to enable users to send form data to a customer's system for further processing, essentially making the Submit even the last step of a Quik! integration workflow. See steps below on how to implement a Submit button for this use case.

1. Determine a location to save the form data

Form data is submitted though a HTTP POST to a URL where customers can receive the posted data. The format of the data sent is value pair format by default, but can be changed to URL Encoded or JSON with with the SubmitContentType property.

Your URL must receive the posted data and process (i.e. save) it. Typically this information is saved into a database record but can also be saved to an XML file, JSON file or other flat file that is easily accessible to your system.

2. Configure the Submit event in the Quik! API

1. Set HTMLButtonSubmit.Show property to TRUE to show the Submit button.
2. Provide a value for the HTMLButtonSubmit.SubmitURL property to set the URL location of where the submitted forms will be posted.
3. OPTIONAL: Set the content type of the posted data with the SubmitContentType property.
4. OPTIONAL: Set a value for the HTMLButtonSubmit.SubmitJavascript property with your own javascript function to perform AJAX or custom processes instead of a HTTP POST.

Use Case #2: Submit form data prior to E-Signature

Another common use of the Submit button is to enable users to send form data to a customer's system prior to E-Signing with Quik!. This is a useful approach for storing and running validations on form data prior to sending for e-signature (at which point users will not be able to edit field information). See steps below on how to implement a Submit button for this use case.

1. Determine a location to save the form data

Form data is submitted though a HTTP POST to a URL where customers can receive the posted data. The data is sent the same way as any other HTTP POST event in value-pair format (field name:field value). Your URL must receive the posted data and process (i.e. save) it. Typically this information is saved into a database record but can also be saved to an XML file, JSON file or other flat file that is easily accessible to your system. 

2. Configure the Submit event in the Quik! API

1. Configure all required e-sign settings in your Quik! implementation (more information in the E-Signature Integration section)
2. Set HTMLButtonSubmit.SubmitURL property to TRUE to set the URL location of where the submitted forms will be posted.
3. Set SignSubmitCombined property to TRUE. This will cause the submit event to fire when the Sign button is clicked. 

When a user clicks the Sign button, a submit event will fire to first validate all the required fields (if any) are completed on the form, and then to post the data to the assigned URL. The E-Sign pop-up will then open, allowing the user to fill out all signer information and e-sign settings before sending the forms off for e-signatures.