[jboss-user] [jBPM] - Re: Human Task Assignment -- actor status changed

[Chris Melas]

Chris Melas [http://community.jboss.org/people/melc] created the discussion

"Re: Human Task Assignment -- actor status changed"

To view the discussion, visit: http://community.jboss.org/message/644801#644801

--------------------------------------------------------------
Hi,
I'll try to see how each of your reqs are solved with "out of the box" functionality


> A task associated with the first node can be claimed by any member of a given group. When complete, the subsequent task can also be claimed by any member of some group (possibly a different one). However, the id of the actor that completed the previous task is retained as a process variable.
- So, task1 and task2 are assigned to a group - ok
- The id of the actor that completed task1 will have to be mapped to a process variable - ok ( can be done either by using #{some expression} or a little magic around kcontext within the on exit action etc)


> So here is the scenario. For the 2nd task, the actor completing that task will set "approved" to true or false. If "approved" is false, then:
> 
> --the process should return to the previous node and be assigned to the actor that completed it before...
> 
>      unless:
> 
>           --either that actor no longer exists
>                or
>           --that actor exists but is no longer a member of the group that can claim the task
>                ...in which case, the task should be claimed by some other member of this group
- Assigning the actor based on the variable value is ok..... however i'm not sure what happens if both actorid and groupid are present in task1.... whether the actorid will supersede....-> although you can always place a task3 which is the same as task1 and everything works fine.
- Regarding the "unless" part this is a little strange, because if the actor no longer exists and you assign the actorid 
the following might happen (sry havent tried it)
a. the system complaints that the specific user no longer exists
b. the system has no problem that the users no longer exists and the group part works - then all ok 

....keep in mind that i'm talking about zero code situations  i.e. not even user-group callback etc....

If the actor exists but no longer part of the group then this gets complicated. Because, if the user exists then the actorid will be assigned along with the groupid, but the engine must not assign it to this user since is not a member of the group - not ok (this i'm almost certain that will not work for this engine as well as two more i.e. activiti and intalio, .... in jbpm this can be achieved with a little programming in a clean manner).
--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/644801#644801]

Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20120105/201c8a2d/attachment-0001.html