Salesforce Financial-Services-Cloud Dumps

The following FSC features should be part of the solution design for managing confidential deal information and notes sharing among deal teammembers:

Financial Deal Management: Financial Deal Management is a feature in Financial Services Cloud that allows you to track and manage complex deals that involve multiple parties, products, and stages. You can use Financial Deal Management to store confidential deal information such as deal name, amount, status, or participants. You can also use Financial Deal Management to associate opportunities, products, or tasks with a deal.

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 trackingand storage of certain dataprivacy 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.

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 out of the box capabilities come with Financial Services Cloud Lead & Referral Management:

Referral Conversion: This capability allows you toconvert a referral to an opportunity, a contact, or an account. You can use this capability to track the progress and outcome of a referral and measure its impact on your business.

Assigning a Referral: This capability allows you to assign a referral to another user, queue, or line of business. You can use this capability to route a referral to the appropriate person or team who can best meet the customer’s need or interest.

Accepting a Referral: This capability allows you to accept a referral that is assigned to you or your queue. You can use this capability to acknowledge that you have received a referral and are ready to work on it. Verified References: : Salesforce Help Article 1 : Salesforce Help Article 3 : Salesforce Help Article 5

Rollup By Lookup (RBL) is a feature in Financial Services Cloud that allows you to display summary calculations of financial account information, such as balances, market values, and cost bases. You can use RBL to roll up financial data to all joint owners’ primary households by doing the following:

Create custom RBL rules to rollup the joint owner balances using the Joint Owner field on the Financial Account object.

Enable RBL rules that rollup balances using Financial Account Role for joint owners using the Account Role field on the Account Contact Relationship object. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 75.

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

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 withthis 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.

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. AFlexCard 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 edgesof 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. 

Thefollowing names are Association Type picklist field values:

Trust, which is a value that indicates that the accounts are related through a trust relationship.

Family, which is a value that indicates that the accounts are related through a family relationship.

Peer, which is a value that indicates that the accounts are related through a peer relationship.

The best way for the Admin to access a Financial Services Cloud pre-configured org, including data and the right licenses, to learn about theproduct 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 getpreconfigured 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 youraccount executive or solution engineer. Verified References: : Trailhead Module 5

 To model a requirement where more than one person can be joint owners on a Financial Account, the Admin can map additional owners using the Financial Account Role. The Financial Account Role is a junction object that links a contact or an individual to a financial account and defines their role or relationship with that account. By using Financial Account Role, the Admin can addmultiple owners to a Financial Account and specify their ownership percentage, primary status, and other details.

 The following actions regarding functionality and features should be suggested to help guide Cumulus Insurance users through their complex business processes:

Configure Dynamic Actions for Lightning pages. Dynamic Actions are a feature that allows you to customize the actions that appear on a Lightning page based on criteria such as record type, field value,device type, or user profile. You can use Dynamic Actions to show or hide actions that are relevant or irrelevant for each stage of the business process, such as creating a case, sending an email, or generating a quote.

Enable In-App Guidance to providewalk-throughs. In-App Guidance is a feature that allows you to create prompts and guided tours that appear within the Salesforce app to help users learn new features, complete tasks, or adopt best practices. You can use In-App Guidance to provide step-by-step guidance for complex business processes, such as onboarding a customer, submitting a claim, or renewing a policy.

Use flows to remove the need for complex Lightning pages. Flows are a tool that allows you to automate business processes and guide usersor customers through screens that collect and display information. Flows can have multiple steps and branching logic that ask for different information depending on the responses. You can use flows to simplify and streamline complex business processes, such as applying for a loan, enrolling in a plan, or changing a beneficiary. Verified References: : Salesforce Help Article [12] : Salesforce Help Article [13] : Salesforce Help Article [14]

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 Individualsfirst, 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. 

To give a group of users access to a Financial Deal, you need to share a financial deal record with a group by adding them as participants to the record from the Financial Deal Participants related list. The Financial Deal Participants related list is a custom related list on the Financial Deal object that allows you to add users, groups, or queues as participants of a financial deal.Participants can have different roles and access levels for a financial deal, such as Owner, Collaborator, Viewer, or Approver. By adding a group as a participant, you can grant access to all the members of that group for a specific financial deal. Verified References: : Salesforce Help Article [6] : Salesforce Help Article [7]

The following standard fields are available to track a customer’s retirement goal progress:

Actual value, which is a currency field that represents the current value of the goal.

Target value, which is a currency field that represents the desired value of the goal.

Target Date, which is a date field that represents the expected date of achieving the goal.

