Yes, something like that would definitely be very useful. Not necessarily in the form of transient runtime actions (which would have to be registered every time before triggering process execution), it could also be in the form of process events with general, application scope.
For example, we would like to notify each user of every task they receive, by email. Currently every task in every process definition needs to include an on-create event with the notify action, which is an unnecessary complication of process definitions and a waste of database and server resources. We would also like to implement monitoring of process execution, for statistics and to prevent process cycles and such. For that, we would again need to manually include the monitoring action in every process node. This is all unnecessary work, which business analysts definitely should not be bothered with. A possible solution would be to have a declaration of general events somewhere alongside JBPM configuration files, so that they would only need to be configured in one place and then automatically executed each time an event of the specified type is triggered. Or is there another possible solution for those problems? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919388#3919388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919388 ------------------------------------------------------- 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
