The Quik! Field Definition is currently designed to meet form automation needs. As businesses change their policies, procedures, and workflows involving forms, Quik! incrementally upgrades the field definition to accommodate customer needs. Customers who use Quik! to automate their forms will find that the form automation solutions also need to adapt and change quickly.
...
If a field problem arises from bundling forms, report the issue to the Quik! Forms team, indicating all the forms involved. Then, discontinue bundling the problem form or warn users about the problem until it can be fixed.
| Warning |
|---|
DO NOT USE Non-Quik! (Generic) Fields for AutomationWhen building automation around the Quik! forms, you can safely rely on fields named according to the Quik! Field Definition, but not randomly named generic fields. If a non-Quik! (Generic) field is used for automation purposes, the field name may change without notice the next time the form is built. What is a “Generic” field name? - 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.,
|
...
Q: Can I map to generic fields?
A: NO. Quik! does not support mapping to generic fields as they are subject to change without notice. This has a high risk of breaking workflows and is against our policies. Quik! will NOT revert generic fields back to a previous version.
Q: Why does adding a new field take 90 days or more?
A: The process involves approvals, development, and scheduling the update in a software release. We always aim to address requests as quickly as possible.
...