I do not recommend that approach, I recommend to copy the same approach used in the WSHT human task module. there is no need to clarify that Human Task are only one of the possibilities for a wait state situation. But, WSHT contains a good approach to achieve the same that you are looking for.. you can copy that.. at the end the WSHT module is jut a Work Item with steroids.
On Tue, Mar 30, 2010 at 7:31 PM, tolitius <[email protected]> wrote: > > Long running process is not always a Human Task, that means the Task is not > always needed. Let's say we are waiting for the response from the external > system, and once response comes in, we would like to complete _this_ work > item. > > Therefore we are looking to do this _without_ WS HT handler, and use > Variable Persistence mechanism instead, so we can load the process, and do > "processInstance.getVariable("workItemId")". > > What would be the best approach to do that? > -- > View this message in context: > http://n3.nabble.com/Drools-Flow-WORK-ITEM-ID-as-a-flow-variable-tp680939p687176.html > Sent from the Drools - User mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > -- - http://salaboy.wordpress.com - http://www.jbug.com.ar - Salatino "Salaboy" Mauricio -
_______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
