Chunzhi Hong I'm using 7.1.9 and also tried a "Persist Case"-Shape which did not help (also pxUpdate, pxSaveCase, pxCommit, aso.) - since I can't wait for a user/system to perform the assignment (I also tried auto-perform with "Always") this is not feasible for me. I have a workaround by using the integration-assignment which is waiting for another soap-call, so I end up with 3 soap-calls (start,wait,wait).
Joel Mcleish I tried that also and it worked, but I also consider that as a workaround and it might start some discussions about "why is this necessary". At least a "Persist Case"-Shape should do the trick imho.
Mohammed Burhanuddin Sorry that did not worked - I got a tempPage with the correct class and everything but my pyWorkPage is messed up anyway.
This "bug" is really easy to spot, if you try to do a pxMove in between a assignment-shape and the start-shape. I would consider that as a standard use-case for attaching cases to another cases without any user-interaction.
My understanding is the persist shape is to make a temporary work object permanent.
The wait shape is a necessary evil I've found in instances where there's no user interaction before any straight through processing as an 'assignment' of some sort is required to make the first commit and calculate the inskey et al.