I've seen things here and there in the forums on ad-hoc tasks in a workflow... but nothing in particular to handle this situation. Does anyone have a good way to accomplish this?
SITUATION A process is in progress when a performer realizes they have to perform some ad-hoc task or tasks for just this instance of the workflow. These are not part of the normal process but some sort of exceptions/additions that must occur. The tasks must happen at some particular point in the future of the workflow... essentially executing after an existing node leaves and then allowing the node to actually leave after they have completed. THOUGHTS 1) Programatically create a new process definition to represent our ad-hoc process and add the various nodes that need to be executed as part of this process. 2) Override the leave function of the node object to check whether we are supposed to execute some ad-hoc process before really leaving. 3) If we are to execute some adhoc process, store the transition we were going to take and execute the ad-hoc process. 4) Once the ad-hoc process has completed call the leave function we interupted, but allow it to actually leave this time. Any thoughts on that? Thanks so much for any suggestions! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203434#4203434 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203434 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
