Salesforce Financial-Services-Cloud Dumps

The following functions should be added to the Delegated Administrator group for its franchise users:

• Unlock users, which is a function that allows delegated administrators to unlock users who have been locked out due to incorrect login attempts or password expiration.
• Assign or remove permission sets for users in their delegated groups, which is a function that allows delegated administrators to grant or revoke additional permissions for users in their delegated groups by using permission sets.
• Create and manage membership of specified public groups, which is a function that allows delegated administrators to create public groups for sharing purposes and add or remove users from those groups. 

The following statements are true for the Financial Services Cloud Person Account Data Model:

• The Person Account is a virtual object displaying data from Accounts and Contacts objects. It represents all aspects of the person and includes data such as date of birth or tax ID number. You can use Person Accounts to store information about individual people by combining certain Account and Contact fields into a single record.
• The Person Account model uses the standard Account object to hold all of the details about a person. The Account object has been extended with custom fields and a Person Account Record Type. You can use Person Accounts to simplify your data model and reduce the number of records you need to manage.

The following objects do support Group-Level Rollups:

• Financial Accounts: You can use Group-Level Rollups to display the total balance, total market value, and total cost basis of all the financial accounts that belong to a group.
• Action Plans: You can use Group-Level Rollups to display the number of action plans, the number of completed action plans, and the completion percentage of all the action plans that are associated with a group.
• Opportunities: You can use Group-Level Rollups to display the total amount, expected revenue, and weighted amount of all the opportunities that are related to a group. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 80. : Salesforce Financial Services Cloud Implementation Guide, page 81. : Salesforce Financial Services Cloud Implementation Guide, page 82.

The Admin can change the color of important life events to red by using custom CSS in a Lightning App Builder theme layout component. This way, the agents can quickly scan the Life Events component and find the information they need without much effort. The color red can draw attention and indicate urgency or importance for certain life events.

To integrate with an external system, Salesforce needs to have objects and fields that can store the data that will be sent from the external system via an API. These objects and fields should match the data structure and format of the external system as much as possible. Additionally, Salesforce needs to have an integration user and an integration profile that can enable the connection between Salesforce and the external system. The integration user is a dedicated user account that has access to the API and can perform data operations on behalf of other users. The integration profile is a custom profile that defines the permissions and settings for the integration user.

The best way for the Admin to access a Financial Services Cloud pre-configured org, including data and the right licenses, to learn about the product is to request a 30-day Financial Services Cloud trial org. You can sign up for the 30-day trial using this form 4. You get preconfigured and preloaded sample data so you can start playing around in your new org right away. Once you’re done testing it out, you can transition your trial org to a production org with the help of your account executive or solution engineer. Verified References: : Trailhead Module 5

A Relationship Group is a construct in Financial Services Cloud that allows you to model complex and dynamic relationships between clients and accounts. You can use Relationship Groups to link duplicate client records and create a consolidated view of their financial data, activities, and interactions. You can also use Relationship Groups to sync data between Salesforce and the source system using external IDs and integration tools. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 67.

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 References: : Salesforce Help Article 1 : Salesforce Help Article 2 : Salesforce Help Article 3

The following objects should be used when planning to use the Mortgage Data Model to integrate with external Loan Origination and Customer Onboarding applications to accurately track the pipeline:

• Opportunity: An Opportunity is a standard object that represents a potential sale or deal for your products or services. You can use the Opportunity object to track and manage the stages, amounts, probabilities, and expected revenue of your deals. You can also use the Opportunity object to associate products, price books, quotes, contracts, orders, or assets with your deals.
• Account: An Account is a standard object that represents a person or an organization that has a business relationship with your company. You can use the Account object to store information about your customers, such as name, address, phone number, website, industry, or rating. You can also use the Account object to associate contacts, opportunities, activities, cases, or notes with your customers.
• Financial Account: A Financial Account is a custom object in Financial Services Cloud that represents a financial product or service that is owned by an account holder or related to an account holder’s financial goal. You can use the Financial Account object to store information about your customers’ financial accounts, such as type, balance, status, or interest rate. You can also use the Financial Account object to associate financial transactions, financial account roles, or financial goals with your customers’ financial accounts. Verified References: : Salesforce Help Article [6] : Salesforce Help Article [7] : Salesforce Help Article [8]

Salesforce offers various tools and capabilities to integrate Financial Services Cloud with external systems, such as core banking, insurance, or mortgage platforms. Some of the tools and capabilities that a consultant can recommend are:

