Salesforce Financial-Services-Cloud Dumps

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

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. 

To grant restricted access to 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 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). 

The following security settings must be set up in Salesforce to meet the requirements of using out-of-the-box Financial 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 to allow 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 Relationship Groups. 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 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.

The Referral Score is updated when an opportunity associated with the Referral is Closed Won. The Referral Score is a metric that measures the quality and quantity of referrals that a user creates or receives. The Referral Score is calculated as the number of referrals converted to opportunities divided by the total number of referrals. The Referral Score is displayed in the Referral Summary component on the user’s Home page or record page. The Referral Score is updated whenever a referral is converted to an opportunity or an opportunity is closed as won or lost. Verified References: : Salesforce Help Article 2 : 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]

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 with other 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.

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. 

Financial Services Cloud contains a number of custom objects to model a client’s financial information, and each object can be configured to appear as tabs in your org. Some of the custom objects are:

• Financial Goal: An object that represents a client’s financial objective, such as saving for retirement, buying a house, or paying off debt. A financial goal has fields to store information, such as name, amount, target date, priority, and status.
• Financial Holding: An object that represents a holding in an investment account, such as a security, a mutual fund, or a bond. A financial holding has fields to store information, such as symbol, shares, price, gain/loss, and market value.
• Revenue: An object that represents revenue generated from a client’s financial accounts, such as an increase in stock value, a dividend payment, or an interest income. A revenue has fields to store information, such as type, amount, date, and source.

References:

• Financial Services Cloud Associated Objects
• Learn About the Financial Services Cloud Data Model

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 ownership structure 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 of relationship 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 group account. Verified References: : Salesforce Help Article 2 : Salesforce Help Article 3 : Salesforce Help Article 4

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 provide more 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 support the 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]

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.

A Financial Services Cloud consultant can suggest utilizing Insurance Flow Templates to resolve the issue of improving the call center’s productivity and reducing the time spent on capturing data for beneficiary details and premium payment details. Insurance Flow Templates are prebuilt flow templates that guide users through the steps of creating or updating insurance policies and beneficiaries in Financial Services Cloud. The templates can be customized to suit the specific needs and requirements of the insurance company. By using Insurance Flow Templates, the call center agents can streamline their data entry process and provide better service to their customers.

References:

• [Insurance Flow Templates]
• [Customize Insurance Flows]

A Contact-Contact Relationship is a construct in Financial Services Cloud that allows you to model the relationship between two contacts, such as a business contact and a client that is modeled as a person account. The Reciprocal Role is a field on the Contact-Contact Relationship object that defines how each contact relates to the other. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 64.

Salesforce provides features and tools to help financial institutions improve the efficiency of their mortgage processes and provide better experiences for their customers. Some of the features and tools that a consultant can suggest to Cumulus Bank to implement are:

• The standard mortgage flow templates to build a mortgage flow in Financial Services Cloud: These are prebuilt flow templates that guide users through the steps of creating a mortgage application, capturing borrower information, and submitting the application for approval7. The templates can be customized to suit the bank’s specific needs and requirements8.
• Flow Builder to automate these business processes: Flow Builder is a point-and-click tool that lets users create flows to automate business processes in Salesforce9. Flow Builder can be used to create custom mortgage flows that integrate with other Salesforce features, such as data models, objects, fields, validation rules, and actions10.

References:

• Flow Builder for Mortgage
• Customize Mortgage Flows
• Flow Builder
• Create a Mortgage Flow

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

My Domain is a feature in Salesforce that allows you to create a subdomain for your org. You need to enable My Domain to access Financial Services Cloud Lightning Components, such as Actionable Relationship Center, Relationship Map, Life Events & Business Milestones, etc. To enable My Domain, you need to do the following:

• Register a subdomain using the My Domain wizard in Setup > My Domain.
• Deploy it to your users after testing it in your sandbox or developer org. Verified References: : Salesforce Help Article [7]

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.

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 Salesforce Admin can hide sensitive Life Events on the Life Events component on the Lightning Page using the Properties pane. The Life Events component is a Lightning component that displays a timeline of life events and business milestones for a client or a group. The Admin can use the Properties pane to customize the component and select which event types to show or hide on the timeline.

The most suitable option for Cumulus Cloud Bank to provide its customer service staff with real-time access to customer accounts, including the ability to view current transactions and balances, is to embed custom Lightning web components on the Account and Financial Account pages, and use custom Apex to make callouts to the core system services. This option allows the bank to leverage the Lightning Platform features and capabilities, such as Lightning web components, Apex, and callouts, to create a seamless and performant integration with their core systems. By using custom Lightning web components, the bank can create custom user interfaces that display the data from the core systems on the Account and Financial Account pages. By using custom Apex, the bank can write code that makes callouts to the core system services using HTTP requests and responses, and handle any authentication, error handling, or data transformation logic.

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 gap analysis is a key step in identifying different business processes and outlining encompassing system flows based on the existing environment when setting up Salesforce Financial Services Cloud (FSC). A gap analysis is a method of comparing the current state of a system or process with the desired future state and identifying the gaps or differences between them. By conducting a gap analysis, a consultant can understand the customer’s pain points, requirements, and expectations and design a solution that leverages the best practices and features of Salesforce FSC.

References:

• Gap Analysis
• Salesforce Financial Services Cloud Implementation Guide

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 Salesforce feature that should be used for the digital onboarding process is Flows. Flows are a tool that can automate business processes and guide users or 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. Flows can also integrate with existing data and prefill fields with information that the bank already has on file, reducing the need to ask the customer for redundant information. Flows can be embedded in Lightning pages, Experience Cloud sites, mobile apps, or websites to provide a seamless and engaging digital onboarding experience. Verified References: : Salesforce Help Article 1 : Salesforce Help Article 2

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.

