Updates that generate notifications
These scenarios describe the updates, which generate notifications,
and who receives the notifications, if notifications are set up.
If the resource who is performing the update is the resource who owns the task or is part of the team that owns the task, then they do not receive a notification.
| Scenario | Receiver of notification |
|---|---|
| Reassigned task at the team ownership level to a specific resource on the team | The resource to whom the task is assigned. |
| Reassigned task from a specific resource to another resource | Both resources. |
| A resource who owns a task reassigns it to the team | All team members. |
| A task that requires approval upon completion | The resource who is associated with the
first level of approval. If the level is set for team approval, then all
members of the team receive a notification. Subsequent approval level resources
receive a notification after approval by the previous approval level. Note: The notification is automatically created by Process Automation (IPA). If a resource does not have
their notifications turned on, they still receive a notification about tasks
that are awaiting their approval.
|
| Rejected task that requires approval | The resource owner of the task. |
| Completed task that is a prerequisite of another task | The resource owner of the task with the prerequisite. If the task with the prerequisite is only assigned to a team, then all of the team members receive a notification. |
| Voided task | The resource owner of the task receives a notification. If the task is only assigned to a team, then all of the team members receive a notification. |
| Reopened completed task | The resource task owner. |
| A process is completed when all of its detail tasks are completed. | After completion of a process, the individual owner of the process receives a notification. If the process is only assigned to a team, then all members receive a notification. |