Salesforce OmniStudio-Developer Salesforce Certified OmniStudio Developer (SP25) Exam Practice Test

 According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with three elements: Step, Block, and Telephone. The Step element is an empty object, the Block element is an object with two properties: Text and Telephone, and the Telephone element is a string. Therefore, the JSON code that correctly represents the step in the OmniScript Structure panel shown is option C, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.

 Checking the Send Only Additional Input checkbox allows the Remote Action element to send only the key/value pairs specified in Additional input to the Apex method. The Additional input should have the same keys as the method parameters, and the values should be set to {{InputData.node}} for each node. For example, AccountId: {{InputData.AccountId}} and ProductId: {{InputData.Details.Products}}.

According to the OmniScript Action Elements page, a DataRaptor Extract Action can be used to “get data from one or more Salesforce records” and an HTTP Action can be used to “get, save, or delete data through a web application programming interface (API)”. 

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. 

 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.

OmniStudio best practices dictate that versioning is used when enhancements are required within the same logical flow, while cloning is preferred when the new flow is functionally different and used separately.

B. The new Integration Procedure will be used independently – Correct. Cloning creates an entirely new IP definition, ideal for building a similar but standalone process, rather than altering behavior for an existing process.

Incorrect Options:

A. Using a Cache Block is unrelated to cloning vs. versioning.

C. Replacing stub data does not require cloning; could be done in a version.

D. Chainability does not influence whether you should clone or version.

 The merge code syntax for passing data from a DataRaptor Extract Action to an HTTP Action is %DataRaptorName: NodeName%. In this case, it is %DRReadCase: CaseNumber%.

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

The correct syntax for merge codes in OmniScript is %%sNodeName%%, where NodeName is the name of the JSON node in the data source. The other options are either missing the s or using incorrect symbols.

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.

From OmniStudio Best Practices for Modular Script Design, OmniScript Actions are the preferred mechanism to invoke another OmniScript within a parent OmniScript. This approach enables reusability and modularization, especially when a function (like updating billing information) is common across many interactions.

A. OmniScript Action – This is the correct and standard method for embedding or launching one OmniScript from another. It allows developers to reuse common scripts without duplicating logic.

Incorrect Options:

B. Custom Action requires custom Apex or LWC development, which is unnecessary for this use case.

C. Lightning Action is typically used to invoke OmniScripts from Lightning pages, not within OmniScripts themselves.

The correct answer is Option B, which shows a FlexCard with a header, a body, and a footer. The header contains the title and the icon of the FlexCard. The body contains a Data table element that displays the records from the parent FlexCard. The footer contains a navigation Action that invokes an OmniScript. Option A is incorrect because it shows a FlexCard with only a header and a body, and no footer.

 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

A DataRaptor Turbo Extract is a simplified version of a DataRaptor Extract that can retrieve data from a single object without changing the structure of the output data. It is easier to configure because it does not require defining extraction steps or JSON paths. It also has better performance at runtime because it uses a native query engine instead of a custom one

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.

Versioning a FlexCard allows the developer to make changes to the FlexCard without affecting the existing instances of the FlexCard. The developer can choose to update all instances of the FlexCard with the new version or keep them as they are. This is useful when the changes are minor and do not affect the functionality or layout of the FlexCard. Cloning a FlexCard creates a copy of the FlexCard with a new name and ID. The developer can make changes to the cloned FlexCard without affecting the original FlexCard. This is useful when the changes are major and require a different configuration or design of the FlexCard1. In this case, since all instances of the FlexCard must be updated with the changes, versioning is the best course of action.

To retrieve (read) data from Salesforce objects:

A. Data Mapper Extract Action – Correct. A DataRaptor Extract is specifically used to retrieve data from Salesforce, based on input parameters or context.

C. Lookup Input Element – Correct. This is used within OmniScripts to look up a record by matching input data, essentially performing a read operation.

Incorrect Options:

B. DataRaptor Post is not a valid DataRaptor type.

D. DataRaptor Load Action is used for writing/updating data, not retrieving it.

 According to the FlexCard Designer Overview page, another possible cause of a field showing only the label is that “the field is null on the Salesforce record”.

the calculation procedure version that would execute on 2/15/2020 at 12:00 PM is the one that has the start date time and end date time that include that date and time, and also has the highest priority among the enabled versions. In this case, only version number 4 meets these criteria, as it has a start date time of 2/1/2020 12:00 AM, an end date time of 4/1/2020 12:00 AM, a priority of 1, and is enabled. The other versions either have a different start or end date time, a lower priority, or are not enabled.

The Set Values element with a ContextId key/value pair was used for testing purposes and is not needed for production. The developer should delete or deactivate the Set Values element before moving the OmniScript to a production org.

The Invoke Mode Fire and Forget feature enables the OmniScript to invoke the Integration Procedure without waiting for a response. This is useful when the response is not needed for the user to proceed

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

The correct syntax for the Send JSON Path is ActionName: BlockName, where ActionName is the name of the action element and BlockName is the name of the block element that contains the output data. The other options are either missing the colon or using incorrect names.

A Text Block element allows the developer to display read-only text in a table format, using merge codes to dynamically include data from the data JSON. A Rich Text Area element is used to display formatted text with images and links. A Text Area element is used to display editable text in a single line or multiple lines. An Edit Block element is used to display editable fields in a form layout.

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

According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with six elements: ContactName, ContactPhone, ContactEmail, CaseNumber, CaseSubject, and CaseStatus. The DRGetContactDetails action is a DataRaptor Extract action that retrieves data from the Contact and Case objects in Salesforce. The BlkCases element is a Repeat Block that displays a list of cases related to the contact. Therefore, the JSON from the DRGetContactDetails action that would display all six values correctly shown is option A, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown.

An OmniScript and a Child FlexCard are both valid components that can be embedded in a flyout. An Integration Procedure and a DataRaptor are not components, but actions that can be performed within an OmniScript or a FlexCard.

The PREVIEW tab in OmniScript allows the developer to test the DataRaptor Extract by providing a record ID and viewing the output data. This is a quick and easy way to troubleshoot whether the DataRaptor Extract is retrieving data correctly.

According to the Integration Procedure Actions page, a Calculation Action can be used to “call a Calculation Procedure that performs calculations on input data” and a Matrix Action can be used to “call a Calculation Matrix that performs calculations on input data”.