Notifications

Notifications are configured at the Organization level and are delivered as email. Two kinds of notification are supported today.

​

Anomaly digests

An anomaly digest sends a summary of anomalies raised within a configured time interval. Each digest is configured with:

• An optional System Integration scope, restricting the digest to anomalies tied to that integration
• A list of anomaly codes to include
• A digest interval that controls how often the digest is sent
• A list of recipient Users

This makes it possible to route specific kinds of issues to the people best equipped to deal with them, without requiring anyone to monitor the backoffice continuously.

​

System Data Events

A System Data Events digest lists entities that were created or updated during the configured interval. Currently this is supported for the Employee domain only. For updated employees, the digest can also say what changed. The Change details for updated employees setting has three choices:

• None lists each updated employee without details.
• Twine properties that changed lists the Twine properties that changed on each employee, such as “Email 1” or “Cost Center 1”. This needs “Track employee attribute changes” switched on, on the organization’s “Pipeline safety” card.
• Target properties that were written lists, per target system, the fields Twine wrote for each employee, such as “Full-time salary” or a dimension like “Kostnadsställe”. You can limit the list to chosen target systems. Changes Twine computed but held back, for example a suppressed section, are listed as “not sent”. A target system that does not record its changes is named once at the top.

The digest never includes values, only the names of the fields that changed. For instructions on configuring notifications in the UI, see Configuring Notifications.