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.

The following insurance processes are managed by the PolicyAdministration component:

Payments: Payments are the amounts that a policyholder pays to an insurance company for a policy or a claim. You can use the Policy Administration component to manage the payment schedules, methods, and statuses for your policiesand claims. You can also use the Policy Administration component to integrate with external payment systems and track the payment transactions and balances for your policies and claims.

Approvals: Approvals are the processes that an insurance company follows to review and authorize a policy or a claim. You can use the Policy Administration component to configure and automate the approval workflows, rules, and criteria for your policies and claims. You can also use the Policy Administration component to assign approvers, send notifications, and monitor the approval statuses and histories for your policies and claims.

Endorsements: Endorsements are the changes or modifications that a policyholder requests or an insurance company makes to a policy. You can usethe Policy Administration component to manage the endorsement requests, types, and statuses for your policies. You can also use the Policy Administration component to update the policy details, coverages, premiums, or terms based on the endorsements for your policies. Verified References: : Salesforce Help Article [9] : Salesforce Help Article [10] : Salesforce Help Article [11]

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

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.

A Custom 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 it to represent collaborative customer business operations that arenot captured by standard household or account structures. Verified References: : Salesforce Financial Services Cloud Implementation Guide, page 67.

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

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

Again, Action Plans are a feature that can help users track and manage common client processes. For a commercial loan due diligence process, users can create an Action Plan Template with tasks such as verifying income, checking credit history, appraising collateral, etc. Users can also assign different task owners and deadlines for each task to distribute the work and monitor the progress. Users can also use dashboards and reports to view the % completion of the due diligence process per client and report on the performance of the department to show possible bottlenecks.

To prevent users from accidentally creating more than one event of such an event type, the Admin should create a validation rule that will stop the user if they attempt to add multiple one-time events. A validation rule is a rule that verifies that the data a user enters in a record meets the standards you specify before the user can save the record. By creating a validation rule, the Admin can ensure that only one event of a certain type can be created for each contact.