Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
user:monitor:reg [26/09/2018 13:10]
tagr
user:monitor:reg [12/09/2019 17:23] (current)
alse
Line 4: Line 4:
 Different events can be registered in the unit history and then shown in the corresponding reports. Some events such as speeding, idling, visits to [[user/​geo/​geo|geofences]],​ [[cms/​units/​sensors/​sensors|sensor]] values, etc. can be detected automatically by the system with the help of [[user/​notify/​notify|notifications]]. Other events such as fuel filling, maintenance or any custom events are registered in unit history manually with the help of a special tool — **Events Registrar**. ​ Different events can be registered in the unit history and then shown in the corresponding reports. Some events such as speeding, idling, visits to [[user/​geo/​geo|geofences]],​ [[cms/​units/​sensors/​sensors|sensor]] values, etc. can be detected automatically by the system with the help of [[user/​notify/​notify|notifications]]. Other events such as fuel filling, maintenance or any custom events are registered in unit history manually with the help of a special tool — **Events Registrar**. ​
  
-To display the registrar, ​press the button ​in the monitoring panel {{:​icons:​reg.png?​nolink}}. If you do not see such a button, it can be added with the help of the [[user/​monitor/​icons|monitoring panel customizer]]. ​+To display the registrar, ​click on the button {{:​icons:​reg.png?​nolink}} ​in the monitoring panel. If you do not see this button, it can be added with the help of the [[user/​monitor/​icons|monitoring panel customizer]]. ​
  
 :!: //​Attention!//​\\ To register events for a unit, the //Manage events// access right is needed. Otherwise, the registrar button is not active. ​ :!: //​Attention!//​\\ To register events for a unit, the //Manage events// access right is needed. Otherwise, the registrar button is not active. ​
Line 93: Line 93:
 |**Time received** ​ |Date and time when event was registered.| |**Time received** ​ |Date and time when event was registered.|
 |**Event text** ​ |Text is taken from the //​Description//​ field. For maintenance,​ if there is no description,​ the text can be taken from the //Kind of work// field.| |**Event text** ​ |Text is taken from the //​Description//​ field. For maintenance,​ if there is no description,​ the text can be taken from the //Kind of work// field.|
-|**Location** ​ |Unit location at the time of the event. It is taken from the coordinates indicated while registering the event (press the //Select Location// button, and double-click on the map). |+|**Location** ​ |Unit location at the time of the event. It is taken from the coordinates indicated while registering the event (click on the //Select Location// button, and double-click on the map). |
  
 If any of the above-mentioned fields are not filled out correctly, the corresponding columns will be empty. ​ If any of the above-mentioned fields are not filled out correctly, the corresponding columns will be empty. ​
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2019 Gurtam