Free Practice Questions for the Salesforce Financial Services Cloud AP-208 Exam (2026 Updated)

The consultant should use the packaged Insurance Flow Templates and associated guided insurance service processes rather than creating a custom user interface from scratch. Salesforce ' s insurance capabilities provide prebuilt guided processes that standardize common policy-servicing activities and reduce the amount of manual navigation and data entry required by service representatives.

Current Agentforce Financial Services documentation continues this architecture through prebuilt insurance service-process templates. These templates provide ready-made process attributes, intake forms, and fulfillment flows and are intended to accelerate insurance service delivery across assisted and self-service channels.

Premium-payment servicing is a concrete example. Salesforce supplies guided processes in which an agent selects the active policy, reviews the current premium due date and frequency, selects the new payment frequency and effective date, and submits the change through an OmniScript. Insurance policy processes similarly use OmniScripts to guide users through payment-plan information and payment-frequency selection.

This packaged approach is preferable to custom Lightning web components because it reduces development and maintenance while enforcing consistent data capture. An Action Plan manages tasks and deadlines but does not replace a guided data-entry process for updating beneficiary or premium-payment information.

The broker organization should be represented by an Account, while each individual broker is represented as a Contact associated with that organization. This preserves the distinction between the business entity and the individual professionals who operate within it and allows each broker to receive individually controlled portal access.

The assistant should likewise be modeled as a Contact. Where an assistant works across multiple broker relationships, Salesforce ' s Contacts to Multiple Accounts architecture provides a scalable way to represent those associations without duplicating the Contact record. The model maintains one Contact as the authoritative individual record while using relationship records to connect that Contact to additional relevant Account relationships.

This structure is preferable to creating separate Account-and-Contact pairs for every individual broker because it would unnecessarily duplicate business entities and complicate relationship management. A Contact-to-Contact relationship can describe interpersonal relationships but does not provide the same account-based affiliation model required where one person participates across multiple broker organizations or account contexts.

Record access for portal users is handled separately through Experience Cloud sharing and security controls. Modeling brokers individually as Contacts does not require brokers to see one another ' s information. The sharing architecture can restrict users to their own records and specifically authorized relationships.

The Account-plus-Contact approach therefore best satisfies the required broker and assistant data model.

Mortgage functionality in Agentforce Financial Services is controlled through the appropriate permission-set and user-access configuration. A user who must create or work with Residential Loan Application records needs access to the mortgage feature and to the mortgage-related objects. Consequently, failure to assign the required Mortgage permissions prevents the consultant from creating the application record.

Salesforce ' s Financial Services setup guidance includes assigning the Mortgage permission set as part of granting users access to mortgage functionality. Salesforce also provides enhanced mortgage permission-set configurations for personas such as loan officers and underwriters.

Current configuration guidance shows that mortgage-oriented permission sets must grant the system permission that licenses the user to access mortgage functionality in Financial Services and must provide the necessary object permissions for Residential Loan Applications and related Loan Applicant and Loan Application objects.

The issue is therefore not resolved by enabling a Residential Loan Application flow or by selecting a user-level Mortgage User checkbox. Nor is there a general Allow Mortgage Access setup switch corresponding to the required user entitlement. Access is established through the prescribed mortgage permissions and associated object-level access.

The required architecture combines Document Generation with a DataRaptor, now called an OmniStudio Data Mapper in current Salesforce terminology.

Document Generation merges Salesforce or OmniStudio data into predefined document templates and can produce documents that are subsequently converted to PDF. It is designed for outputs such as forms, contracts, proposals, reports, and customer correspondence where variable information must be populated dynamically.

The DataRaptor or Data Mapper supplies the data used to populate the template. An Extract retrieves fields from Salesforce, while mapping capabilities connect those extracted values to document tokens. Salesforce document-generation architecture supports automatic resolution of template token data from configured mappings such as DataRaptor Extracts.

In this scenario, the customer ' s newly entered address must populate predetermined address placeholders in the generated document. Document Generation produces the document, while the DataRaptor or Data Mapper provides and maps the Salesforce data.

Calculation Procedures perform calculations, and Integration Procedures orchestrate integrations. Neither replaces the dedicated document-generation and data-mapping capabilities required to create the prefilled PDF.

Salesforce provides three primary sets of preassembled Financial Services flows: Mortgage, Retail Banking, and Insurance. These templates accelerate implementation by supplying guided business processes that consultants can clone and adapt rather than constructing every user journey from the beginning.

