First and foremost, forms generated by Quik! do NOT manage, store, archive, interpret or make it possible for Quik! systems to access client data entered onto forms. While Quik! may offer software that can store data on a client’s behalf, using a Quik! form by itself via a link, API or other access method will not cause Quik! to store the form data. Quik! API’s primary function is to help customers manager their library of forms and to deliver forms to users when they need them and on the device they’re using. With this goal in mind, Quik! Forms are designed to keep data in the control of the customer and user.

If you are interested in the security model of data that a turnkey Quik! application provides, please the specific security white paper for that product. This white paper applies to the APIs and forms themselves.

How Forms Are Generated

In order to view a Quik! Form it must first be generated by the Quik! software. By always running a Quik! software component to generate the form the user will always receive the latest form version and never turn in a form that is no longer in service. The Quik! software, at its core, is like the engine of a car: it takes in fuel and creates power, or in Quik!’s terms, it takes in data and outputs a form for the user to see.

Like an engine can be used to power a car, boat, plane, truck and more, the Quik! Forms Engine is used to power websites, mobile apps, desktop software, server-side software and more. Regardless of what application is using the Quik! Forms Engine, the underlying operations are always the same, as illustrated in the pictures below.

Option 1: Install Quik! on Your System

For convenience, security and control, customers can implement the Quik! API (QuikFormsEngine.dll) directly within their application.

Option 2: Use Quik! as a Web Service

For customers who cannot implement the Quik! software directly within their application, a web service can be used instead. The Quik! Forms Engine web service is the same QuikFormsEngine.dll hosted by Quik! and works essentially the same way as the software but is accessible via SOAP and REST methods.

Process Flow Explained

1. The Quik! software is provided with data to prefill onto forms (DLL or Web Service) and run.
2. The Quik! software calls the Quik! Environment to retrieve the requested forms
3. The forms are sent back to the customer application, populated with the customer data
4. The customer application serves the resulting Quik! form in HTML format to user's browser
5. The forms display prefilled with data
6. The user enters data and completes the form
7. The form can be sent back to the customer application for further processing, signature and storage.