Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

At the heart of the Quik! Forms Engine is a core architecture that all Quik! products and services share in common: the Quik! Field Definition. The purpose of the Field Definition is to make all forms and documents work in the same manner through a defined set of field types with common field names. Sometimes field mapping is needed when pulling customer data from a system like Salesforce, then matching that data to fields on a Quik! form. The pages below will detail the various ways Quik! can make that easier.

Field Mapping APIs

Quik! maintains a web service for managing your implementation and field mapping. Details on these APIs can be found on the Configuration and Field Mapping Web Service page.

Quik! Field Definition

While the Quik! Forms Engine is the primary way in which Quik! delivers forms, the Quik! Field Definition is the power behind how we manage them. The purpose of the Quik! Field Definition is to make all forms and documents work in the same manner through a defined set of field types with common field names. Whether a given form's job is to open a new account or change an address or inform a customer about something, any time the form requires the customer's first and last name, that name should appear on the form in the correct place regardless of how the form is visually designed. The Quik! Field Definition makes this possible by having the same field on different forms built the exact same way.

For an in-depth look at the Quik! Field Definition, naming conventions, and a list of all Quik! fields, please visit the Quik! Field Definition Guide. Consulting this guide has proven immensely helpful for customers when setting up field mapping for their implementation.


  • No labels