Notification action is the action the system will perform when a notification triggers.
This action is used to set up email notifications. You can indicate one or more email addresses to send a notification to. When all fields for entering addresses are filled in, additional slots appear automatically. The header of the message will contain the name of the notification and the name of the unit in the parentheses. The body of the letter will contain the text of the notification, where the tags will be replaced with specific values.
In addition, if the device allows, an image sent by the unit in the message may be attached to the notification. To do this, check the Attach image from triggered message option.
To receive a notification by email, in the general properties of the billing plan, specify the email address from which system messages will be sent.
This action is used to set up SMS notifications. Type in one or more telephone numbers in the international format, for example, +375293293294. When all fields for entering phone numbers are filled in, additional slots appear automatically.
If the Can send SMS check box is not activated in user properties, the corresponding notification delivery method becomes unavailable.
This action allows sending alerts about triggered notifications to the Telegram messenger.
This action is used to set up online notifications that will be displayed in a pop-up window. Such a notification can be silent or accompanied by a specific sound. If no URL is given for the sound, the standard tune will be used. To use a custom tune, enter the URL of the sound. The recommended file size is up to 0.5 MB.
It is possible to receive notifications in the minimap once a notification triggers. To enable this option, check the Blink minimap box in this section.
Different browsers can have restrictions regarding formats of audio files:
Internet Explorer 9+
Google Chrome 11+
Mozilla Firefox 12+
To highlight a notification, you can set an individual colour to it. This colour will be applied to the background of the triggered notification so that you could easily notice it.
This action is used to set up mobile notifications from the selected application. Choose the required application in the Applications field. Next, the system checks to what users the current user and the creator of the resource have the View detailed item properties and Act as given user access rights and creates the list of users. Specify the users who should receive mobile notifications (hold the Ctrl key and check any box to select all users). For the convenience of search, use the dynamic filter above the list.
Note that the availability of mobile notifications service depends on the chosen service package.
To receive mobile notifications, the user of the application for iOS and Android should authorize in the application and enable the Notifications option in the settings.
This action allows sending alerts about the triggered notifications to third-party systems. When choosing this action, indicate the server address as well as the method of the HTTP request (POST or GET).
This action allows registering a notification as an event in the unit history. As a result, you can generate a report on these events.
To work with this action, make sure that the Manage events access right has been provided.
This action works together with the Register event for unit action and allows to register a notification not only as an event, but also as a violation. As a result, the Violations report becomes available.
When you select this action, a command is sent to the unit (units) when a notification is triggered. Select a command from the list of the available ones. The list contains all commands configured in the properties of selected units if a user has the Execute commands access rights towards them. Next to the header of the command can be special icons that signify the following:
all selected units support this command;
not all of the selected units support this command (see details in the tooltip).
If necessary, set the parameters.
If you send commands that require the input of text or a message (for example, Send custom message or Send message to driver), you can use tags (the same as for the notification text). When the command is executed, the entered tags are converted to the values that correspond to them.
Tags are converted to values only if a command is selected as a notification action (not if a command is sent manually from the Monitoring panel).
You can read more about commands here.
This action allows changing access rights to units once the notification is triggered. Select users whose access rights should be modified when trigger conditions occur. Specify the access rights that should be applied to these users after the notification triggers. You can use this feature, for instance, in the following situation: suppose you have created a user who monitors the transportation of their cargo, that is, they have access rights to certain units. After the cargo is delivered to the agreed place (that is, after the unit entered a geofence), these units automatically become unavailable to the user.
To work with this action, the Manage access to this item access right is required.
This action is used to change (or reset) counter values when notification triggers. Select one or more counters (mileage counter, engine hours counter, traffic counter) and set new values for them.
To work with this action, the Edit counters access right is required.
This action is used to store the current values of mileage or engine hours counters as parameters in unit data messages (odometer or engine_hours, correspondingly). These parameters can be used to create sensors on their basis (for example, engine hours sensor) and to get initial/ or final mileage in reports. For more precise calculations, it is recommended to store counters while the unit is parked, for example, once a day at night time.
To work with this action, the Edit counters access right is required.
This action is used to set a new status for a unit when a notification triggers. For instance, when unit enters a geofence, the private state can automatically switch to business.
To work with this action, the Manage events access right is required.
This action is used to change the contents of unit groups when a notification triggers (units can be added or removed from the group). On the left, there is a list of all available unit groups. Move the required groups to the Add to group or Remove from group sections. As a result, after the notification triggers, the unit will be added or removed from the group.
This action is used to send a report to the specified email address(es) once the notification is triggered. Indicate the resource to which the required report template belongs (select All available to view the templates of all available resources), report template, object (only the objects that belong to the same resource as the template are displayed), file format(s), time interval and report parameters. Note that when choosing an object, sometimes it is convenient to use the Triggered unit option. In this case, a report is generated for the same unit that the notification triggers for.
Afterwards, for the Content item, specify whether you would like to receive files/archives or the link to the FTP server (Wialon or a custom one) where the corresponding files/archives are stored. Indicate the report interval: choose particular dates or specify any time interval for the previous X minutes/days/weeks/months/years. Enter an email address(es) to which the report should be sent upon notification triggering. To generate a report, the View messages and reports access right is required. To find out more about file formats or parameters description, see the Export Report to Files section.
The information about the geodata in such a report is shown in accordance with the settings of the user-creator of the resource in which this notification was created.
If the access right to the object (or the object itself) was removed, the created notification is not executed.
This action is used to replace the icon of the current unit by the specified one when the notification triggers. Click on the Library button to open the window with the available icons.
After the notification triggers, a new round can be created for a unit. For example, when one round is finished, a new round can be assigned, or when a unit leaves the geofence (for example, a garage), a new round is automatically created for it. More about the parameters that can be configured for rounds are described in the Routes section.
This action is used to reset driver automatically when the notification triggers. This action can be useful when, for example, you want to unbind the driver from the unit once the unit returns to the depot.
The Create, edit, delete drivers access right is required for this action. Driver resetting can take place only within the resource to which the notification belongs.
This action is used to reset trailers when the notification triggers.
To work with this action, the Create, edit, delete trailers access right is required. The same as for driver resetting, trailers should belong to the same resource in order for the action to be executed correctly.