Certified OmniStudio DeveloperDemo

Integration Procedure Preview uses an action’s ElementNameDebug node to show the input data provided to that action. The Remote Action’s ordinary element-name node contains its returned result, so the input for FetchCart is shown in FetchCartDebug.

A FlexCard field must reference the JSON property returned by its data source. If the field name in the FlexCard state does not match the DataRaptor Extract’s Output JSON Path name, no value is available for that field, although its label still displays. Salesforce documents that a Data Mapper Extract defines the returned property through its Output JSON Path.

A Calculation Matrix matches the supplied input to a matrix row and returns the output from that matching row. The exact ProductCode HRA320 matches the row with BasePrice 12.99; HRA320B is a separate value. Salesforce documents that calculation matrices use input columns to match inputs and return the corresponding output.

An Integration Procedure version is a revision of the same procedure. Only one version can be active at a time, and activating a version deactivates the other versions, so versioning is used when the new revision is meant to replace the existing one.

The Set Element to Required if True conditional-view type makes an element required when its configured condition evaluates to true. Configure the condition to test whether the Non-Disclosure Agreement checkbox is true; checkbox conditions use true or false values. Salesforce Help: Conditionally Display OmniScript Elements

OmniScript merge fields are enclosed in single percent signs and use colon-separated JSON paths. For a value in a repeatable array of objects, |n selects the applicable array entry, so %Details:Customer|n:ID% resolves that entry’s ID value.

Integration Procedure merge fields enclose the full JSON path in percent signs, using a colon for nested nodes. A CaseNumber returned under the DRReadCase action is referenced as %DRReadCase:CaseNumber%.

A DataRaptor Extract Action retrieves Salesforce data for use in an OmniScript and supports extracting and mapping multiple fields, including complex mappings. Salesforce Help: OmniScript Data Mapper Action Elements

An external API call can fail when its endpoint is not allowlisted. The Integration Procedure Action must also send JSON that matches the Integration Procedure’s expected input structure so that its actions can use the required values and return data. Integration Procedure preview parameters are used only for preview testing; they do not determine the input sent by an OmniScript at runtime.

A DataRaptor Transform performs intermediate data transformations and can convert JSON input to XML output. Configure the Transform with JSON input and XML output, and define the required XML structure and mappings so the transformed payload can be passed to the external web service.

OmniStudio evaluates FlexCard states from top to bottom on the FlexCard canvas and displays the first state whose conditions evaluate to true. When more than one state is true, the highest sequenced qualifying state takes precedence.

A DataRaptor Load maps JSON nodes to Salesforce object fields, so its Input JSON should reflect the data structure produced by the OmniScript. Copying the OmniScript Data JSON into the Input JSON preserves the actual node paths and supports accurate mappings.

Integration Procedure action properties support formulas in Additional Input and Additional Output value fields. CONCAT and DATEDIFF are supported OmniStudio functions, so they can be evaluated in a Response Action’s Additional Input value and a Remote Action’s Additional Output value.

A FlexCard must have the Community Page target enabled in Publish Options to be available as a component on an Experience Builder (Community) page. The target value is CommunityPage.

A FlexCard flyout can display additional information by embedding an OmniScript or a child FlexCard. DataRaptors and Integration Procedures provide data transformation and orchestration capabilities rather than flyout UI components.

A DataRaptor Transform maps the OmniScript JSON input to fields in a target PDF, thereby populating the PDF with OmniScript data.

Attributes passed from a parent FlexCard are referenced in a child FlexCard with the Parent context variable using the form {Parent.attributeName}. Therefore, a passed attribute named postalcode is accessed as {Parent.postalcode}.

The Lookup element queries Salesforce sObject data and can return configured record field values for use in an OmniScript.

DataRaptor Turbo Extract is optimized for simple retrieval from a single Salesforce object type and does not provide output mappings for restructuring the response. It offers simpler configuration and better runtime performance than a standard Extract when complex mappings are unnecessary.

A linked mapping is used when a DataRaptor Load must pass data created in a previous mapping step—here, the newly created Contact’s ID—into a field on a related record, such as the Account’s Primary Contact lookup. Salesforce describes linked mappings as mapping data created in previous mapping steps to new fields.

The DataRaptor Extract Action’s Add Response To Response JSON setting controls whether its extracted output is added to the Integration Procedure response JSON. If it is not enabled, the extract can succeed and appear in the debug log while the preview response remains empty. A Response Action returns the procedure’s configured response to its caller, while the DataRaptor action itself supplies the data that must be included in that response. Salesforce Help: Integration Procedure Actions

ContextId is a reserved OmniScript key that is intended to receive the record ID from the URL; it should not be assigned within an OmniScript. A Set Values element used only to set a test ContextId must therefore be deleted or deactivated before production deployment.

A DataRaptor Extract retrieves records by applying configured input and filter values. Supplying a key/value test input directly to the DataRaptor validates that its query receives the required parameter and can return matching data before troubleshooting the consuming FlexCard, OmniScript, or console page.

A DataRaptor Extract Action retrieves data from Salesforce objects. A Remote Action invokes Apex from an OmniScript; Apex can perform the required integration or callout to an external AWS Order Management system.