Financial Services includes different sets of preassembled flows tailored to specific business requirements: mortgage flows, insurance flows, and retail banking flows. Mortgage flows are supplied with Financial Services Cloud, while insurance and retail banking flows are provided through the Lightning Flow for Financial Services package. The installed flows are delivered as standard flow templates and can be cloned and customized according to organizational processes.

Mortgage templates support activities associated with collecting borrower information and assets and liabilities. Retail banking and insurance packages similarly include predefined service-request flows.

Commercial Banking and Institutional Banking have dedicated Financial Services capabilities, but they are not the three categories of preassembled flow sets described by this package architecture. Therefore, the correct selections are Mortgage, Retail Banking, and Insurance.

This design requires objects that represent participation in the interaction, sharing of the interaction summary, and participation in the financial deal.

Interaction Participant associates internal users or groups with an Interaction. This enables engagement records to reflect which internal stakeholders participated in the client interaction and provides the connection between the interaction and the involved users or groups.

Interaction Summary Participant controls access to the detailed interaction notes. Salesforce allows an Interaction Summary to be shared with a specific user or group by adding that user or group through the Interaction Summary Participants related list. Compliant Data Sharing must be enabled for Interaction Summary to use this participant-based model.

Financial Deal Participant performs the corresponding function at the deal level. Financial Deal records can be shared with users or groups by adding them as participants, allowing specialists from another line of business to receive controlled access to the relevant transaction.

These objects work together effectively: the Interaction captures the engagement, the Interaction Summary contains the detailed notes, and the Financial Deal represents the underlying transaction. Participant records provide controlled association and sharing across these layers without broadly exposing sensitive information to unrelated users.

Agentforce Financial Services extends the standard Salesforce Lead object with record types appropriate to financial-services acquisition and referral processes. The relevant Lead record types are General, Referral, and Retirement Planning.

The General record type supports ordinary prospect-management scenarios. Salesforce ' s Financial Services configuration documentation identifies General as an available Lead record type and provides a corresponding Lead page-layout assignment. Retirement Planning is a business-to-consumer Lead record type intended for retirement-focused prospect scenarios.

The Referral record type is particularly important in Financial Services. Salesforce uses it to allow users to create and route referrals based on an expressed customer interest. Administrators can also create additional referral record types by deriving a custom Lead record type from Referral and configuring the corresponding Referral Record Type Mapper custom metadata.

Salesforce ' s Financial Services data model identifies the Lead record types as General, Referral, and Retirement Planning.

Opportunity is a separate Salesforce object and therefore is not a Lead record type. Adjustments likewise is not one of the standard Financial Services Lead record types applicable to this configuration.

The relationship structure in option C reflects the essential Agentforce Financial Services household-modeling rules. Rachel ' s own household is her Primary Group, and Rachel is its Primary Member. Her spouse, Nigel, is another household member related through the spouse relationship. The Addams Charitable Trust is represented as a related business account, while the attorney is represented as a related professional contact.

Salesforce household modeling uses this same conceptual structure. A customer such as Rachel is represented by a Person Account and can be marked as both the household ' s Primary Member and as having that household as the Primary Group. A spouse is added as another group member and is connected through an explicit spouse relationship. A trust is represented by a Business Account and related to the household through an account relationship.

A person can participate in multiple groups but can have only one Primary Group because that designation determines the household to which eligible financial information and activities roll up. Rachel can therefore belong to the Symonds household as a beneficiary while retaining the Addams household as her Primary Group.

This structure provides the advisor with a complete view of Rachel ' s immediate household, family affiliations, trust relationship, and professional connections.

Compliant Data Sharing supplements Salesforce ' s standard record-sharing architecture with participant-based access. Record owners can add participants and assign Participant Roles that determine whether those users receive read-only or read/write access. Salesforce also permits non-owner participants who have Edit access through CDS to manage participants, giving them sharing capabilities comparable to the record owner. Users above the owner can separately retain access through role hierarchy where hierarchy access applies.

Salesforce also imposes a lifecycle dependency between object enablement and Participant Roles. If Compliant Data Sharing must be disabled for a supported object, the participant roles associated with that object must first be removed.

CDS is not limited exclusively to Financial Services objects plus Account and Opportunity. Current Salesforce implementations support additional standard and custom objects and use CDS across multiple Salesforce industry solutions.

