All of Quik!'s HTML forms are designed for seamless and easy e-signature with DocuSign. The default and simplest approach is to have the user click the "SIGN" button on the form to start the e-sign process. The form will display an inline pop-up that asks for "envelope" information or the info required by DocuSign including name, email, sign type, etc. The user will complete the data fields and click SEND. This event will then send the form to your server which will then relay it to the Quik! server for preparation.

 To sign a document with DocuSign generally requires three major steps:

1. Create an envelope containing (performed by Quik!)
   1. Document
   2. Recipients
   3. Sign Field Location
2. Poll for status (performed by Customer)
3. Archive the signed document (performed by Customer)

Performed by Quik!

The first step requires a lot of processing and set up including:

• Creating a flattened, read-only PDF with form data
• Tagging the form with signature fields with location and role data in XML
• Setting up recipients to sign and receive forms, including attributes including:
  • Signing order
  • Recipient email addresses
  • Security settings for identity checks
• Initiating the e-sign process with DocuSign

Due to the complexity of the document, fields, roles, recipients and more, the process to generate the necessary data and final document to send DocuSign must be performed by a Quik! server. To enable this architecture, Quik! provides web service methods that give customers various methods to perform this first step.

Performed by Customer or Partner

The second and third step, to poll for status and download the final document, is the responsibility of the user interface, workflow and archive system that the customer is using. Since Quik! does not provide or manage the user experience beyond filling out the form and kicking off the e-sign process, the customer must call the DocuSign API directly using the EnvelopeID to get the status of the envelope and to download the final document for archival and workflow purposes.

E-Sign Workflow Options

Electronic signature by itself is not difficult, per se, but the desired workflow can make the signature integration more challenging. Here are several different approaches to consider in the design of your e-sign workflow.

• Straight To DocuSign
• Submit and Validate, Then Sign
• Submit and Redirect To Sign

Straight To DocuSign

If your forms-based process results in a form that is ready to sign, then the process is straight-forward.

1. User completes the form details.
2. User clicks the SIGN button and fills in the needed data for the e-sign popup window.
3. User clicks the SEND button and the form is sent to DocuSign* to start the signing ceremony.
4. DocuSign sends out email notifications to the each signer and recipient in order.
5. Each recipient signs and completes the process.
6. Final signed document is available for download from DocuSign.

This process may be most applicable to smaller organizations or business processes that don't require electronic validation and processing before signing a document.
*The steps to prepare the PDF and XML for DocuSign are still performed by Quik!.

Submit and Validate, Then Sign

If you need to validate and process the form prior to signature, then this basic workflow may serve your needs.

1. User completes the form details.
2. User clicks the SUBMIT button on the form to send data to a server for processing.
3. Server receives, validates and processes data, then replies with next step for user.
4. If next step is to sign, then user clicks the SIGN button and fills in the needed data for the e-sign popup window.
   1. If next step is to not sign, then customer decides next steps (e.g. redirect to a new page, print form, wait for approval, etc.)
5. User clicks the SEND button and the form is sent to DocuSign* to start the signing ceremony.
6. DocuSign sends out email notifications to the each signer and recipient in order.
7. Each recipient signs and completes the process.
8. Final signed document is available for download from DocuSign.

This process allows for forms and related data to be validated and processed before signing. For example, an account can be opened or approved prior to signature.
*The steps to prepare the PDF and XML for DocuSign are still performed by Quik!.

Submit and Redirect To Sign

If you need to validate and process the form prior to signature, and sign the document at a later date using your own process, then this basic workflow may serve your needs.

1. User completes the form details.
2. User clicks the SUBMIT button on the form to send data to a server for processing.
3. Server receives, validates and processes data, then replies with next step for user.
4. User is redirected to a new web page and provided status of the workflow.
5. When ready, the customer's server creates and sends the DocuSign envelope*.
6. DocuSign sends out email notifications to the each signer and recipient in order.
7. Each recipient signs and completes the process.
8. Final signed document is available for download from DocuSign.

This process allows for forms and related data to be validated and processed before signing. For example, an account can be opened or approved prior to signature.
*The steps to prepare the PDF and XML for DocuSign are still performed by Quik!.

Seamless E-Signature Methodology Options

There are a variety of ways in which a customer can implement the e-sign component with the Quik! Forms Engine. The two main approachs are called:

1. Callback E-Sign Integration
2. Pass-Thru E-Sign Integration
3. Self-Serve E-Sign Integration

The Callback option is designed to be the simplest and fastest to implement. This is also the best choice for when your application cannot control or has limited ability to interact with the Quik! HTML form and e-signing process (e.g. your server cannot accept much or any data, your application cannot take control of the process or data, etc.). Your system will ultimately be called by the form via a callback URL that you designate to receive the DocuSign EnvelopeID if desired.
The Pass-thru option is designed to be nearly as easy to implement as the Callback method but the data and control of the process passes through your system. Your system acts as the Pass-Thru of the data between your form and Quik!. It's a great option when you want to capture data, process information and stop the process in the middle.
The Self-Serve option was designed to be easy to implement but 100% flexible for customers who wants to control and implement an e-sign process according to their specific workflow needs. This method can be broken down into simple web services so you can design your own user experience, or practically turnkey using the Quik! user interface. This is by far the most flexible option.

 NOTE: The Callback method uses the DocuSign OAuthToken instead of passing your DocuSign credentials, which is required in the other two methods.