• Industry Integration Solutions with the MuleSoft Anypoint Platform: These are prebuilt integration solutions that leverage the MuleSoft Anypoint Platform to connect Financial Services Cloud with common industry systems, such as Fiserv, FIS, Jack Henry, and Guidewire1. These solutions enable bi-directional data synchronization, orchestration, and transformation between Salesforce and the external systems2.
• OmniStudio Integration Procedures: These are reusable components that define the logic and sequence of steps for integrating data from external sources into Financial Services Cloud3. Integration procedures can be triggered by events, such as a button click or a record update, and can invoke other components, such as DataRaptors or OmniScripts4.
• OmniStudio DataRaptors: These are data transformation components that can extract, load, and manipulate data from various sources, such as Salesforce objects, REST or SOAP web services, or CSV files5. DataRaptors can be used to map data between different formats, perform calculations or validations, or create or update records in Financial Services Cloud6.

References:

• Industry Integration Solutions
• MuleSoft Anypoint Platform
• OmniStudio Integration Procedures
• Create an Integration Procedure
• OmniStudio DataRaptors
• Create a DataRaptor

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

The following things must be kept in mind when creating Action Plan Templates:

• When creating Action Plan Templates with the UI, you can designate a plan owner different from the plan creator. The plan owner is the user who is responsible for executing the tasks in the Action Plan. The plan creator is the user who creates the Action Plan Template or the Action Plan from the template. You can assign a different plan owner for each Action Plan Template or Action Plan.
• An Action Plan is a run-time instance of the template that allows you to automate the sequence of the tasks you defined in the template. An Action Plan Template is a reusable blueprint that defines the tasks, owners, and deadlines for a common business process or service request. An Action Plan is a specific implementation of the template that applies to a particular target record, such as an account, contact, or opportunity.
• When you create an Action Plan from a template for a specific target record, item deadlines are calculated using the start date and date offset defined in the Action Plan Template. The start date is the date when you create the Action Plan from the template. The date offset is the number of days before or after the start date when each task is due. You can specify different date offsets for each task in the template. Verified References: : Salesforce Help Article 2 : Salesforce Help Article 3 : Salesforce Help Article 4

To skip non-work days in Action Plan when setting task completion dates, the administrator should configure the day without business hours, as it is considered a non-work day, even if the day is a recurring holiday. This means that the administrator should leave the start and end time fields blank for any day that is not a working day, such as Saturday or Sunday. Action Plans will then automatically omit those days when calculating the task completion dates based on the business hours1. Recurring holidays are not considered by Action Plans when determining the non-work days to skip2.

References:

• Set Business Hours
• Set Up Company-wide Holidays

 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 related lists are visible within Actionable Relationship Center (ARC) associated with the Account object:

• Client Financial Goals, which is a related list that displays the financial goals of the account, such as retirement, education, or debt payoff.
• Financial Holdings, which is a related list that displays the financial accounts of the account, such as bank accounts, investment accounts, or insurance policies.
• Household Financial Accounts, which is a related list that displays the financial accounts of the account’s primary group, such as household or business group.

To prevent the data import from creating duplicates when importing records from a system outside of Salesforce, you should use External ID. External ID is a custom field type that can be used to store unique identifiers from other systems. You can use External ID to match records during data import and avoid creating duplicate records in Salesforce. You can also use External ID to enable upsert operations, which can insert new records or update existing records based on the External ID value. Verified References: : Salesforce Help Article [5] : Salesforce Help Article [6]

The following value outcomes should the company’s stakeholders expect from implementing Salesforce Financial Services Cloud (FSC):

• Achieved higher CSAT & NPS scores attributed to personalized customer experiences driven by shorter waits due to decreased average case handle times and improved self-service solutions via Einstein Bots for FSC. This outcome means that the company improved its customer satisfaction (CSAT) and net promoter score (NPS) metrics by providing customized and relevant interactions with customers, reducing their waiting time by handling cases more efficiently, and offering self-service options through chatbots powered by artificial intelligence.
• Improved customer onboarding experiences by fast-tracking and simplifying document tracking and approvals via FSC Action Plans. This outcome means that the company enhanced its customer onboarding process by speeding up and streamlining the document management and approval workflow using Action Plans, which are features that allow users to create templates for common client processes, such as account opening, loan application, or financial review.
• Drove Advisor productivity with a daily task list, client life events, opportunities, and aggregated household information directly from the FSC Home Page. This outcome means that the company increased its advisor productivity by providing them with a daily task list that shows their priorities and action items, a client life events component that shows important events in their clients’ lives, an opportunities component that shows potential sales deals, and an aggregated household information component that shows a holistic view of their clients’ financial situation, all on the FSC Home Page

