Salesforce Certified Financial Services Cloud Practice Test - Questions Answers, Page 12

The following considerations should be included when configuring the report with branch management reportable objects:

Bankers with Branches with Opportunities, Accounts, Leads, and Contacts report types are available for creating reports with Branch Unit Related Records. These are standard report types that allow users to create reports that show data from Banker, Branch Unit, Opportunity, Account, Lead, Contact, and Branch Unit Related Record objects.

The reportable objects include Banker, Branch Unit, Branch Unit Related Records, and Branch Unit Customer. These are custom objects that are part of the branch management feature in Financial Services Cloud. Banker is an object that represents a banker or an employee who works at a branch unit. Branch Unit is an object that represents a physical location where bankers provide services to customers. Branch Unit Related Record is an object that represents a record that is related to a branch unit, such as an opportunity, an account, a lead, or a contact. Branch Unit Customer is an object that represents a customer who has a relationship with a branch unit.

When Branch Unit is the primary object, the administrator can select Branch Unit Customers or Branch Unit Related Records as related objects. This means that the administrator can create reports that show data from Branch Unit and its related objects by using lookup fields or junction objects

The following considerations should be included when configuring the report with branch management reportable objects:

Bankers with Branches with Opportunities, Accounts, Leads, and Contacts report types are available for creating reports with Branch Unit Related Records. These are standard report types that allow users to create reports that show data from Banker, Branch Unit, Opportunity, Account, Lead, Contact, and Branch Unit Related Record objects.

The reportable objects include Banker, Branch Unit, Branch Unit Related Records, and Branch Unit Customer. These are custom objects that are part of the branch management feature in Financial Services Cloud. Banker is an object that represents a banker or an employee who works at a branch unit. Branch Unit is an object that represents a physical location where bankers provide services to customers. Branch Unit Related Record is an object that represents a record that is related to a branch unit, such as an opportunity, an account, a lead, or a contact. Branch Unit Customer is an object that represents a customer who has a relationship with a branch unit.

When Branch Unit is the primary object, the administrator can select Branch Unit Customers or Branch Unit Related Records as related objects. This means that the administrator can create reports that show data from Branch Unit and its related objects by using lookup fields or junction objects.

To add new values for how a customer can be related to a financial account, the administrator should add new values on the Role field of the Financial Account Role object. The Financial Account Role object is a junction object that links a contact or an individual to a financial account and defines their role or relationship with that account. The Role field is a picklist field that specifies the role of the contact or individual for the financial account, such as owner, beneficiary, trustee, or custodian. By adding new values on the Role field of the Financial Account Role object, the administrator can create new categories of financial account relationships for customers.

To ensure the data is loading into the correct fields in Financial Services Cloud, the consultant should utilize a field mapping file with the external system allocation and the corresponding field in Salesforce. A field mapping file is a file that specifies how fields from an external system map to fields in Salesforce. By using a field mapping file, the consultant can ensure that the data from the new custom object is imported into the correct fields in Financial Services Cloud and avoid any data loss or inconsistency.

The following steps should be taken by the consultant to offer a high level of customization to boost user productivity for the wealth management division:

Create a Custom Field Set solely for the Wealth Managers without affecting the Investment Bankers. A Custom Field Set is a construct in Financial Services Cloud that allows you to define a collection of fields that can be displayed in a Lightning component, such as the Financial Summary or the Financial Account List. You can use Custom Field Sets to customize the fields that are relevant for different user groups or business scenarios, without modifying the underlying data model or page layout. You can create a Custom Field Set by going to Setup > Object Manager > Financial Account > Field Sets and adding or removing fields according to your requirements.

Assign the Custom Field Set to the Financial Summary component. The Financial Summary component is a Lightning component that displays aggregated financial data for a selected record, such as an account, contact, or opportunity. You can use the Financial Summary component to provide a holistic view of your client's financial situation and goals. You can assign a Custom Field Set to the Financial Summary component by using the Lightning App Builder and selecting the Custom Field Set from the Component Properties panel.

Assign the Custom Field Set To a Lightning component. A Lightning component is a reusable unit of user interface that can be added to any Lightning page, such as record pages, app pages, or Home pages. You can use Lightning components to enhance the functionality and user experience of your pages. You can assign a Custom Field Set to a Lightning component by using the Lightning App Builder and selecting the Custom Field Set from the Component Properties panel. Verified

Reference: : Salesforce Help Article1: Salesforce Help Article2: Salesforce Help Article3

The consultant should consider the following from a customer onboarding perspective:

If the company struggles with the low efficiency of collecting data in questionnaires and meeting compliance with the company policies, Action Plan can be used to improve the current state. Action Plan is a feature in Financial Services Cloud that allows you to automate and standardize common business processes or service requests, such as customer onboarding, account opening, or loan application. You can use Action Plan to create templates that define the tasks, owners, and deadlines for each process or request. You can also use Action Plan to create instances of templates that apply to specific target records, such as accounts, contacts, or opportunities. Action Plan can help you collect data in questionnaires and ensure compliance with company policies by providing step-by-step guidance and validation rules for each task. Verified

Reference: : Salesforce Help Article [4] : Salesforce Help Article [5]

The consultant should design the FlexCards as follows to meet the requirements:

Parent FlexCard with multiple Child Flex Cards and Card Actions. A Parent FlexCard is a construct in Financial Services Cloud that allows you to display information from one record in a card-like format on a Lightning page. A Child FlexCard is a construct in Financial Services Cloud that allows you to display information from related records in a card-like format within a Parent FlexCard. A Card Action is a construct in Financial Services Cloud that allows you to perform actions on a record from within a FlexCard, such as edit, delete, renew, or view details. You can use Parent FlexCards, Child FlexCards, and Card Actions to create an agent console that provides a 360-degree view of your customers and enables quick actions on their records. Verified

Reference: : Salesforce Help Article [6] : Salesforce Help Article [7] : Salesforce Help Article [8]

To design the future state business process using FSC features, the administrator should create an action plan with tasks to follow up in 2 days, 2 weeks, and 2 months when an account status is changed to ''Customer''. An action plan is a feature that allows users to create templates for common client processes, such as account opening, loan application, or financial review. An action plan template consists of action plan items that define the tasks, subtasks, and deadlines for each step of the process. By creating an action plan with tasks to follow up in 2 days, 2 weeks, and 2 months when an account status is changed to ''Customer'', the administrator can automate the email reminder process and track and report on the progress in FSC

The solution that the consultant should suggest the client explore to improve its clients' documentation submission and tracking is the Send Documents flow for Retail Banking. The Send Documents flow for Retail Banking is a prebuilt flow that allows users to send documents requests to clients via email and track the status of the requests in FSC. The flow uses DocuSign eSignature integration to enable clients to sign and return documents electronically. By using the Send Documents flow for Retail Banking, the consultant can help the client streamline and simplify its document management process and improve its customer service agents' efficiency