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.
Configuring Form Field Sync
Configuring Dropdown: Show data from the forms
Add a feature to the Blue Arrow dropdown select that will allow selection from Client Folder data, as well as data entered on this or another form in the work item. This is helpful for an advisor when filling out paperwork in a bundle, as it allows to re-use data entered on a form that is not yet stored in the client folder.