My company needs to interact with some legacy SOAP services that are not strongly typed. As such, we make heavy use of the Customize Envelope functionality in the SOAP Execute snap. While the variable substitution seems to work fine for values, we need to use it to insert XML snippets into the envelope.
For example, I have a Script snap that constructs and stores a string in the document that looks something like:
"AddPersonPayload" : "<Name><Person><First>Kevin</First><Last>Kelley</Last></Person></Name><Address><NonStandardUS><Line1>5000 Riverside Dr</Line1><City>Austin</City><State>TX</State><Zip>78105</Zip></NonStandardUS></Address>"
In the Customize Envelope dialog box, I do something like:
This almost works but the inserted content is “encoded” (but the surrounding content is not) so that it looks something like this:
The server is rejecting this because it is treating the content as a value rather than XML. It would be nice if there were a mechanism to mark a particular variable substitution so that the content would not be XML encoded prior to inserting it…