Update: what’s new in January 2019?

Last month, we updated Wialon and Fleetrun twice. Hope you haven’t missed the first article to get on with the new opportunities that January brings. 

Wialon Hosting

Filter data in “Custom fields” table

There are custom fields in the unit, driver, trailer, and user properties. Here, you can store additional information of any type: a link to the driver’s Facebook profile, WiaTag password for remote configuration, VIN, etc. 

The diverse data can be presented in the “Custom fields” report table. But if you don’t need them all, check out the new filtration by a field mask. Now, you will find the info you need even if you don’t remember the exact text in the field: 

“?” will replace one character, “*” – any number of characters

Summing up: fin?ing informa* in the table is ?asier now.  

Mind the recipient – send a file instead of an archive

The system can automatically send a report to your client’s email through “Jobs.” 

Previously, the system compressed the report before sending it even when the file was not big. It meant extra time spent by the recipient on downloading and extraction. Now, the system automatically compresses only HTML reports and files larger than 20Mb (one or several). For all other files, it depends on “Compress report files” option being activated or not. 

Log in as another user

You can activate the option by clicking on the new icon to the left of the username. To the right, there is a regular icon for the top user (if you work in a sub-account). Thus, now it is much easier to log in to the site and get back to the top user.

Fleetrun

New opportunities for maintenance management 

Editing Services in the archive

Archive tab stores closed and rejected Services for further reporting. But if you made a mistake – specified the wrong date, engine hours, and mileage – data in reports will be irrelevant. In a while, when it comes to maintenance:    

The odometer says “it’s time,” while the report sets against it 

In Fleetrun, you can rearrange it by editing information in the “Archive” tab or even deleting the Service where everything went wrong.  

Making sure that mileage and engine hours are relevant  

Again, correct data in archive Services make your reports valid. Since January, Fleetrun automatically pulls in relevant information on mileage and engine hours. 

1. Present-day data  

Say, you plan oil change in 40,000 km and create a notification 1,000 km before it. When the notification triggers, you decide to change the oil right now (not to forget about it in 1,000 km). In this case, Fleetrun will register the Service at the 39,000th kilometer, which is the actual value on the odometer. 

2. Data at the time of service works

For instance, the mechanic changed oil two days ago, but you only recalled it today. Register “Closed” Service dated “two days ago,” and Fleetrun will suggest adding data on mileage and engine hours on that very day. 

All this makes data in reports correspond to actual odometer and service-meter readings. 

We released two updates in January to rest in February! Just joking. 

Early in February, we’ve already released the new versions of Fleetrun and NimBus. Wialon Hosting update is the testing stage – be the first to know about it from the “What’s new” dialog in the system interface. 

Last but not least, tell us about how you use the new functions in real life at marketing@gurtam.com.