A suitable use case for Flow Builder is to collect input from internal users with a form placed on a Lightning page or launched by a button. Flow Builder is a tool that allows users to automate business processes by building flows that guide users through screens, executelogic, manipulate data, and interact with Salesforce and external systems. By using Flow Builder, the system administrator can create a flow that collects input from internal users with a form and performs actions based on the input.

The following records support Document Checklist Items out of the box in Financial Services Cloud:

Account: An Account is a record that represents a person or anorganization that has a business relationship with your company. You can use Document Checklist Items to request and track documents from your account holders, such as identity proofs, tax forms, or contracts.

Residential Loan Application: A Residential Loan Application is a record that represents a request for a loan to purchase or refinance a residential property. You can use Document Checklist Items to request and track documents from your loan applicants, such as income statements, credit reports, or property appraisals.

Opportunity: An Opportunity is a record that represents a potential sale or deal for your products or services. You can use Document Checklist Items to request and track documents from your opportunity owners, such as proposals, quotes,or agreements. Verified References: : Salesforce Help Article 2 : Salesforce Help Article 3 : Salesforce Help Article 4

The following processes are part of Claims Management:

Auto Adjudication, which is a process that allows claims to be processed automatically without humanintervention, based on predefined rules and criteria. Auto adjudication can improve the efficiency and accuracy of claims processing and reduce operational costs.

Reserve Management, which is a process that involves estimating and setting aside funds for future claims payments. Reserve management can help insurers manage their cash flow and solvency and comply with regulatory requirements.

Payment, which is a process that involves disbursing funds to claimants or providers after a claim has been approved. Payment can involve different methods, such as check, electronic funds transfer, or debit card. Payment can affect the customer satisfaction and retention rate of insurers.

The following types of Account-Account relationships are displayed in the Actionable Relationship Center (ARC):

Accounts & Businesses: This type of relationship shows the accounts that are related to a business account, such as owners, partners, or beneficiaries. You can use this type of relationship to understand the ownershipstructure and financial interests of a business account.

Accounts & Peers: This type of relationship shows the accounts that are related to another account by a peer-to-peer relationship, such as friends, colleagues, or associates. You can use this type ofrelationship to identify potential referrals and cross-selling opportunities from an account’s network.

Accounts & Groups: This type of relationship shows the accounts that are related to a group account, such as household members, trust members, or business group members. You can use this type of relationship to view the aggregated financial data and activities of a groupaccount. Verified References: : Salesforce Help Article 2 : Salesforce Help Article 3 : SalesforceHelp Article 4

The following considerations indicate that a new Salesforce org is the better choice for implementing Financial Services Cloud:

The bank wants to use this project as an opportunity to retire customization. A new org will allow the bank to start fresh and avoid carrying over unnecessary or outdated customization that may conflict with Financial Services Cloud features or best practices.

The current implementation is using a product-centric view and the bank wants to move to a customer-centric view. A new org will allow the bank to adopt the Financial ServicesCloud data model, which is designed to provide a holistic view of the customer and their relationships, goals, financial accounts, activities, and interactions.

Existing business capabilities and processes can be redesigned to deliver a higher business impact. A new org will allow the bank to leverage the Financial Services Cloud capabilities, such as Action Plans, Relationship Groups, Rollup By Lookup, Service Processes, etc., to optimize their business processes and enhance their customer experience. Verified References: : Salesforce Help Article 6

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 Settingsare 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 GroupsEnabled, select True.

Click Save.

The following activities should be prioritized by the implementation team during planning for designing the Financial Services Cloud implementation:

Prepare for integrations with transactional systems, external data sources, custodians, and any other platforms that the company’s business relies on. Integrations are the connections or interactions that allow data or functionality to flow between different systems or platforms. You should prepare for integrations with your existing or new systems or platforms that support your business processes, such as transactional systems, external data sources, custodians, or other platforms. You should also consider the integration methods, tools, requirements, and challenges that you will need to address during the implementation.

Beyond the preconfigured settings, evaluate whether they need advanced customizations. Customizations are the changes or modifications that you make to Salesforce to meet your specific business needs or preferences. You should evaluate whether you need advanced customizations beyond the preconfigured settings that Financial Services Cloud provides out of the box, such as custom objects, fields, formulas, validation rules, workflows, triggers, or components. You should also consider the impact, benefits, and risks of your customizations on your data model, user interface, performance, security, or maintenance.

Review the out-of-the-box capabilities and compare them to the company’s current needs. Out-of-the-box capabilities are the features or functions that Financial Services Cloud offers without any customizations or configurations. You should review the out-of-the-box capabilities and compare them to your company’s current needs and expectations. You should also identify any gaps or opportunities for improvement that you can address with configurations or customizations during the implementation. Verified References: : Salesforce Help Article [12] : Salesforce Help Article [13] : Salesforce Help Article [14]

 The relationships between the parties when the FinancialServices Cloud consultant sets up Rachel’s person account should be as follows:

