Pass the Salesforce Developer OmniStudio-Developer Questions and answers with ValidTests

A Data Mapper Transform is used to restructure input JSON into the output JSON format required by a target system. Since the target requires a nested array of objects, the developer must map the source value into the correct nested target path so the Data Mapper output structure creates the ContactDetails array and Phone object. A flat direct mapping does not describe the required parent array and child object structure. A Formula is not required just to place an existing source value into a nested output structure; formulas are used when the value itself must be calculated or transformed. Mapping to the root node would lose the required ContactDetails and Phone hierarchy. The correct method is nested target path mapping.

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

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.

The Node field for the parent FlexCard should be set to {Records}, which is an array of all the records retrieved by the parent FlexCard data source. This will allow the child FlexCard to access the records and display them in a DataTable.

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

< ParentBlock > . < ChildBlock > . < ActionElement >

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

A Data Mapper Extract Action is the correct choice when an OmniScript must retrieve many fields from a Salesforce record. Data Mapper Extracts are built specifically to read Salesforce data, select the required fields, apply filters, and return the data in JSON, XML, or another configured output structure. A Lookup element is appropriate for retrieving or selecting a single record or field value, but it is not the best tool for pulling many fields. HTTP Action is for calling external HTTP endpoints, not directly querying Salesforce records. Select is a user-input element, not a Salesforce data retrieval tool. For a multi-field Salesforce record retrieval requirement, Data Mapper Extract provides the correct declarative query and mapping capability.

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

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. 

When data changes every five minutes, the cache lifetime should be close to that refresh cycle. A 300-second Cache Duration gives the Integration Procedure a performance benefit while limiting stale data exposure to approximately the same interval as the source data change frequency. A contextual key controls cache separation by context, but it does not define when cached data expires. Disabling caching ignores the stated requirement that the developer wants to use caching. A very high value, such as 24 hours, is dangerous because users could receive stale data long after the underlying source changed. Salesforce’s OmniStudio caching guidance explains that Integration Procedures can cache results and that Cache Blocks are appropriate when different data must expire at different times.

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

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

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.

Salesforce OmniStudio Guide → Cloning vs. Versioning Integration Procedures

The correct best practice is to use one Data Mapper Load configured for the related object mappings. Salesforce documentation explains that Data Mapper Load supports updates to multiple Salesforce objects and displays separate mapping tabs for each target object. It also documents Multiple Related Object Loads, or Link Mappings, for propagating data between related objects during a load sequence. This avoids unnecessary multiple sequential Data Mapper Load Actions and keeps the update logic declarative, maintainable, and transactionally cleaner. A Remote Action with Apex should only be used when declarative mapping cannot satisfy the requirement. A Salesforce REST API HTTP Action is also unnecessary because the operation is inside Salesforce and OmniStudio already provides Data Mapper Load for this exact use case.

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