You need to complete the Human Task before the flow moves from there. To do that you can get hold of the "Mina Client" to complete the associate WSHT task which in turn should generate the event to complete the associated Work Item. Take a look at the following test classes within the drools source. org.drools.task.service.TaskLifeCycleTest org.drools.task.service.TaskServiceLifeCycleTest Vijay -----Original Message----- From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Touma Sent: Tuesday, April 13, 2010 10:12 AM To: rules-users(a)lists.jboss.org Subject: [rules-users] Resuming a simple process involving human task Hi all, For the past few weeks I've been trying to get a simple drools flow example involving human tasks up and running. I've done quite a bit to the point that my session, process, task and workitems are being persisted in the database. Here is what my flow looks like: Start -> Ruleflow -> Decision node -> Human Task -> Printing Node -> End The work item handler for the Human task simply performs the task of persisting the Task instance. After reaching the Human Task, the flow stops and the state is persisted. But how would I go about restarting/resuming the flow so that the 'Printing node' is reached? I've tried using the loadStatefulKnowledgeSession(sessionId) to load the session but querying the list of all the processes for the given session returns an empty list. Ditto with the list of all the process events. I have all the ID's with me (workitem, process, task, session) but am pretty confused as to how these can be put to use to resume my suspended workflow. Any pointers would be much appreciated. TIA. Peace, /T\ -- View this message in context: http://n3.nabble.com/Resuming-a-simple-process-involving-human-task-tp716... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

@Touma, There are a couple of ways to resume the flow: 1. Complete a work item that causes the process to wait. 2. Post (signal) the event, which is a different thread, hence can restart / resume the flow at any point. In your case, as Vijay pointed out, you would have to complete a work item. However you don't have to rely on MinaServer / Client to do that. The out of the box WS-HT Drools Flow implementation is tightly coupled with MinaServer (it is not pluggable with any other solutions), hence you would have to create your own WorkitemHandler to do that. If you already have all the IDs ( session, work item, etc.. ), it should be as simple as: // re-load the session ksession = JPAKnowledgeService.loadStatefulKnowledgeSession( YOUR_SESSION_ID, knowledgeBase, null, env ); // DON'T FORGET TO RE-REGISTER ALL THE WORK ITEM HANDLERS HERE... // complete the work item ksession.getWorkItemManager().completeWorkItem( YOUR_WORK_ITEM_ID, null ); Good Luck, /Anatoly -- View this message in context: http://n3.nabble.com/Resuming-a-simple-process-involving-human-task-tp716... Sent from the Drools - User mailing list archive at Nabble.com.

@Touma I'm doing something very similar and it is working for me. Well, I have a different problem that I'm trying to solve but I am able to successfully resume the flow. I am not using the Mina server either. I am just hooking a regular WorkItemHandler to the HumanTask. This is my flow : (start) --> (Human Task) --> (Print Out Node) --> [end] I start the flow the following way: @Test public void shouldSuspendOnHumanTask() { ksession = JPAKnowledgeService.newStatefulKnowledgeSession(knowledgeBase, null, env); dbLogger = new WorkingMemoryDbLogger(ksession); registerWorkItemHandlers(ksession); //nothing special here.... I just register my work item handlers. Map<String, Object> params = new HashMap<String, Object>(); params.put( "user", "nick" ); ksession.startProcess("approval", params); } The WorkItemHandler for the HumanTask doesn't complete the workItem so the flow suspends and gets persisted. I reload and resume the flow the following way: @Test public void shouldResumeFlow() { System.out.println("Resuming flow..."); MyDAO dao = new MyJpaDAO(emf.createEntityManager()); MyEntity myEntity = dao.findById(ID); //id of the entity that holds the session id for the flow I want to resume ksession = JPAKnowledgeService.loadStatefulKnowledgeSession( myEntity.getSessionId(), knowledgeBase, null, env ); registerWorkItemHandlers( ksession ); //register work item handlers again. dbLogger = new WorkingMemoryDbLogger( ksession ); ksession.getWorkItemManager().completeWorkItem( myEntity.getWorkItemId(), null ); } The only thing to notice which is different and will vary depending on your implementation is that I am using an Entity to store the different IDs that I'll need. So, before the flow suspends I persist this entity and when the flow resumes I use DAO to retrieve it. My entity looks something like: MyEntity { private long id; //entity id private int sessionId; //drools-flow session id private int processInstanceId; //drools-flow process instance id private int workItemId; //drools-flow work item id ....... //Constructor //Setters and Getters } So, before resuming the flow I retrieve this entity and then use "myEntity.getSessionId()" to reload the flow. Oh, just in case... my "env" drools runtime environment object looks like this: env = KnowledgeBaseFactory.newEnvironment(); env.set(EnvironmentName.ENTITY_MANAGER_FACTORY, emf); env.set(EnvironmentName.GLOBALS, new MapGlobalResolver()); I think that's it...... It resumes and the "Print Node" executes and the flow completes. Let me know if you need more details or explanation about what's presented above. I hope it helps!!! Nick. -- View this message in context: http://n3.nabble.com/Resuming-a-simple-process-involving-human-task-tp716... Sent from the Drools - User mailing list archive at Nabble.com.

Hi Touma, Did you manage to get this working? I am getting the same issue. My usecase is, a Process with a ruleflow group and a workitem. BTW, my workitem is simple pojo (wanted to keep it simple for testing purpose which prints a msg). When I try reload the session and try signalling the work item complete status getting into this issue. If anyone tried let us know how did you fix. if anyone wants to try, then try similar usecase (ruleflow group with workitem). Thanks K R Kaleraj -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Resuming-a-simple-pro... Sent from the Drools - User mailing list archive at Nabble.com.