To modify a published Action Plan to support an additional task, Jen should use the Action Plan item feature to add an additional task to the published Action Plan. An Action Plan item is a construct in Financial Services Cloud that allows you to add, edit, or delete tasks in an existing Action Plan. You can use Action Plan items to customize your Action Plans according to your specific needs and preferences. Verified References: : Salesforce Help Article 1

Record alerts are a feature of Financial Services Cloud that let users create and display alerts on record pages to highlight important information or actions. Record alerts are based on OmniStudio, a low-code platform for building digital experiences in Salesforce. To access or extend permissions for record alerts in Financial Services Cloud, users need to have one of the following permission sets:

• FSC Standard permission set: This permission set grants access to the core features of Financial Services Cloud, including record alerts. Users with this permission set can view and create record alerts on supported objects, such as accounts, contacts, financial accounts, and opportunities1.
• FSC Foundations permission set: This permission set grants access to the common features of Financial Services Cloud that are shared across subverticals, such as retail banking, wealth management, and insurance. Users with this permission set can view and create record alerts on supported objects2.
• OmniStudio User permission set: This permission set grants access to the OmniStudio features, such as OmniScripts, DataRaptors, Integration Procedures, and Record Alerts. Users with this permission set can view and create record alerts on any object that has the Record Alert component enabled3.

References:

• FSC Standard Permission Set
• FSC Foundations Permission Set
• OmniStudio User Permission Set

The administrator did not assign the Mortgage permission set to the user. The Mortgage permission set is required to access the Residential Loan Application object and its related objects, such as Loan Application Form, Loan Assessment, and Loan Product. Without this permission set, the user cannot create, edit, or view residential loan application records. The administrator can assign the Mortgage permission set to the user from the user detail page in Setup. References: [Mortgage Permission Set], [Residential Loan Application Object]

The order of uploading Salesforce objects during an FSC data migration is important to ensure data integrity and avoid errors. The recommended order is:

• Accounts and contacts: These are the core objects that store the basic information about the customers and their relationships. They should be uploaded first to establish the foundation for the FSC data model4.
• Financial accounts: These are the custom objects that store the financial information about the customers, such as balances, interest rates, fees, and transactions. They should be uploaded after the accounts and contacts, and linked to them using lookup fields5.
• Account groups and households: These are the custom objects that group the accounts and contacts based on common attributes or relationships, such as family members or business partners. They should be uploaded after the financial accounts, and linked to them using junction objects6.

References:

• Financial Services Cloud Data Model
• Data Migration Best Practices
• Accounts and Contacts
• Financial Accounts
• Account Groups and Households

To hide highly sensitive Life Events or Business Milestones until they happen, the Admin can hide them on the Events & Business Milestones Lightning Component page properties. The Events & Business Milestones Lightning Component is a component that displays a timeline of life events and business milestones for a client or a group. The Admin can use the page properties to customize the component and select which event types or milestone types to show or hide on the timeline2. Verified References: 2

The order that the consultant should follow when performing the data migrations is Individuals, then Financial Accounts, then Financial Account Roles, then Financial Account Transactions. This order ensures that the data dependencies and relationships are maintained and that the data integrity and quality are preserved. By migrating Individuals first, the consultant can create the records that represent the customers of the bank. By migrating Financial Accounts next, the consultant can create the records that represent the financial products or services that the customers own or use. By migrating Financial Account Roles next, the consultant can create the records that link the individuals to the financial accounts and define their roles or relationships with those accounts. By migrating Financial Account Transactions last, the consultant can create the records that represent the transactions or activities that occur on the financial accounts. 

Feed tracking has to be enabled for the Action Plan object in order to add a Chatter component to the Action Plan Lightning record page. Feed tracking allows you to see updates on records in Chatter feeds. You can enable feed tracking for custom objects, such as Action Plan, from the setup menu. Once feed tracking is enabled, you can add Chatter components, such as Feed or Publisher, to the record page using the Lightning App Builder. References: [Feed Tracking], [Chatter Components]

To ensure the correct profiles and permissions for an API integration between Salesforce and a risk control system, the consultant should do the following steps:

