Selected AP-208 Financial Services Cloud Questions Answers

An Action Plan is the appropriate Agentforce Financial Services capability when an organization has a standardized sequence of activities that must occur at defined intervals and needs those activities to remain visible and reportable in Salesforce. Action Plan Templates define repeatable tasks, task ownership, sequencing, and date offsets. When an Action Plan is instantiated, those template items become operational tasks that relationship managers can complete and track.

In this scenario, the meaningful business event is the customer ' s transition to an established Customer state after opening the first banking relationship. That event should initiate an Action Plan containing follow-up tasks scheduled at the required 2-day, 2-week, and 2-month offsets. This accurately aligns the operational workflow with the point at which the individual becomes a customer.

Simple email notifications do not provide the same task lifecycle, completion status, ownership, reporting, and dashboard capabilities. Similarly, triggering the plan at initial Account creation or lead conversion could occur before the required customer milestone. Salesforce specifically positions Action Plans for repeatable engagements such as account openings and allows task deadlines and ownership to be standardized while supporting reports and dashboards for progress monitoring and compliance.

Agentforce Financial Services group-level record rollups aggregate qualifying records belonging to members of a Primary Group so advisors can see consolidated household information. Salesforce ' s supported-object matrix includes Tasks, Financial Accounts, and Opportunities.

Financial Accounts are surfaced through financial-account components at the group level. Once group rollups are enabled and the financial account is associated with a member of the Primary Group, the household-level experience can present the aggregated account information.

Tasks are displayed within the Activities related list at the group level. This enables advisors to review relevant work and interaction activity across household members from the household context.

Opportunities are also supported and appear in the Household Opportunities related list. Opportunities can require additional configuration in managed-package implementations, such as adding the appropriate value to the Rollup__c field on Account Contact Relationship.

Alerts and Action Plans are not included in the documented group-level record-rollup object set tested here. They have their own data structures and visibility mechanisms.

Thus, the supported choices are Tasks, Financial Accounts, and Opportunities.

Chatter components in Lightning App Builder depend on Feed Tracking being enabled for the underlying object. Therefore, if the administrator edits the Action Plan Lightning record page before enabling feed tracking for Action Plan, Chatter-related components are not presented as available components.

Salesforce guidance states that Chatter Publisher, Chatter Feed, and Chatter components can be absent from Lightning App Builder when Feed Tracking is not enabled for the object. Once the administrator enables Feed Tracking through Setup, Feed Tracking, the Chatter components become available for placement on the object ' s Lightning record page.

Feed tracking serves two related purposes. It enables users to follow activity associated with a record, and it provides the object-level capability required for the Lightning Chatter feed experience. Salesforce supports configuring feed tracking for custom and managed-package objects where the feature is available.

This is independent of whether the administrator personally has the Action Plans permission set. The absence of the component in Lightning App Builder is a configuration issue rather than a user entitlement issue. Nor is there a separate Action Plan-specific Chatter switch that replaces standard Feed Tracking. Once Feed Tracking is enabled for Action Plan, the administrator can return to Lightning App Builder and add the required Chatter component.

Salesforce applies platform limits to the number of sharing rules configured for an object. The standard allocation is 300 total sharing rules per object, including owner-based and criteria-based rules. This limitation matters when designing a franchise architecture because creating separate sharing rules for every franchise, region, or user population can result in an unnecessarily complex sharing model and eventually approach platform limits.

Architects should prefer scalable mechanisms such as roles, public groups, role-and-subordinate relationships, sharing sets or appropriate Experience Cloud sharing constructs, and criteria-driven sharing where those mechanisms meet the security requirements.

The default total sharing-rule limit can in some circumstances be increased through Salesforce Support, but the standard architectural limit tested here is 300 rules per object.

A user occupies one role in Salesforce ' s role hierarchy, not multiple simultaneous roles. Browser selection is unrelated to the fundamental role-and-sharing architecture. Public groups are supported as reusable sharing targets, but the stated 1,024 limit is not the relevant restriction identified in this scenario.

Therefore, the architect must account for the per-object sharing-rule allocation when designing a large franchise access model and should avoid a design that depends on a separate rule for every franchise unless absolutely necessary.