Notifications
This module describes an electronic message sent automatically to recipients when an event happens on a content or a business object: state change of a lifecycle or run of a batch. The module defines the message; the lifecycle or the batch decide when it is sent.
Notifications apply to contents as well as to business objects (Case). A switch in the navigation bar moves from one configuration to the other.
Several notifications can coexist. The "+" icon adds a new one.
Recipients
Notification recipients: a user, a group or a metadata holding users or groups.
Allow external mail: allows including email addresses outside the directory among the recipients.
Message template
Depending on the platform configuration, the notification is delivered by email, by Teams notification, or by both at once. The title of this section adjusts accordingly.
Sender email address: without it, the default sender address of the platform is used.
Language: the message is entered for each language, chosen in the drop-down list.
Subject: subject of the message.
Body: text of the message.
The subject and the body accept wildcards, replaced on send by their value. To insert a metadata, use ${<aspect>.<metadata>}, for instance ${core.name} for the name of the document. The following wildcards are also available:
| Wildcard | Inserted value | Availability |
|---|---|---|
${recipient_name} | Name of the recipient | Contents and business objects |
${document_link} | Link to the content | Contents |
${data_object_link} | Link to the business object | Business objects (Case) |
Attach the content to the message
Add content as attachment: for a notification on a content that has formats, attaches it to the message. The format used is the one configured in the export flow.