Looks like that I have the same problem ...
My swimlane looks like this:
<swimlane name="ordermgm"> <assignment expression="group(ordermgm)" /> </swimlane>
And my identity.db.xml ...
<user name="omagent1" email="firstname.lastname@example.org" password="omagent1" /> <user name="omagent2" email="email@example.com" password="omagent2" /> <group name="ordermgm" /> <membership user="omagent1" group="ordermgm" /> <membership user="omagent2" group="ordermgm" />
All "taks" are assigned to 'null' and not to an user out of the the group.
If I replace the swimlane in the processdefinition with:
<swimlane name="ordermgm"> <assignment expression="user(omagent1)" /> <assignment expression="user(omagent2)" /> </swimlane>
... tasks will be assigned to an user!
I'm a bit confused ... do I have to write my own AssignmentHandler for this?
I solved this problem. Your scenario should work since you are dealing with users and groups within JBPM. Basically, the all the users in the group will figure in the JBP_ACTORPOOL table. Tasks will be assigned to a pool of actors (group) and any one of the actors in the pool can pick up the task and complete it.
You will only need to extend the AssignmentHandler if you are using another database repository such as LDAP to store users and groups.
Do you have a sample how to extend the AssignmentHandler for Groups??