When to Send:
Send when: This specifies the condition that must be met for the notification to be sent. For example, it could be when a specific event is fired, such as “request.item.approved” or “event.is_canceled”.
Advanced condition: This allows for more complex conditions using scripts. You can use global variables like current (the current record) and event (the event that triggered the notification) to define when the notification should be sent.
Who Will Receive:
This section defines the recipients of the notification. It can include specific users, groups, or roles within the organization.
What It Will Contain:
This section details the content of the notification, including the subject, message body, and any attachments. You can use templates and variables to customize the content dynamically based on the event and record data.
When Notifications are Triggered
Notifications in ServiceNow are triggered based on the conditions specified in the “When to Send” section. Here are some common scenarios:
Event-based triggers: Notifications can be sent when specific events occur, such as the approval of a request or the cancellation of an event. For example, if the event name is “request.item.approved”, the notification will be sent when a request item is approved.
Condition-based triggers: Using the advanced condition script, you can define more complex conditions that must be met for the notification to be sent. This could include changes in field values, specific system properties, or other criteria.
Example
Let’s say you have a notification configured to send an email when a catalog approval request is approved. The configuration might look like this:
Send when: Event is fired
Event name: request.item.approved
Conditions: (Optional) Additional filter conditions can be added to further refine when the notification is sent.
In this case, whenever a catalog approval request is approved, the notification will be triggered, and the specified recipients will receive the email with the defined content.