• Create a dedicated Integration User that will be used to authenticate and authorize the API calls between Salesforce and the risk control system. The Integration User should have a unique username, password, and security token that are not shared with other users or systems. The Integration User should also have the minimum permissions and access settings required to perform the integration tasks.
• Create a new custom profile and ensure API Only is selected. The API Only option restricts the user from logging in to the Salesforce user interface, but allows the user to access the Salesforce API. The custom profile should also have the appropriate object permissions, field-level security, record types, page layouts, and other settings that are relevant for the integration. The custom profile should be assigned to the Integration User.

To enable Multiple Relationship Groups, which is a feature that allows users to add individuals to more than one group or household, the Admin needs to use Custom Settings. Custom Settings are similar to custom objects and enable application developers to create custom sets of data, as well as create and associate custom data for an organization, profile, or specific user. The Admin can use Custom Settings to enable Multiple Relationship Groups by following these steps:

• From Setup, enter Custom Settings in the Quick Find box, then select Custom Settings.
• Click Manage next to Group Member Record Type Mapper.
• Click Edit next to Default Organization Level Value.
• In Multiple Relationship Groups Enabled, select True.
• Click Save.

To make sure that Scott’s data is rolling up to the Adams Household, the Banker should make the Adams Household Scott’s primary Group and edit the Activities & Objects to Roll Up. A primary Group is a construct in Financial Services Cloud that allows you to define the main group for a client. You can use primary Group to roll up financial data from all the financial accounts that are related to the client or the group. By making the Adams Household Scott’s primary Group, the Banker can ensure that Scott’s financial data is included in the household summary. The Banker can also edit the Activities & Objects to Roll Up to specify which items, such as financial accounts, goals, or referrals, should be rolled up for Scott. Verified References: : Salesforce Help Article 4

The following steps are needed to document the requirement for digitizing and automating the customer onboarding process following the discovery session:

• Document the business process flows. You need to document the current and future state of the business process flows for customer onboarding, such as the steps, inputs, outputs, decisions, and dependencies involved in each flow. You can use tools such as diagrams, charts, or tables to illustrate the process flows and identify the pain points, gaps, or opportunities for improvement.
• Understand the journey for the multiple personas involved in the process. You need to understand the journey for each persona that participates in or interacts with the customer onboarding process, such as the customer, the client specialist, or the manager. You can use tools such as personas, journey maps, or user stories to capture the needs, goals, pain points, and expectations of each persona and how they experience the process from their perspective.
• Determine the best e-signature solution to use. You need to determine the best e-signature solution to use for collecting and processing digital signatures from customers during the onboarding process. You can use tools such as research, analysis, or comparison to evaluate different e-signature solutions based on criteria such as functionality, compatibility, security, cost, or user feedback. Verified References: : Salesforce Help Article [11] : Salesforce Help Article [12] : Salesforce Help Article [13]

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

To enable advisors to capture Once-in-a-Lifetime events and prevent users from accidentally creating more than one event of such an event type, the consultant should configure Unique event types. Unique event types are event types that can only be created once for each contact or individual, such as birth, death, or marriage. By using Unique event types, the consultant can ensure that advisors can capture important life events for their customers and avoid duplication or inconsistency. 

Enable Compliant Data Sharing for Interaction Summaries, Use Interaction Summary Participants to provide the right access to individuals or groups, and Disable Role-Hierarchy-Based Sharing for Interaction Summaries.

Consent Management for Financial Services Cloud is a feature that helps financial institutions honor and respect their customers’ wishes when they request only specific forms of contact from their company or opt-out of certain types of data-sharing. This feature helps institutions comply with the data protection and privacy regulations that apply to their company11. A consultant can suggest the following actions to implement Consent Management for Financial Services Cloud:

• Set up tracking and storage of certain data privacy preferences: This involves creating data privacy records for customers who have opted out of certain types of communication or data-sharing, and selecting the appropriate options in the record to indicate their preferences12.
• Use the Consent API: This is an API that lets users query, create, update, or delete consent records for customers who have given or withdrawn their consent for certain types of communication or data-sharing.
• Protect your Salesforce organization: This involves setting up organization-wide sharing settings, encryption, field-level security, and other measures to ensure that only authorized users can access or modify customer data according to their consent preferences.

References:

• Consent Management for Financial Services Cloud
• Set Up Tracking and Storage of Certain Data Privacy Preferences
• [Use the Consent API]
• [Protect Your Salesforce Organization]

The following Permission Set Licenses give users access to Financial Services Cloud features:

