On the wizard page, click the “back” button:
Then check the Advanced settings check box and click Next:
Select all at once option:
configure the “required responses” – slots:
Now you will see a default destination set created on the next screen:
Click edit and then click Add to create a destination. On the destination textbog, drag and drop the repeating XML node <User> from the XMLDocument which you have defined as a Process XMLField. This is grabbed from the context browser’s Data tab:
You are done. Deploy and run the process. You will realise that K2 only resolves the first of the repeating node values and only assigns to that user 🙁 The issue is K2 destination rule can handle this scenario if the node being used as the destination is a repeating node itself. Not a child of a repeating parent node.