Skip to main content

Notifications (groups, triggers, channels)

BETA Preview

This feature is still being finalized by Development.

In briefA notification group watches agents, relays, workflows or jobs, and tells people when one of them changes state. You switch on triggers from a fixed catalog for the group's type, and each trigger sends its actions once when it fires: an Email, an In-App notification in each recipient's feed, or an OpCon Event submitted back into the platform.

WhereDesign › Notifications lists the groups. New Notification Group creates one; a group's row menu offers Edit and Delete. The group dialog has two tabs, Select {type}(s) for its members and Triggers & Actions. Your own in-app notifications are behind the bell in the main header.

When

  • An agent or relay goes offline or comes back, or an agent is marked offline or draining.
  • A job fails, is late to start or finish, or runs past its Max Run Time.
  • A workflow starts, completes, or is placed on or released from hold.
  • Something should happen automatically when a trigger fires — restart a job, tag it, set a property.

To send mail from a job's own event without a group, use $NOTIFY:EMAIL instead. Escalation can't be set up in this interface.

How

  1. Go to Design › Notifications and select New Notification Group.
  2. Enter a Name and choose the Type. The type cannot be changed later.
  3. On the first tab, add at least one member: a named object, a Name Pattern, or for a Job group a Tag.
  4. On Triggers & Actions, switch on a trigger, add an action with + Action, and fill in its channel's fields.
  5. Use Test to send that trigger's actions now, then Save.

For the full steps, see Manage notifications.

Notes
  • Name patterns match case-sensitively: EOD-* does not match eod-close.
  • A saved change takes effect within about 5 seconds.
  • Each occurrence notifies; only agent and relay Online/Offline repeats in the same 5-minute block of clock time collapse into one notification.
  • A property token that can't be resolved arrives as its own name, and the message still goes out. An OpCon Event action is the exception: it refuses to send.
  • In a Job or Workflow notification, an email's To, Cc and Bcc can name a property set on the job, its workflow or its agent, captured when the event fired. A property's value may list addresses separated by ; or ,.
  • In-App roles are matched by name, so renaming a role stops delivery to it.
Watch out
  • A trigger that fires with no enabled action is recorded as SENT, and nobody is told.
  • A test is a real send. An OpCon Event in a test runs for real, and a timed-out test may still arrive, so testing again can send twice.
  • An encrypted property in an Email or In-App message shows as ********, and saving an action that names a property you cannot view is refused.
  • An OpCon Event action keeps firing after its author loses the permission it needs. Review these actions when you remove someone's access.