The various standards of workflows are usually emphasized that the definition of the process itself is not mentioned, and this is essential for workflow applications.
JBPM implements two task assignment mechanisms:
1 Client Based Assignment
Basic thinking is that users are very clear from which people from the whole process. The node steps that only specify the process execution in the process definition file. Before each step of the user interface, let the user enters the executor of the next node. This is a bit similar to the free process of OA.
2 Process Based Assignment
Is the process definition to specify who is performed by any node. There are many different AsignHandler, such as directly username, or designated as a username executed by the previous process, or use some expression to give the user.
Additional addition: About assigning a task to a group
Specific scene: For example, the call center receives a warranty task, the reporter points to the maintenance department, the maintenance department has many people to handle this business, so when the process is executed, we don't know who will eventually execute. Can only be The current hand free person is executed.
This is the method of processing is to establish two task lists that contain groups where users and users are located.
Personal task list 1 do ... [action] 2 do .. [action] group task list 1DO .. [take]
When a task is assigned to a group, the task appears in the group task list of all members of the group. This task can be implemented
Users, click Take, take this task from the group task list inside your task list. Now this task belongs to this person, and this task is no longer displayed in other people's group task list. Here, I completed an enathment.
Note: For actors, in JBPM, people, groups, systems are indicated by an actorID.
