Skip to main content

Manage notifications

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 for the group's type, and each trigger sends its actions when it fires: an Email, an In-App notification in each recipient's feed, or an OpCon Event submitted back into the platform. Groups live on Design › Notifications.

Notes
  • A group needs a name and at least one member before it saves; a group with every trigger off is valid, and is how you quieten it for maintenance.
  • Name patterns match case-sensitively.
  • 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 and fails the send.
  • In a Job or Workflow group, an email recipient can name a property set on the job, its workflow or its agent. A property's value may separate addresses with ; or ,.
  • Only agent and relay Online/Offline repeats in the same 5-minute block of clock time collapse into one notification; every other trigger notifies each time.
  • In-App roles are matched by name.
  • An encrypted property shows as ******** in an Email or In-App message, and naming a property you cannot view stops the action saving.
Watch out
  • Test sends real notifications. An OpCon Event action in a test really runs, and a timed-out test may still arrive, so testing again can send twice.
  • A trigger switched on with no enabled action records its notification as sent, and nobody is told.
  • An OpCon Event action keeps running after its author loses the permission it needs.