-
1. Re: Assigning Taks to the same user when sent back
jpechanec Feb 5, 2008 2:34 AM (in response to zahidmaqbool)Hi,
I think that swimlanes is something that you are looking for
http://docs.jboss.com/jbpm/v3/userguide/taskmanagement.html#swimlanes
J. -
2. Re: Assigning Taks to the same user when sent back
bentins Feb 5, 2008 3:35 AM (in response to zahidmaqbool)A swimlane, as fas as I understand, will keep the same actor. If TASK B is for a different actor then a swimlane will not solve this. What we did was to extend the taskInstance with our own object that keeps the information on the former actors on the task (Tasks can also be reassigned so you need to keep as fas history as needed). Then we used a Task Assignement Handler that checks for a flag to restore the former actor.
-
3. Re: Assigning Taks to the same user when sent back
zahidmaqbool Feb 8, 2008 7:21 PM (in response to zahidmaqbool)Thanks for your response, to keep track of previous users i am storing it now a variable in business process. Then i assign the task through my class.
It works fine. I thought there is a way to track all the users, but couldnt find one so had to do something.
Between I have found that jbpm_taskInstances does maintain a list of users assigned to tasks. So i believe even if we know the taskID of previous stage we can get this information. -
4. Re: Assigning Taks to the same user when sent back
kukeltje Feb 9, 2008 9:48 AM (in response to zahidmaqbool)jpechane is correct in suggesting swimlanes. Task A and Task B need to have different swimlanes. If there is a transition back from B to A, the original actor (or group of actors) will be assigned to Task A again. So no need to store this somewhere.