1. Developing SOA Applications with Oracle SOA Suite
  2. Using the Human Workflow Service Component
  3. Configuring Human Tasks
  4. Selecting a Routing Policy
  5. How to Configure the Error Assignee and Reviewers

How to Configure the Error Assignee and Reviewers

Tasks can error for reasons such as incorrect assignments. When such errors occur, the task is assigned to the error assignee, who can perform corrective actions. Recoverable errors are as follows:

  • Invalid user and group for all participants

  • Invalid XPath expressions that are related to assignees and expiration duration

  • Escalation on expiration errors

  • Evaluating escalation policy

  • Evaluating renewal policy

  • Computing a management chain

  • Evaluating dynamic assignment rules. The task is not currently in error, but is still left as assigned to the current user and is therefore recoverable.

  • Dynamic assignment cyclic assignment (for example, user A > user B > user A). The task is not currently in error, but is still left as assigned to the last user in the chain and is therefore recoverable.

The following errors are not recoverable. In these cases, the task is moved to the terminating state ERRORED.

  • Invalid task metadata

  • Unable to read task metadata

  • Invalid GOTO participant from state machine rules

  • Assignment service not found

  • Any errors from assignment service

  • Evaluating custom escalate functions

  • Invalid XPath and values for parallel default outcome and percentage values

During modeling of workflow tasks, you can specify error assignees for the workflow. If error assignees are specified, they are evaluated and the task is assigned to them. If no error assignee is specified at runtime, an administration user is discovered and is assigned the alerted task. The error assignee can perform one of the following actions:

  • Ad hoc route

    Route the task to the actual users assigned to the task. Ad hoc routing allows the task to be routed to users in sequence, parallel, and so on. Note: Do not add adhoc assignees either above or below a FYI participant.

  • Reassign

    Reassign the task to the actual users assigned to this task

  • Error task

    Indicate that this task cannot be rectified.

If there are any errors in evaluating the error assignees, the task is marked as being in error.

This dialog box enables you to specify the users or groups to whom the task is assigned if an error in assignment has occurred.

To configure the error assignee:

  1. Click the Add icon to assign reviewers or error assignees, as shown in Figure 29-46.

    Figure 29-46 Error Assignment Details

    Description of Figure 29-46 follows
    Description of "Figure 29-46 Error Assignment Details"
  2. Click the Add icon and select a user, group, or application role to participate in this task.

    The Identification Type column of the Starting Participant table displays your selection of user, group, or application role.

  3. See Step 5 through 7 of Creating a Single Task Participant List for instructions on selecting a user, group, or application role.
  4. If you are using parallel participant types, you can specify where to store the subtask payload with the following options.

    • Use server settings

      The SharePayloadAcrossAllParallelApprovers System MBean Browser boolean property in Oracle Enterprise Manager Fusion Middleware Control determines whether to share the payload of subtasks in the root task. By default, this property is set to true. If set to true, the All task participants share the same payload (better performance and less storage space) option is used. If this property is set to false, the Each parallel participant has a local copy of the payload option is used. To change the settings, see How to Change Server Settings.

    • All task participants share the same payload (better performance and less storage space)

      The payload for the subtasks is stored in their root task. This situation means that the payload of the root task is shared across all its subtasks. Internally, this option provides better performance and storage space consumption. Less storage space is consumed because the payload of the root task is shared across all its subtasks.

    • Each parallel participant has a local copy of the payload

      Each subtask has its own copy of the payload. Internally, this option provides lesser performance and storage space consumption because more storage space is consumed.

  5. Click OK.

For more information about users, groups, or application roles, see Task Assignment and Routing.