Primary Group Household - Addams Household

Primary Member - Rachel Addams

Spouse - Nigel Adams

Trustee - Addams Charitable Trust

Household - Symonds Household

Primary Member -Neil Symonds

Beneficiary - Rachel Addams

Related Accounts - Addams Charitable Trust

Related Contacts - Ivan M. Kohl

Unify and improve team collaboration by sharing and managing customer leads and referrals across multiple lines of business at the bank to drive customers’ financialneeds 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.

Process Builder and Screen Flows are two features thatcan be used to design a business process for identity verification. Process Builder is a tool that allows you to automate business processes by creating workflows that trigger actions based on certain criteria. Screen Flows are a type of flow that guide users through a series of screens to collect and update data. You can use Process Builder to launch a Screen Flow when a customer contacts the bank, and use the Screen Flow to capture and verify the customer’s identity information.References: [Process Automation], [Screen Flows]

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 cancapture important life events for their customers and avoid duplication or inconsistency. 

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 toolsand capabilities that a consultant can recommend are:

Industry Integration Solutions with the MuleSoft Anypoint Platform: These are prebuilt integration solutions that leveragethe 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 theexternal systems2.

OmniStudio Integration Procedures: These are reusable components that define the logic and sequence of steps for integrating datafrom external sources into Financial Services Cloud3. Integration procedures canbe 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 orSOAP web services, or CSV files5. DataRaptors can be used to map data between different formats, perform calculations or validations, or create or updaterecords in Financial Services Cloud6.

The following objects dosupport 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 Financial Services Cloud featurethat is most suitable for tracking clients’ hobbies for marketing purposes is Interest Tags. Interest Tags are features that allow users to add tags to contacts or individuals based on their interests or preferences. Users can create custom interest tags or use predefined ones from FSC. By using Interest Tags, the wealth management firm can capture its clients’ hobbies and use them for marketing segmentation or personalization.

To document the current state business process for implementing Salesforce Financial Services Cloud, the consultant should create an end-to-end visual map of the process using personas, systems, inputs, and outcomes. A visual map is a tool that can help illustrate the flow of a business process from start to finish, showing the steps, decisions, and dependencies involved in each stage. A visual map can also include personas, systems, inputs, and outcomes to providemore context and detail for each step of the process. Personas are fictional characters that represent the different roles or users that participate in or interact with the process. Systems are the tools or applications that are used to perform or supportthe process. Inputs are the data or information that are required or provided for each step of the process. Outcomes are the results or outputs that are achieved or delivered by each step of the process. Verified References: : Salesforce Help Article 3 : Salesforce Help Article [4]

To grant restricted accessto users like Bank Tellers who need only limited access to Financial Services Cloud features, the Admin can use Financial Service Cloud Basic permission set license. This license enables user access to a license with contractual restrictions for FinancialServices 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). 

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 userwho 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 processor 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 dateis 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 taskis 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

Financial accounts management is a Salesforce Financial Services Cloud feature that enables financial advisors totrack and manage client accounts. A financial account is any account managed by a financial institution, such as a bank, an insurance company, or an investment firm. Financial Services Cloud supports many kinds of financial accounts, such as checking accounts, savings accounts, mortgages, credit cards, investment accounts, insurance policies, and more3. Financial advisors can use Financial Services Cloud to view, create, update, and delete financial accounts for their clients, as well as link them to other objects, such as households, goals, referrals, or opportunities4.

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]

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 coreobjects that store the basic information about the customers and their relationships. They should be uploaded first to establish the foundationfor 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 lookupfields5.

Account groups and households: These are the custom objects that group the accountsand 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.

To create a relationship between Rachel and her attorney before assigning the reciprocal role of “Attorney”, the Wealth Advisor should create a Contact-Contact Relationship between the primary member of the Adams Household and the attorney. A Contact-Contact Relationship is a junction object that links twocontacts or individuals and defines their relationship with each other2. By using Contact-Contact Relationship, the Wealth Advisor can capture Rachel’s extended network of relationships with people outside of her household.Verified References: 2

To configure a custom field for reporting when relating two business accounts to each other, the administrator should configure the custom field on the Account-Account Relationship object. The Account-Account Relationship object is acustom object in Financial Services Cloud that allows you to create and manage relationships between two accounts, such as Household Member, Business Owner, Trustee, or Friend. You can use the Account-Account Relationship object to store additional information about the relationship between two accounts, such as role, start date, end date, or status. You can also use the Account-Account Relationship object to report on the account-account relationships and analyze their impact on your business. Verified References: : Salesforce Help Article [4] : Salesforce Help Article [5]

