Trigger Events are best thought of as a causefor an Action. Within VI MonitorPlus, Trigger Events occur as the direct result of something that has happened. Once the Event has occurred, it will be followed by an Action designated by the Administrator through the application interface.
...
Trigger Events can be considered as the “IF” in an “If, Then” statement (IF Trigger event occurs, THEN do this Action). When creating a Rule, the Administrator should first consider which occurring Event needs to have an Action follow it.
Trigger Event Setup
It is important to determine whether the Event needs to meet Multiple Criteria or if it requires only one Event to occur prior to an Action.
Knowing that information allows the Administrator to determine whether the Trigger Event will work as desired with the Action that follows.
To keep things simple, it is suggested to create the first Rule created with as few items as possible. Once the Rule has been successfully created, it will be easier to determine if there is a problem down the line.
Examples:
Single Event (ANY) - IF a Camera becomes unresponsive OR a specific user logs in to IP Server.
Multiple Events: (AND) - IF Camera becomes unresponsive AND specific user logs into the IP Server.