Quik Forms Mapping & Build Policies

Efficient Technology Inc. maintains a library of thousands of forms with constant updates and new additions. In addition, Quik! is leading the way in developing form automation standards for the entire industry, requiring Quik! to be flexible and immediately responsive.

Each new form that is built offers new opportunities for the Quik! Field Definition to change and grow to meet new demands and requirements.

When considering the constantly changing environment of forms and the breadth of the Quik! Field Definition (over 1.2 million fields as of Summer 2023): it has become relatively impossible to build every form to perfection or to take advantage of each new field added to the definition. Adding a field to the definition takes careful planning to train the form builders, update Quik! software, update existing forms with the new fields, and roll out the changes to the industry.

Form Building Principles:

As a result of the complexity involved with forms automation, Quik! employs the following principles when building forms:

The "Standard" Service Level is intended to make it easy to pre-fill standard form fields (not premium form fields)
The "Premium" Service Level is for submitting data electronically from the form but not for pre-filling purposes.
- "User Defined Fields" are an option the Quik! team can create for “customer-only” forms when Quik! does not find the field common enough to add to the Quik! Field definition.
Quik! uses its best efforts to ensure forms adhere to the Quik! Form Standard and appropriate service levels by putting each form through a rigorous process of pre-build, build, test, review, and final review by the form owner (optional).
Quik! will fix form field errors and treat the fixes as a high priority.
The Quik! Field Definition allows for the ability to "bundle" or merge multiple Quik! Forms into a single document (form bundle), creating links between repetitive fields across the forms.

Important notes:

Quik! does not guarantee flawless bundling of forms. In rare instances, fields across multiple forms may create conflicts and unexpected outcomes.
- For example, if multiple forms in the package contain fields with the same name, the fields will prefill with the same value, even if different values are expected. This behavior occurs due to our Quik! Field Definition. To prevent this, you can configure Form Group Instances, which allows distinct values to be used for fields with the same name across forms.
“Generic” field names - When a field on a form does not match a field defined in the Quik! Field Definition: the field is given a random field name with a prefix name that reflects the form's naming convention (e.g., NFSVC2349.txt1.01 for text fields or NFSVC2349.chk1.01 for checkboxes).
- Please note: We advise against mapping to Generic field names, as they may change in future form updates and are not part of our Quik! Field Definition.

In This Section...