• Financial Services Cloud Standard: This license enables user access to a license with contractual restrictions for Financial Services Cloud and provides access to core objects such as accounts, contacts, leads, opportunities, cases, activities, reports, dashboards, and custom objects. This license also provides access to some Financial Services Cloud features such as Action Plans, Actionable Relationship Center (ARC), Branch Management, Complaint Management, Data Consumption Framework (DCF), Discovery Framework (DF), Document Generation (DG), Groups (Householding), Intelligent Document Automation (IDA), Intelligent Need-Based Referrals and Scoring (INRS), Referral Management (RM), Relationship Builder (RB), Relationship Groups (RG), Relationship Map (RM), Timeline (TL)1.
• Action Plans: This license enables user access to the Action Plans feature, which allows users to create templates for common client processes, such as loan approval, account opening, or financial review. Action Plans can create repeatable tasks and automate the task sequences when executed2.
• FSC Insurance: This license enables user access to the Insurance feature, which allows users to manage insurance policies and claims for clients. This license also provides access to some Insurance objects such as Policy, Claim, Coverage Type, Policy Product, Policy Product Offering. Verified References: 12

The following are the building blocks of Flow Orchestration:

• Steps: Steps are discrete units of work that can be performed by a user or a system within a flow orchestration. Steps can have different types, such as user input steps, system action steps, decision steps, or subflow steps. Steps can also have different attributes, such as name, description, icon, input variables, output variables, or preconditions.
• Stages: Stages are logical groupings of steps that represent phases or milestones within a flow orchestration. Stages can have different attributes, such as name, description, icon, entry criteria, exit criteria, or completion actions.
• Work Items: Work Items are instances of flow orchestrations that track the progress and status of each execution. Work Items can have different attributes, such as name, description, owner, assignee, due date, priority, status, stage history, or step history. Verified References: : Salesforce Help Article [7] : Salesforce Help Article [8] : Salesforce Help Article [9]

The following OmniStudio tools should be used to design a solution that meets the requirements for creating a car insurance quote process for the website:

• OmniScripts, which are tools that allow users to create guided, interactive, and intuitive scripts that capture data and execute actions. By using OmniScripts, the consultant can create a script that guides the user through the car insurance quote process and captures the contact and address information, the driver’s age, and the car model and year.
• Integration Procedures, which are tools that allow users to orchestrate data and actions across multiple systems using RESTful APIs. By using Integration Procedures, the consultant can create a procedure that calls the core system service to calculate an insurance quote based on the data provided by the user and returns the quote to the OmniScript.
• Business Rules Engine, which is a tool that allows users to define business logic and validation rules using natural language expressions. By using Business Rules Engine, the consultant can create rules that validate the data entered by the user and enforce any business policies or conditions for the car insurance quote process.

To meet the requirements of sharing special deposit products for employees, the administrator should create a Financial Account sharing rule based on criteria. A Financial Account sharing rule is a sharing rule that grants access to financial account records based on record owner or field values. A sharing rule based on criteria is a type of sharing rule that grants access to records that meet certain criteria. By creating a Financial Account sharing rule based on criteria, the administrator can share the special deposit products with the customer service employees within a specific group based on a field value that indicates the product type.

Compliant Data Sharing (CDS) is a feature of Financial Services Cloud that lets administrators and compliance managers configure advanced data-sharing rules so that they can improve compliance with regulations and company policies. Some of the things to consider when implementing CDS in Financial Services Cloud (FSC) are:

• CDS in FSC allows record owners to grant access to their records to other FSC users. Record owners can use the Manage Participants component on record pages to share their records with other users who have relevant roles or permissions6.
• CDS can only be applied to FSC objects and Account and Opportunity objects. CDS supports sharing for Account, Opportunity, Financial Account, Financial Holding, Financial Goal, Referral, Relationship Group, Action Plan Template, Action Plan, Action Item Template, Action Item, Interaction Summary, Interaction Summary Participant Role Assignment, Interaction Summary Participant Role Definition7.
• To get the benefits of CDS, administrators must set organization-wide sharing settings for supported objects to the Private access model. This ensures that only record owners and users above them in the role hierarchy have access to the records by default8.

References:

• Compliant Data Sharing
• Work with Compliant Data Sharing

Rollup By Lookup (RBL) summaries are available for the following objects:

• Financial Accounts, which are records that represent financial products or services that a client owns or uses1.
• Assets and Liabilities, which are records that represent the value of what a client owns or owes1.
• Contacts, which are records that represent individuals who are associated with an account3.

