This content has been marked as final. Show 7 replies
Nope the Approver node must exist for that to happen. You can replace nodes that exist so if you changed the Approvers node with the new XML then you would get your desired result.
I need the old data plus the new so I end up with the same problem creating the new XML. My work around is to do it with Strings then replace, but it is messy.
I need something similar: I have a document var with a xml document. I need to take part of that xml (a specific nodeset) and add it to a string.
any ideas to acomplish this?
First you want to put the content of the document into a XML var so you can use xPath.
You can use xPath to get to the node you want (ex. /process_data/myXMLVar/Root/Customers).
Then use the serialize function from the xPath editor (under Misc) to convert the nodes into a string:
Finally you can use the concat function from the xPath editor (under string) to merge two strings together:
Write an ExecuteScript activity?
I don't understand your question.
A node can be added to an XML instance using XSL in an XSLT Transform service, also.
My sample process uses two input process variables:
1. 'inputXml' of type xml
2. 'approverId' of type string
I define the following XSLT template which consumes the input process variable 'approverId':
The result of the applying the XSL is as follows:
The process could be designed to iterate over the input XML and the XSL.