Sounds like a subprocess is exactly what you need. Your user interface related to a particular state/task could provide a button, and each time the user clicks it, a new "candidate" sub process is started. When ending the parent process, you would likely have to provide code that would terminate each sub process according to your needs, and then terminate the parent.anonymous wrote : Is there a way to control from the process definition that the candidate-process can only be created or started if I am on the approved state? I"m pretty sure that the answer to this is 'no'. You will have to construct your UI in such a way that the option is only available when you intend it to be.
-Britt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914514#3914514 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914514 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
