Explanation:

This question tests how to configure an OmniScript Action button on a FlexCard so that it launches a specific OmniScript with required input data. The key is mapping the FlexCard's data JSON (CaseId) to the OmniScript's expected input parameter using the Input Map.

Correct Option:

✔️ A: Set the OmniScript Type and SubType, and configure the Input Map property to pass the ID.
To launch an OmniScript from a FlexCard, the developer must specify the OmniScript's Type and SubType so the system knows which script to run. The Input Map property is then used to map fields from the FlexCard’s data JSON (e.g., CaseId) to the OmniScript’s input parameters (e.g., Case ID). This ensures the OmniScript receives the correct Case ID when launched, without requiring manual entry or context assumptions.

Incorrect Options:

❌ B: Set the Input Map to a Data Mapper Load that will update the Case.
The Input Map on an OmniScript Action is used to pass data from the FlexCard into the OmniScript, not to define a Data Mapper Load. Data Mapper Load actions are configured inside the OmniScript itself to write updates to Salesforce. Using Input Map for this purpose is conceptually incorrect and does not configure how the Case ID is passed.

❌ C: Set the OmniScript Lightning Web Component (LWC) Name and use the Parameter section to pass Case ID as a key/value pair.
This describes how to embed a FlexCard inside an OmniScript or pass data from a FlexCard to an embedded OmniScript, not how to configure an OmniScript Action button on a FlexCard. For launching an OmniScript via a button, you use the OmniScript Type/SubType and Input Map, not LWC Name and Parameter section.

❌ D: Set the OmniScript Type and SubType, and the OmniScript will automatically detect the Case ID from the context.
An OmniScript does not automatically detect record IDs like CaseId just from the FlexCard context. The required input must be explicitly passed using the Input Map configuration. Without mapping, the OmniScript may run with missing or incorrect data, violating best practices for reliable integrations.

🔧 Reference:
→ Salesforce Help: Set Up Card Actions to Update a Flexcard
Confirms that FlexCard actions can be configured to launch external processes and that parameters can be passed to those processes, supporting the use of Input Map to map data from the FlexCard to the OmniScript.

→ Salesforce Help: Update an Omniscript from a Flexcard (Managed Package)
Confirms how to configure actions in a FlexCard to update or launch an OmniScript and how to pass data via Input Parameters (key/value pairs), illustrating the pattern of mapping FlexCard fields to OmniScript inputs.

Explanation

This question tests understanding of how to configure the Attributes section on a parent FlexCard to pass a specific data field to an embedded child FlexCard. The parent's Attribute Value must reference the field using a simple merge field syntax pulled directly from the parent's own data source, since the child will later access it through its own dedicated syntax.

✅ Correct Option

C. {postalcode}
When configuring the Attributes section on the parent FlexCard, the developer enters the attribute name (such as "postalcode") and sets its Value using a merge field from the parent's data source, written as {postalcode}. This passes the field's value from the parent to the child, where it becomes accessible in the child FlexCard.

❌ Incorrect Options

A. {Parent.postalcode}
The Parent merge field syntax is used specifically when referencing data passed from an LWC OmniScript to an embedded FlexCard, not for passing attributes between a parent and child FlexCard. This syntax does not apply to the Attribute Value configuration on a parent FlexCard.

B. {Params.postalcode}
The Params syntax is used inside the child FlexCard to retrieve the value that was passed to it as an attribute. It is not used on the parent FlexCard when setting the Attribute Value, since Params refers to incoming parameters, not outgoing ones.

D. {attr.postalcode}
This is not valid OmniStudio FlexCard merge field syntax. There is no "attr" context variable used for passing attribute values from a parent to a child FlexCard, making this option incorrect.

Reference:
→ Trailhead – Work with Child Flexcards — confirms attribute values on the parent FlexCard use direct merge field syntax such as {fieldname} to pass data to a child FlexCard.

Summary
The requirement involves two distinct operations: retrieving data from Salesforce and sending data to an external system. The solution requires using specialized elements designed for each specific task. One element is optimized for internal Salesforce data queries, while the other is designed for external web service communication.

Correct Option

