From the transaction /EDGE/TC_AL_01, the user will have access to the alarm configuration.
PRODUCT DEFINITION
The user will have access to the list of products for which he can configure the necessary alarms.
It will be necessary to select a product to configure each of the available sections.
CHANNEL DEFINITION
The user must configure the channels required for the parameterization of their alarms
For more details, you can go to the Channels section.
ALARM TRIGGERS
After selecting the required product, from the Alarm Triggers section, the user can view the configured triggers in the product and also add, modify, or delete any necessary triggers.
The 'Alarm triggers' folder has two (2) different views. One exclusively for the Core - b+ Electronic invoice product (eInvoice), and the other for the rest of the products (e.g., LROE - b+ LROE).
→ Core - b+ Electronic invoice
→ LROE - b+ LROE
For more details, you can go to the Alarm triggers section.
RECIPIENT LIST
From this section, the user must configure the lists of users who will receive the notifications of the alarms to which they are assigned.
The configuration of the lists must be done by role or by class, not allowing the configuration of both parameters for a list of recipients.
For more details, you can go to the Recipient list section.
ALARMS
From the Alarms section, the user can configure the required alarms.
An alarm can be defined for each product object and type of alarm, defining in them the channels, recipients and escalations that it requires, as well as the body of the message that you have defined for each of them.
From this section, the user can activate or deactivate the corresponding alarms. It should be taken into account that if an alarm is no longer necessary, the user can deactivate or delete it, not allowing modifications to them.
The 'No. Escal. Notices' field does not differentiate between empty and zero (0) values. Therefore, if the 'Escalation list' field is filled, a value different from empty and greater than zero (0) must be indicated in the 'No. Escal. Notices' field.
Starting from version 1.3, a new column is available in the 'Alarms' section, the 'Max Notif. No.' column, through which you can specify the maximum number of notifications an instance can send. If the field is left empty, notifications from the instance will be sent indefinitely.
Additionally, the value to be entered in the 'Max Notif. No.' field cannot be less than the value indicated in the 'No. Escal. Notices' field if the 'Escalation list' field has been filled.
ALARM CONDITIONS
To define the conditions of each of the alarms, the user must select the corresponding alarm and access the conditions section
From this section, the fields that will determine the launch of each of the alarms will be defined, as well as the values for each of the conditions.
You can define as many conditions as necessary for each type of alarm, taking into account that the seats must meet each and every one of the conditions determined for the alarm to be launched.
INITIAL VALUES - FINAL VALUES
After defining the conditions, the user must define the initial and final values that will determine the start and end ranges for an alarm to turn on or off.
For each type of alarm there are certain values.
For more details on the alarms section, you can access the link: Alarms