you can use the same approach used in the WSHT implementation.
Persist the work item Id related with the business activity that cause the wait state.
In the Human task case, the work Item id is persisted in the node instance (that is running) that causes the wait state
yes, I understand they are persisted, but once you reload a session, you have
no knowledge of _which_ Processs Instance to use, and _which_ Work Item is
the one that caused the flow to wait.
Therefore I am looking for the way to save a workitem ID as a variablea,
using a Variable Persistence mechanism.
This way when the session is reloaded, I can do
processInstance.getVariable("workItemId"), which will return me an ID of the
latest work item that caused this flow to wait.
--
so let me try this again.. having a workitem, what would be the best
approach to persist a WorkItemID using VariablePersistence?
View this message in context: http://n3.nabble.com/Drools-Flow-WORK-ITEM-ID-as-a-flow-variable-tp680939p686872.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users