Financial-Services-Cloud Sample Questions Answers

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 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 unmanaged extension package for Intelligent Need-Based Referrals and Scoring provides users access to referral dashboards and reports, as well as referral scoring and routing features.

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, execute logic, 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 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 options are available to view and update Account-Account, Account-Contact, and Contact-Contact Relationships in Financial Services Cloud:

• Actionable Relationship Center: This is a Lightning component that displays a list of all the relationships for a client or a group. You can use it to view, create, edit, and delete relationships.
• Relationship Map: This is a Lightning component that displays a graphical representation of all the relationships for a client or a group. You can use it to visualize and navigate the relationship network.
• Group Members Component: This is a Lightning component that displays a list of all the members of a group. You can use it to view, add, and remove group members. Verified References: : Salesforce Financial Services Cloud User Guide, page 34. : Salesforce Financial Services Cloud User Guide, page 36. : Salesforce Financial Services Cloud User Guide, page 38.

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.

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

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

The following OmniStudio tools should be recommended to generate the prefilled PDF:

• OmniStudio Action Document Generation, which is a tool that allows users to create documents from templates and data sources using OmniScripts and Integration Procedures. By using OmniStudio Action Document Generation, the consultant can create a document template with placeholders for the contact and address information and generate a PDF file from it using an OmniScript.
• DataRaptor, which is a tool that allows users to extract and transform data from Salesforce or external systems using Integration Procedures. By using DataRaptor, the consultant can create a data source that retrieves the contact and address information from Salesforce and maps it to the document template placeholders.

The following statements are correct about the Actionable Relationship Center Manager (ARC):

• To enable users to see the ARC, you will need to add the component for ARC to the page layout. The ARC is a Lightning component that can be added to any Lightning page that supports components, such as record pages, app pages, or Home pages. You can use the Lightning App Builder to drag and drop the ARC component to the desired location on the page layout.
• ARC displays up to 5 related lists that have a configured compact layout. The ARC shows a graphical representation of the account-account relationships for a selected record, as well as related lists of other records that are associated with the account, such as contacts, financial accounts, or opportunities. The ARC can display up to 5 related lists at a time, and each related list must have a compact layout configured to show relevant fields.
• The Association Type picklist controls the account-account relationship that display in the ARC. The Association Type picklist is a field on the Account Relationship object that defines the type of relationship between two accounts, such as Household Member, Business Owner, Trustee, or Friend. The ARC uses this field to filter and display the account-account relationships for a selected record. You can customize this picklist to add or remove values according to your business needs. Verified References: : Salesforce Help Article 3 : Salesforce Help Article 4 : Salesforce Help Article 5

The following limitations should be considered before enabling Person Accounts in Financial Services Cloud:

• Person Accounts cannot be disabled once they were enabled. Enabling Person Accounts is an irreversible action that affects your data model and user interface. You should carefully evaluate your business needs and test the functionality in a sandbox or developer org before enabling it in production.
• Creating a client record via Salesforce Inbox is not supported. Salesforce Inbox is a feature that allows you to access Salesforce data and actions from your email application. However, you cannot use Salesforce Inbox to create a client record as a Person Account. You can only create a client record as an Individual Model record using Salesforce Inbox. Verified References: : Salesforce Help Article 4 : Salesforce Help Article 5

The following statements are true for a Group in Financial Services Cloud:

• Financial Services Cloud includes a group record type for households, which is a record type that represents a collection of individuals who share financial goals, such as family members or roommates.
• A group is a type of account record that people and businesses can be related to through the account contact relationship object, which is a junction object that links an account to a contact or an individual and defines their role or relationship with that account. 

Actionable Relationship Center (ARC) is a tool that a Salesforce FSC consultant can recommend to a wealth manager who needs to make sense of complex client relationships and discover new business opportunities. ARC is an advanced visualization engine that provides a holistic view of customers and their relationships with actionable insights, all in one place5. ARC helps users understand relationships among people and businesses by presenting them in interactive components, such as graphs, cards, lists, and filters6. ARC also allows users to perform actions on the customer data, such as creating tasks, sending emails, or updating records7.

References:

• Actionable Relationship Center (ARC)
• Get Started with Actionable Relationship Center
• Work with Actionable Relationship Center

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

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

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.

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. 

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

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

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

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

As explained in the previous question, Action Plans are a feature that can help users track and manage common client processes. By creating an Action Plan Template with associated pre-determined Tasks, such as reviewing credit & debit card usage, reviewing account payables, and discussing credit needs, users can ensure that these activities are tracked and followed up on in a timely manner. Users can also automate the periodical creation of Action Plans for customer accounts using Process Builder or Apex triggers. 

To assign a task to the next available Advisor, the Admin should use Queues as the assignment logic when configuring the template task. Queues are collections of records that can be assigned to multiple users who share workloads and responsibilities. By using Queues, the Admin can ensure that any Advisor who is part of the Queue can pick up the task when they are available. 

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]

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]

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

