Fliteca v1.3 — Our Biggest Update Yet
Today we’re releasing Fliteca v1.3, the biggest update to the Fliteca Fleet Management System so far.
This release marks an important milestone for us: the redesign of Fliteca is now complete. Over the past releases, we have gradually rebuilt the platform screen by screen. With v1.3, the last remaining parts of the application have moved to the new Fliteca design language.
But v1.3 is much more than a visual update. It introduces alert webhooks for integration with external systems, a completely redesigned alert configuration experience, address and coordinate search directly on the map, KML import and export, improved map performance, Jimi IoT JC181 camera support, and many smaller improvements across the platform.
A consistent Fliteca experience, everywhere
The redesign started several releases ago. Rather than simply applying a new theme, we gradually rebuilt the interface and the components behind it. Every page, dialog, table, button, menu, tab, wizard, dropdown, toggle and notification now uses our own shared design system. The result is a much more consistent experience throughout Fliteca. A table or dialog behaves the same regardless of where you encounter it, with consistent spacing, typography, colors and interaction patterns.
There is a technical benefit too: removing the remaining legacy UI components means less code needs to be shipped to your browser, helping Fliteca load and respond faster. As part of this work, both the Dashboard and SIM card pages have been redesigned, with cleaner charts, improved information hierarchy and layouts that work better on smaller screens.
A better overview of your fleet
The vehicle map sidebar now includes a fleet status overview. It shows at a glance how many vehicles are moving, parked, offline or in another state. Clicking one or multiple statuses immediately filters both the vehicle list and the vehicles displayed on the map.
We’ve also added the ability to decide what Fliteca uses as the primary vehicle name on the map. You can set a priority between Vehicle name or License plate. If the preferred value is empty, Fliteca automatically falls back to the next configured field.
Alerts have been rebuilt
Alerts are an increasingly important part of Fliteca, so in v1.3 we rebuilt the alert creation and editing experience from the ground up. Creating an alert is now a guided step-by-step process. Each stage becomes available as you progress, making even more advanced alert configurations easier to understand.
Geo-zones selected for an alert can now be previewed directly on a map. You can expand the map to full screen or open the geo-zone editor as a dedicated page when you need more space for drawing and editing.
We have also introduced an alert cooldown, set to five minutes by default.
This is particularly useful for geo-zone alerts: a vehicle hovering around the boundary of a zone will no longer produce a stream of duplicate events.
Connect Fliteca to your own systems with webhooks
One of the biggest additions in v1.3 is alert webhooks. Alongside email and Fliteca notifications, an alert can now trigger an HTTP request to a system of your choice.
You can configure the URL, HTTP headers and payload, allowing Fliteca alerts to integrate with internal systems, automation platforms, messaging services or other third-party applications.
Webhook payloads support dynamic data from the alert, including information such as Vehicle name, License plate, timestamp, etc… This allows the receiving system to get the data it needs in the structure it expects.
Search for addresses and coordinates directly on the map
Finding a specific place in Fliteca no longer requires opening another mapping application. A new search box is available on both the vehicle map and geo-zone map. Fliteca can also recognise coordinates pasted in many commonly used formats.
Address search is a subscription-limited feature and availability depends on your Fliteca subscription.
KML joins GPX
Fliteca already supported GPX in several parts of the platform. With v1.3, we are expanding interoperability with full KML support. Vehicle tracks can now be exported as KML directly from the map, making it easy to inspect Fliteca data in tools such as Google Earth. Geo-zones and complete geo-zone groups can also be exported to KML.
Import works in the other direction too. Fliteca can now create geo-zones from KML and GPX files. GPX tracks are imported as line-type geo-zones, while GPX waypoints can be converted into circular geo-zones. This makes moving geographic data between Fliteca and other mapping tools considerably easier.
And a lot more!
v1.3 includes many smaller improvements throughout Fliteca. These fixes include, but are not limited to:
- Unassigned trackers are now grouped into a single persistent notification instead of generating one notification per tracker, and affected trackers are clearly marked in the tracker table.
- Tracker bulk import from Excel now supports Teltonika FTC/ATC trackers, while vehicles can be exported to CSV using the same column structure supported by the vehicle name import.
- The tracker data table now supports drag-and-drop column reordering, and all pending or queued GPRS commands can be deleted at once.
- Geo-zone alert emails now include the exact event time, invitation emails clearly show when an invitation expires, and system-level notifications have been adjusted so they only reach the relevant employees.
- We’ve also fixed issues across registration, trip auto-detection, GNSS data decoding, GPX exports, GPRS commands, SIM charts and mobile layouts.
- Several iOS and Android map issues have been resolved as well, including misplaced controls, coordinate actions and incorrectly rendered form elements.
- When creating a vehicle, only the vehicle name is now required. Manufacturer, model, license plate and other vehicle-specific information can be left empty. This is especially important for asset tracking, where the trackable object might not need additional information
- We’ve made several changes under the hood to improve map performance. Switching between and interacting with vehicle groups is now much more responsive, particularly for companies managing large numbers of vehicles.
What comes next
v1.3 closes one of the largest chapters in Fliteca’s development. The gradual UI migration is mostly finished, our shared design system now covers the entire application, and the underlying interface architecture is in a much better position for what we want to build next.
At the same time, features such as webhooks, improved alerts, KML interoperability and map search continue moving Fliteca beyond basic vehicle tracking and toward a platform that can fit more naturally into the systems and workflows businesses already use.
Thank you to everyone using Fliteca and providing feedback. Many of the improvements in this release come directly from real-world usage and requests from our customers.
-Happy tracking!
Fliteca Team