For Organization-Wide Defaults, supported objects can use Private or Public Read Only for CDS to provide meaningful incremental access. Public Read/Write makes CDS ineffective because all users already have record access. Therefore, the assertion that OWD must always be Private is too restrictive under the current implementation.

Relationships between two business accounts are modeled through Account-Account Relationships, with reciprocal relationship definitions specifying the role each account plays relative to the other. Therefore, the administrator should create the appropriate Account Reciprocal Role rather than simply adding an arbitrary value to a relationship-object picklist.

Salesforce Financial Services relationship modeling supports connections among households, businesses, trusts, professional organizations, and other entities. Reciprocal roles describe the meaning of each side of a relationship—for example, Proprietor and Business, or another organization-specific pair. Salesforce provides commonly used reciprocal role records and permits administrators to configure additional roles when the packaged options do not represent the organization ' s business relationships.

The Account-Account Relationship object is the structural record that relates business accounts, while the relationship-role definition supplies the semantics of that relationship.

Account-Contact and Contact reciprocal roles apply to relationships involving contacts or individuals, so they do not satisfy a two-business-account requirement. The proper configuration is therefore a new Account Reciprocal Role.

Agentforce Financial Services provides several specialized components for understanding and maintaining complex customer relationships. The relevant options here are Actionable Relationship Center, Relationship Map, and Group Members.

Actionable Relationship Center renders an interactive relationship hierarchy for accounts and contacts and combines multiple Financial Services relationship types in a single visual experience. It can work with Account-Account Relationship, Account-Contact Relationship, Contact-Contact Relationship, and reciprocal-role information.

The Relationship Map provides a visual representation of relationships involving Accounts, Contacts, and individuals. It helps users navigate interconnected customer relationships and understand how people, households, and organizations relate to one another.

The Group Members component displays the members of a relationship group and their associated information. Financial Services provides group-member experiences that enable users to work with household or group membership and related customer information.

The Family Members component is not one of the standard Financial Services relationship-management components represented in this architecture. The Life Events component serves a different purpose: it presents significant events and business milestones so advisors can identify changes in customer circumstances and take timely action.

Therefore, the relationship-oriented Financial Services components are Actionable Relationship Center, Relationship Map, and Group Members.

A transformation from the individual account model to Person Accounts is a significant data-model change and must be approached with strong data-protection controls. The implementation team should therefore prioritize a complete data backup before changing or converting existing customer records.

Salesforce ' s conversion guidance includes performing a backup as a core prerequisite in the transformation sequence. The process ultimately changes individual Account and Contact records into Person Account records, and Salesforce emphasizes that the transformation must first be tested carefully because the Person Account model cannot simply be disabled after it has been enabled.

Salesforce also recommends creating a sandbox to assess how Person Accounts affect the organization ' s technical architecture, integrations, automation, components, reports, and customizations. However, from a migration-risk perspective, preservation of the existing production data is fundamental before irreversible data transformation activities are performed.

Subsequent implementation activities include enabling Person Accounts, enabling them for Agentforce Financial Services, configuring record types through the Individual Record Type Mapper, validating source records, and executing the conversion. These activities depend on careful preparation. A reliable backup provides the implementation team with an authoritative pre-migration data state and should therefore be treated as a top planning priority.

A system-to-system API integration should operate through a dedicated integration user whose access is limited to the permissions required by that integration. Salesforce recommends creating a distinct user for each integration because this improves traceability, isolates credentials, enforces least privilege, and limits the impact if an integration account is compromised.

The integration identity should also be configured for API-only access. An API-only profile prevents interactive Salesforce UI access while allowing the external system to authenticate and perform permitted API operations. Current Salesforce architecture also provides the Minimum Access - API Only Integrations profile for the Salesforce Integration user license.

The required object, field, and system permissions should then be granted through appropriately scoped permission sets or permission-set groups. This provides tighter control than assigning the System Administrator profile.

Options C and D violate the principle of least privilege. A System Administrator profile provides substantially more capability than a risk-control integration should require, and changing that profile to API-only would also be inappropriate because it affects users assigned to that profile.

The correct security pattern is therefore a dedicated Integration User with API-only profile access, plus narrowly tailored permission assignments for the objects and API operations required by the external risk-control system.

The custom reporting field belongs on the Contact-Contact Relationship object because Agentforce Financial Services uses that relationship object to represent relationships between two individuals represented as Person Accounts.

