The only area of complexity is updating the
order directly within the task payload. This is for the same reason we mentioned earlier when implementing the
getOrderDetails operation; as the payload is defined as
xsd:any, we can't use the XPath mapping tool to visually map the updates.
The simplest way to work around this is to first extract the
order from the task payload into a local variable (which we do in exactly the same way that we did for our
Once we've done this, we can update the
shipTo element of the
order to hold the shipping details as well as update
nextAction to Enter Shipping Costs to reflect the next step in the workflow.
Once we have updated the
order, we must insert it into the ...