OmniStudio-Developer Salesforce Certified OmniStudio Developer (SP25) Questions and Answers

 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

 The Send JSON Path syntax for accessing an element from an Integration Procedure structure is BlockName.ElementName. In this case, the BlockName is BlockX and the ElementName is ActionZ. The colon (:) is used to separate the input and output parameters, not the block and element names. The order of the block and element names should follow the hierarchy of the structure, from top to bottom. The Additional input parameter is not needed in this case, as it is already included in the Send JSON Path.

 Setting the element to require if true allows the developer to configure a Disclosure element to require user input only if a condition is met. In this case, the condition is that the user already checked a Non-Disclosure Agreement Checkbox. The other options are either incorrect or irrelevant for this requirement.

The correct syntax for merge codes in Integration Procedure is {(NodeName)}, where NodeName is the name of the JSON node in the data source. The other options are either missing the parentheses or using incorrect symbols.

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 LWC PubSub Message flag in the Set Values action of the parent OmniScript enables the parent OmniScript to send data to the embedded OmniScript using a custom event. If this flag is not set, the data will not be passed to the embedded OmniScript.

A DataRaptor Transform can simplify nested data by transforming it into a flat structure. The developer can use JSON paths to map the input data to the output data and define the output structure.

According to the OmniStudio DataRaptor Extract documentation, if a developer wants to limit the number of records returned, the best way is to set the " Limit " property on the element or action that is calling the DataRaptor, such as in an Integration Procedure or OmniScript Action.

A. Set the Limit property on the action that calls the Data Mapper Extract – This is the correct method. The calling context (e.g., OmniScript Action or Integration Procedure) includes a property for setting the limit on query results, which is a recommended and clean method to ensure only one record is retrieved.

Incorrect Options:

B. There is no " LIMIT " clause within the DataRaptor Extract definition UI or JSON definition itself.

C. Custom Output Type controls the structure, not the quantity of output.

D. The Filter function applies conditional logic, not record count.

Salesforce OmniStudio Developer Guide → DataRaptor Extract Configuration

A formula element allows the developer to define formulas using functions and operators to manipulate data in an OmniScript. The output of the formula element can be displayed to the user immediately in the current step using a display element. The CONTIF function counts how many times a value appears in a list1. A Calculation Action element executes a calculation procedure and returns the output as a JSON object. A Set Values element assigns values to variables or fields in an OmniScript. A Range element defines a range of values for a variable or field in an OmniScript1. Based on best practice, a formula element is the most suitable element to use the CONTIF function in this scenario.

The correct answer is D. Data Mapper Turbo Extract, based on best practices in the official OmniStudio documentation.

From the OmniStudio Developer Guide → DataRaptors → Turbo Extract:

DataRaptor Turbo Extract is a lightweight, high-performance extract designed specifically for retrieving data from a single Salesforce object, where no data transformation or complex joins are required.

It is recommended over DataRaptor Extract for performance reasons when only one object and minimal transformation is needed.

Why not the others?

A. DataRaptor Load is used for writing data to Salesforce, not retrieving.

B. DataRaptor Transform is used when you need to transform data, not simply extract it.

C. DataRaptor Extract can be used, but Turbo Extract is preferred for the use case of single object, no transformation — per best practices.

Salesforce OmniStudio Developer Guide → DataRaptor Turbo Extract Best Practices

OmniStudio Certification Study Guide → " When to use Turbo Extract "

In OmniStudio, the Edit Block element is purpose-built for allowing users to dynamically add, edit, or delete rows of related data, such as dependents under a policy. To save these changes, Remote Actions (typically backed by Apex or API) are used to process each record operation (Create/Update/Delete).

A. Use an Edit Block element configured with Remote Actions – Correct. This is the recommended and most scalable way to support CRUD operations in OmniScripts for collections (e.g., dependents). The Edit Block provides UI-level support, while Remote Actions handle back-end interaction with Salesforce or external systems.

Incorrect Options:

B. Text Block is for display purposes and cannot manage data input or backend actions.

C. Input Block elements do not support row-level add/edit/delete functionality as Edit Blocks do.

D. SOQL is a read-only query language and cannot be used to update or delete records directly within an OmniScript.

