anonymous wrote : When a task is assigned to a group, the actorId property 
should be set, rather than the pooledActorArray. The meaning is that the task 
is shared by all members of that group, whoever they are. This way new members 
can quickly get involved with the responsibilities of the group.
  | 
  | It follows that the findTasksByActorId(actorId) query should retrieve tasks 
assigned to that actorId plus tasks assigned to each group that actor belongs. 
In fact, things already work like that:  

Alex, 
I see a few problems with this approach--unless I've missed some changes in the 
last couple months.  

The first is that if I'm using my own user/group directory (Active Directory 
for instance), jBPM isn't going to have any idea which user belongs to which 
group and will only return tasks directly assigned to that group as an 
'actorId'.  Behavior of such a basic API call should be consistent whether I'm 
using jBPM's user management system or my own enterprise system.

The second issue is a little more subtle, but is the kind of reason my company 
is passing by Oracle's BPEL solution and using jBPM.  Consider that a 
particular trouble ticket task is associated with a 'Ticket Pool' from which 
members of the Customer Care group claim tasks.  A user named Bill claims a 
task out of the pool but does not perform the task for some reason, and the 
ticket must revert back to the pool.  If our system supports separate work 
group assignment, our task contains assignment data related to both the current 
actor (Bill) and it's governing work group (the Ticket Pool); consequently, 
simply disassociating Bill from the task allows the system to see this task as 
being back in the Ticket Pool.  If we didn't have both user and group data 
simultaneously associated with the task, the system wouldn't know to which pool 
to return the task.  We could not determine this simply by referencing to which 
pool Bill belongs, because Bill may work out of more than one pool.   To handle 
this scenario, we're using 'pooledActors' to hold the pool/group name to which 
the task belongs.

Am I way off base, or does some of this make sense?

Thanks,
Britt

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921964#3921964

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921964


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to