--- title: Release notes id: "en:tracking:ROOT:release-notes.adoc" site: en component: tracking module: ROOT version: 3.0 lang: en url: "https://help.rtlscloud.io/en/tracking/3.0/release-notes.html" source_repo: "https://github.com/iot-invent/xCloud.git@3.0.x" source_path: "tracking/docs/en/modules/ROOT/pages/release-notes.adoc" --- # Release notes All changes per version, grouped into Added, Changed, Fixed and notes. For a shorter summary of the highlights see [What’s New in Tracking 3.0](whats-new.md). ## Tracking 3.0 > **NOTE:** Version 3.0 is still under development. The information on this page may still change before release. ### Added - Calibrated floor plans are shown on the world map ([Locations](locations.md)). - Delays are grouped by number of days; the list of the tracks behind a group can be opened from it ([Reports](reports.md)). - New report "Silent assets": how many assets have not reported for how long. Also covers assets without a route ([Reports](reports.md)). - New report "Locations by asset stock": how many assets are standing where right now, per location and broken down by asset type. A click on a bar lists them ([Reports](reports.md)). - New report "Location dwell times": minimum, median, mean and maximum standing time per location, sorted by median. Based on route data ([Reports](reports.md)). - New report "Movement matrix": between which locations the assets move, how often, and how long a transport takes. Based on route data ([Reports](reports.md)). - New cockpit tile "Assets out of contact" showing how long the assets have been silent ([Cockpit](cockpit.md)). - New cockpit tile "Top locations by asset count" showing where most assets are standing right now ([Cockpit](cockpit.md)). - New read interface for tracking events: events can be retrieved page by page or exported as a stream. Intended for integrations with third-party systems. - Application spaces: a space can hold the business data of one use case and obtain locations, devices and position events from an infrastructure space. Several use cases therefore run on one installation, each with its own assets, tracks and rules ([Space type](../../accounts/3.0/spaces.md#space-type)). - A switch on the maps turns layers on and off, in groups rather than one at a time ([Locations](locations.md)). - Automatic assignment rules that could claim the same tag can no longer be saved — this is checked when the rule is entered and when the asset type is saved, across all asset types of the space ([Automatic asset assignment](admin/assettypes.md#automatic-asset-assignment)). ### Changed - Every report tile in the overview carries a description that appears on hover ([Reports](reports.md)). - If you work in an application space, locations, devices and tags come from its infrastructure space and are read-only there. They are still maintained in their own space ([Locations](locations.md)). - Switching application can change the selected space: infrastructure spaces are no longer offered in Tracking, and a use case running on them is selected instead. - All map views were moved to a new map component ([Locations](locations.md), [Cockpit](cockpit.md)). - [Reports](reports.md), [cockpit](cockpit.md) and key figures are computed in the database and are therefore much faster on large data sets. - Assets at the same position are merged into one map pin, and only the visible part of the map is loaded ([Locations](locations.md)). ### Fixed - Data was missing from the distribution charts: a location without sub-locations produced no bar at all, and a parent location counted the assets of its sub-locations twice ([Dashboard](dashboard.md)). - An incompletely filled automatic assignment rule created an asset from any tag in range; it now has no effect until it is complete ([Automatic asset assignment](admin/assettypes.md#automatic-asset-assignment)). - A separator at the end of the tag value produced an asset without a name; none is created now ([Automatic asset assignment](admin/assettypes.md#automatic-asset-assignment)). - When two server instances created the same asset at once, the position report of the losing one was lost; it now uses the asset that was already created ([Automatic asset assignment](admin/assettypes.md#automatic-asset-assignment)). - Overlapping automatic assignment rules are reported in the log as a configuration error instead of a technical failure. ### Update notes - MongoDB 6.0 is now the minimum requirement. - The user interface was moved to a new version of the UI framework. Please check your usual workflows after updating. - If a tag is assigned to an asset in two application spaces, two separate tracks are created there. Per-tag figures therefore cannot be added up across application spaces — whoever evaluates across spaces filters by space ([Reports](reports.md)). ## Tracking 2.1.6 _Released on 9 July 2026._ ### Added - A track can be started when a POI is entered and finished when another POI is entered ([Routes](admin/routes.md), [POIs](admin/pois.md)). - New route type "waypoints": several route point and waypoint configurations can be defined for one route ([Routes](admin/routes.md)). - A confidentiality agreement can be shown before an export, which the user has to accept ([Export templates](admin/exporttemplates.md)). ### Fixed - A custom value could not be added in a multi-select field. ## Tracking 2.1.5 _Released on 13 May 2026._ ### Added - A route point can have several targets, and a target several identifiers ([Routes](admin/routes.md)). - Periodical rules can restrict the assets they apply to by label ([Rules](admin/rules.md), [Labels](admin/labels.md)). - New rule condition for entering and leaving a location, plus an additional comparison operator ([Rules](admin/rules.md)). - The dashboard can additionally group by label and by location ([Dashboard](dashboard.md)). ### Changed - The heatmap report only evaluates events of the same coordinate system, so indoor and outdoor positions are no longer mixed ([Reports](reports.md)). ### Fixed - Assets from indoor position events were drawn in the centre of the location instead of at their real position ([Locations](locations.md)). - Periodical rules were not executed ([Rules](admin/rules.md)). - The location path was sometimes in the wrong order. - The asset name was cut off in the grouped event view ([Events](admin/events.md)). - Long location names overlapped on the map ([Locations](locations.md)). - The filter of the heatmap report was not applied automatically when the report was reopened ([Reports](reports.md)). ## Tracking 2.1.4 _Released on 16 April 2026._ ### Added - Heatmap report: events are rendered as a density layer on the map ([Reports](reports.md)). - New view showing the number of assets per location for a selected asset type ([Dashboard](dashboard.md)). - The stored events of an asset type can be re-processed, which helps after rules have been changed ([Asset types](admin/assettypes.md)). - Asset and track labels can be set with the viewer role as well ([Labels](admin/labels.md)). ### Changed - Rules load locations and POIs only once per run, which speeds up processing ([Rules](admin/rules.md)). ### Fixed - Setting a label in the asset list reset the dwell time of the asset ([Assets](admin/assets.md)). - The label actions were missing from the views without administration rights ([Labels](admin/labels.md)). ## Tracking 2.1.3 _Released on 26 March 2026._ ### Changed - An asset no longer changes its location when its current location is among the detected near-by locations, so it stops jumping between neighbouring locations ([Locations](locations.md)). - Position events are enriched with the asset data before they are stored, so evaluations have to load less ([Events](admin/events.md)). ### Fixed - An export without a selection produced an empty file instead of all records ([Export templates](admin/exporttemplates.md)). - The CSV export of the position events contained the wrong columns ([Events](admin/events.md)). - The empty value was missing from the filter popup after it was reopened. ## Tracking 2.1.2 _Released on 19 March 2026._ ### Added - Lists show the real number of matches beyond 1000 rows — for assets, tracks and tags ([Assets](admin/assets.md), [Tracks](admin/tracks.md)). - The account settings have a back button. ### Changed - Selection fields reload their values on demand, so a newly created entry appears without reopening the form. - Error messages no longer contain technical stack traces. ### Fixed - A track was not finished when its target was a location that can only be entered ([Routes](admin/routes.md)). - Renaming an asset reported that the tag was already used for another asset ([Assets](admin/assets.md)). - The cockpit sometimes showed "Unknown Location" because the location was determined differently per view ([Cockpit](cockpit.md)). - Opening the track details raised an error, and the active track was sometimes missing from the asset details ([Tracks](admin/tracks.md)). - The filter of the track list had no effect ([Tracks](admin/tracks.md)). - New assets and asset types could not be created ([Assets](admin/assets.md), [Asset types](admin/assettypes.md)). - Changes in individual form fields were discarded on save. - String values are quoted in the CSV export ([Export templates](admin/exporttemplates.md)). - Leaving the administration started the wizard for a new space. ## Tracking 2.1.1 _Released on 4 March 2026._ ### Added - The CSV export supports date and time values ([Export templates](admin/exporttemplates.md)). ### Changed - The current-track list of the track and asset details shows the full location path ([Tracks](admin/tracks.md)). ## Tracking 2.1.0 _Released on 2 March 2026._ ### Added - Export with templates: an export template defines which properties are written, and a wizard guides through the export ([Export templates](admin/exporttemplates.md)). - Automatic asset resolution: per asset type you can define how an unknown tag is turned into a new asset ([Asset types](admin/assettypes.md)). - Tracks are marked incomplete when a target was not reached, and the track list can be filtered by delayed and incomplete ([Tracks](admin/tracks.md)). - New rule action that publishes an asset event to the event stream, and a new condition that detects local movement ([Rules](admin/rules.md)). - Audit events can be exported ([Audit Events](admin/auditevents.md)). - Actions in lists are also available through a button in the toolbar, not only through the context menu. - The online help of the app is opened with a button in the header. - The MAC ID can be copied from the asset list ([Assets](admin/assets.md)). ### Changed - Tracking and IoT Spaces use the same map component, so the maps look and behave the same ([Locations](locations.md)). - The location of an asset and of a track is determined the same way in every view ([Cockpit](cockpit.md)). - A track section shows the target that was reached and, in addition, the expected one ([Tracks](admin/tracks.md)). - After signing in, Tracking is the first app to open. ### Fixed - The filter of the tag list behaved unpredictably because it was partly applied before and partly after loading. - Creating an asset with an existing key produced a technical error message ([Assets](admin/assets.md)). - The automatic asset assignment was not visible in the user interface ([Asset types](admin/assettypes.md)). - Map popups are placed so they are no longer cut off at the edge of the map ([Locations](locations.md)). ### Update notes - The user interface was moved to a new version of the UI framework. Please check your usual workflows after updating. - Events are now distributed through the event streaming system instead of inside the application. Make sure the streaming service is reachable.