Prefix fields

Configure the default pre-population rules, so that data from the client folder is pre-populated to Owner fields regardless of the type of client. This will allow business rules for the pre-population of forms on work item creation to align with the type of client. 

Example: 

Person or Prospect -> Owner fields in PDF 

Business/Entity -> Entity fields in PDF 

Insured -> Insure fields in PDF 

Trust -> Trust fields in PDF 

Pros – This will eliminate issues with entity/trust/ data incorrectly populating Owner fields on forms that do support entity data. Data will not be wrong on forms. 

Cons – For multi-use forms, where the same fields are used for Owners and Entities, no data pre-population will occur. 

Compromise – Blue Arrow drop-down select will allow an easy two-click population of the client folder data once in the form. 

 Step 1: Configuring the prefixes for client types

1	Navigate to Administration > List Domains > Client Types (149).	Client types names
2	Check the Prefix column for value and confirm that the Quick! Prefix is correct. The prefix fields are used for proper form mapping.	Client types prefixes
3	Click Save and Close.

Application Preferences

Three application preferences must be enabled: 

• Form Field Sync: List of fields that will be synced for excluded forms 

• Dropdown: Show data from the forms 

• Starting Point: Enable prompting inside html5 viewer 

Form Field Sync: List of fields that will be synced for excluded forms 

Change the default so that form synchronization is off for all forms, unless a form has explicitly been approved for sync automation. As a default, forms can have certain Quik prefixes enabled/disabled for syncing within a bundle. Best practice would be to have syncing off by default. This avoids the issue where two forms within the same bundle may have the same field names, but different meanings. These issues typically present themselves on entity registration types where the owner field on the new account form and owner fields on other forms should not match.  

Example: On an ACH/Transfer form for an entity account that has owner fields, these would usually be an Authorized Individual and not necessarily the primary owner (the entity). Only forms that have been explicitly reviewed by registration type and may have specific business rules built in Forms Mapping should be allowed for syncing. This approach eliminates data syncing issues across forms.