Page Comparison

The Callback E-Sign Integration is for customers who want to use Quik! Forms directly with DocuSign without having to play a part in calling the DocuSign APIs to kick off the signing process. This methodology was specifically designed for customers using SalesForce.com and similar systems where it is difficult or impossible to intercept a POST from the form in order to call the DocuSign APIs. 
While this method will start the e-signing process, customers will still need to call the DocuSign APIs for other functions (e.g. to check for status, to download the final signed document, etc.). The assumption in this model is that the customer has an existing account with DocuSign and sets up an OAuthToken (see next section on setting up the OAuthToken) with Quik! to call the API on behalf of the customer. An OAuthToken can be established via web service or manually by request. This integration method is optimal for retail or individual customers, or enterprise-level customers who need a streamlined method to start the envelope process (e.g. SalesForce users).

...

1. The user clicks the "Sign" button, which captures the envelope data needed for signing.
   1. The Sign button event displays the Quik! Form's e-sign popup screen.
   2. User enters relevant envelope data and clicks the SEND button.
   3. The SEND event posts the form data directly to Quik! (https://websvcs.quikforms.com/rest/esignature/docusign/sign )
2. Quik! starts an envelope with DocuSign
   1. The customer must have previously set up an OAuthToken with Quik! and DocuSign (only once per CustomerID, CustomerUserID and Docusign environment) 
   2. Quik! uses the provided information to lookup the Customer's OAuthToken stored by Quik! and then calls the DocuSign REST web service to start the envelope
3. DocuSign responds with the EnvelopeID
   1. The EnvelopeID is stored with the QFVUNID in the Quik! system for later retrieval by the customer via web service as a backup method for retrieving EnvelopeIDs.
4. Quik! responds to user's Quik! Form (HTML window) with the EnvelopeID in JSON format.
5. The user's Quik! Form posts the EnvelopeID to the Customer's SignCallBackURL in JSON format along with any status message returned by the signing process
   1. The HTML form's SEND event does a callback to the SignCallBackURL with the EnvelopeID.
   2. The customer's SignCallBackURL receives the EnvelopeID and should then respond in JSON format to the user's form with a status message. If customer has entered custom JavaScript using the ESignVendorSuccessJavaScript property, a JS command will run after a successful transaction.
6. Customer independently downloads the envelope and documents from DocuSign
7. The customer will be able to access/sign the form by logging into their DocuSign account.

...