Notify Recipients
- 27 May 2024
- 3 Minutes to read
- Print
- PDF
Notify Recipients
- Updated on 27 May 2024
- 3 Minutes to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The third action in the Custom Scheduler is Notify Recipients. This action allows to send notification to the respective recipient at any point of time without any delay.
Use Case User Persona: Analyst | Solution |
NovaTech has certain tasks which are moved to pending status with reason "awaiting user response". These have not been updated for 5 days. The Analyst wants to update the status of these tickets to cancel and send a notification to the callers on the status. The Analyst wants to reduce manual efforts in this task. | To achieve this, Sam an Application Designer configures the scheduler to auto cancel the incident and send a notification to callers for individual records. The scheduler runs the job and cancels all the tickets moved to pending status with the reason "awaiting user response" and not updated for 5 days. Simultaneously a notification is sent to the caller that these tickets have been cancelled. |
Configure Notify Recipients
The action Notify Recipients is configured by defining Notification Frequency Per Record, Medium, Templates and Recipient records. For more information, refer the field description table below.
Figure: Configure Notify Recipients
Field | Description |
Notification Frequency per Record* | Choose the number of times notification has to be triggered for each record. Note The number of times selected should be less than the scheduler occurrence. |
Records to be sent per Notification* | Choose how many records will be sent per notification. This field is only available with the number of records in the condition stepper is greater than 1. Single Record per Notification - A single record will be sent with each notification. Summary of Records per Notification - A summarized form will be sent per notification. |
Notification | |
Select Notification Template | Specify the template to be selected. For example, Incident Reopened: To Requestor, Cancelled Incident: To Analyst. Note: Click the Information icon if a new template has to be created. |
Medium | Specify the medium for notification to be chosen from the drop down menu. For example, Email, SMS, Microsoft Teams, Web App. A preview of the notification is available for the user, when they click on the following system message. |
Recipients | |
Recipient | Choose the recipients that need to be notified of the task being scheduled. User - Type the name of the user you want to add as a recipient and select the searched name from the result section. All the active users added in the application are displayed in this type of recipient. This recipient is selected, by default. Static Group - All the users configured in the Static Group created are displayed in this section based on the selected Application. User Attribute Group - All the users configured in the User Attribute Group created are displayed in this section based on the attributes. Dynamic Group - All the users configured in the Dynamic Group based on the specific transaction table and module are displayed in this list. Approver - In the "Approver" recipient type, you have the option to choose the Current Approver or All Approvers from the provided list. This action triggers a notification to the current approver. Roles - You can select to search the user based on their roles. The listed fields are displayed as below.
Custom Email ID - |
To | The "To" field is used to specify the primary recipients of the notification. These are the individuals or groups that the sender expects to read and respond. Include the main recipients who are directly involved or expected to take action. Note When the Current Approver or By Role is being added, then no additional recipient can be added to the 'To' field. When we try to add another role in the "To" field, the following validation message appears. |
Send all the records or group records* | When the "To" recipient is selected "By Role" or "By User Properties", then the field is activated. Send all records - We can send all the records matching the condition Grouped records - We can group records by persona |
Notifications per Recipient | Specify the number of times notification needs to be sent per recipient. This field has been provided to ensure that all the respective recipients get notified based on their roles. Note This field is activated when the recipient is selected as "Approver". |
Cc | The "CC" field is used to include additional recipients who may be interested in the notification content. CC recipients are not the main addressees but are still receiving a copy for information. Inform others or keep them in the loop without making them the primary audience. |
Bcc | The "BCC" field is used to include recipients whose identities should remain hidden from other recipients. This can be useful when the sender wants to protect the privacy of certain individuals without revealing everyone's email addresses. |
Was this article helpful?