Pass the Salesforce Financial Services Cloud AP-208 Questions and answers with CertsForce

Agentforce Financial Services uses Individual Record Type Mapper custom metadata to map custom individual record types to the appropriate Account and Contact record-type architecture. This allows an organization to differentiate individual personas such as customers and independent advisors while preserving Financial Services behavior that depends on correctly identifying those records as individuals.

The administrator first creates and enables the required Person Account record types. The administrator then opens the Individual Record Type Mapper custom metadata and creates or updates the appropriate mapping records, specifying the record type used for each individual classification.

This metadata is important because Agentforce Financial Services components and processes need to know which Account record types represent individuals. Additional mapping records can be created when an organization has multiple person-oriented business roles that require different page layouts, processes, or referral behavior.

Creating custom fields does not establish record-type semantics. A Contact record type alone is insufficient because Person Accounts are represented through the Account architecture with associated Contact behavior. Likewise, a generic custom setting is not the mechanism used to distinguish the two requested Person Account types.

The correct configuration is therefore to create the necessary Person Account record types and define their corresponding Individual Record Type Mapper metadata.

Interest Tags enable Financial Services users to categorize customer interests and associate those interests with supported records, including Interaction Summaries. Access is controlled through specific Financial Services permissions rather than being universally included in every Financial Services permission set.

Salesforce identifies Financial Services Cloud Extension and Financial Services Cloud Foundations as permission sets that provide the relevant Interest Tags capabilities. Current Salesforce documentation lists these permission sets among those used in Financial Services for access to Interest Tags functionality.

Salesforce also states that users who add Interest Tags to Interaction Summaries require appropriate Financial Services access, including Financial Services Cloud Extension or Financial Services Cloud Foundations, depending on the product configuration. Before users can work with the feature, administrators must also enable Topics and Interest Tags and configure the relevant object for Topics.

Cloning one of these permission sets provides an appropriate baseline when an organization needs a specialized permission set while retaining the required Interest Tags permission. The Financial Services Cloud Standard and Basic permission sets serve other user-access patterns and do not constitute the specified source permission sets for this capability. Therefore, Extension and Foundations are the appropriate permission-set templates.

Actionable Relationship Center is designed specifically to help Agentforce Financial Services users understand complex relationships among customers, households, businesses, trusts, contacts, and other related entities.

ARC presents these connections through an interactive relationship graph rather than requiring the wealth manager to interpret separate related lists manually. It can connect business accounts, Person Accounts, and Contacts and display relevant relationship information in the graph.

The Addams scenario is an ideal use case. The wealth manager needs to understand the wife ' s membership in the Addams Household, her spouse relationship, their shared connection to the Addams Charitable Trust, and her separate connection to the Symonds Household. ARC can visualize these multi-party relationships through Account Contact Relationship, Account Account Relationship, and Contact Contact Relationship junction objects.

ARC also supports configurable custom relationship graphs, record actions, node display fields, details panels, highlights panels, and preconfigured Financial Services templates.

Tableau and Marketing Cloud Intelligence provide analytics and visualization capabilities but are not designed to present the operational Financial Services relationship graph directly within the advisor workflow. ARC provides the relationship context needed to understand spheres of influence, recognize connections, and identify potential service or business opportunities.