Configuring notifications in the activity
Prerequisites
- Access to the Process (PM063) menu.
- Previously created and modeled process.
- User activity, system activity, or decision added to the process flowchart.
Introduction
Notification configuration defines the activity/decision events that will generate notifications and the users to which they will be sent.
See how to configure this feature:
Configuring notifications
1. On the activity/decision data screen, click on Configurations > Notification.
2. The notification configuration screen will be opened.
3. In the Notified tab, define which events will generate notifications and who will be notified by them. To do so, click on the 
button.
4. On the screen that will be displayed, configure the following fields:
Define the user group that will be notified:
| User | A specific user will receive the notifications. Search filters will be enabled so that the intended user can be located more easily. |
| Department | The users of a specific department in the organization will receive the notification. Search filters will be enabled so that the intended department can be located more easily. |
| Position | The users who exercise a determined position in the organization will receive the notification. Search filters will be enabled so that the intended position can be located more easily. |
| Department/Position | The users who exercise a position in a determined department in the organization will receive the notification. Search filters will be enabled so that the intended department and position can be located more easily. |
| Team | The members of a determined team will receive the notification. Search filters will be enabled so that the intended team can be located more easily. |
| Starter | The process starter will receive the notification. |
| Starter leader | The leader of the process starter will receive the notification. |
| Executor | The activity executor will receive the notifications. |
| Executor leader | The leader of the activity executor will receive the notifications. |
| Process manager | The process manager will receive the notification. |
| Instance manager | The instance manager will receive the notification. |
| Requester | The instance requester will receive the notification. |
| Attribute - User name | The notification will be sent to the user whose name has been entered in a certain attribute of the instance. Search filters will be enabled so that the intended attribute can be located more easily. |
| Attribute - User ID | The notification will be sent to the user whose ID has been entered in a certain attribute of the instance. Search filters will be enabled so that the intended attribute can be located more easily. |
| Attribute - E-mail | The notification will be sent to the user whose e-mail has been entered in a certain attribute of the instance. Search filters will be enabled so that the intended attribute can be located more easily. |
| Specific e-mail | The notification will be sent to a specific e-mail. Enter the e-mail that will receive the notification in the search filter that will be enabled for completion. |
| Form field - User name | The notification will be sent to the user whose name has been entered in a certain field of the instance form. Search filters will be enabled so that the table and the field of the intended form can be located more easily. |
| Form field - User ID | The notification will be sent to the user whose ID has been entered in a certain field of the instance form. Search filters will be enabled so that the table and the field of the intended form can be located more easily. |
| Form field - E-mail address | The notification will be sent to the user whose e-mail has been entered in a certain field of the instance form. Search filters will be enabled so that the table and the field of the intended form can be located more easily. |
Define whether the user or group selected in the previous field will have permission to receive event notifications:
| Notify | If this option is selected, the user will receive the notification for the activity event. |
| Do not notify | If this option is selected, the user will not receive the notification for the activity event. |
Select which events will generate notifications:
| Activity start | If this option is checked, as soon as the activity is enabled, a notification of the activity start will be sent. |
| Activity end | If this option is checked, as soon as the activity is closed, a notification of the activity end will be sent. |
| Due date alert | If this option is checked, as the activity's end date approaches, an activity due date alert notification will be sent. When this option is checked, the Due date alert section will be enabled in the Configuration tab, allowing you to define the amount of days prior to the due date the notification will be sent, as well as the notification recurrence. |
| Past due alert | If this option is checked, as soon as the activity is past due, a past due alert notification will be sent. When this option is checked, the Past due alert section will be enabled in the Configuration tab, allowing you to define the notification recurrence. |
Lastly, use the fields in the Filter section to locate the users or user groups to be notified. The fields will be enabled according to the previously selected notified user type.
5. After filling out the fields, click on 
.
Repeat steps 4 and 5 to record as many events and notified users as necessary.
6. On the notification configuration screen, access the Configuration tab.
7. Configure the available fields:
Due date alert
This section will only be enabled if, in the Notified tab, there is a notification record configured with the Due date alert event. In that case, fill out the following fields:
| Deadline is before the due date | Enter the deadline before the due date of the activity so that the system sends a notification via e-mail to alert that the activity's due date is near. 1: The activity duration time is defined in the Duration (General data) section on the activity data screen. For example, if the activity duration is planned for 4 hours and a deadline of 30 minutes is set in this field, the notification will be sent 30 minutes before the 4 hours of the planned duration are completed, that is, 3h30min after the activity is enabled for execution, according to the configured calendar. 2. It will not be possible to select a time shorter than 15 minutes as the due date. |
| Recurrence | Check this field so that, when the due date alert period starts, notifications are sent, informing that the execution deadline is approaching. Every: configure in this field the frequency with which the notifications will be sent. Considering the example from the previous field, by defining the notification sending frequency to be every 10 minutes, three e-mails will be sent: the first, 3h30min after the start (enabling for execution) of the activity; the second, 3h40min after the start; and the third, 3h50min after the start. It will not be possible to select a time shorter than 15 minutes as recurrence interval. Total notifications: enter the total number of notifications that can be sent. For example: up to 5 notifications. |
Past due alert
This section will only be enabled if, in the Notified tab, there is a notification record configured with the Past due alert event. In that case, fill out the following fields:
| Recurrence | Check this field so that, as soon as the activity becomes past due, notifications are sent, informing that its execution deadline has expired and it is past due. Every: configure in this field the frequency with which the notifications will be sent. For example, by defining the notification sending frequency to be every 4 hours, as soon as the activity is past due, an e-mail will be sent every 4 hours until the notification total is reached, the activity is executed or its deadline is redefined by the instance/process manager. It will not be possible to select a time shorter than 15 minutes as recurrence interval. Total notifications: enter the total number of notifications that can be sent. For example: up to 5 notifications. |
Content
Through this section, it is possible to define the template and the content to be displayed in the notification e-mail of each activity event. To do that, check the Content will be read from HTML file option and define the template to be used in each event.
| Activity start | Define, in this field, which template will be used in the e-mail that notifies that the activity has been enabled for execution. If no templates are selected, the system will use the default notification template. |
| Activity end | Define, in this field, which template will be used in the e-mail that notifies that the activity has been closed. If no templates are selected, the system will use the default notification template. |
| Due date alert | Define, in this field, which template will be used in the e-mail that notifies that the activity execution deadline is close to due date. If no templates are selected, the system will use the default notification template. |
| Past due alert | Define, in this field, which template will be used in the e-mail that notifies that the activity execution is past due. If no templates are selected, the system will use the default notification template. |
8. After completing the fields, click on Save and exit.
Conclusion
Thus, the activity/decision notifications have been successfully configured!