Salesforce OmniStudio Guide → OmniScript Edit Block Element

OmniStudio Best Practices → CRUD Operations in OmniScripts

According to the Integration Procedure Actions page, a Remote Action can use a function in an Additional Output value field or in a Remote Options value field. According to the Response Actions page, a Response Action can use a function in an Additional Input value field.

In Expression Sets, for any intermediate step (like Calculation) to be referenced in subsequent steps, such as Aggregation, the value must be made available via Output.

B. It must be included in the output – Correct. Each step has an " Include in Output " checkbox. If not checked, its result is not accessible to following steps like Aggregation or Sub Expression.

Incorrect Options:

A. Constants are global but do not affect step dependency.

C. It does not have to be a Calculation Step; any previous step’s output can be used if exposed.

Salesforce OmniStudio → Expression Sets - Step Configuration

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 Params node contains the data that is passed from the parent FlexCard to the child FlexCard. The developer should use {Params.postalcode} to refer to the contact’s postal code in the child FlexCard.

 Setting the collapsible property on the block element allows the user to expand or collapse the block as needed. Using a Data table element is not suitable for displaying contact information. Setting the class’’ collapsible’’ on the block element has no effect. Using a conditional FlexCard State requires a condition to be met, not a user choice.

 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.

 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.

According to the DataRaptor Transform Overview page, a DataRaptor Transform can be used to “pre-populate data in PDFs used by OmniScripts”.

Functions like CONCAT, DATEDIFF, and IF are supported in value fields where expressions can be parsed at runtime.

B. In a Set Values Action in a Value field – Correct. The Set Values element supports expression functions in its Value field, allowing for real-time evaluation during IP execution.

C. In a Data Mapper Action in an Input Parameters value field – Correct. Input Parameters to DataRaptors in Integration Procedures can use expression logic to dynamically compute and pass values.

Incorrect Options:

A. Output JSON Path in DataRaptor is for structural mapping, not function execution.

D. Remote Action Output fields typically receive data, not compute it.

Salesforce OmniStudio Developer Guide → Expression Functions in Integration Procedures

 Deleting a row in Version 3 will only affect that version, not any previous or future versions. The row that contains the Code CA-SF will remain in Versions 1 and 2, as well as any versions created after Version 3. The other options are incorrect because they imply that deleting a row in one version will affect other versions as well.

OmniStudio does not natively support direct JSON-to-XML transformation using DataRaptors. When a transformation to specific XML formats is needed for integration with external web services, it is recommended to use Remote Actions that invoke custom Apex classes.

A. Use a Remote Action that calls the XMLStreamWriter class – Correct. The XMLStreamWriter Apex class provides precise control over XML structure and is the Salesforce-recommended way to programmatically generate XML from data within a Remote Action step in an Integration Procedure.

Incorrect Options:

B. The XML checkbox in DataRaptor does not convert JSON to XML; it defines output data format for display or API serialization.

C. XMLStreamReader is used for parsing XML, not for generating it.

D. DataRaptor Transforms only manipulate JSON structure; they do not support converting JSON into XML format.

Salesforce Developer Guide → Apex XMLStreamWriter Class

OmniStudio Integration Procedures → Using Remote Actions with Custom Apex

 The correct syntax for passing all of the parent FlexCard’s records to a child FlexCard is {Records}, which represents an array of records. The other options are incorrect because they either use an invalid syntax or refer to a single record instead of an array of records.

The Add Response To Response JSON property on the DataRaptor Action indicates that the output of the DataRaptor should be added to the response JSON of the Integration Procedure. If this property is not set to true, the response will be empty even if the DataRaptor extracts data successfully. 

A DataRaptor Load Action can be used to retrieve data from a Salesforce object by specifying the object name, fields, and filter criteria. A Lookup Input Element can be used to retrieve data from a Salesforce object by allowing the user to search for a record using a lookup field

The Target property in publishing Options determines where the FlexCard will be displayed. Setting it to the Community page will make the FlexCard available in the community

According to the OmniStudio Developer Guide, “DataRaptor Transform actions can convert JSON to XML and vice versa.” Therefore, the correct answer is C.