One-shot events

When working with Event Rules, there are scenarios where you need the rule's condition to reset (turn false) before triggering another notification. This is especially relevant when dealing with recurring events or continuous monitoring.

One-shot events provide a practical solution in these cases. They ensure that notifications are sent only once per "true" evaluation of the condition, preventing redundant alerts. Once the rule's condition becomes false, it resets, allowing a new notification to trigger the next time the condition is met.

This behaviour is particularly useful for sending notifications for each track point or event occurrence, ensuring clear and actionable updates without overlap.

The one-shot event rule

1. Edit/create an event rule by accessing the Main Menu > Admin > Event Rules menu in your application.

2. In Step 2. Who this rule applies to select only the asset tag(s) that will make use of this rule.

Note: this step is important to avoid performance issues on your server.

3. In Step 4. Expressions add the same expression that triggers the event in Show advanced options

Example 1: using SOS as a variable to track updates of the SOS state.

Example 2: Using the Temperature (Analog) signal to capture every temperature variation.

Example 3: use the variable Speed (Analog) to trigger a one-shot event.

4. Save your event rule.