Notifications
Notifications |
Notifications are intended to provide information on important developments in the field of energy management. For example, a workflow could monitor consumption and generate a notification if a threshold is exceeded.
Unlike system notifications, which inform administrators of system malfunctions, these notifications relate exclusively to energy management.
Required permissions
To view notifications, the project, location or medium permission “Notifications” with “Read” access is required. To view, create or edit notifications, the project, location or medium permission “Notifications” with “Edit” access is required. To delete a notification, the project, location or medium permission “Notifications” with “Full” access is required. |
The concept of these notifications is based on the following considerations:
Plain text: Each notification source can output individually defined notification texts. For example, a workflow used to monitor consumption could contain text along the lines of “The planned weekly electricity consumption limit for Hall 3 has been exceeded...”
Repeat counter instead of a flood of data: notifications that already exist are not generated again; instead, their counter is incremented. In practice, it is quite common for notifications to be pending and thus to generate an entry on a regular basis, for example, every day. Before long, important events are overlooked or even ignored amidst the sheer volume of notifications.
Status: Notifications can have the statuses “New” and “Confirmed”. Confirmation by a user is logged.
Processing via a measure: A notification can be converted into a measure with a single click of the mouse. This allows you to organise the work required to rectify the issue.
Create / generate notifications
Notifications are typically created and updated by automation objects / workflows. Nevertheless, a new notification can be created using the button.
Properties
ID | Number – Unique notification ID for identification purposes. This is generated automatically when the initial notification is created and cannot be edited. |
Initial notification | Date/Time – Time of the initial notification. This date/time is not overwritten if the same notification is triggered repeatedly. |
Last notification | Date/Time – Time of the last notification. The date/time is overwritten if the same notification is triggered repeatedly. |
Notification text / title | Text – As informative a statement as possible. Those responsible for energy management should be able to gain an immediate overview of the issue from the notification text. |
Description | Text – Please provide as detailed a description as possible of the reason for the notification. It can also be edited by the user at any time and, for example, further information can be added. |
Status | Selection – New or Confirmed
|
Confirm now | Action – A one-off action in which the currently logged-in user confirms the notification. See the property “Status” |
Confirmed by | Username (for display only) – Shows the user who confirmed the notification. |
Confirmed on | Date / Time (display only) – Shows the time of confirmation. |
Priority | Selection – Priority of the notification. 0 (no priority) up to 6 (very high priority). |
Repetitions | Count (for display only) – The number of times this notification has been triggered since the initial notification. |
Selecting and assigning tags enables you to filter and sort lists. | |
| List – Displays the assigned workflows and services. |
List – Displays the links associated with visual energy objects. |