Page Comparison

The following assumptions are included in the design of this system:

...

1. The customer will implement the Quik! Forms Engine web service within their application.
    
2. The customer must have a valid account with Quik! and supply credentials with each request.
    
3. The Quik! Forms Engine component will have read/write access to the web-server's temporary file location or a location specified by the customer.
   
   
4. The customer will implement one or more web services with a Quik! server in order to retrieve/send data used with the Quik! Forms Engine.
   
   
5. To use DocuSign:
   1. E-signing requires SSL (HTTPS) and without it will result in "Access Denied" in Internet Explorer browsers.
   2. Customers will directly procure and use their own account with DocuSign, set up a DocuSign API Key and reference Efficient Technology Inc as the referral source.
   3. Customer assumes responsibility for the validity and acceptance of electronic signatures with the form owners, if electronic signature is used.
   4. Customer will deploy the QuikESignTransport in the same domain as the HTML forms in order to facilitate the e-signing process.
   5. Customer will implement the DocuSign API to poll for status and retrieve final documents from DocuSign – this software only includes the ability to send documents to DocuSign to begin the signature process.

...