When configuring SEND/RESPONSE TRANSFORMATIONS to send exactly the same data as an Integration Procedure element with Additional Input, which configuration achieves this if Send Only Additional Input is unchecked?

When configuring SEND/RESPONSE TRANSFORMATIONS to send exactly the same data as an Integration Procedure element with Additional Input, which configuration achieves this if Send Only Additional Input is unchecked?

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

To pass exactly the same data as the Integration Procedure element’s Additional Input, you need a JSON Path that binds to the IP's input structure dynamically and carries the entire object under that input. The correct path uses a dynamic reference to the SecondaryAccount wrapper and targets the DRExtractAction:Account field in a way that preserves the full payload under that Additional Input, so every field is included and in the right shape. Using the percent-delimited dynamic wrapper (%SecondaryAccount%) ensures the path binds to the actual Additional Input instance rather than a static literal path. The leading dash signifies mapping at the node level to include the whole object, not just a single subfield. Other options omit this dynamic binding or point to a specific subfield without preserving the full Additional Input structure, which would fail to reproduce the exact data the Integration Procedure expects.

To pass exactly the same data as the Integration Procedure element’s Additional Input, you need a JSON Path that binds to the IP's input structure dynamically and carries the entire object under that input. The correct path uses a dynamic reference to the SecondaryAccount wrapper and targets the DRExtractAction:Account field in a way that preserves the full payload under that Additional Input, so every field is included and in the right shape.

Using the percent-delimited dynamic wrapper (%SecondaryAccount%) ensures the path binds to the actual Additional Input instance rather than a static literal path. The leading dash signifies mapping at the node level to include the whole object, not just a single subfield. Other options omit this dynamic binding or point to a specific subfield without preserving the full Additional Input structure, which would fail to reproduce the exact data the Integration Procedure expects.