February release: UI updates & saved value device mapper scripts
It's all about quick access and accurate reporting this month. UI updates for fast info access include event panel updates, a shortcut to 'peek' behind map layers, and better application tab branding. Plus new saved value device mapper scripts give you ultimate flexibility and precise reporting.
We’ll start with the features that improve the speed of access to information. After that, we’ll dive into the new saved value device mapper scripts. It has a big impact on reporting, but we’ve saved it for last because it is a bit more technical.
Event Panel - fast access to the info you need
Events often need to be addressed immediately. This month’s release helps operators have the information they need at all times.
Open event count in tab
The number of open events displays in the event panel tab title. Operators can see if any new events occur while working in other areas of the VehicleTracker. If you are working in other panels, you don’t need to switch to the event panel to keep track of new events.
Time interval event search
Event search now supports specific time intervals. When searching for an event on a specific date, you can select down to a 30 minute interval. For fleets with lots of vehicles and events, this narrows down your search so you don’t waste time scrolling.
Larger fleets will also benefit from other updates. The max event rules limit has been increased to 1000, so operators will never miss an important event. Notifications are also off by default. Operators can choose which business-critical events trigger notifications.
Additional performance, filtering, and localization updates are included in February’s release. More details are available in the full release notes.
‘Peek’ feature - hide map layers to quickly consult the map
Map layers let you see only the information you need. Vehicles, events, geofences, etc. are all overlaid on the map. You can hide them with a click to focus on the information you need.
We’ve introduced a new time saver. Check out the new ‘peek’ feature! You can now hold “p” to peek at the underlying map.
All layers are temporarily dimmed. You can quickly consult the map without losing your focus.
VehicleTracker tab branding - your app name comes first
You may often have multiple applications open at once. It can be tricky to keep track of them in multiple tabs, and clicking on the wrong one can be frustrating.
We’ve changed the tab names to display application name plus the selected view. The name convention is “App | View”. In the example below, we have three VehicleTracker applications named VT, VT2, and VT3 with the view selected as ‘All.’ Misclicks are now a thing of the past - seamlessly switch between application windows!
Saved value device mapper scripts
Saved value scripts are here! These scripts are only evaluated once. Changing the script or re-processing tracks will not change the stored value. Put simply, your data analysis for Feb 14, 2019 uses the custom field value from Feb 14, 2019.
Real world solutions using saved value device mapper scripts:
- • Save history of a custom field - You can save historical values of Custom Fields. Persistable scripts no longer need to be recreated with every message from the device.
- • Handle key = value data from device - The script updates the variables only when there is a new key value coming in.
- • Counters - Use to count how many times a condition has been true or count a device output value in a cumulative fashion
But what does this really mean? Let’s take a quick dive into a custom field history use case with temperature.
If you deliver food & perishables, you need to be sure the delivery stays within acceptable temperatures. On Day 1, you might be delivering vegetables that must be kept cool. On Day 2, you might delivery ice cream that must be kept frozen. Your custom field that sets the temperature threshold for deliveries would change each day for a given vehicle.
When you run the temperature exception report, you will not get false positives with persistable fields. The report will compare the Day 1 data to the Day 1 custom field value, and Day 2 data to the Day 2 custom field data. The persistable field scripts ensure accurate analysis using the appropriate variable value.
To learn more about using persistable scripted message fields, click here.
To see the full list of updates in the February release, please visit the release notes linked below.