...
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+ dgtal Ticketbai 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.
Annotation expiration alarms
To parameterize an alarm of this type, you will have to create an entry in this table and choose the type of alarm "EXPIRATION" and the product object that applies, for example "ANNOTATION".
...
Entries can be included in the alarm conditions table to set invoice conditions. For example, the company code, or any other field that belongs to the extraction table of the object
...
In this way, several expiration alarms can be created by setting each of them an alarm condition, for example a specific company. (In case it is necessary, for example, create several expiration alarms to send to different recipients depending on the company).
In the table of initial values, a single entry will have to be created indicating the days (calendar) that have to pass for an annotation (not sent) to trigger an expiration alarm along with the factory calendar (if required).
...
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 annotations. So, for these states, it will not create expiration alarms and if at some point they were created, when the annotations reach these states, they will be turned off.
...
Status alarms for annotation
To have status alarms for annotations, an entry must be created in this table for the "STATUS" alarm type and the object of the applicable product, for example "ANNOTATION".
...
Entries can be included in the alarm condition table to set conditions for annotations. For example, the company code, or any other field that belongs to the extraction table of the object
In this way, several status alarms can be created by setting an alarm condition in each one, for example a specific company.
...
In the table of initial values, it will be necessary to indicate the different states for which the alarm is to be triggered. The states indicated in these inputs will be the ones that create alarms.
...
In the table of final values, it will be necessary to indicate all the states of the seat that will turn off the alarm.
...
Status alarms for batches
To have status alarms for batches of annotations, an entry must be created in this table for the type of alarm "STATUS" and the object for the product "LOT".
...
In the table of alarm conditions, entries may be included to set conditions for the batches. For example, the company code, or any other field that belongs to the extraction table of the object.
In this way, several status alarms can be created by setting an alarm condition in each one, for example a specific company.
In the table of initial values, it will be necessary to indicate the different states for which the alarm is to be triggered. The states indicated in these inputs will be the ones that create alarms.
In the table of final values, it will be necessary to indicate all the states of the batch that will turn off the alarm.
The possible statuses for annotations and batches are listed below.
ANNOTATIONS
Status | Description |
|---|---|
1000 | Created |
1001 | Corrected |
1002 | Detained |
1010 | Included in lot |
1011 | Mapping error |
1020 | Accepted with errors |
1030 | Correct |
1032 | Incorrect |
LOTS
Status | Description |
|---|---|
2000 | Lot created |
2001 | Error mapping records |
2002 | Transform to XML failed |
2010 | Error appending XML request |
2011 | Send failed |
2012 | Error appending response XML |
2013 | Error processing response |
2020 | Processing response |
2021 | Correct |
2022 | Partially correct |
2023 | Incorrect |
Error code alarms for annotations
To have error code alarms for annotations, an entry must be created in this table for the type of alarm "ERROR CODE" and the product object "ANNOTATION".
...
In the table of alarm conditions, entries can be included to set conditions for the annotations. For example, the company code, or any other field that belongs to the extraction table of the object
In this way, several error code alarms can be created by setting an alarm condition in each one, for example a specific company.
...
In the table of initial values, it will be necessary to indicate the different error codes for which the alarm is to be triggered. The error codes indicated in these inputs will be the ones that create alarms.
...
In the table of final values, it will be necessary to indicate all the states of the annotation that will turn off the alarm.
...