From the product, 4 triggers with their full functionality are offered as standard so that they can be used directly in the product.
These triggers have the following parameterization and can be copied or adapted as detailed in the following table:
| Alarm type |
| Field starts trigger | Field starts trigger | Final value type | Field ends trigger | Field ends trigger |
|---|---|---|---|---|---|---|---|
ANNOTATION | CADUCIDAD | C |
| /EDGE/CL_LROE_DET_CADUC_ANOTAC | F | STATUS |
|
ANNOTATION | CÓD_ERROR | F | COD_ERROR_ALARMA |
| F | STATUS |
|
ANNOTATION | STATUS | F | STATUS |
| F | STATUS |
|
LOT | STATUS | F | STATUS |
| F | STATUS |
|
ANNOTATION - EXPIRY
These triggers are created for expiration alarms for annotations. The trigger type is per class.
The alarms will turn off from the value of the field parameterized in "Field ends trigger", in this case the "STATUS" field of the annotation.
ANNOTATION - ERROR CODE
These triggers are created for alarms of annotations rejected with a response from the Foral through an error.
The field that starts the trigger will be the error code that is parameterized and the field that ends the trigger will be the "STATUS" field of the annotation.
ANNOTATION - STATUS
This trigger is parameterized for annotations, and it will be triggered from a specific state (alarms by state).
Both the alarm creation trigger and the alarm end trigger will be from the "STATUS" field of the annotation.
ANNOTATION - LOT
This trigger is parameterized for batches, and will be triggered from a specific status of the batch (status alarms).
Both the alarm creation trigger and the alarm end trigger will be from the "STATUS" field of the annotation.
Once the entry is created in this table, it cannot be modified. If you want to make any changes, you will have to delete the entry and create a new one.
What's more. a trigger input cannot be deleted if it is being used in an alarm.