I had a similar problem where I have an approval process that requires approvals to be done in order. If an approval is rejected, the process ends.
My solution was to generate all the tasks up front but assign only one. Upon receiving an approval (ie task was completed), I assigned the next actor to the next available task and then ended the previous task. This was custom code in a servlet. For your case, I'd suggest creating and assigning all the tasks up front, store the Master task ID in a process instance context variable. Then, when all child tasks are completed, you could locate and end the Master task, then the workflow will continue. -fm View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3925700#3925700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3925700 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
