In an EPC, the following modeling conventions must be observed for functions of the Human task type:
If no e-mail has been modeled, no e-mail is sent, but the task to be performed is still displayed as a task in My tasks.
Various options exist for assigning human tasks to an executor.
Assignment with organizational elements and the connection 'carries out'
The human task must be linked to exactly one automation-relevant organizational element by the carries out connection. Possible organizational elements here are Person, Role, Position, and Organizational unit.
Organizational elements of the Role or Organizational unit type must be assigned at least one user who is activated for process automation, unless the Commit employee attribute is set and/or a predefined user exists.
If a human task is assigned an organizational element of the Person type, the user must be activated for process automation.
If no active user is found the escalation manager is notified by e-mail. If no escalation manager is defined, the human task is given the status Failed.
You can optionally specify the Executor selection and Commit employee attributes for the carries out connection. The default values are Only one required and Same executor(s) required (commit employee).
In the data flow it is possible to assign other data that will overwrite the assignment of the organizational element described above. This should be avoided unless the Executor selection attribute at the carries out connection has the value All from preselection.
Assignment using the 'Commit employee' attribute
The attribute value for all human tasks within a process instance, which are assigned to the same organizational element (Role or Organizational unit), must be specified with either Commit employee or Segregation of duties. Only the attribute value No policy can be combined with one of the other attribute values within an instance.
Same executor(s) required (commit employee)
The Commit employee attribute with the value Same executor(s) required (commit employee) is considered only if the value Only one required is selected for the Executor selection attribute. This corresponds to the default settings.
It ensures that the user who is editing the first task of the process instance also performs all further tasks. Only then do the tasks receive the status Completed. Nevertheless, these tasks can be passed on to other executors in My tasks (delegate, specify substitution).
Example
The first task in a process instance is assigned to the QM user group. This means that all persons assigned to this organizational element in the organizational chart can edit the first task. If, for example, the user Peter Smith edits the first task, that user is assigned all other tasks in this process instance.
Other executor(s) required (segregation of duties)
If segregation of duties is specified for the tasks of a process instance the tasks must be carried out by different executors. To ensure this, from the second human task in a process instance, the executor who already carried out a task in the process instance is excluded from execution. However, it is possible to pass on (delegate) the tasks in My tasks to an executor who has already carried out a task in the process instance.
No policy
Tasks whose Commit employee attribute has the value No policy can be carried out by all executors assigned via the organizational element.
If a chain of tasks for which Commit employee is specified is interrupted by a task with the attribute value No policy, the subsequent task with resource commitment is handled as though it were the first task in the process instance. This means that the task can again be carried out by any user from the assigned group and the resource commitment is specified again for the subsequent tasks.
Example
There are four tasks in a process instance, all of which are assigned to the QM user group, to which Peter Smith and Frank Brown belong. The first task can be carried out by both. Peter Smith is the one who carries out the task, for which Commit employee and Only one required are specified. Therefore, the second task is assigned to him, as well. No policy is specified for the third task. This means that both persons are assigned for execution again. This time, Frank Brown is faster and thus is assigned the fourth task, as well.
Assignment via the data flow with the attribute 'Login of the predefined executor'
With this attribute, the first executor of tasks in a process instance can be specified. If, in addition, the value Same executor(s) required (commit employee) is specified for the attribute Commit employee, the employee is specified for the entire instance.
This predefined executor must be activated for process automation and belong to the organizational element (Role or Organizational unit) that is assigned to the human task. The value Only one required must be selected for the Executor selection attribute. If these conditions are met, all other persons in this organizational element are not assigned any human tasks in this process instance.