Notification events in processes
Item notifications
The item notifications listed below are predefined by the system, based on which you can create new custom notifications and configure trigger conditions, recipients, and content of your choice. These predefined notifications cannot be deleted but can only be toggled on or off.
S.no. |
Notification event |
Trigger |
Recipient |
1 |
Item assigned |
When an item is assigned to a user |
Assignee |
2 |
Item sent back |
When an item is sent back to the previous step by a step assignee |
Assignee |
3 |
Item completed |
When an item completes its workflow |
Initiator |
4 |
Item rejected |
When an item is rejected by a step assignee |
Initiator |
5 |
Item withdrawn by the initiator |
When an item is withdrawn by an initiator |
Assignee |
6 |
Item reassigned |
When an item is reassigned to a user |
Assignee |
7 |
Item breached its deadline |
When an item breaches its deadline |
Assignee |
Note:
Notifications for all process related steps that is sent to the respective user will be redirected to the delegated user (if task delegation is ON), but Item completed (S.no. 3 in the above chart) notification alone will be received only by the requestor or initiator of the item, even if the initiator/requestor has delegated their task to another user .
Process management notifications
S.no. |
Notification event |
Trigger |
Recipient |
1 |
Member added to the process |
When a member is added to the process |
New member |
2 |
Developer added to the process |
When a developer is added to the process |
New developer |
3 |
Report Admin added to the process |
When a Report Admin is added to the process |
New Report Admin |
4 |
Data Admin added to the process |
When a Data Admin is added to the process |
New Data Admin |
5 |
Admin added to the process |
When an admin is added to the process |
New admin |
6 |
Process renamed |
When a process is renamed |
All members |
7 |
Published new version of a process |
When a new version of a process is published |
Admins and developers |