0

I have a process with many tasks that should be done by different users and I don't want to use the bonita predefined actor filters (initiator & initiator-manager) Is there a way to exactly choose which user can do the task by changing actor mapping or defining a new actor filter?

I tried to add three actors and in configuration--->Actor mapping and chose 1 user for every actor but the problem is that when the specified actor(user) in a step takes the task, after submitting the information in the form there is no option to release the task and let the process to proceed to next task that another actor(user) has to do. (sorry for poor English)

Jason Aller
  • 3,541
  • 28
  • 38
  • 38
Navid
  • 157
  • 2
  • 2
  • 14

2 Answers2

2

I think your approach to use actors and configure actor mapping is correct and should provide the result you are expecting.

In a scenario where:

  • Step1 is for ActorA and ActorA is mapped to user walter.bates
  • Step2 is for ActorB and ActorB is mapped to user helen.kelly

when Walter see the task list it will be able to:

  • select the task
  • take it: he still needs to take it as potentially group of users or multiple users can be mapped to an actor
  • submit the form
  • process execution will continue to Step2
  • at this point walter.bates doesn't have any task to do and helen.kelly have one task to do.

Once walter.bates submit the form the task is done and no need to release it.

You can download the basic example I create to illustrate this behavior.

Also in your use case I think it might be intersting to use the "single user" filter so user does not have to take the task. I create another diagram to illustrate this solution.

Antoine Mottier
  • 1,185
  • 1
  • 8
  • 13
0

I solved it by :

Used Actor filter single User for every task and specified the user ID with a Groovy script Using : apiAccessor.identityAPI.getUserByUserName("walter.bates")

Some other methods of identityAPI can be usefull too.

Navid
  • 157
  • 2
  • 2
  • 14