The text is used for the following notification actions: notify by SMS or email, register event for unit, display online notification in pop-up window.
The text of a notification can be written in any language, contain any characters, words, and phrases, and be of any size. In addition, you can use tags, that is, parameters encrypted with special characters. In a message, such characters will be replaced with real values. If you want to receive a notification by SMS, do not write long messages.
The text «'%UNIT%' violated speed limitations. At '%POS_TIME%' it moved %SPEED% near '%LOCATION%'» can be transformed to «'Rover-119' violated speed limitations. At '2000-01-01 12:01:37' it moved 136 km/h near 'KU 8, Thurnau, DE'».
The units of measurement (kilometers or miles) used to decrypt the tags depend on the resource settings to which the notification belongs. The date and time format is taken from the settings of the creator of this resource.
In the text of the notification with the Send a request action type, enter the parameters of the request. When composing the text of the notification yourself, use URL encoding. Note that when using this type of notification action together with others (such as Notify by email, Notify by SMS, and so on), the same text is created for all notifications.
Below is the list of tags applicable to most types of notifications.
There are also tags that are applied only to specific types of notifications.
If the data is unknown, the tags are displayed as they are (not substituted with any values). The exceptions are the following tags which do not appear in the notification text when there is no data: %UNIT%, %USER%, %CURR_TIME%, %LOCATION%, %LAST_LOCATION%, %SPEED%, %POS_TIME%, %MSG_TIME%, %UNIT_GROUP%, %ENGINE_HOURS%, %MILEAGE%, %LAT%, %LON%, %LATD%, %LOND%, %GOOGLE_LINK%, %INSURANCE_CASE%, %ZONES_ALL%, %ZONE_MIN%, %UNIT_ID%, %MSG_TIME_INT%, %NOTIFICATION%, %TAG_NAME%, %TAG_ID%, %LOSE_RESTORE%, %LOCATOR_LINK%.