Identify the escalation and notification mechanisms available for human tasks
An escalation is a notification that is sent out when an expected result from a task has not been achieved within a set period of time. For example, an escalation could be used to alert a manager when a staff member is unable to complete a task by the deadline.
Note: The duration value for a human task is separate from the escalation function. Although the duration value will indicate when a task is due, it will NOT trigger an escalation.
When you create an escalation for your human task, you will need to know the following ahead of time:
- The state that the task is in when the escalation period begins (this is also known as the activation state).
- The state that you want the task to be in when the escalation period ends (it is when the task is NOT in this expected state at the end of the period that the actual escalation is thrown).
- The escalation period, or how long you want the system to wait for the expected state to be reached before notification occurs.
- The manner in which the notification takes place.
If you are creating more than one escalation for an activation state, you have two options:
- Chained escalation In a chained escalation, the escalations are executed sequentially, or one after the other. In such a case, the first escalation must fully complete before the next one is initiated.
- Parallel escalation With a parallel escalation, the escalations are in two separate paths, and are executed at the same time (or in accordance with the escalate after setting as described below).
Related links
- Escalations (wps612)
- Human tasks (IBM Guided Tour)
No comments:
Post a Comment