Notifications

On this page you can make all settings for the display and behavior of notifications. Some settings affect all notification types, others relate to certain types such as alarms or user reports.

Notifications

Notify current alarm chain user by email

If this option is activated, the user who is responsible for an alarm according to the currently running alarm chain receives an email if the device acknowledges the alarm of its own accord.

Notify the author of a user report by email

If one of these options is enabled, the sender of a user report (usually the tenant) will be notified by email when the respective situation occurs. This option should be enabled if you want to be able to send comments entered when user reports are closed to the sender of the ticket to inform them about the measures taken.

Ticket colors

For each individual ticket type, specify the color in which the tickets of this type are to be displayed in the ticket list (see chapter Ticket list) or in the Avelon Heads-up! app.

System alarms

Depending on the system, you can configure different system alarms. For each type of alarm, you can define whether a ticket should be created and whether an alarm chain should be triggered. If an alarm chain is selected, notifications will be sent to users in this alarm chain.

Note that system notifications will generate a specific type of ticket. If you want to see tickets of this type, you will need to enable them on the ticket list or in Avelon Heads-up!.

Disk space

Only available on Alcedo Inhouse. This alarm will be triggered when the available disk space on any of the system partitions falls below the specified threshold. If you select a threshold from the dropdown, it will also be displayed as a dotted line on the partition overview.

Server TLS certificate

Only available on Alcedo Inhouse. This alarm will be triggered before the TLS certificate of the server is about to expire. You can select the desired advance notification period in the dropdown.

Beetle TLS certificates

This alarm will be triggered before the TLS and OpenVPN certificates of a Beetle are about to expire. You can select the desired advance notification period in the dropdown.

Data exchange

This alarm will be triggered whenever there is an issue during one of the data imports or exports. Alarms for imports and exports can be configured separately, but they will apply to all imports and all exports, respectively.

Notification texts

Change the text blocks used by the system in emails. To do this, first select the appropriate notification type and language, and then edit the text in the Subject field and the text field below it.

Warning

Make sure that you make any changes on both the HTML tab and the Text tab. Emails are always sent with both variants, and the settings of the recipient’s email program determine whether the formatted message or the plain text message is displayed.

The following notification types are available:

  • Device Alarm: New alarm (sent to alarm chain user)

  • Device Alarm: Acknowledgment (sent to alarm chain user)

  • User Report: New report (sent to alarm chain user)

  • User Report: Confirmation (sent to original author)

  • User Report: Status changed (sent to original author)

  • User Report: Responsibility changed (sent to original author)

  • User Report: Responsibility changed (sent to new reponsible)

  • User Report: Ticket updated (sent to current responsible)

  • User Report: Ticket closed (sent to original author)

  • Final report (sent to observer)

You can reset a notification text to its standard version by clicking on Reset Template.

The following special expressions are available within the subject and notification text. These are replaced dynamically by the system at runtime:

Placeholders

Expression

Meaning

All alarm types

{ticketId}

The unique ID of the ticket.

{date}

The current date.

{time}

The current time.

{clientName}

The name of the client account from which the alarm was triggered. Can be configured in the Settings.

{companyName}

The name of the company. Has the same value as {clientName} by default, but can be configured in the Branding if you want to use a company name in your emails that is different from the client name.

{domain}

The domain name from which the alarm was sent.

{loginURL}

The URL that the recipient of the message can open to log in to the system.

Device alarms

{prefix}

The prefix for alarms. Available only in in-house systems where the prefix is configured accordingly.

{title}

The subject for alarm reports (“Alarm report” in the respective language of the recipient).

{ticketLabel}

The alarm text, which is also contained in the corresponding ticket.

{locationLabel}

The name of the Beetle from which the alarm was sent.

{serialnumber}

The serial number of the Beetle from which the alarm was sent.

{dataPointLabel}

The name or designation of the data point that triggered the alarm.

{systemName}

The system name (AKS code) of the data point that triggered the alarm.

{realEstates}

The real estate or real estates to which the ticket refers. This corresponds to all real estates that have at least one data point filter assigned which contains the alarm data point.

{buildings}

The building or buildings to which the ticket refers. This corresponds to all buildings that have at least one data point filter assigned which contains the alarm data point.

{alertingTag}

The custom flag that was configured in the alerting of the data point that triggered the alarm. This allows different alarm texts for different alarm conditions to be defined for the same data point. For information on how to set custom flags, see paragraph “Settings” in Manage alerting.

User reports

{propertyAndBuildingName}

The name of the real estate and/or building that is the subject of the user report.

{senderName}

The name of the tenant or sender of the user report.

{senderPhone}

The telephone number of the tenant or sender of the user report.

{senderEmail}

The email address of the tenant or sender of the user report.

{message}

The message from the tenant or sender of the user report.

{comment}

The comment entered when the ticket was closed.

{responsible}

The name of the responsible person to whom the user report is currently assigned for processing.

{dueDate}

The date by which this ticket should be completed.

{nrOfAttachments}

The number of files that are currently attached to this ticket.

{changedFields}

The names of the fields that were modified by a user.

{user}

The user who modified the ticket.

Alarm texts

Change the text blocks that are used by the system in alarm messages. To do this, first select the appropriate alarm type and language, and then edit the text in the text fields below.

Alarm Template

Text template that is used for alarm messages.

Acknowledged Alarm Template

Text template that is used for alarm acknowledgments.

The following special expressions are available within the template text. These are replaced dynamically by the system at runtime:

Placeholders

Expression

Meaning

General

{message}

The generated message.

{alertingTag}

The tag that was defined on the alerting.

Alarm state

{fromState}

The alarm state prior to the intrinsic alarm.

{toState}

The new alarm state.

{what}

Notification type: One of ALARM, EVENT, ACK_NOTIFICATION.

Data point

{busAddress}

The bus address of the data point.

{description}

The description of the data point.

{deviceId}

The BACnet device ID.

{instance}

The BACnet instance number.

{object}

The BACnet object type.

{systemName}

The system name of the data point.

Device

{deviceName}

The label of the unreachable device (for alarm type Device Failure only).

{serialnumber}

The serial number of the device (for alarm type Device Failure only).

Substitution

Additionally, a regular expression and replacement pattern can be added to any placeholder in the following form:

{name|search|replace}
Example

Input

Placeholder values

Result

{systemName|_|-}

systemName = A_B_C

A-B-C

{systemName|(.*)_(.*)_(.*)|$1-$2.$3}

systemName = A_B_C

A-B.C

Warning

The regular expressions in name, search and replace must not contain curly braces {, } or pipes |, as these characters are reserved for the search-replace expression delimiters. To check for a specific amount of characters, you have to repeat the pattern, e.g. \d\d\d instead of \d{3}.

Conditional strings

Different strings can be used depending on the value of a certain placeholder. Conditional strings can be defined using the following syntax:

(?<name>=<regex>)(<A>)(<B>)

If the value of the placeholder named <name> matches the regular expression <regex>, the <A> is used. Otherwise, the <B> is used (also if the regular expression is invalid). The entire string must match the syntax above.

Example

Input

Placeholder values

Result

 
(?message=.*[a-z]+-[0-9]{2}.*)({message})(Alarm from {systemname})
systemname = XXX-01
message = Alarm from XXX-01

Alarm from XXX-01

 
(?message=.*[a-z]+-[0-9]{2}.*)({message})(Alarm from {systemname})
systemname = XXX-02
message = Alarm

Alarm from XXX-02