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:
An administrator is logged into Data Loader with their own credentials to insert new Business Account records into their Salesforce environment. They forget to specify the Account Owner field in the import file.
Assuming there are no other issues, what should happen when the administrator uploads the import file?
When using Data Loader to insert new records into Salesforce, if the Account Owner field is not specified in the import file, the default owner will be the user who is logged into Data Loader. In this case, since the administrator is logged into Data Loader with their own credentials, they will be assigned as the owner of all the new Business Account records. This behavior is consistent with the standard Salesforce rule that every record must have an owner.
While working for an insurance client implementing Financial Services Cloud, an API integration between Salesforce and a risk control system has been configured. The consultant is asked to ensure the correct profiles and permissions were set up for this connection. Which two steps should the consultant take?
To ensure the correct profiles and permissions for an API integration between Salesforce and a risk control system, the consultant should do the following steps:
Create a dedicated Integration User that will be used to authenticate and authorize the API calls between Salesforce and the risk control system. The Integration User should have a unique username, password, and security token that are not shared with other users or systems. The Integration User should also have the minimum permissions and access settings required to perform the integration tasks.
Create a new custom profile and ensure API Only is selected. The API Only option restricts the user from logging in to the Salesforce user interface, but allows the user to access the Salesforce API. The custom profile should also have the appropriate object permissions, field-level security, record types, page layouts, and other settings that are relevant for the integration. The custom profile should be assigned to the Integration User.
Kallie
5 days agoKati
24 days agoSylvie
1 months agoEdmond
2 months agoDenny
2 months agoNguyet
2 months agoGoldie
3 months agoMajor
3 months agoAhmed
3 months agoJerlene
4 months agoKasandra
4 months agoChauncey
4 months agoViva
5 months agoBobbie
5 months agoLynelle
5 months agoArminda
5 months agoRolland
5 months agoKayleigh
6 months agoKrissy
7 months agoIn
8 months agoLeota
8 months agoRoslyn
8 months agoMelodie
8 months agoDelsie
8 months agoMaryann
8 months agoEloise
9 months agoSophia
9 months agoCharlotte
9 months agoLoreta
9 months ago