A. DataRaptor Extract Action
This element is specifically designed to retrieve data from Salesforce objects. A DataRaptor Extract can be configured to query the Asset object and fetch the necessary device details. It provides a declarative, efficient way to access Salesforce data and make it available in the OmniScript's data pipeline for use by subsequent actions.

E. HTTP Action
This element is used to call external REST APIs or web services. The developer can configure the HTTP Action with the external system's endpoint, headers, and the request body. The device details retrieved by the DataRaptor Extract can be used to construct the troubleshooting commands that are sent via this HTTP Action to the external device management system.

Incorrect Option

B. REST API Action
This is not a standard element in OmniStudio. The correct element for making external REST API calls is the HTTP Action.

C. Navigation Action
This element is used to control the user's flow within the OmniScript, such as moving to the next step or a different step set. It does not retrieve data or call external systems.

D. SOQL Action
While SOQL is used for querying data, there is no standalone "SOQL Action" element in OmniStudio. SOQL queries are executed within DataRaptor Extract actions, which are the declarative and recommended way to retrieve Salesforce data in OmniStudio.

Reference
Salesforce OmniStudio Developer Guide: DataRaptor Extract
Salesforce OmniStudio Developer Guide: HTTP Action

Summary
The error indicates that the DataRaptor Load is not receiving the lastName value. The "Send Only Additional Input" checkbox is selected on the DataRaptor action, which means it will ignore the standard data pipeline and only use the key-value pairs defined in its "Additional Input" section. Since the lastName and firstName values from the Set Values element are not mapped there, the DataRaptor receives an empty request, causing the missing field error.

Correct Option

A. SetValuesContactDetails should have been added to Additional input of DataRaptor Post Action in Integration Procedure
This is the correct solution. Because "Send Only Additional Input" is checked, the developer must explicitly map the pipeline data from the SetValuesContactDetails action to the DataRaptor's input parameters in the "Additional Input" section. For example, they would create entries with Key lastName and Value {SetValuesContactDetails:lastName}, and Key firstName and Value {SetValuesContactDetails:firstName}.

Incorrect Option

B. The Set values Action Keys should include the DataRaptor Post Action element name path, e.g LoadContactDetails, lastname
This is not a valid configuration. The "Keys" in a Set Values element are the names of the variables it creates in the pipeline (e.g., lastName). They do not need to include the name of subsequent actions. The issue is not with the Set Values configuration but with how its output is passed to the next action.

C. The DataRaptor Post Action in the integration procedure should have been executed before the Set Values Action
The action order in the exhibit is correct. The Set Values action must execute first to create the lastName and firstName variables in the pipeline before the DataRaptor can use them. Reversing the order would mean the DataRaptor runs before the values are set, which would also cause an error.

D. The valid field names should be added in the Domain object field in the DataRaptor
The DataRaptor's configuration is correct, as proven by the fact that it "works as expected when previewed." The Domain Object Field mappings (firstName to FirstName, lastName to LastName) are already properly set. The problem is not within the DataRaptor's internal setup but in the Integration Procedure's data piping to it.

Reference
Salesforce OmniStudio Developer Guide: DataRaptor Interface Types

Explanation:

This question tests the understanding of Data Mapper configuration tabs and where to define outputs for formula results. In a Data Mapper, the Output tab is where developers specify the structure of the final JSON output, including fields derived from formulas, to ensure they are available in the resulting JSON.

✔️ Correct Option:

Option D:
The Output tab defines the final JSON structure that the Data Mapper produces. After creating a formula, you must map its result to an output field on this tab to include it in the Data Mapper's JSON output. This makes the combined identifier available for subsequent actions or components.

❌ Incorrect options:

Option A:
The Transform tab is used for mapping input JSON to intermediate structures or performing transformations, not for defining the final output fields of a formula result.

Option B:
The Mapping tab is used for mapping input fields to Salesforce fields or target objects in a Data Mapper Load, not for defining formula outputs in the JSON.

Option C:
The Extract tab is used for defining query parameters and filters when retrieving data, not for mapping formula results to output fields.

🔧 Reference:
→ Salesforce Help: Data Mapper Overview - Explains the purpose of the Output tab for defining JSON output structure.

→ Trailhead: Data Mapper Transform - Covers configuring output fields in the Output tab for formula results.