Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Rw ui steps macro
Rw step

In the Application Preferences (242) domain search for “enable prompting inside html5“ in the description field or for pdf.edit.html5.prompting.enabled in the external ID field. 

BlueArrows_pref_prompt.png
Rw step

Check that the preference is enabled. If not, click on the preference to open it. 

Rw step

Select Yes in the Boolean Value dropdown list to turn on the Blue Arrow feature inside the PDF viewer. 

BlueArrows_pref_prompt_on.png
Rw step

Click Save and Close.

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.

Rw ui steps macro
Rw step

In the Application Preferences (242) domain search for “Dropdown. Show data from the forms“ in the description field or for pdf.view.dropdown.include.forms in the external ID field.

BlueArrows_pref_drpdwn.png
Rw step

Check that the preference is enabled. If not, click on the preference to open it. 

Rw step

Select Yes in the Boolean Value dropdown list to allow the Blue Arrows to show data from other forms in the work item. 

BlueArrows_pref_drpdwn_on.png
Rw step

Click Save and Close. 

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.  

Tip

To disable synchronization for specific forms, go to the Forms Library (222) domainand edit each Form as described here:  

Configuring Forms Details 

Info

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:

Rw ui steps macro
Rw step

In the Application Preferences (242) domain search for “Form Fields Sync: List of fields that will be synced for excluded forms“ in the description field or for pdf.edit.alwaysSync.fieldNames in the external ID field. 

BlueArrows_pref_list.png

Rw step

Click on the preference to open it.

Rw step

Enter into the Memo Value field the masks for Met Field Names that should always be synced.

Info

Example: Use this Memo Value “AccountInformation1.*, PARAM.*” to trigger the Blue Arrows to sync all fields that have Meta Field Names starting with “AccountInformation1." and all internal fields starting with "PARAM.".

BlueArrows_pref_list_edit.png
Rw step

Click Save and Close.