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 »

Overview: Starting Point is a wizards within Docupace that walks a user through creation of work items for new accounts or for account maintenance. It is the engine that bundles forms for each work item.

 Version History

Date

Change

May 2023

Updated for current functionality.

October 2020

Initial Version

When an advisor launches the Docupace Starting Point either from the Docupace system or from a 3rd party CRM integration, a wizard opens and guides them through a step-by-step process to help determine the required form set.

Based on the advisor’s answers, the system assembles appropriate forms into a packet (Work Item) for the advisor to process. The advisor can either print the forms for a client's wet signature (and subsequent imaging into Docupace), or process the work completely electronically (eSign).

Forms Matrix

You can configure the Starting Point logic in the Forms Matrix (338) domain.

To set up a new set of questions and the corresponding bundle of forms:

Audience: BAs, CAs, Administrators, Developers.

Functionality: The Docupace Client Activity workflow is a highly configurable framework.

 Fields and Sections for a Forms Matrix

Field or Section Name

Description

Request Group

This is more of a general grouping, such as New Account, Maintenance, etc., that is used to classify the general request (Wizard Question #1).

Derived Request Type

This determines the correct request type for routing the work through the workflow. This is the request type that will be automatically assigned to the created work item.

Derived Client Subfolder Type

When a new account is requested, a Docupace Client Subfolder is created and the Subfolder Type is assigned (usually Brokerage or Advisory, but it may be different depending on the broker-dealer (BD) configuration).

Required

A Yes/No field. If you select Yes, then all forms listed in the record reside in the Work Item and must be used. If No, then there is a separate process (explained in more detail in the Forms page of this guide).

Description

An optional description of the forms bundle.

Reason for Adding/Changing

A reason, such as internal issue tracking number.

Vendor/Custodian

This is used to select the vendor.

Example: The Clearing Firm, BD, or Direct (Wizard Question #2).

Product Type

This is used to select what product type may drive specific forms (Wizard Question #3).

Product Name

This is used to select what product name may drive specific forms.

Registration Type

(Wizard Question #4).

Forms

Search for and add the forms that will be associated to the various linkages/combinations.

Account Options

Not required. This is a free list to give user more flexibility. (Wizard Questions #6).

Account Service

Not required. This is a free list to give user more flexibility. (Wizard Question #5).

Entity

This provides the ability to filter the request by entity (if it is set up in your site).

Example: After defining a matrix, a completed record may look like this:

Tip: In this example, the following will occur:

  1. A client subfolder will be created with the associated subfolder information of Subfolder Type Brokerage, Registration Type of Individual, and Product Type of Brokerage.

  2. A subfolder linked to a newly created work instruction with a Request Type of New Account – Brokerage and a single form will be assigned to this work item: Pershing New Account Instructions (based on the fact that only one form was selected in the matrix).

Completed Record Example

Example of a completed record

  • Request Group: New Accounts

  • Vendor/Custodian: Pershing

  • Product Type: Brokerage

  • Registration Type: Individual (not visible)

  • No labels