Configuring SubmitContentType to generate an e-signable PDF

The SubmitContentType property can be used when customers prefer to process submitted data in JSON format, rather than key value pairs or UrlEncoded. This JSON can then be used when calling the Quik! Print API, in order to create a PDF of the original form.

NOTE: The JSON SubmitContentType was specifically designed to work with the Quik! Print API and therefore has some limitations, notably the JSON will NOT include any hidden fields. Thus, if your intent is to capture the hidden field data in JSON format, that data will be missing and is only available via the default key value pair format.

Follow the steps below to achieve this.

1. Customer generates HTML form with Submit button displayed

   1. Set HTMLButtonSubmit.Show property to TRUE to show the Submit button

   2. Set HTMLButtonSubmit.SubmitURL property to the location of where the submitted form data will be posted

   3. Set SubmitContentType property to RequestContentType.Json

2. User completes the form, and when finished, clicks the Submit button to post the form data to customer’s server

3. Once customer receives the form data JSON, customer calls the REST Print service to post the same exact JSON with one important change:

   1. Set the ForSign parameter to TRUE. This will allow for signature fields to be included on the PDF form

4. The REST Print service will return a PDF form with signature fields and all original field data included. Customer can now send this PDF to e-signature vendors with signature fields included for clients to e-sign.