...
- 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 given pre-specified form or Form Group.
Form Search page example as seen in the Quik! Sample Website
...
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.
...
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.).
...