Defining Rules Using Responsibilities

Use

With this rule category you can select agents based on values from the workflow or the task. To do this, you transfer container elements from the task or workflow container to the rule container using binding. In the rule you define responsibilities that relate Organizational Management objects (job, position, organizational unit, user, and so on) with possible values from container elements in the rule container.

A responsibility is itself an organizational object that requires no Customizing settings and no ABAP source text.

Prerequisites

Before you define a rule using responsibilities, you must know the task or the workflow step whose agents you want to determine using the rule. You need information about the container elements used in the workflow/the task, so that you can use them in your responsibility rule.

You are on the Rule: Change or Rule: Create screen.

Procedure

  1. On the Rule Definition tab page, choose the category Agent Determination: Responsibilities, and assign an abbreviation and a name for the rule.
  2. Creating Rule Containers

    The Rule Container must contain the container elements whose values you want the system to check when the rule is executed. At runtime, binding fills the rule container with data from the task or workflow container. To create the rule container, you therefore need to know the definition of the task or workflow container.

  3. Creating a Responsibility

    With a responsibility you define the container element values that you want to trigger processing by the same users. In the responsibility, you define values or value ranges for the container elements of the rule container. If you wish, you can assign a priority to each responsibility.

  4. Assigning Users or Organizational Objects to the Responsibility

    You assign Organizational Management objects to a responsibility. These are then returned as the result of the rule, if the responsibility check is positive.

  5. If you only want the rule to return users or persons who are directly assigned to the responsibility, set the Personal Rule flag. Otherwise the rule also returns users who are indirectly assigned to the responsibility (for example via an organizational unit).
  6. During rule resolution, the system evaluates only the responsibilities with the highest priority. If no agent is determined, rule resolution is terminated. If the Take secondary priorities into account flag is set, rule resolution is not terminated. Instead, the system also evaluates responsibilities with a lower priority.

    All responsibilities with the same priority are evaluated independently, and the respective agents determined are all returned as a result.

  7. If you want the workflow to receive the Error status if rule resolution does not produce a result, set the corresponding flag. For more information, see Cancellation for Rule Resolution Without Result.