...
You must configure the default pre-population rules
...
so that data from supported CRMs, PreciseFP, and the Client Folder will fill out Owner fields on a form regardless of the client type
...
. The prefix fields for each Client Type are used to map client information to the fields on a form.
| Info |
|---|
Example: The list below displays some example connections:
|
...
|
...
|
...
|
...
Insured -> Insure fields in PDF
...
|
...
|
| Tip |
|---|
Pros – This will eliminate issues with |
...
Entity/ |
...
Trust data incorrectly populating the Owner fields on forms that do not support entity data. Data on forms will |
...
be |
...
correct. |
| Warning |
|---|
Cons – For multi-use forms |
...
that use the same fields |
...
for Owners and Entities, |
...
data |
...
will not be filled in automatically. |
Compromise – The Blue Arrow
...
dropdown allows you to manually select which client data you need to appear on the form.
...
| title | Step 1: Configuring the prefixes for client types |
|---|
...
To make sure the Client Types are configured correctly:
| Rw ui steps macro | |
|---|---|
Navigate to Administration > List Domains > Client Types (149). |
...
Client types names
...
2
...
Check that the values specified in the Prefix column |
...
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.
...
| title | Step 2: Configuring Application Preferences |
|---|
...
1
...
2
...
match the actual Client Type.  |