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

According to the OmniStudio Developer Guide, “To return a response from an Integration Procedure, add a Response action as the last action in your Integration Procedure.” Therefore, the correct answer is C.

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

The Additional Input property allows the developer to specify additional input parameters to be sent to the Integration Procedure element. The input parameters can be specified as a JSON object or as a list of key-value pairs. If the developer checked Send Only Additional Input, then only the input parameters specified in Additional Input are sent, and the SEND/RESPONSE TRANSFORMATIONS are ignored. Therefore, the developer needs to specify the same input parameters as in the SEND/RESPONSE TRANSFORMATIONS in Additional Input. Option C shows how to do this using a JSON object with two properties: “DBExtractAction:Account” and “DBExtractAction:SecondaryAccount”. The values of these properties are the same as in the SEND/RESPONSE TRANSFORMATIONS. 

The Upsert Key checkbox indicates that the field is used as a key for upserting records. The Is Required for Upsert checkbox indicates that the field is mandatory for upserting records. The developer needs to check both checkboxes on the Account Id field to update the Account status only if the Account record already exists. Otherwise, a new account will be created.

 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.

According to the Salesforce OmniStudio DataRaptor documentation, specifically under DataRaptor Load Best Practices and Common Issues:

A. “The Input JSON paths in the Data Mapper Load do not match the JSON sent from the OmniScript.”This is a common configuration issue. If the paths between the OmniScript's structure and the DataRaptor Load mapping are mismatched, fields may not map correctly, resulting in partial updates or no updates.

B. “The fields that are not updated are read-only in Salesforce.”If a field is Read-Only at the field-level security (FLS) or object schema, DataRaptor Load will not be able to write to it, which explains why only some data is updated.

Incorrect Options:

C. The RecordId from the wrong record type would typically cause a complete failure, not a partial update.

D. A misspelled ContextId could prevent data from being linked correctly, but this is less likely to cause partial field-level issues, and more likely to affect record association.

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.

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.

 According to the FlexCard Designer Overview page, one possible cause of a field showing only the label is that “the field name in the FlexCard state does not match the DataRaptor Extract’s Output JSON Path name”. 

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

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.

The Data Node field for the FlexCard is required to specify which data source will be used to populate the FlexCard. If it is empty, the FlexCard will not display any data. The Record Id in the Test Data Source settings is used to preview the layout with a specific record. If there is no Salesforce record for that Record Id, the FlexCard will not display any data either.

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.

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

Setting the Timeout property on the HTTP Action in the Integration Procedure allows the developer to specify how long to wait for a response from the external system before timing out. Checking the Chain on Step Check on the HTTP Action in the Integration Procedure allows the developer to chain multiple HTTP Actions together and execute them sequentially. Configuring a Remote action with timeout settings of 120000 is not necessary, as it is already done by default in OmniStudio. Checking the Chainable checkbox on the integration procedure Action in the OmniScript has no effect on calling an external system.

Checking the Enable Cancel checkbox in the Setup tab under Cancel Options allows the developer to enable the cancel functionality for all steps in the OmniScript. The user can cancel the OmniScript at any time by clicking the Cancel button in the top right corner of the OmniScript. Adding a navigation Action inside each step is not necessary and would clutter the OmniScript design. Setting the Component name or Element Name to ‘’Cancel’’ has no effect on enabling the cancel functionality.

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

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.

The JSON code correctly represents the step in the OmniScript Structure panel shown. The JSON code has the following properties:

The type is “Step”, which indicates that this is a step element in the OmniScript.

The label is “Step 1”, which matches the label shown in the panel.

The name is “Step1”, which matches the name shown in the panel.

The elements property is an array that contains one element, which is a text field.

The text field element has the following properties:

The type is “Text”, which indicates that this is a text field element.

The label is “Text Field 1”, which matches the label shown in the panel.

The name is “TextField1”, which matches the name shown in the panel.

The value property is an empty string, which indicates that this text field has no default value.

The Timeout property on the HTTP Action in the Integration Procedure specifies how long to wait for a response from the external system before throwing an error. The Chain On Step checkbox on the HTTP Action in the Integration Procedure indicates that the next action should be executed only if the current action is successful. These two configurations should be used to implement the call to the external system given its known performance issues. 

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.

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.

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

A Set Values Action in a Value field and a Remote Action in an Additional Output value field can execute a function like CONCAT or DATEDIFF by using the syntax {{function(parameters)}}. For example, {{CONCAT(‘Hello’, ‘World’)}} or {{DATEDIFF(‘2021-01-01’, ‘2021-01-31’)}}.

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 suitable for this scenario because the developer does not need to transform or load the data