Customizing Global Notifications Settings

Introduced in 8.5

Global notifications settings apply to both e-mail notifications and push notifications. These settings define the following:

  • How often to check the Notification Queue;
  • Whether to generate self-notifications;
  • How to process notifications with no recipients.

The default global notification settings are usually sufficient. However, you can customize them as follows:

  1. From the Sidebar, navigate to Notifications > Global Settings.

  2. The Automation Server regularly checks the notification queue and makes an attempt to send all pending messages. The default interval is 5 minutes (300 seconds). If needed, change the default interval in the Check notification queue every [n] second(s) field.

    NOTE: Each time the Automation Server checks the Notification Queue, Alloy Navigator Express logs a new record in the Outgoing Notifications Log. For details, see Alloy Navigator Express Logs.

  3. By default, the Alloy Navigator Express workflow mechanism has the self-notification option enabled. Self-notification means a notification to the person (technician) who performed a workflow Action which generated the notification.

    For example, when Assignee makes a change (e.g. adds a record to the Activity Log or completes the Ticket), the Automation Server notifies him or her about the performed change because the default business logic notifies the Assignee every time a ticket is updated.

    To avoid redundant self-notifications, select the Do not send notifications to users who trigger them check box.

    NOTE: This option affects only recipients specified in the To field of e-mail notifications. Selecting the Do not send notifications to users who trigger them check box does not prevent Alloy Navigator Express from sending self-notifications to recipients specified in CC and BCC fields. For details, see Customizing E-mail Notifications.

  4. Specify how to process notifications that have no recipients at the moment of sending. For example, this could happen when the recipient is specified as an expression, and that expression does not resolve to a valid value at runtime.
    • To mark such notifications as failed and leave them in the queue, click Mark the notification as failed and leave it in the queue. The Automation Server will attempt to send them again the next time the queue is checked.

    • To delete such notifications from the queue, click Delete the notification from the queue.

  5. Click Save on the Standard toolbar to save your changes.