OmniStudio-Developer Questions and Answers

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

 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.

 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.

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

 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.

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.

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.

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.

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

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.

In OmniStudio Integration Procedures, when you want to reference the output of an element in a nested block (e.g., for use in a Remote Action or another step), you must use dot notation that mirrors the block structure hierarchy.

In the exhibit:

Action1 is nested inside:

BlockB, which is nested inside:

BlockA

Therefore, the correct Send JSON Path to access the result of Action1 is:

CopyEdit

BlockA.BlockB.Action1

This format complies with the standard output reference syntax in Integration Procedures, which follows the pattern:

php-template

CopyEdit

..

Incorrect Options:

B. BlockA:BlockB:Action1 – Uses colons instead of dots. This is invalid syntax in JSON path resolution within Integration Procedures.

C. Action1:BlockB:BlockA – Incorrect order and invalid separators.

D. Action1.BlockB.BlockA – Incorrect order (reversed path).

According to the Calculation Matrix Overview page, a Calculation Matrix is “a lookup table that takes an input and returns an output”. In this case, the input is the ProductCode and the output is the Price. The exhibit shows a Calculation Matrix with four rows, each with a different ProductCode and Price. The input given is ProductCode: HRA3320, which matches the second row of the matrix. Therefore, the output is Price: 13.99, which is the value in the same row. 

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.

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.

In OmniScripts, if you need to apply a function (like COUNTIF) to dynamic data and show the result immediately, the Formula element is the correct choice.

B. Formula element – The Formula element supports real-time calculation using OmniStudio expression functions (like COUNTIF, SUM, etc.) and updates values instantly on the screen without the need for server calls.

Incorrect Options:

A. Set Values element is used to set static or conditional values but doesn’t support formula evaluation.

C. Range element is used for value comparisons and conditions, not for calculations.

The element name for the missing data must match the JSON node key in the Integration Procedure Response, otherwise the data will not be mapped correctly. The JSON sent from the Integration Procedure Action must match one of the Original Input for the Integration Procedure, otherwise the Integration Procedure will not execute properly. The Integration Procedure Preview Input Parameters and the Response JSON Path have no effect on displaying data in OmniScript.

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

 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.

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

The FlexCard Player component is used to display FlexCards in a community page. The developer needs to add the FlexCard’s API name to the FlexCard Player component to configure the FlexCard for deployment in a community.