According to the Salesforce documentation1, record rollups at the group level allow you to aggregate information from related records for several objects in Financial Services Cloud. When you enable record rollups at the group level, all corresponding records are stamped with the Primary Group in the Rollup__c lookup field. This field is added to the Account, Contact, Account Contact Relationship, and Financial Account objects. You can then use this field to create reports and dashboards that show aggregated data for each group.

The following steps should be taken by the administrator to configure Financial Services Cloud correctly based on the scenario:

• Assign the record type to users. You need to assign the new record type to the user profiles or permission sets that need to create or access referrals of that type. You can assign record types by going to Setup > Profiles > Object Settings > Leads > Record Types or Setup > Permission Sets > Object Settings > Leads > Record Types.
• Create a new record type Referral’ on the Lead object. You need to create a new record type on the Lead object and name it Referral. You can use this record type to distinguish referrals from other types of leads and apply different page layouts, business processes, or validation rules for referrals.
• Update the lead page layout. You need to update the page layout for the Referral record type and add or remove fields according to the requirements. You can also make some fields required or read-only on the page layout level. You can edit page layouts by going to Setup > Object Manager > Lead > Page Layouts. Verified References: : Salesforce Help Article 3 : Salesforce Help Article [4] : Salesforce Help Article [5]

From the Life Events card, a Wealth Advisor can take the following actions:

• Create Lead & Referral: This action creates a lead record for a new prospect or a referral record for an existing client based on the life event information.
• Request Record Approval: This action initiates an approval process for the life event record to ensure compliance and quality standards.
• Create Opportunity: This action creates an opportunity record to track the potential revenue from the life event. Verified References: : Salesforce Financial Services Cloud User Guide, page 30. : Salesforce Financial Services Cloud User Guide, page 31. : Salesforce Financial Services Cloud User Guide, page 32.

The following statements are true for Rollup By Lookup (RBL) in Financial Services Cloud:

• An RBL (Rollup By Lookup) rule displays summary calculations of financial account information, such as account balances. You can use RBL rules to aggregate financial account data across different levels of client relationships.
• The Rollup By Lookup (RBL) configuration updates the corresponding RBL summaries at the diem and group levels. You can use RBL configuration to define which fields are rolled up and how they are calculated for each diem and group type.
• Salesforce does not recommend or provide support for creation or customization of Financial Services Cloud RBL rules. RBL rules are complex and require extensive testing and validation. If you need to create or customize RBL rules, you should contact a certified Salesforce partner or consultant. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 75. : Salesforce Financial Services Cloud Implementation Guide, page 76. : Salesforce Financial Services Cloud Implementation Guide, page 77.

To configure a custom field for reporting when relating two-person accounts to each other, the Financial Services Cloud consultant should configure the custom field on the Account Account Relationship object. The Account Account Relationship object is a junction object that links two accounts together and defines their relationship type and role. By configuring a custom field on the Account Account Relationship object, the consultant can capture additional information about how two-person accounts are related to each other and use it for reporting purposes. 

 The following out of the box capabilities come with Financial Services Cloud Lead & Referral Management:

• Referral Conversion: This capability allows you to convert 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

To set up a permission set for Actionable Relationship Center (ARC), the administrator should select FSC Standard as the license on the Permission Set setup page. FSC Standard is a permission set license that enables user access to a license with contractual restrictions for Financial Services Cloud and provides access to core objects and features, including ARC1. By selecting FSC Standard as the license, the administrator can grant users access to ARC and its related objects and fields

To build the required sharing model for sensitive deal data, the consultant should use the Financial Deal object to capture the deal data and use restriction rules to block user access above the banking associate in the Role Hierarchy. The Financial Deal object is a custom object in Financial Services Cloud that allows you to track and manage complex deals that involve multiple parties, products, and stages. You can use the Financial Deal object to store sensitive deal information, such as deal name, amount, status, or participants. You can also use restriction rules to limit the visibility of Financial Deal records based on criteria such as role, profile, or ownership. Restriction rules can override the organization-wide default sharing settings and block user access to records that they would otherwise be able to see through the Role Hierarchy or other sharing mechanisms. Verified References: : Salesforce Help Article 1 : Salesforce Help Article 2

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

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 architect at Cumulus Insurance should be aware of the limitation that the administrator can define up to 300 total sharing rules for each object when using the Role Hierarchy and sharing rules to implement the franchise business model. Sharing rules are a way of granting additional access to records based on criteria, such as record owner, role, or field values. The Role Hierarchy is a way of organizing users into a hierarchy that reflects the reporting structure of the company. The Role Hierarchy and sharing rules can be used together to control the access and visibility of records for different users in Financial Services Cloud. However, there is a limit of 300 sharing rules per object, which means that the administrator may need to use other methods, such as public groups or manual sharing, to grant access to records beyond this limit.

References:

• [Sharing Rules]
• [Role Hierarchy]
• [Sharing Rule Limits]

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