In an Integration Procedure with a Remote Action named FetchCart and a Response Action named ResponseCart, which JSON node displays the data sent to the remote action during preview?

In an Integration Procedure with a Remote Action named FetchCart and a Response Action named ResponseCart, which JSON node displays the data sent to the remote action during preview?

• A. FetchCart
• B. ResponseCartDebug
• C. ResponseCart
• D. Response

Answer: (B)

When you preview an Integration Procedure, OmniStudio exposes a debugging JSON node that shows exactly what is sent to the remote action. That data appears under the JSON node named after the related Response Action with a Debug suffix. In this case, the node that displays the data sent to the remote action during preview is the one called ResponseCartDebug. This node specifically captures the outbound request payload for the remote action, so you can inspect what is being sent. The other options don’t fit this purpose: FetchCart is the actual remote action, not the debug display; ResponseCart is the action that handles the response, not the outbound request payload; and a generic Response node isn’t the debug view for the outbound data.

When you preview an Integration Procedure, OmniStudio exposes a debugging JSON node that shows exactly what is sent to the remote action. That data appears under the JSON node named after the related Response Action with a Debug suffix. In this case, the node that displays the data sent to the remote action during preview is the one called ResponseCartDebug. This node specifically captures the outbound request payload for the remote action, so you can inspect what is being sent.

The other options don’t fit this purpose: FetchCart is the actual remote action, not the debug display; ResponseCart is the action that handles the response, not the outbound request payload; and a generic Response node isn’t the debug view for the outbound data.