Versions Compared

Old Version 11

changes.mady.by.user Kim Coker

Saved on

compared with

New Version Current

changes.mady.by.user Sarah Zacky

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 repQuik!tive repetitive fields across the forms.

Note

Important notes:

  • Quik! does not guarantee flawless bundling of forms. In rare instances, fields across multiple forms may create conflicts and unexpected outcomes.The leading cause of this problem - Is the difference between text boxes and form checkboxes. If a textbox on one form has a field name the same as a checkbox on another form and the two forms are bundled, Adobe will automatically treat both fields as textboxes or checkboxes. Quik! is working on an improved definition to fix this problem

    • 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.FieldName1).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...

...