Responsibility Rules

Specifying responsibilities is optional. The rules used for establishing recipients are described below.

Responsibility for processing a step in a workflow

The responsible agents are established as follows:

  1. Evaluation of step definition
  2. The points below are only executed by the workflow system if the step in question is an activity.

  3. Evaluation of the default role for the agent in the definition of the single-step task.
  4. Evaluation of the possible agents of the single-step task.

All responsible agents who are also possible agents become the recipients for the work item.

If the single-step task is defined as a general task, the possible agents are all users of the system. Therefore, it is essential that you define responsible agents for such outcomes.

Responsibility rules for missed deadline notification

Notification when deadlines missed for step in workflow

The recipients are established as follows:

  1. First, recipients are looked for in accordance with the step definition.
  2. If the step in question is an activity, the relevant missed deadline default role of the associated task is evaluated.
  3. The workflow system administrator is used as recipient.

Notification when deadlines missed for subworkflow

The recipients are established as follows:

  1. First, recipients are looked for in accordance with the step definition.
  2. The missed deadline recipient for the subworkflow, who is defined in the basic data, is evaluated.
  3. The workflow system administrator is used as recipient.

Responsibility rules for completion notification

Notification upon completion of step in workflow

The recipients are established as follows:

  1. First, recipients are looked for in accordance with the step definition.
  2. If the step in question is an activity, the relevant default role of the associated task is evaluated.

Notification upon completion of subworkflow

The recipients are established as follows:

  1. First, recipients are looked for in accordance with the step definition.
  2. The specification in the basic data of the subworkflow on the tab page Notification is evaluated.

Notification upon completion of workflow

The recipient is established in accordance with the entries in the basic data of the workflow.

Behavior in the event or errors resolving responsibilities at runtime

The following occurs if the system cannot establish any users at runtime:

Problem

Behavior at runtime

The responsibility was defined via a role. The indicator Cancel if role resolution has no result is set in the role definition: The role resolution is terminated with an exception.

The workflow is forced into status error and the workflow system administrator is informed.

The exception no responsible party established occurred in the resolution of the responsibility entry.

The system tries to establish a user in accordance with the rules above.

Another exception occurred in the resolution of the responsibility entry.

The workflow is forced into status error and the workflow system administrator is informed.