A Person Account combines Account and Contact characteristics, but person-to-person relationship modeling occurs at the Contact relationship layer. Salesforce ' s Groups and Households data model states that Contact Contact Relationship relates person accounts to each other. For an inverse relationship such as spouses, two Contact Contact Relationship records can be used to model both directions of the relationship.

Salesforce household examples use Person Accounts for the client, spouse, and child, while Contact Contact Relationship records model client-to-spouse, client-to-child, spouse-to-child, and their inverse relationships. The relationship ' s semantic meaning is further described through associated reciprocal or party-role relationship records.

Therefore, if the financial institution needs a custom attribute specifically about the relationship between two individuals—and subsequently needs that value for reporting—the field should reside on the relationship record itself rather than on either Person Account.

Account Contact Relationship is used primarily for person-to-business or person-to-group membership relationships. Account Account Relationship connects business accounts. Neither accurately represents a direct relationship between two Person Accounts. The appropriate object for relationship-specific reporting data is therefore Contact-Contact Relationship.

Salesforce Insurance Claims Management supports the complete post-loss claims lifecycle, including reserve management, payment processing, and automated adjudication. These processes operate after a covered loss has occurred and are central to evaluating, funding, and settling a claim.

Reserve Management enables adjusters to establish and modify reserves representing expected future claim exposure. The claim workspace consolidates coverages, reserves, loss items, expense items, and other claim financial information so adjusters can assess current and projected financial exposure.

Payment is another core Claims Management process. Adjusters can create payment details and issue payments while Salesforce validates applicable policy limits and updates the corresponding claim-financial records.

Auto Adjudication applies configured rules and policy information to automate claim-processing decisions where appropriate. This reduces manual handling for qualifying claims and supports straight-through processing.

Quoting belongs to the pre-policy acquisition process, while underwriting evaluates risk before coverage is issued. Those functions are part of other insurance lifecycle capabilities rather than Claims Management. Claims Management therefore centers on Reserve Management, Payment, and Auto Adjudication.

Immediately following discovery, the consultant should concentrate on accurately documenting what the business does today and what the users need, rather than prematurely selecting technologies. This requires understanding each relevant persona, documenting business-process flows, and creating visual representations of those flows.

Salesforce process-mapping guidance defines process mapping as a visual representation of business processes showing responsibilities, process steps, inputs, outputs, and how activities connect. A strong process map provides an end-to-end view and establishes the baseline from which future-state improvements can be designed.

Understanding multiple personas is equally important because onboarding often involves customers, bankers, compliance personnel, operations teams, and approvers. Personas clarify user goals, behaviors, responsibilities, pain points, and the tools each participant uses.

Selecting a particular e-signature solution and designing the detailed Agentforce Financial Services component architecture belong to later solution-design activities. Discovery documentation must first establish the validated requirements and current or future process boundaries. Therefore, the correct deliverables are the persona journey, visual process flow, and documented business-process flows.

A Financial Services household can have only one Primary Member. Both Oliver and Macie have Primary Member enabled, which violates this household-modeling rule and causes the configuration error.

Salesforce household guidance states that designating a primary member is optional, but a household can have only one primary member. The primary member commonly represents the principal client or primary relationship within the household. Other members receive roles that describe their relationship to that primary member, such as Spouse or Dependent.

The other settings shown are valid. Multiple members can designate the same household as their Primary Group. Primary Group identifies the household to which a person ' s qualifying records and activities should roll up. A spouse can be a valid relationship role, and multiple household members can have their eligible activities and financial information summarized to the same primary household.

The advisor should therefore retain one individual—typically the principal client—as Primary Member and clear Primary Member for the spouse while leaving the appropriate relationship and Primary Group settings in place.

A successful Agentforce Financial Services implementation begins by understanding the customer ' s current-state processes, documenting the systems and participants involved, and comparing those requirements with Salesforce ' s standard capabilities. The consultant then performs a gap analysis to determine where configuration, integration, process redesign, or justified customization is required.

Gap analysis prevents two common implementation failures: reproducing inefficient legacy processes without improvement and introducing unnecessary customization for capabilities already available in Salesforce. The consultant first identifies business requirements, process stages, handoffs, data sources, integrations, regulatory controls, and user personas. Those requirements are then mapped against Agentforce Financial Services capabilities such as Action Plans, OmniStudio, Financial Accounts, Compliant Data Sharing, Interaction Summaries, household modeling, referrals, and industry-specific service processes.

