During a project's design phase, a consultant must provide a Financial Services Cloud solution that can support Compliant Data Sharing (CDS). What are three things the consultant should consider regarding CDS?
Compliant Data Sharing (CDS) is a feature of Financial Services Cloud that allows granular control over access to sensitive data in Account and Opportunity objects. CDS can help financial services companies comply with regulations and policies that restrict data visibility based on user roles. Some considerations regarding CDS are:
Participant Roles provide another way to grant data access without overwriting sharing behavior from existing sharing features. Participant Roles are custom objects that define the possible roles for users who need access to Account or Opportunity records. For example, a Participant Role can be Advisor, Client, Specialist, or Decision Maker. Each Participant Role has an associated access level that determines what data fields the user can view or edit. For example, an Advisor can have full access to all fields, while a Client can have read-only access to some fields.
Compliance managers and Salesforce administrators can enable CDS for Account and Opportunity objects. CDS is not enabled by default in Financial Services Cloud. To enable CDS, compliance managers or administrators need to create an integration definition record for each object that they want to enable CDS for. An integration definition record specifies the object name, the field name that contains sensitive data (such as Notes), the field name that contains the record owner (such as OwnerId), and the field name that contains the record type (such as RecordTypeId).
Role Hierarchy---based sharing is disabled by default in CDS. Role Hierarchy is a feature of Salesforce that allows users to inherit access to records from their managers or peers in the role hierarchy. For example, if a user has access to an Account record, their manager also has access to that record by default. However, in CDS, role hierarchy---based sharing is disabled by default for Account and Opportunity objects. This means that users do not inherit access to records from their role hierarchy unless they are explicitly granted access through Participant Roles or other sharing features.
An insurance company aims to improve a call center's productivity. A detailed analysis discovered that agents spend a lot of time capturing data while adding and updating beneficiary details. Capturing premium payment details (payment date and frequency) is another time-consuming task. Which action should a Financial Services Cloud consultant take to resolve the issue?
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.
[Insurance Flow Templates]
[Customize Insurance Flows]
Cumulus Insurance has a franchise business model with a large number of franchisees who operate independently but report to regional managers who are Cumulus employees. The company would like the franchise owners and their employees to have access to the Cumulus Salesforce Financial Services Cloud (FSC) instance. The company plans to use the Role Hierarchy and sharing rules to implement this. What should the architect at Cumulus Insurance be aware of for this solution?
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.
[Sharing Rules]
[Role Hierarchy]
[Sharing Rule Limits]
A Financial Services Cloud (FSC) administrator wants to create a new FSC permission set that includes the Access Interest Tags for Financial Services Cloud permission.
Which two permission sets should be cloned to create this new permission set and give access to interest tags?
The Access Interest Tags for Financial Services Cloud permission is included in two permission sets that are provided by FSC:
To create a new FSC permission set that includes the Access Interest Tags for Financial Services Cloud permission, either of these permission sets can be cloned and modified as needed.
A system administrator at a financial services company wants to build a report to show Interest Tags.
Which two things should the administrator consider when configuring the report?
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:
Jerlene
18 days agoKallie
2 months agoKati
2 months agoSylvie
2 months agoEdmond
3 months agoDenny
3 months agoNguyet
4 months agoGoldie
4 months agoMajor
4 months agoAhmed
5 months agoJerlene
5 months agoKasandra
6 months agoChauncey
6 months agoViva
6 months agoBobbie
6 months agoLynelle
6 months agoArminda
7 months agoRolland
7 months agoKayleigh
7 months agoKrissy
8 months agoIn
9 months agoLeota
9 months agoRoslyn
9 months agoMelodie
9 months agoDelsie
9 months agoMaryann
10 months agoEloise
10 months agoSophia
10 months agoCharlotte
10 months agoLoreta
10 months ago