Eliminate Risk of Failure with Salesforce Plat-Dev-210 Exam Dumps

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

Salesforce OmniStudio Developer Guide Integration Procedure Element JSON Pathing

Best Practices for Send JSON Path Nested Blocks and Element Referencing

From the OmniStudio OmniScript Documentation:

A Repeat Block (like BlkContacts) expects an array of objects.

Each item in the array must contain fields that exactly match the UI elements inside the block.

The parent JSON must include any top-level values used by individual input fields (like AccountName, AccountPhone).

Why the Other Options Are Incorrect:

B . Uses Contacts instead of BlkContacts, and is incomplete/malformed.

C . Repeats keys at the same level instead of using an array structure. This causes the data to overwrite and fail to display properly.

D . Uses incorrect keys like 'Name' and 'Phone' instead of expected 'ContactName' and 'ContactPhone', breaking field binding.

Salesforce OmniStudio Developer Guide OmniScript Repeat Blocks & Data JSON Structure

DataRaptor Extract Output Mapping JSON for OmniScripts

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

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