A generic implementation ignores business-specific requirements. Immediately creating a new Salesforce instance does not establish whether the proposed design addresses the customer ' s processes, and importing legacy information unchanged can preserve obsolete structures and data-quality issues.

The appropriate discovery activity is therefore to map the current environment and conduct a structured current-state-to-Salesforce capability gap analysis before finalizing the future-state design.

The access requirement is determined by the characteristics of the Financial Account records, not by who owns those records. Therefore, the administrator should use a criteria-based Financial Account sharing rule.

Criteria-based sharing rules allow Salesforce to identify records by field values and automatically extend access to a defined user population or public group. A criteria-based sharing rule determines record access by values on the record rather than record ownership.

For this design, the Financial Account data should contain a reliable attribute that identifies employee-only deposit products—for example, an appropriate product type, record type, classification field, or another controlled criterion. The sharing rule can then identify Financial Accounts matching that criterion and extend the required access to the specific customer-service group.

An Account sharing rule would be too broad because the employees themselves must continue to be serviced as ordinary customers. The sensitive information is the special Financial Account, not necessarily the entire customer Account. Similarly, an owner-based Financial Account rule is inappropriate because whether a deposit is an employee product is independent of who owns the Salesforce record.

Salesforce sharing rules create automatic exceptions to restrictive organization-wide defaults while preserving least privilege. A criteria-based Financial Account sharing rule therefore provides the required targeted access without unnecessarily exposing the employee ' s financial products to unrelated users.

The requirement distinguishes between generally accessible interaction metadata and sensitive detailed notes. In Agentforce Financial Services, those detailed notes are represented by Interaction Summaries, making the security configuration for Interaction Summary the primary concern.

Salesforce supports Compliant Data Sharing for Interaction Summary. After CDS is enabled, users can add specific users or groups as Interaction Summary Participants and assign participant roles that define their record-level access. The Manage Participants component supports precisely this controlled-sharing pattern.

Role hierarchy requires particular attention because Interaction Summary records are Private by default, but Grant Access Using Hierarchies is normally enabled. For controlled Interaction Summary access, administrators disable Role Hierarchy-Based Sharing for Interaction Summary and then enable CDS for the Interaction Summary object. This prevents confidential notes from automatically becoming visible to managers merely because they sit above the record owner in the hierarchy.

The Interaction record itself can retain non-sensitive information such as meeting dates and attendees without applying the same restrictive model to the detailed notes. Interaction Summary is specifically designed for structured note-taking with compliant, role-based sharing.

Accordingly, the solution is to use Interaction Summary Participants, enable CDS for Interaction Summaries, and disable hierarchy-based sharing for those Interaction Summary records.

Agentforce Financial Services provides purpose-built objects for modeling customer financial information beyond standard CRM records. Among these are Financial Goal, Financial Holding, and Revenue.

The Financial Goal object represents objectives such as retirement funding, purchasing a home, education planning, or other target financial outcomes. A Financial Holding represents investments or securities held within a financial account. Salesforce references Financial Holding throughout Financial Services capabilities, including financial-detail and portfolio-performance functionality that operates on Financial Account, Financial Account Role, Financial Holding, Financial Goal, and related client records.

The Revenue object is also part of the Financial Services financial model and represents revenue generated from operating a person ' s financial account or through advisory services.

These objects complement other specialized Financial Services records such as Financial Account, Assets and Liabilities, and Identification or Identity Document, allowing institutions to construct a comprehensive view of a client ' s financial position and objectives.

Billing is associated with separate financial or insurance servicing capabilities rather than being one of the client financial-information objects represented by this question. Inheritance likewise is not the corresponding packaged FSC financial object.

Interest Tags are the Agentforce Financial Services capability designed to capture customer interests, preferences, needs, and potential engagement opportunities. They are particularly suitable for wealth-management organizations that want to preserve lifestyle information discovered during advisor conversations and subsequently use it to personalize future interactions.

Salesforce cites personal hobbies such as golf and skiing as examples of Interest Tags that can be applied to Person Account records. Salesforce also supports business-oriented tags such as investment interests, allowing the same framework to capture both personal and professional customer preferences.

Interest Tags can be organized into hierarchical Tag Categories. For example, an administrator could create a Hobbies category containing Golf, Travel, Sailing, and Skiing. This controlled taxonomy provides greater consistency than unstructured notes and makes the captured information suitable for reports and dashboards.