To set up the new record types for Person Accounts, the administrator should configure Individual Record Type Mapper custom metadata. The Individual Record Type Mapper is a custom metadata type in Financial Services Cloud that defines how records are created when using certain features, such as Einstein Data Capture or Salesforce Inbox. The Individual Record Type Mapper maps Person Account record types to Individual record types, so that when a new Individual record is created from an email or calendar event, it automatically creates a corresponding Person Account record with the same record type. To configure Individual Record Type Mapper custom metadata, you need to go to Setup > Custom Metadata Types > Individual Record Type Mapper > Manage Records and create a new record for each Person Account record type and its matching Individual record type. Verified References: : Salesforce Help Article [8] : Salesforce Help Article [9]

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 statements about Action Plans are true:

• When you work with Action Plans, you first create Action Plan Templates, which are reusable sets of tasks that define a common client process1.
• Action Plans make it easy to create reports and dashboards, so you can monitor progress and ensure compliance. Users can use standard report types or custom report types to create reports on action plans, action plan templates, action plan items, action plan item templates, and action plan item owners1.
• Action Plans can be used to automatically assign task owners and deadlines for specific client engagements. Users can specify task owners by using assignment logic such as specific user, role, queue, action plan creator, or account team1. Verified References: 1

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

To capture and display commercial customers and their parent companies, Lake Tahoe Bank SF Admin can use the following steps:

• Add the Business record type to the Group record type mapper, which is a custom metadata type that defines which record types can be added as members of a group1.
• Leverage Groups to capture the majority owner of a commercial customer, which is a business entity that has a stake in another business entity1. Groups are a feature that allows users to create and manage household and business relationships1.
• Use Account hierarchy to capture minority owners of a commercial customer, which are business entities that have less than 50% stake in another business entity2. Account hierarchy is a feature that allows users to see how accounts are related to each other in a parent-child relationship2.
• Link multiple owners to the business entity as a Group, which allows users to see all the stakeholders of a commercial customer in one place1

 A possible cause for why the portfolio manager cannot see ARC when trying to set up relationships between two accounts is that he has not been given the permissions that enable users to view and manage ARC. To access ARC, users need to have certain permissions and settings enabled in their user profile or permission set, such as:

• View Setup and Configuration
• Customize Application
• Manage Custom Permissions
• Financial Services Cloud Standard User
• Financial Services Cloud Admin If any of these permissions or settings are missing, users may not be able to see or use ARC properly. Verified References: : Salesforce Help Article 5

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]

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.

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.

A screen flow is a type of flow that guides users through a series of screens to complete a task or collect information2. Screen flows can also interact with external systems using Apex actions or invocable actions3. In this case, the consultant can create a screen flow that collects the caller’s name and social security number from the agent, and then invokes an Apex action or an invocable action that makes a web service call to an external authentication service.

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.

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 an organization 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 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 Services Cloud 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

• Flows provide step-by-step guidance for common service requests, such as change of address, or change of beneficiary, without the need to navigate to different screens. Flows can simplify and streamline the customer onboarding process by automating tasks and collecting information in an easy and intuitive way. You can use Flows to create service requests that capture the customer’s details and update the related records in one place.
• Flows enable customers to schedule appointments via customer communities, mobile apps. or websites. Flows can integrate with Experience Cloud sites, mobile apps, or websites to provide self-service options for customers. You can use Flows to create appointment scheduling forms that allow customers to book appointments with the right specialist at the right time and place. Verified References: : Salesforce Help Article 3 : Salesforce Help Article 4

Group Membership is a construct in Financial Services Cloud that allows you to define the relationship between a group and its members. You can use Group Membership to specify the following information:

• The role of the member within the group, such as Owner, Beneficiary, Trustee, etc.
• Whether the group is the primary group for the member, which affects how financial data is rolled up and displayed. Verified References: : Salesforce Financial Services Cloud User Guide, page 38.

 The following steps should be taken by the Financial Advisor in Financial Services Cloud App to capture the information about opening an Education Savings Account for their client’s first child:

• Create a Life Event for the birth of the child and a Referral for the Education Savings Account. A Life Event is a construct in Financial Services Cloud that allows you to track significant events in your client’s life that may affect their financial needs or goals. You can use Life Events to create a record for the birth of the child and link it to the client’s account. A Referral is a construct in Financial Services Cloud that allows you to capture a customer need or interest and assign it to another advisor or line of business. You can use Referrals to create a record for the Education Savings Account and route it to the appropriate banker.
• Create a Life Event for the birth of the child and a Financial Goal for the Education Savings Account. A Financial Goal is a construct in Financial Services Cloud that allows you to track your client’s financial objectives and measure their progress towards achieving them. You can use Financial Goals to create a record for the Education Savings Account and associate it with the client’s account and financial accounts. Verified References: : Salesforce Financial Services Cloud User Guide, page 29. : Salesforce Financial Services Cloud User Guide, page 30. : Salesforce Financial Services Cloud User Guide, page 33.

To speed up and simplify Referral creation in Salesforce, the Admin can use Global Action to create Referrals. Global Actions are actions that let users create records without leaving their current page or context. By using Global Actions, the Admin can enable Hank to create Referrals from any page in Salesforce, such as Chatter, Home, or Account pages. The Admin can also customize the layout and fields of the Global Action to capture only relevant information for Referrals