Core Setup Components

Once customers have a Quik! account established, it is best to scope out the work needed for each part of their forms automation solution. Below is a common roadmap for setting up a Quik! implementation, with links to relevant articles.

Part 1: Determine form search user experience

In a typical form filling solution, customers must first provide some way for their users to choose which forms they want to work on.

• Typically accomplished with a form search function. The /forms/search REST endpoint offers several form attributes (Form Name, Company Name, Literature Number, etc.) which customers can perform query's against to help users narrow down exactly which forms they need from a larger list.
• Alternatively, customers can limit any kind of form selection experience for users, and simply present a static list of form(s) that users will always generate on a given page. Present a link or button that users click to call the Execute method to generate a pre-specified form or Form Group.

Form Search page example as seen in the Quik! Sample Website

Part 2: Determine how to prefill client information

Once a user has their forms, they often want to select client information to be prefilled onto the forms. Client data is usually stored in a CRM or internal client database where it is pushed to the selected form(s). To set this up, customers must establish field mapping that matches their data fields (first name, phone number, etc.) to Quik! base fields as named in the Quik! Field Definition. Customers can reach out to Quik! with their field names if assistance is needed on the best Quik! fields to match each data point with. Review the field mapping guide for more information on field mapping best practices.

Once field mapping is finished, customers must build a user interface that enables users to assign clients to roles on the selected forms. Otherwise, the Quik! Forms Engine will not know which fields to prefill on the forms. The /forms/roles/client REST endpoint will return a list of roles for a given set of Form IDs.

Choose Clients page example as seen in the Quik! Sample Website

Part 3: Determine how the Form Viewer will look

Once the user has selected their forms and added clients for prefill, the last step is to craft the Form Viewer where they will be completing the forms and moving them to the next step of the overall customer workflow. There are hundreds of properties that customers can configure to customize how the Form Viewer will look for their users (corporate logos, custom text, HTML buttons, etc.). This is also where customers must establish an e-signature integration if their users will be e-signing forms. No matter what, the Execute method must be called in order to generate the form and create the HTML file, which customers must then present to the user in some way (new browser tab, iframe, etc.).

Form Viewer example