Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

For Blue Arrows to work, you must enable three application preferences: 

  • pdf.edit.html5.prompting.enabled - enable prompting inside the PDF viewer

  • pdf.view.dropdown.include.forms - allow dropdowns to show data from the forms 

  • pdf.edit.alwaysSync.fieldNames - list the fields that will be synchronized for forms that are excluded from sync

Enable Prompting in the PDF Viewer

Enable Data from Other Work Item Forms

Add a feature to the Blue Arrow dropdown that will pull data from other forms that have been filled out 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.

Configure Form Fields for Synchronization

Usually, the form fields get automatically populated by the data available in Client Folders or in other forms. Also, when a user enters a value in a form, it is then written to the Client Folder or to other forms. As best practice, disable synchronization in one or both directions on all forms and then explicitly approve sync for specific form fields.

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 allow syncing. This approach eliminates data syncing issues across forms. 

To specify the fields that will be synchronized:

  • No labels