Assumptions

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

1. The customer will implement the Quik! Forms Engine dll or web service within their application.
2. The customer will create a secured SSL connection between their user's browser and their web application for delivering Quik! output and forms to their user.
3. The customer must have a valid account with Quik! and supply credentials with each request.
4. Quik! servers do not store, save or persist any client data that may be transmitted to the server for the purposes of generating, printing, signing or transmitting forms. Data, if sent, is encrypted during transport and discarded the moment it has been processed.
5. 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.
6. The customer's web server or program is responsible for deleting any temporary files that are generated by the use of the software (e.g. HTML files, error logs, etc.).
7. 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.
8. Requests to combine multiple forms into a single form package are limited to 100 FormIDs.
9. Form pages automatically expire and are no longer viewable after a maximum of 10 days from the date they are generated, or earlier at the customer's discretion.
10. Forms will not fully function for iPad users using Private Browsing (e.g. the SAVE and LOAD buttons will not allow for local storage and saving as designed by Apple).
11. 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.
12. Editable PDFs cannot be saved unless the user has a version of Adobe Acrobat that enables saving. Also, field collisions with combined forms may occur in editable PDFs due to standard PDF functionality and design.
13. Internet Explorer may restrict certain features (e.g. print, save, etc.) if the Quik! Form is not hosted from a HTTP or HTTPS location.
14. Internet Explorer may have JavaScript disabled on a specific page, leading to reduced functionality of our HTML Forms. i.e. - Missing 'Save' button from top navigation or 'Print' button generating a JSON file rather than a PDF.