This action set is placed behind a button on the case review harness, with the intention that it creates a copy of the case and opens that copy for editing. However, when I click the button, I get the following error:
Various other testing has led me to believe that in the Action Set the two actions are being run in parallel and hence the second action starts attempts to open the case before the first one has finished creating it. When I split the "Run Activity" (pxCreateTopCase) action and the "Open Work By Handle" action to two buttons, then click the two buttons in order, it works as desired.
Any idea why this happens? Do actions in an action set run in parallel by default, and if so is there any mechanism to make them run in sequence?
***Updated by moderator: Lochan to edit screenshot to remove proprietary information***
I inserted between the Run Activity (pxCreateTopCase) and Open Work By Handle steps another Run Activity that does nothing but calls wait for ten seconds. The screen pauses for ten seconds before giving the same error ("Empty Work Item Handle"). So the two steps aren't being run in parallel - the Open Work By Handle is clearly waiting for the previous steps to complete - but the CloneInsHandle setting doesn't reflect (to the client?) until just after the menu item completes in it's entirety. Not sure why this would be, or if there is a different way to get it to reflect manually (Set Value?)
I raised an SR for this and this is the conclusion:
within a menu item on a navigation, it turns out that the actions in an action set are run in parallel;
behind a button on a form, the actions in an action set are run in sequence.
It turns out that this is default behaviour.
Building the navigation to call a local action instead, setting it to "modal dialog", then defining a new flow action with an associated section with a button with an action set defined with the two actions above, works instead.