- assign it to multiple actors (pooled actors)
- it shows up in the poolerd list
- once an actor has to perform it, assign it to that actor
- it shows up on the personal list
- have the actor act on it (no concurrency)
- done
hth
View the original post :
In my case actually the task instances (yes it's plural) can not be just
assigned to pooled actors because each of the actors will have their own task
instance of the same task. And the task has a task-end event that will change a
process instance variable whenever a task instance is finished.
Ahhh ok, then look at the workflowpatterns testcases in the sourcecode where
there (afaik) is a N out of M example. Look at www.workflowpatterns.com to see
the patternnumber
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3952759#3952759
Reply to the post :
I've checked the pattern no 15 Wfp15MiWithAPrioriRuntimeKnowledgeTest in the
jbpm test source code. But the test case was built on the assumption that the
task instances are executes sequentially, one after another. In my case the
task instances can be executed concurrently.
Regards,
Martin
