In an integration scenario, which approach correctly mirrors the same data using SEND/RESPONSE TRANSFORMATIONS when Additional Input is used?

In an integration scenario, which approach correctly mirrors the same data using SEND/RESPONSE TRANSFORMATIONS when Additional Input is used?

• A. Send JSON PathSend JSON Node -SecondaryAccountDRExtractAction:Account
• B. Send JSON PathSend JSON Node -%SecondaryAccount%DRExtractAction:Account
• C. Send JSON PathSend JSON Node -DRExtractAction:Account%SecondaryAccount
• D. Send JSON PathSend JSON Node -DRExtractAction:AccountSecondaryAccount

Answer: (B)

Using SEND/RESPONSE TRANSFORMATIONS to mirror data when Additional Input is provided relies on injecting dynamic values into the outbound payload by referencing the Additional Input with a token. The token %SecondaryAccount% tells the transformation engine to substitute the actual value supplied as Additional Input named SecondaryAccount at runtime. Mapping that into the target node DRExtractAction:Account with the syntax -%SecondaryAccount%DRExtractAction:Account ensures the same data appears in the response payload just as it was provided, preserving the data you shared through Additional Input. This approach is correct because it uses the runtime value from Additional Input rather than a literal string, and places it exactly where you want it in the outbound JSON. The other patterns would either treat the input as a literal or place the token incorrectly, resulting in mismatched or missing data in the mirrored payload.

Using SEND/RESPONSE TRANSFORMATIONS to mirror data when Additional Input is provided relies on injecting dynamic values into the outbound payload by referencing the Additional Input with a token. The token %SecondaryAccount% tells the transformation engine to substitute the actual value supplied as Additional Input named SecondaryAccount at runtime. Mapping that into the target node DRExtractAction:Account with the syntax -%SecondaryAccount%DRExtractAction:Account ensures the same data appears in the response payload just as it was provided, preserving the data you shared through Additional Input.

This approach is correct because it uses the runtime value from Additional Input rather than a literal string, and places it exactly where you want it in the outbound JSON. The other patterns would either treat the input as a literal or place the token incorrectly, resulting in mismatched or missing data in the mirrored payload.