A Data Mapper Transform is the correct tool because the requirement is to restructure incoming JSON before a FlexCard displays it. The source data already comes from a REST API, so the developer does not need a Data Mapper Extract, which retrieves Salesforce data, or a Data Mapper Load, which writes data to Salesforce. An Integration Procedure can orchestrate the REST call and invoke the transform, but the actual no-code restructuring of JSON field names and paths is performed by a Data Mapper Transform. Salesforce documentation states that Data Mapper Transform mappings use input paths and output paths to reshape data, including JSON structures, which directly matches this scenario.

================

A permission set license is an entitlement layer. The OmniStudio User PSL makes the user eligible to access OmniStudio functionality and related OmniStudio objects. It does not by itself grant every object, field, or administrator permission needed to build or manage assets. Those permissions still come from assigned permission sets such as OmniStudio User or OmniStudio Admin, plus object and field-level security. Option A is wrong because package installation and administration require separate administrative permissions. Option B is too broad and refers to general Salesforce platform access, not OmniStudio entitlement. Option C incorrectly treats the PSL as the permission set itself. The PSL’s primary purpose is licensing entitlement to OmniStudio features and custom objects.

================

 According to the OmniStudio Developer Guide, “If multiple states have true conditions, the state that is closest to the top of the FlexCard canvas displays.” Therefore, the correct answer is A.

According to the Integration Procedure Actions page, “To pass data from a Set Values action to a DataRaptor action, add the Set Values action name to the Additional Input field of the DataRaptor action.” 

In OmniStudio, the Invoke Mode: Fire and Forget setting allows an OmniScript to call an Integration Procedure asynchronously, meaning it does not wait for the response to complete before continuing user interaction.

C. Invoke Mode Fire and Forget – This is the correct setting. It’s designed specifically for use cases where the user experience should not be blocked by backend processing.

Incorrect Options:

A. Use Future is not a valid OmniScript configuration option.

B. Invoke Mode Non-Blocking is not an official setting in OmniStudio terminology.

D. Toast Completion is a UI notification setting and does not impact execution behavior.

OmniStudio Developer Guide → Integration Procedure Actions in OmniScripts

The AccountId is not the issue because the Debug Log already shows that the Data Mapper Extract retrieved data successfully. The failure is at the response-return stage of the Integration Procedure. In OmniStudio, a Response Action is used to end the Integration Procedure and return data to the caller. If the Data Mapper action runs but no Response Action is configured, the internal debug data can exist while the external response remains empty. Option A is weaker because the core requirement is not only adding data to an internal response JSON property; the Integration Procedure needs a Response Action to send the final output. Option C adds unnecessary and inaccurate wording about Send JSON Path. The clean verified cause is that no Response Action was added.

================

The Repeatable Mode property on the data table elements allows the developer to display multiple records in a single data table. The Repeat Records feature on the FlexCard Setup tab is used to display multiple FlexCards for each record in a data source. The Record Looping feature on the data table elements is used to iterate over a list of records and perform actions on each record. The Overwrite Target for all Null input checkbox on the Account id field is used to overwrite the existing value in the target object with null if the input value is null.

A DataRaptor Transform can be used to transform data from one format to another, such as JSON, XML, or CSV. The developer can specify the input and output paths for each field in the Transform tab. The developer can also use formulas to manipulate data in the Formula tab1. To transform contact data into a JSON array, the developer can use either of these methods:

Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab. This will create a list of contact objects from the input JSON and output it as a JSON array.

Set the Input JSON Path as Contact, the Output JSON Path as Contact, and the Output Data Type as List. This will output each contact object as an element of a JSON array.

The best practice for configuring the Input JSON for a DataRaptor Load is to copy the Input JSON from the OmniScript {Data} modal. This ensures that the Input JSON matches the data structure and format of the OmniScript data. The DataRaptor Action Debug node may not have the same data as the OmniScript data, and building the Input JSON node by node in an editor or in the DataRaptor Designer may introduce errors or inconsistencies.

 An OS Action is the most efficient way to configure the action that invokes the OmniScript, as it allows the developer to reuse the same OmniScript across multiple FlexCards without creating separate actions for each one. A Custom Action is used to invoke a custom Apex class or Lightning web component. An OmniStudio Action is used to invoke an Integration Procedure or a Calculation Procedure. A Lightning Action is used to invoke a Lightning component or a Visualforce page.