Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Grammar updates only.
Info

Introduction: This guide provides information about the process of New Account Opening (NAO) through Docupace Start when starting the process from a CRM (Customer Relationship Management) system such as Salesforce, SmartOffice, Wealthbox, or others.

Table of Contents:

Table of Contents

Change Log:

Date

Changes

February 2021

Comprehensive documentation about the process of New Account Opening (NAO).

Audience: Financial Professionals and Account Managers.

Functionality: This feature allows users to open a new account directly from Docupace Start.

Prerequisites for New Account Opening

  • Core 23.4 and Connect 4.59.

  • Completed Mappings/Validations setup.

Search for an

existing

Existing Client

based on ID's sent from

Based on IDs Sent from a 3rd Party

's

Search for a client based on CRM external ID:

  1. Search for a client based on CRM external ID, if provided in Owner1.ClientID.

a) If the exact match is found, the system displays the Account Setup screen (see Figure 1).

On the Account Setup screen, an app skips client search and navigates directly to Main Info with all app fields populated based on data from CRM (linked client is for indexing purposes only).

b) If no client match is found by CRM external ID and Owner1.Ari.Id is populated, search by Owner1.Ari.Id.

If the exact match is found, the system/app displays the Account Setup screen.

On the Account Setup screen, the app skips client search and goes directly to Main Info with all app fields populated based on data received from CRM (linked client is for indexing purposes only).

Figure 1: Searching Client based on CRM external ID

2. If no client record match is found by CRM external ID or Owner1.Ari.Id, the Autofill link is enabled (next to the Last Name / Entity Name) on the Client Search that will be populated with names/data sent from 3rd party (see Figure 2).

If prefill is used, and the existing client is found/selected in Client Search, data from 3rd party will be used to prefill app and will not overlay by the selected client (Owner1.Ari.Id).

Essentially, the selection of the client folder is for indexing of client to Work Item purposes only and not data population (Standard Blue Arrow logic).

Figure 2: Searching Client with Autofill option

CRM Client

search and data mapping functionality

Search and Data Mapping Functionality

Functionality allows to initiate and perform a search for existing clients by CRM External ID or Client ID (app setup) and pre-fill Docupace Start app with data from 3rd party CRM XML payload (Form Field Groups, Form Fields Meta and FM M-to-M mapping configuration).

  1. If there is a client match by either of the IDIDs, a Client Search page is skipped and Account Holder data is prefilled with incoming data from CRM. Like with Blue Arrows functionality, Client Folder is used only to index client information and not to fill Work Item data.

  2. If no client record match is found by CRM External ID or Client ID, Client Search fields are populated with data from incoming CRM XML, and additional search can be performed based on these values. In case after Client Search the existing client is selected, related data received from CRM XML will be prefilled to the app as well (likewise, Client Folder will be used only for indexing purposes).

  3. For Registration types with multiple account holders (Joint accounts), on subsequent Client Searches, the auto-fill link will be enabled next to the Client Name / Entity Name fields and will contain a selection of first name/last name options from 3rd party CRM XML payload. If an existing client is found/selected in Client Search, related data from 3rd party CRM will be used to prefill app BASE fields. Selection of Client Folder is for indexing of client to work item purposes only, not data population (Blue Arrow functionality).

For all this to work, the data mapping must be configured correctly.

Rw ui steps macro
Rw step

Set Application Preference Starting Point: enable prompting inside html5 viewer to Yes (see Figure 3).

Figure 3: Setting the Application Preference

Rw step

Add or modify Form Field Group entries Prompt Field Name and Fields Group Prefix for All Owners (see Figures 4 and 5).

Figure 4: Modifying Form Field Group settings

Figure 5: Modifying Form Field Group settings

Rw step

Add Form Fields Meta records for each of the field types you want to have prompting(see Figure 6).

Figure 6: Modifying Form Fields Meta settings

Rw step

Configure FM M-to-M Converters.

Type:

#{isAllEmpty('*[].Role') ? value() : value('*[].Role') + ': ' + value()}

in the Value Mapping field(see Figure 7).

Figure 7: Modifying FM M-to-M Converters settings