The Role of Customers Using Quik! Forms Automation

The Quik! Field Definition is currently designed to meet the automation needs on a form. As businesses change their policies, procedures and workflow that involves forms, Quik! makes incremental upgrades to the field definition to accommodate customer needs. Customers who use Quik! to automate their forms will find that the forms automation solutions also need to adapt and change quickly. However, in certain instances, it is not possible and not realistic for Quik! to move as fast as customer requirements change. The end result is that the automation is subject to imperfections and requires that the customer partner with Quik! to find a resolution, sometimes requiring the customer to make changes to their process flow and/or form design.
To better anticipate and deal with form changes and field inconsistencies, customers should follow these guidelines:

• When designing a solution to pre-fill forms, the best practice is to prefill common, repetitive fields found in our Standard Service Level – prefilling the Premium Service Level fields is possible but more costly to implement and maintain over the long-run.
• If a field problem arises from bundling forms, report the problem to the Quik! Forms team indicating all the forms involved, and then discontinue bundling the problem form or warn users about the problem until it can be fixed.
• When building automation around the Quik! forms, you can safely rely on fields named according to the Quik! Field Definition, but not randomly named fields:
  • If a non-Quik! field is used for automation purposes, the field name may change without notice the next time the form is built
  • ETI does not promise to build new versions of a form with the same non-Quik! field names that were used in the old version
• When requesting a new field to be added to the Quik! Field Definition, expect the process of adding the field to take at least 90 days or longer, depending on whether ETI determines the field can be added and when the next release of the software is scheduled for
  • ETI always makes best efforts to add fields and deploy them fast to satisfy customer needs
  • If ETI releases a field prior to full production release, there are defined methods for using the new field as a non-Quik! field in the Quik! software (please refer to software reference guides)