From the transaction /EDGE/TC_AL_01, the user will have access to the alarm configuration.
...
| Info |
|---|
The 'Alarm triggers' folder has two (2) different views. One exclusively for the
|
→ Core - b+ Electronic invoice
...
→ OSAT - b+ TicketBAI
...
→ LROE - b+ LROE
...
For more details, you can go to the Alarm triggers section.
...
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.
...
| Info |
|---|
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. |
| Info |
|---|
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
...