The setting in Action Plans that helps toavoid non working hours, company holidays, and other non working days for deadline calculation is Skip Non-Work Days for Deadlines. This is a custom setting that determines whether to exclude non work days when calculating the due date for action plan items based on the action plan item template duration. By enabling this setting, the Admin can ensure that the deadlines are realistic and achievable

Interest Tags are a feature of Financial Services Cloud that let users add custom tags to client records to capture client needs, interests, and prospecting opportunities. Some of the things to consider when configuring a report to show Interest Tags are:

When the user defines the custom report type, Topics should be selected as the Primary Object. Topics is the standard Salesforce object that stores the Interest Tags data4. The user can then add other objects as secondary objects, such as Accounts, Contacts,or Opportunities.

To show Interest Tags applied to specific objects, the user can add a filter in the report and select the object name. For example, to show only Interest Tags related to Accounts, the user can add a filter for Entity Type equals Account5.

Predefined reciprocalroles are available only in English and Referral record type labels are supported only in English are two language-related limitations of Financial Services Cloud. Predefined reciprocal roles are the roles that define the relationship between two individual clients or between an individual client and a group. For example, Spouse, Child, Parent, etc. These roles are not translated into other languages and cannot be edited or deleted. Referral record type labels are the labels that indicate the type of referral, such as Client Referral or Prospect Referral. These labels are also not translated into other languages and cannot be edited or deleted.References: [Predefined Reciprocal Roles], [Referral Record Type Labels]

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 anintegration profile that can enable the connection between Salesforce and the external system. The integration user is a dedicateduser 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 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 References: : Salesforce Help Article [6] : Salesforce Help Article [7] : SalesforceHelp Article [8]

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 Financial Services Cloud capability that provides the ability to accommodate the request of sharing specific records with certain users who are not typically engaged in that account is Compliant Data Sharing.Compliant Data Sharing is a feature that allows users to share records withother users based on criteria such as record type or field value. Users can create sharing rules for objects such as account, contact, individual, financial account role, opportunity participant role, or case team role. By using Compliant Data Sharing, the financial institution can share records with legal and compliance members who must be engaged for particular deals based on a field value that indicates the deal type.

QUESTIONNO: 114

Early in the discovery and solution meetings, it was determined that the client would primarily use out-of-the-box Financial Services Cloud (FSC) objects and components with minimal custom objects needed. In addition, it was decided that records should be private, but the managerial chain would require visibility into all their direct reports' records.

Which three security settings must be set up in Salesforce to meet these requirements?

A. Only Custom Profiles should be configured and assigned to all users to use FSC components and field-level security. The ^ administrator should configure custom profiles and assign them to all users

B. Organization-wide sharing defaults should be set to meet sharing requirements for all objects in use.

C. Each object sharing should be set up, explicitly sharing each user's record with the manager.

D. The Role Hierarchy in setup should be configured to allow for managers to automatically see records of those under them.

E. Custom permission sets and out-of-the-boxFSC permission sets should be configured or updated and assigned to all users for the use of FSC components and field-level security.

Answer: BDE

The following security settings must be set up in Salesforce to meet the requirements of using out-of-the-boxFinancial Services Cloud objects and components with minimal custom objects and private record sharing with managerial visibility:

Organization-wide sharing defaults should be set to meet sharing requirements for all objects in use. Organization-wide sharing defaults are the baseline level of access that users have to records that they do not own or are not explicitly shared with them. You can use organization-wide sharing defaults to specify the default access level for each object, such as Public Read/Write, Public Read Only, or Private. You can also use organization-wide sharing defaults to enable or disable features such as grant access using hierarchies, external access, or external org-wide defaults.

The Role Hierarchy in setup should be configured toallow for managers to automatically see records of those under them. The Role Hierarchy is a structure that represents the levels of data visibility and access that users have in an organization based on their role or position. You can use the Role Hierarchy to define the roles and subordinates for each user and grant access to records owned by or shared with users below them in the hierarchy. You can also use the Role Hierarchy to control the visibility of dashboards, reports, and territories.

Custom permission sets and out-of-the-box FSC permission sets should be configured or updated and assigned to all users for the use of FSC components and field-level security. Permission sets are a collection of settings and permissions that give users access to various tools and functions in Salesforce. You can use permission sets to grant additional permissions or access levels to users without changing their profile. You can also use permission sets to control the field-level security for each object and field, which determines whether users can view, edit, or delete data in those fields. Financial Services Cloud provides several out-of-the-box permission sets that grant access to FSC components and features, such as Action Plans, Financial Accounts, or RelationshipGroups. You can also create custom permission sets to meet your specific business needs. Verified References: : Salesforce Help Article 1 : Salesforce Help Article 2 : Salesforce Help Article 3

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 thejourney 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]