When the need for new fields arises (based on customer feedback, new laws and regulations, new form designs and new industry processes), ETI must consider multiple factors in deciding how best to automate the new fields. These factors include, but are not limited to:
- Which level of field definition to place the new field
- Top level field or base level field
- Service Level to apply to the field
- The primary intent of how the field will be used
- Pre-filled only from existing data
- Submitted only from manually entered data
- Pre-filled, submitted and validated
- How Quik! software users will experience the new field
- How will the user know to pre-fill the new field over another field
- Can the user pre-fill the field
- How data processing systems will use the new data
- How Quik! software will need to be modified to support and/or utilize the new field
- New fields impact both software used by customers and systems used internally by ETI
- The expected data format and content of the field, if any
- Which of the existing Quik! Forms will need to be updated to include the new field definition
- Who will benefit from the new field and how
- All users vs. selected users vs. back-office users vs. systematic processes, etc.
- How will the field be supported by the Quik! Forms and Customer Service Teams
- How to train the Quik! Forms Team to build and support the new field
At first glance, it might seem simple enough to define and add a new field, but the actual definition process is quite comprehensive to ensure the field is designed with the lowest risk and longest longevity. ETI is constantly adding new fields to the definition and publishes these new fields in software form every 3 to 6 months.