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).
Reference:
Salesforce OmniStudio Developer Guide # Integration Procedure Element JSON Pathing Best Practices for Send JSON Path # Nested Blocks and Element Referencing

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.

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.

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.

A DataRaptor Transform can simplify nested data by transforming it into a flat structure. The developer can use JSON paths to map the input data to the output data and define the output structure.