Interest Tags use Salesforce Topics infrastructure underneath, so Topics must be enabled for the applicable objects. However, Topics by itself is the underlying platform capability rather than the Financial Services-specific customer-interest feature. Alerts communicate conditions requiring attention rather than enduring client preferences. For tracking hobbies and supporting personalized wealth-management engagement, Interest Tags are therefore the appropriate feature.

For an insurance implementation, the relevant value outcomes center on customer service, onboarding and document processing, and claims automation. Agentforce Financial Services provides automation and guided-service capabilities that reduce manual handling and enable more consistent customer interactions. Insurance solutions also support self-service and assisted-service experiences, contributing to faster resolution and improved customer experience.

Action Plans directly support onboarding and other document-intensive processes. They standardize repeatable tasks, automate sequencing and deadlines, and can include Document Checklist Items so organizations can track required documents and approval activities consistently. This improves operational control while reducing manual follow-up during onboarding.

For claims, Salesforce Insurance provides first-notice-of-loss processes, OmniScripts, workflow rules, APIs, and automated claims-processing capabilities. Claim rules can initiate coverage and line-item processing, while automation can route work, apply business rules, and reduce manual intervention.

Options A and B primarily describe investment-banking and wealth-management value propositions respectively. Although those capabilities exist within the broader Financial Services portfolio, they do not align with the insurance-company scenario. The expected insurance transformation outcomes are therefore improved service experiences, streamlined onboarding and document workflows, and scalable claims orchestration.

ARC custom nodes can be enhanced with OmniStudio FlexCards so that users see contextual information directly within the relationship graph. Salesforce’s configuration sequence is explicit: open or create an ARC relationship graph, select the required node, navigate to the node ' s Display tab, and select Use FlexCard for this Node. The administrator or developer then identifies the FlexCard that should render the node.

FlexCards are suitable because they provide compact, contextual displays and can expose relevant actions without forcing users to leave the relationship visualization. Developers build and activate the FlexCard in OmniStudio and associate it with the ARC node through the graph configuration. An OmniStudio license is required when FlexCards are used for ARC node customization.

The distinction in the answer choices is important. ARC does not require the developer merely to reference an arbitrary Lightning web component in the node ' s display properties. Similarly, an OmniScript action has a different purpose: it can launch a guided process, but it is not the mechanism used to control the node ' s visual representation. The Use FlexCard option on the node’s Display tab is the supported configuration for customized ARC node presentation.

Custom Field Sets provide a declarative way to tailor the Financial Services interface for different user populations without changing the underlying data model. This is particularly valuable where wealth managers and investment bankers require different information to perform their jobs efficiently.

The Financial Summary component supports field-set-driven configuration. Administrators can define a field set that determines which summary information is presented and configure the Financial Summary component from Lightning App Builder.

Salesforce also provides Financial Services setup procedures for creating custom Account and Financial Account field sets for user-facing Financials experiences. Administrators choose the specific fields that should appear, allowing the presentation layer to be tailored to the operational needs of a persona.

A consultant can therefore create a Wealth Manager-specific field set, associate it with the appropriate Financial Summary or configurable Lightning component, and use persona-specific Lightning-page configuration so that wealth managers receive the information most relevant to their work without forcing the same presentation on investment-banking users.

Creating another Person Account type does not solve a user-interface customization requirement and incorrectly changes the customer data model. The appropriate solution is to use field sets and component configuration to deliver persona-specific experiences while retaining a common underlying financial data model.

The appropriate permission-set license for this Actionable Relationship Center configuration is Financial Services Cloud Standard. ARC is a core Agentforce Financial Services capability that provides an interactive graphical representation of relationships among customers, households, businesses, contacts, and other supported records. It is intended to operate within the Financial Services security and licensing framework rather than as an independent OmniStudio-only feature.

When administrators establish ARC access, the permission set must be associated with an appropriate Financial Services license so that users have entitlement to the underlying Financial Services functionality and components. Users without the required Financial Services permission set or associated license can encounter missing components, unavailable actions, or access failures.

ARC itself can build graphs from standard and custom objects, expose record actions, and display relationship information on Lightning record pages. OmniStudio becomes relevant when administrators enhance ARC nodes with FlexCards, but that does not make OmniStudio the base license for the ARC permission set. The Financial Services Standard licensing model provides access to the standard Financial Services components required by users working with core FSC functionality.

