A handy new feature in Madrid is the payload builder. This allows for reasonably simple name-value pairs payloads to be crafted into a payload object. The ability to use the inputs combined with a payload builder lowers the bar for building dynamic integration actions.
You can see the Name-Value pair setup is pretty straight forward using the data pill setup that is now familiar in Flow/Action Designer. Output format can be JSON (default) or XML.
The XML option comes with a couple of extra fields which allow you to specify the namespace and parent node. The choices for include outer structure will remove/provide the parent node structure in your payload.
Note the expand arrow at the edge of each name-value pair. This will allow you to select if you wish to omit if empty any of the name-value pairs. This flexibility is convenient when trying to be as flexible as possible when building your actions. If the input action->user data pill contained no data at run time, I might want to choose to omit that in the payload.
To use the payload output data pill is as simple as you would expect. In your REST/SOAP step you can grab and use the payload step data pill just as easy as drag and drop!
While this isn’t the most extended blog entry, I hope you will find the value in the new payload builder step, and the advanced name/value pair features it adds to the header and query areas in REST & SOAP steps. You can expect to see the use of this payload builder as soon as next week in the Live Code Happy Hour stream. Happy integrating.