the actorId in jBPM is just a string. If you do not need the pooledActors thing and are able to map the user who logs-in to a role, you can store this rolename in the actorId. You do miss the functionality of the pooledActors however. The choice is yours
What I do is use Assignable.setPooledActors(String actorIds) to store the names of work pools (roles). This allows me to get much of the functionality of JBPM's pooled actor features. Of course, your own application will need to be aware that everything set in PooledActors should be considered a work pool (role) and not an individual actor, and your application would also need to take care of knowing to which pools your users belong.
So what is the solution ?
As for my case, i need the actorId mapped as the users and a role mapped as a dedicated team ..
does anyone have a role use case ?
I am leading myself astray with role/group !!
All of these, because I can't find a way to define a new group with two existing groups !!