What merge code passes the CaseData node from an HTTP Action's output to a DataRaptor Transform Action?

What merge code passes the CaseData node from an HTTP Action's output to a DataRaptor Transform Action?

• A. %DRXfromCaseData:CaseData%
• B. ResponseCartDebug
• C. {{CaseData}}
• D. %HTTPGetCaseDetails:CaseData%

Answer: (D)

In OmniStudio, wiring data between actions uses merge fields that reference a previous action’s output. The merge field syntax is a percent sign, the API name of the action, a colon, the node you want, then another percent sign. This tells the system to take that node from the specified action’s response and feed it into the next action. So, to pass the CaseData node from the HTTP Action’s output to a DataRaptor Transform Action, you would use the merge code %HTTPGetCaseDetails:CaseData%. This correctly targets the HTTP action that retrieved the case details and the CaseData node within its output. Other options don’t follow this merge-field pattern or reference the correct action/output, so they won’t route the data properly.

In OmniStudio, wiring data between actions uses merge fields that reference a previous action’s output. The merge field syntax is a percent sign, the API name of the action, a colon, the node you want, then another percent sign. This tells the system to take that node from the specified action’s response and feed it into the next action.

So, to pass the CaseData node from the HTTP Action’s output to a DataRaptor Transform Action, you would use the merge code %HTTPGetCaseDetails:CaseData%. This correctly targets the HTTP action that retrieved the case details and the CaseData node within its output.

Other options don’t follow this merge-field pattern or reference the correct action/output, so they won’t route the data properly.