Each Bpm Process Definition can have its own task assignation policy. This policy is applied to all Bpm Process Instances of the Bpm Process Definition.
The task assignation policy can be automatic or not:
If it is automatic each time a task is created is assigned immediately.
If it is not automatic then a backoffice user has to enforce the assignation using the backoffice application.
The available assignation policies are:
BpmNoneAssignationPolicy (this is the default policy)
This is default assignation policy to all Bpm processes. It does nothing and each user has to peek up the tasks from the general bag.
This policy check the number of tasks of each user including tasks of other processes and assign task to the user who has less assigned tasks.
The Fair poilicy is global because check all tasks of each user including tasks of other processes.
This policy check the number of tasks for the given role (of the given task) and assign the task to the user how has less assigned tasks for the role.
The round robin role policy is local because the count of tasks is done for a particular Bpm Process Definition.
This policy check the number of a given task and assign the task to the user how has less assigned tasks of this type.
The round robin task policy is local because the count of tasks is done for a particular Bpm Process Definition.