Please Read!
...
- The customer will implement Quik! within their application (i.e. Quik! is not necessarily hosting an application nor building one on behalf of enterprise customers).
- The customer must have a valid Master Customer Account with Quik! and supply Master Credentials with each request (end-user credentials that are not the Master Credentials will not work).
- If the Quik! Forms Engine component is installed on your computer it may need read/write access to your computer or server's temporary file location or a location specified by you.
- The customer will implement one or more web services with a Quik! server in order to retrieve/send data used with the Quik! services and APIs.
- As of April 2020, supported browsers include: Internet Explorer 9.0+, Safari 5.1+, Firefox 12+, Opera 12+, Chrome 19+. Browsers must have Javascript enabled
- To use e-signature:
- E-signing requires SSL (HTTPS) and without it will result in "Access Denied" in Internet Explorer browsers.
- Customer will directly procure and use their own account with the signing vendor (i.e. DocuSign, Signix), set up a vendor-specific API Key and reference Efficient Technology Inc as the referral source.
- Customer assumes responsibility for the validity and acceptance of electronic signatures with the form owners, if electronic signature is used.
- Customer may need to deploy the QuikESignTransport in the same domain as the HTML forms in order to facilitate the e-signing process.
- Customer will be responsible for calling the e-sign vendor's APIs to retrieve the current signing status and to download final signed documents (i.e. Quik! is only designed to send documents to e-sign vendors to kick off the e-signing process)
...