1. Implementing Product Management
  2. Task Assignment and Routing

Task Assignment and Routing

The BPM Worklist supports declarative assignment and routing of tasks to a single user or group. Additionally, pattern-based support is available for scenarios that require detailed task assignment and routing.

Stage

A stage is a way of organizing the approval process for blocks of participant types. In the Product Development and Product Hub work areas, there is only on stage and it's in a parallel mode. In the parallel mode, the task gets assigned and notifications are sent to all participants at the same time. Within each stage, you can have one or more blocks of participant types. It is recommended not to modify the default settings in stage.

Participant

A participant is a user or set of users in the assignment and routing policy definition.

Participant Type

A participant type corresponds to a user or group. The workflow supports declarative patterns for common routing scenarios such as management chain, and group vote. The following participant types are available:

  • Single approver: The participant maps to a user or group.

    For example, a vacation request is assigned to a manager. The manager must act on the request three days before the vacation starts. If the manager formally approves or rejects the request, the employee is notified about the decision. If the manager doesn't act on the request, the request is treated as rejected and actions are similar to a formal rejection.

  • Parallel: The participant indicates that a set of people must work in parallel. This pattern is commonly used for voting.

    For example, multiple users in a hiring scenario must vote to hire or reject an applicant. You specify the voting percentage that is needed for the outcome to take effect, such as a majority vote or unanimous vote.

  • FYI (For Your Information): Corresponds to a single user, group, or role. This pattern indicates that the participant just receives a notification task and the business process doesn't wait for the participant's response. Participants can't directly impact the outcome of a task, however in some cases can provide comments or add attachments.

    For example, a regional sales office is notified that a product has been approved by the regional manager and is being passed on to the state wide manager for approval or rejection. FYI participants can't directly impact the product approval. They can only provide comments or add attachments.