> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/acron-9.3/en/anlagenkonfiguration/fernbenachrichtigung/fb-ausloeser/register_ausloesebedingungen.md).
# Trigger conditions tab
### Trigger conditions tab
A trigger condition contains a process variable, the condition(s) for which the values of the process variable should be monitored, and a message text for the notification e-mail. Additionally, each condition can be activated or deactivated. Deactivated trigger conditions are not executed.
Note
A maximum of 25 objects for monitoring can be configured under Trigger conditions.
### Icons
| Icon | Group | Trigger |
| ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| !\[]\(../../../../.gitbook/assets/button green\_32.png) | All trigger conditions in the group are active and cannot be deactivated. | The trigger condition is active, it can be deactivated and edited. |
| !\[]\(../../../../.gitbook/assets/button green blass\_32.png) | | The trigger condition is active because the entire group is active. It cannot be deactivated or edited. |
| !\[]\(../../../../.gitbook/assets/button yellow\_32.png) | At least one trigger condition in the group is active - the trigger conditions in this group can be activated/deactivated. | |
| !\[]\(../../../../.gitbook/assets/button red1\_32.png) | All trigger conditions of the group are inactive - the trigger conditions can be activated and edited. | The trigger condition is inactive, it can be activated and edited. |
Info
!\[]\(../../../../.gitbook/assets/button green blass\_16.png) is not clickable. The status of the other buttons !\[]\(../../../../.gitbook/assets/button green\_16.png) !\[]\(../../../../.gitbook/assets/button yellow\_16.png) !\[]\(../../../../.gitbook/assets/button red1\_16.png) is changed by clicking on them.
**Process variable**
Name of the selected process variable
**Active**
Activate/deactivate individual process variables or the process variable group.
**Range limit shortfall**
Notification of range limit shortfalls
**Range limit exceeding**
Notification of range limit exceedings
**Value monitoring**
Cross-check of the current value against a fixed value. The standard comparative operators (=, <>, <, >, <=, >=) are available for this comparison.
Note
For the operators = and <>, the 'Current value' field can be left blank, so then the cross-check is made against 'NoValid' (no value available).
**Use predecessor value**
The predecessor value is used instead of the current value.
Note
By using this option, you can prevent values that have not yet been fully calculated (current interval value of a not yet completed interval) from triggering a notification.
**Notification**
An individual message text can be created for each trigger condition. Various placeholders are available for this:
* $ShortName - Identification of the process variable
* $LongName - Name of the process variable
* $Val - Value of PV at time of check
* $ValLim - The comparative value for monitoring
* $UpperLim - Upper limit value (for the selected analysis level)
* $LowerLim - Lower limit value (for the selected analysis level)
* $TimeStamp - timestamp of the value for which the notification was first triggered.
**New entry**
Selection of process variables to be monitored.
**Delete entry**
The selected process variable is deleted.
### Notification plan tab
Assigning a notification plan specifies who is to be informed when.
#### Re-alert time in minutes
Stipulation of the time after which a new notification should be sent if the trigger condition is still met.
Note
When the value 0 is specified here, the value of the [sampling interval](/acron-9.3/en/anlagenverwaltung/objekt-eigenschaften-anlage.md#abtastintervall) defined in the object properties in plant management is used for the time span. The re-alert time is evaluated separately for each trigger condition within a trigger. Each notification e-mail contains the messages of all trigger conditions of the respective trigger fulfilled at that moment.
A trigger contains trigger conditions for the two process variables PV1 and PV2. For both process variables, monitoring for range limit shortfall and range limit exceeding is active.
The monitored value of PV1 leads to a range limit shortfall. A notification is sent, for PV1 the re-alert time of 1 h starts.
Ten minutes later, a range limit shortfall occurs for PV2. Since no notification has been sent for PV2 yet, an e-mail is sent immediately. For PV2 starts the re-alert time of 1h. If the range limit shortfall for PV1 is still present, the message for PV1 is also included in the e-mail for PV2.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.videc.de/acron-9.3/en/anlagenkonfiguration/fernbenachrichtigung/fb-ausloeser/register_ausloesebedingungen.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.