The following considerations should be considered regarding the data model for the broker web portal:

• The Broker Assistant should be modeled as a Contact. Then, leverage Contact to Multiple Account features if this assistant needs to work for multiple brokers. This is because Contacts are records that represent individuals who are associated with an account. By using Contacts, the consultant can capture the personal information of the broker assistants and relate them to their employers. By using Contact to Multiple Accounts features, the consultant can enable a contact to have relationships with multiple accounts and specify different roles and start and end dates for each relationship.
• Brokers need to be modeled as Account and Contact individually, as each broker is a legal entity in Salesforce. Then, use a Group to model their company. This is because Accounts are records that represent business entities or organizations that are involved in business transactions with your company. By using Accounts, the consultant can capture the business information of each broker and treat them as legal entities in Salesforce. By using Contacts, the consultant can capture the personal information of each broker and relate them to their accounts. By using Groups, which are records that represent collections of accounts or contacts that share financial goals or characteristics, the consultant can model the broker company and associate multiple brokers with it

The following referral metrics are tracked with custom components included in Financial Services Cloud:

• Expressed interests: This metric shows the number of referrals that have a specific expressed interest, such as a mortgage, a credit card, or a checking account. You can use this metric to understand the customer needs and interests that generate the most referrals.
• My Top Referrers: This metric shows the top referrers who have created referrals for you, ranked by the number of referrals and the conversion rate. You can use this metric to identify and appreciate your best sources of business.
• Referrals Assigned to me: This metric shows the number of referrals that are assigned to you and their status, such as New, In Progress, or Closed. You can use this metric to monitor and manage your referral pipeline and prioritize your follow-up actions. Verified References: : Salesforce Financial Services Cloud User Guide, page 40. : Salesforce Financial Services Cloud User Guide, page 41. : Salesforce Financial Services Cloud User Guide, page 42.

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.

Unify and improve team collaboration by sharing and managing customer leads and referrals across multiple lines of business at the bank to drive customers’ financial needs and deepen client relationships; Deliver connected and personalized digital experiences to the bank’s customers thanks to a 360-degree view of its customer data consolidating multiple customer databases and sources from diverse channels at the bank; Modernize client-advisor experiences from engagement to relationship management to effectively drive long-term, trusted relationships.

To configure customized nodes for display in Actionable Relationship Center (ARC), developers should reference the FlexCard in the Display properties of the custom ARC relationship graph. A FlexCard is a tool that allows users to create custom user interfaces for displaying data from Salesforce or external systems using OmniScripts and Integration Procedures. A custom ARC relationship graph is a metadata type that defines the nodes and edges of a custom relationship graph for ARC. By referencing the FlexCard in the Display properties of the custom ARC relationship graph, developers can customize the look and feel of the nodes and display data from various sources on them. 

 In an existing Financial Services Cloud org using the individual account model, custom objects are used to represent other assets, liabilities, and goals. These objects are related to the Account object via lookup relationships. For example:

• The Other Asset object is used to represent non-financial assets owned by an account holder, such as real estate properties, vehicles, or jewelry.
• The Other Liability object is used to represent non-financial liabilities owed by an account holder, such as mortgages, loans, or taxes.
• The Financial Goal object is used to represent financial objectives pursued by an account holder, such as retirement planning, education funding, or debt reduction. Verified References: : Salesforce Help Article [10] : Salesforce Help Article [11] : Salesforce Help Article [12]

Multicurrency is a feature in Salesforce that allows you to work with multiple currencies in your org. If you enable multicurrency in FSC, you need to consider the following:

• When filtering by currency values in reports or list views, users must specify a currency ISO code, such as USD or GBP, before the value. For example, USD500 or GBP300.
• When multicurrency is enabled in FSC, advanced currency management is also available. This feature allows you to track historical exchange rates and apply them to opportunities and forecasts.

To ensure that all users see Person Accounts, but only specific users can view Financial Accounts, the Admin should take the following steps:

• Grant users access to the Financial Account object with permission set, which is a collection of settings and permissions that give users access to various tools and functions. The Admin can use permission sets to grant access to the Financial Account object and its fields to specific users or groups of users1.
• Change Organization-wide Defaults (OWD) sharing on the ‘Financial Accounts’ object to Private’, which is a setting that determines the baseline level of access that users have to records they do not own or share. By setting the OWD sharing on the ‘Financial Accounts’ object to Private’, the Admin can ensure that only the record owners and users above them in the role hierarchy can view the Financial Accounts. Verified References: 1