Flow Orchestration structures complex, multi-user business processes by organizing work into Stages and Steps, with Work Items representing the executable assignments created for interactive steps. A Stage groups related work into a logical phase and controls when the orchestration can progress to the next phase. Steps reside within stages and can execute sequentially or concurrently depending on the process design. Salesforce supports interactive, background, and MuleSoft steps.

When an interactive step becomes active, Salesforce creates an Orchestration Work Item and assigns it to the designated user, group, or queue. The assignee completes the associated Screen Flow through the Orchestration Work Guide. Work Items therefore operationalize the human work represented by interactive steps and provide assignment, completion, and tracking information.

Current Salesforce terminology formally describes Stages and Steps as the building blocks of an orchestration, while Work Items are generated during orchestration runtime. The terminology in this question uses the broader architecture in which Steps, Stages, and Work Items constitute the three operational elements being tested. Processes and Blocks are not defined Flow Orchestration structural elements.

The correct Financial Services architecture is to store the confidential transaction in Financial Deal and control access through Compliant Data Sharing, with Financial Deal hierarchy-based sharing disabled.

Financial Deal Management is specifically designed for investment-banking transactions and confidential deal information. It captures deal stage, status, probability, parties, products, interactions, and related information while providing compliant, role-based data sharing for authorized stakeholders.

By default, Financial Deal participates in Salesforce role hierarchy access. However, Agentforce Financial Services provides a dedicated Role Hierarchy-Based Sharing for Financial Deals setting that can be disabled. Disabling this setting prevents users above the deal owner from automatically gaining access to deals owned by or shared with subordinates.

After hierarchy access is disabled, the administrator enables Compliant Data Sharing for Financial Deal. The banking associate can then add the trusted analyst as a Financial Deal Participant and assign an appropriate Participant Role and access level. This produces an explicit, auditable sharing grant limited to the analyst and other specifically authorized participants.

Opportunity is less appropriate because its standard hierarchy-sharing behavior cannot be disabled in the same Financial Deal-specific manner. Restriction Rules are unnecessary for this requirement because Financial Deal already provides the required combination of hierarchy suppression and participant-based CDS.

The administrator should enable Discovery Framework. Within Agentforce Financial Services, Discovery Framework provides the questionnaire and assessment infrastructure used to construct guided customer-information collection processes. OmniScripts are central to this architecture because they provide the interactive user experience through which assessment questions are presented and responses are captured.

Salesforce ' s setup process requires administrators to enable Discovery Framework from Setup and then configure the relevant general settings. Associated settings can include Enhanced Questions, import or export capabilities, and sample templates. The sample templates themselves can contain OmniScripts, Integration Procedures, Data Mappers, and assessment questions.

When an assessment is built with Discovery Framework, Salesforce can generate an OmniScript of type Discovery Framework, which can then be opened in OmniScript Designer and further configured.

Einstein Relationship Insights serves a different analytical purpose and does not enable the OmniScript metadata capability. Lightning Experience provides the overall user interface but is not the feature switch required by this scenario. Likewise, a custom domain can be required for various Salesforce platform capabilities but does not establish the Discovery Framework and OmniScript assessment architecture. Enabling Discovery Framework is therefore the required configuration.

Reciprocal roles define the semantic relationship between two parties—for example, Client and Attorney, Parent and Child, or Spouse and Spouse. The Related Role lookup can only return reciprocal-role records that actually exist and that the current user is permitted to access.

If appropriate reciprocal roles have not been created, the lookup has no suitable role records to return. Salesforce ' s relationship model uses reciprocal or party-role relationship records to describe Contact-Contact and Account-Account relationships, and administrators can define additional role pairs when the standard vocabulary does not satisfy the business requirement.

Record visibility must also permit the user to access the reciprocal-role records. Financial Services relationship components require users to have appropriate access to the Reciprocal Role object and its fields; the preconfigured ARC relationship experience similarly requires read access to the Reciprocal Role data involved in the graph. Appropriate sharing and security configuration therefore matters when role records exist but do not appear to the user.

The issue is not fundamentally resolved by substituting a Member Relationship action or Edit Group operation. Those interfaces support different relationship-management activities. The stated problem is specifically that the Related Role lookup contains no available reciprocal roles, which points to either the absence of the reciprocal-role records or insufficient visibility to those records.