The most direct and appropriate method to meet the requirement is to place the contact information inside a Block element and enable its "Collapsible" property. The Block element acts as a container for other elements on the FlexCard. By setting its Collapsible property to true, the platform automatically adds a control (e.g., a chevron icon and label) that allows the end-user to expand and collapse the block's content on demand. This precisely fulfills the requirement for the contact information to be visible only as needed by the user, while the account information remains static.

1. Salesforce OmniStudio Documentation

FlexCard Designer: The official documentation details the properties of FlexCard elements. The "Block" element is described as a container that has a "Collapsible" checkbox property. When selected

the block can be collapsed and expanded by the user. This is the standard

built-in feature for this use case. (Reference: OmniStudio Developer Guide

Section: "FlexCard Element Reference"

Subsection: "Block Element Properties").

2. Salesforce Trailhead

OmniStudio FlexCards: The "Build a FlexCard" module demonstrates the use of various elements. It shows that to group elements and make them collapsible

you should use a Block element and check the "Collapsible" property in the properties pane. (Reference: Trailhead

Module: "OmniStudio FlexCards"

Unit: "Add and Configure Elements on a FlexCard").

The Set Values element with a hardcoded ContextId is a standard practice for testing an OmniScript in isolation, simulating its launch from a specific record page. However, when moved to production, the OmniScript is expected to receive the ContextId dynamically from the record page it is launched from. Leaving the testing-specific Set Values element active would override the dynamic ContextId, forcing the OmniScript to always run against the hardcoded test record's ID. Therefore, the developer must either delete this element or deactivate it to ensure the OmniScript functions correctly in the production environment.

1. Salesforce Industries OmniScript Developer Guide: The guide emphasizes that for an OmniScript to be context-aware (e.g.

when placed on a Lightning Record Page)

it relies on the ContextId being passed in the URL. A Set Values element that defines ContextId will override this dynamic value. The guide's best practices for deployment state that test-specific configurations must be removed. (Refer to sections on "Passing Data to an OmniScript" and "Preparing OmniScripts for Deployment").

2. Salesforce Help & Training - Pass the ContextId to an OmniScript: "To pass a Salesforce object's record Id to an OmniScript

the ContextId is passed as a URL parameter... When you hard-code a ContextId in a Set Values element for testing

you must remove it before you deploy the OmniScript to production." (This concept is detailed in the "Test an OmniScript" section of the documentation).

3. Salesforce Help & Training - OmniScript Set Values Element: This documentation describes the function of the Set Values element for setting static or dynamic values. It implicitly supports the understanding that a static

hardcoded value used for testing is not suitable for a dynamic production environment where the context changes.

The Formula element is the most appropriate choice because it is specifically designed to perform real-time, client-side calculations within an OmniScript step. It can use functions like CONTIF to process data from other input elements in the same step and display the result immediately without requiring a server call. This directly fulfills the requirement for the output to be displayed to the user instantly as they enter data. Using a Formula element is the best practice for this type of immediate UI reactivity.

1. Salesforce OmniStudio Documentation

"OmniScript Formula Element": "Formulas perform calculations in real time on the client side. The result of a formula's expression displays in a read-only field. For example

a formula can calculate the sum of two Number elements and update the sum as the user changes the value of either Number element." This directly supports the use of a Formula element for immediate

real-time display.

2. Salesforce OmniStudio Documentation

"OmniScript Functions": The documentation lists CONTIF as a conditional function available for use within OmniScript elements

including the Formula element

confirming its applicability.

3. Salesforce OmniStudio Documentation

"OmniScript Calculation Action": "A Calculation Action element calls a Calculation Procedure or Calculation Matrix to run complex calculations on the server." This highlights its server-side nature

making it incorrect for the client-side requirement.

An Integration Procedure Action is the most appropriate element as it is designed to execute multiple server-side operations in a single transaction from an OmniScript. The developer can configure the Integration Procedure to first use a DataRaptor Post Action to save data to Salesforce and then use an HTTP Action to send data to the external AWS Order Management system. This allows the OmniScript to trigger both distinct data-saving operations through a single, efficient, server-side call, which is ideal for complex transactions involving multiple systems.

1. Salesforce Help

OmniStudio Integration Procedures: "Integration Procedures can read data from and write data to Salesforce and external systems... For example

an Integration Procedure can get data from an external system using an HTTP action

transform it using a DataRaptor Transform action

and save it to Salesforce using a DataRaptor Load action." This demonstrates the capability of an IP to orchestrate actions involving both Salesforce (via DataRaptors) and external systems (via HTTP Actions).

2. Salesforce Help

OmniScript Actions: "Integration Procedure Action: Runs a server-side Integration Procedure without navigating from the current OmniScript step." This confirms it is the OmniScript element used to invoke the multi-step server process.

3. Salesforce Help

DataRaptor Post Action: "A DataRaptor Post Action saves data that the user enters in an OmniScript to Salesforce." This source explicitly limits its function to saving data to Salesforce.