Free Practice Questions for Salesforce OmniStudio-Developer Exam

When an OmniScript receives incomplete data from an Integration Procedure, the issue is typically in Response JSON path mapping or naming mismatches.

A. The missing data is trimmed in the Integration Procedure Action Response JSON Path – If the Response JSON Path only points to part of the structure, any nested or unrelated values are excluded from the output.

B. The element name for the missing data does not match the JSON node key in the Integration Procedure Response – OmniScript expects a matching node name to bind the data to UI elements. If the key doesn’t match, that field will appear blank.

Incorrect Options:

C. Preview Input Parameters are only for testing in the Integration Procedure editor; they don’t affect runtime execution.

D. Even if the JSON from the Integration Procedure Action is different from the original IP input, it would cause a failure or unexpected data, not necessarily missing specific values.

Salesforce OmniStudio → Integration Procedures → JSON Path and Data Binding

The requirement is only to show or hide a section based on a value already present in the OmniScript data JSON. That is exactly what Conditional View is designed for. It evaluates client-side conditions and controls whether a step, block, or element is displayed, editable, or required. Using an Integration Procedure would add unnecessary server-side processing because the required VIP value is already available in the OmniScript. A Data Mapper Transform is also unnecessary because there is no structural transformation requirement. Creating a new version may be part of the deployment process, but it is not the functional configuration that controls visibility. The best implementation is to place the special offers section in the script and configure Conditional View logic against the VIP member value.

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

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.” 

The Id Field for Actions in the FlexCard specifies which field from the FlexCard data source will be used as the record ID for the OmniScript. If this field is blank, the OmniScript will not receive any record ID and will not be able to retrieve any Salesforce data. In the DataRaptor Extract Action, the Input Parameters Filter Value determines how to filter the data based on the record ID. If this value is misspelled, the DataRaptor Extract will not be able to match the record ID and will not return any data.

To launch an OmniScript from a FlexCard, the Action element must identify the target OmniScript by its Type, SubType, and related configuration. Because the OmniScript requires the Case ID, the developer must explicitly pass the FlexCard data value, such as CaseId, through the action’s input mapping. Option D is unsafe because the OmniScript does not automatically know which Case ID to use unless the value is passed through context or input parameters. Option B confuses launching the OmniScript with saving Case data; the Data Mapper Load would be used later inside the OmniScript or Integration Procedure. Option C describes a more custom LWC-style configuration, not the standard OmniScript Action setup from a FlexCard.

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

 In a calculation procedure, the output of a calculation step must be included in the calculation output in order to be used in an aggregation step. The calculation output defines the variables that are available for aggregation

Cloning an Integration Procedure creates a copy of it that can be modified and used independently from the original one. This is useful when the new Integration Procedure has a different purpose or functionality than the original one

A Try-Catch Block is the correct element because the requirement is controlled error handling. The Data Mapper Load can fail because of a validation rule, but the Integration Procedure must keep running and return a user-friendly error message rather than immediately terminating. A Group element organizes or conditionally executes steps, but it does not provide exception handling by itself. A Set Values element can prepare the friendly message after the error is caught, but it cannot catch the failure. A Response Action returns the final payload, but it should not wrap the risky operation. Salesforce Integration Procedure guidance specifically identifies Try-Catch Blocks as the mechanism for handling errors inside Integration Procedures.

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

The correct approach is to use the responsive sizing properties available in the element Display configuration, such as Extra Small, Small, Medium, and Large. These settings align the element with the responsive grid model instead of forcing custom widths. Newport Design System styling is intended to provide consistent visual behavior across OmniScripts and FlexCards, so using framework-supported sizing is cleaner than hard-coding CSS. Option B can add utility classes, but it is not the primary standard grid-sizing property for the input element. Option D is weaker because custom CSS makes the layout harder to maintain. Option A is unrelated because Repeat CSS is not the standard way to control horizontal grid width.

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

 Using the LIMIT filter on the Extract definition allows the developer to specify the maximum number of results to return from the DataRaptor Extract. Defining a formula with the Filter function is used to filter the results based on a condition. Using a Custom Output Type when creating the DataRaptor is used to define the structure of the output data. Setting the Limit Property on the Action that calls the DataRaptor Extract has no effect on limiting the results.