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.
...
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 the info (i.e. save it) and respond to the Submit event to indicate success or failure to the form viewer) 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.<Sample code for response message?>
Austin Logie (Unlicensed) The FormViewer does nothing with the SubmitURL response, currently.
2. Configure the Submit event in the Quik! API
- Set HTMLButtonSubmit.Show property to TRUE to show the Submit button.
- Provide a value for the HTMLButtonSubmit.SubmitURL property to set the URL location of where the submitted forms will be posted.
OPTIONAL: After receiving the submitted data, customers also have the option to get the PDF version of the form with the GetPDFForms method. Use this method to retrieve a PDF for the HTML form that was submitted to your server. This method is best used behind the scenes after your server receives a form's posted form data (i.e. HTTP POST) during a submit event. For example, if a user submits a form for validation and it passes validation you might call this service to get the PDF for archiving or routing through your workflow. More information here.
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
...
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 the info (i.e. save it) and respond to the Submit event to indicate success or failure to the form viewer) 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.<Sample code for response message?>
Austin Logie (Unlicensed) The FormViewer does nothing with the SubmitURL response, currently. So only if validations passed, ESign routine is performed.
2. Configure the Submit event in the Quik! API
- Configure all required e-sign settings in your Quik! implementation (more information in the E-Signature Integration section)
- Set HTMLButtonSubmit.SubmitURL property to TRUE to set the URL location of where the submitted forms will be posted.
- Set SignSubmitCombined property to TRUE - this . 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. Customers can perform validations on the submitted data, then return a success message to the form viewer. 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.
...