This parameterization must be carried out in the project since its configuration is specific to the system and the requirements of the project itself.
This documentation page will explain possible examples of how to parameterize alarms for each type of triggers / alarms that are provided for the b + SILICIE product. It must be taken into account that this parameterization is provided from the product itself but that it can be adapted to the necessary criteria in each project.
Expiration alarms for seats.
To parameterize an alarm of this type, you will have to create an entry in this table and choose the type of alarm "EXPIRY" and product object "SEAT".
In the alarm conditions table you can include entries to set seat conditions. For example, the CAE of the seats, or any other field that belongs to the object's extraction table (/ edge / t_sl_901).
In this way, several expiration alarms can be created by setting an alarm condition in each one, for example a specific CAE. (In case it is necessary, for example, create several expiration alarms to send to different recipients depending on the CAE of the entries).
In the table of initial values, a single entry must be created indicating the days (calendar) that have to pass for a transaction (not sent) to trigger an expiration alarm.
In the table of final values, it will be necessary to indicate all the states that should not create expiration alarm, that is, final states of the entry. So, for these states, it will not create expiration alarms and if at some point they were created, when the seats reach these states, they will turn off. The different states for a seat can be consulted in the guide: