Jbpm job assignment mechanism

The definition of the process is usually emphasized in various standards of the workflow, which is not mentioned in task assignment, and this is an indispensable part of the workflow application.

Jbpm implements two job assignment mechanisms:

1 client based assignment

The basic idea is that the user knows who will execute the entire process. In the process definition file, only the node steps for process execution are specified. Before executing each step of the user interface, let the user manually enter the executor of the next node. This is a bit similar to the free process of Tongda OA.

2 Process Based Assignment

It is to define in the process definition who will execute a node. There are many different asignhandler, such as giving the user name directly, specifying the user name for the previous process execution, or using some expression to give the user.

Additional: about assigning a task to a group

Specific scenarios: for example, when the call center receives a warranty task, the reporter assigns the task to the repair department. Many people in the repair department can handle the service, so when the process is executed, we don't know who will execute it. it can only be executed by people who are currently idle.

The solution is to create a list of two tasks that contain the user and the user's group.

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. The

User: click "take" to get the task from the group task list to your task list. This task is now owned by this person, and is no longer displayed in the group task list of others. Here a reassignment is completed.

Note: For actor, in jbpm, people, groups, and systems are all marked by an actorid.