Event Rule Wizard - a step by step guide

This article walks you through creating a Custom Event Rule using the Event Rule wizard. The wizard lets you define what triggers a rule, who it applies to, when it's active, and what happens when it fires.

New to Event Rules? Start with Event Rules Introduction before working through this guide.

Accessing the wizard

1. Go to Main menu > Events > Manage Event Rules.
2. Click + New Event Rule to open the wizard.

The wizard opens as a window with four sections in the left-hand menu: Triggers, Notifications, Schedule, and Details. You can move freely between sections — nothing needs to be filled in a strict order — but Rule name (in Details) is required before you can save.

Tip: Throughout the wizard, look for the ⓘ icon next to field labels (such as Groups, Trigger matching, Trigger delay, and How does it end?). Hovering over it shows a short explanation of what that field does and how it affects the rule — useful if you're not sure which option to pick.

Triggers

The Triggers section defines what conditions cause the rule to fire, and which objects it applies to.

Groups Select the group(s) this rule applies to. Hover the info icon next to Groups for details on how group membership affects the rule.

Trigger matching Choose how multiple triggers are combined:

• Match any – the rule fires if at least one trigger condition is true
• Match all – the rule fires only when every trigger condition is true

Trigger type / Expression Add one or more triggers. For each one:

• Select a Trigger type from the dropdown (e.g. Variable Expression). The available trigger types are the same as before.
• Configure the Expression — select a variable, a comparison operator (e.g. Greater or equal), and a value.

Click + Trigger (or use the empty trigger row) to add another condition; it will be combined with the previous one using AND/OR based on your Trigger matching setting.

Trigger delay

• Immediate event – the event fires as soon as the trigger condition is met
• Delayed event – the event fires only after the condition has been met continuously for a set duration
  • Delayed event: you can specify the number of minutes before an event triggers. This is useful for avoiding having many notifications at once if an expression is met repeatedly in a short period.
  • Automatically trigger the event after the delay specified above as the events are triggered on incoming data only, this option forces triggering the alert after a specific number of minutes despite not receiving new data. For instance, if you have a 3-minute delay set, and the messages from the asset are sent in 5-minute intervals, it will take up to five minutes before the condition is fulfilled and a notification is generated. Use this option only if strictly necessary. 

How does it end?

• Automatically, when trigger conditions are no longer met – the event closes as soon as the trigger condition becomes false
• When specific end conditions are met – define separate conditions that must be met to close the event

  • The End condition defines the condition that determines when an event should finish. Setting it correctly is critical to ensure the entire event lifecycle behaves as expected.

    Example

    • Trigger Expression:     Speed > 20 km/h

    • Without an End Expression:

      Speed = 25 km/h → Event starts

      Speed = 15 km/h → Event ends immediately

    • With an End Expression (Ignition = Off):

      Speed = 25 km/h → Event starts

      Speed = 15 km/h → Event continues

      Ignition = Off → Event ends

Notifications

The Notifications section defines what happens when the rule triggers.

For each notification:

1. Select a Notification type (e.g. Fleet app, email, SMS, webhook — same types as before)
2. Choose Recipients.
3. Edit the Message to send. Use the Show available [variables] button to insert dynamic values such as [ASSIGNED_VEHICLE_NAME], [RULE_NAME], or [POS_ADDRESS].
4. Set Timing:
   • Send when rule is triggered
   • Send when rule is untriggered
   • Send on both trigger and untrigger

Click the empty Notification type row to add another notification. You can configure as many as you need, each with its own recipients, message, and timing.

Schedule

The Schedule section controls when the rule is active.

For each day of the week, choose one:

• All day – the rule is active all day
• Inactive all day – the rule is disabled that day
• Time span – the rule is only active during a specific time window you define

Finish events automatically when outside schedule — when checked, any open event is automatically closed once it falls outside the active schedule.

Details

The Details section covers the rule's identity and how it behaves in the application.

• Rule name (required) – the name shown in the product
• Description – describe what triggers the rule and what it results in
• Live rule – toggle whether the rule is actively evaluated
• Visible in application – toggle whether the rule/its events are shown in the application
• Event color – pick the color used to represent this rule's events
• Close behaviour:
  • Close automatically when rule expression is false
  • Close manually
• Comment on close:
  • Disabled
  • Optional
  • Required

Saving the rule

Once you've filled in the required fields (at minimum, a Rule name), click Save at the bottom of the wizard. Click Cancel to discard changes and close the wizard.