9.2 release notes

Enhanced contrast across UI elements ensures text and visual components are clearly distinguishable from their backgrounds, improving readability and meeting accessibility standards for users with visual impairments.

All UI elements can now be fully navigated using a keyboard alone, with no mouse required. Navigation follows a logical, predictable sequence across components, reducing cognitive load and ensuring a consistent, confusion-free experience for keyboard-dependent users and those using assistive technologies.

The UI has been enhanced for full compatibility with leading screen readers, including JAWS and NVDA. All interactive elements and images include consistent, descriptive labels and alternative text across every screen, enabling accurate auditory output for visually impaired users. Charts displaying dynamic data now additionally expose their underlying data as a readable table, ensuring no information is lost for screen reader users. These improvements allow visually impaired users to interact with the application effectively and independently, without reliance on sighted assistance.

The UI adapts across a range of zoom levels, ensuring all content remains fully visible and functional without loss of information or usability. This reduces cognitive strain and allows users with visual impairments to read and navigate the application with confidence.

26.3.0.19

26.3.0.19

We fixed an issue where Experience Analytics device event logs could take several minutes to load (even for the first 50–250 rows) in large environments. We’ve optimized the underlying database indexing so device event logs now load significantly faster for on‑premises customers, while retaining existing dashboard performance.

We fixed an issue where not all User Engagement Surveys were displayed in the list view. When surveys spanned multiple pages, the last item on a page could be missing from the list and duplicate entries could appear across pages due to incorrect pagination.

We fixed an issue where the Patch Insights search box could take up to a minute to display the KB number/Title search options when filtering patches in large environments. The API and UI have been updated to correctly use pagination, so Patch Insights search options now appear much faster and the page remains responsive even with large patch datasets.

We fixed an issue where the Endpoint Automation dashboard was taking a long time to render for customers with a large number of devices.

We fixed an issue where the Business Intelligence Consolidator (BIC) could hang or take an excessively long time to complete in environments with large datasets, particularly when consolidating data from multiple connectors (for example, both Tachyon and SCCM). The stored procedure has been optimized, significantly reducing BIC processing time.

We fixed an issue where user device data was not displaying in Experience Analytics for users who have more than one primary device. Device data is now displaying for users who have more than one primary device.

We fixed an issue where the Tachyon Sync connector could fail with an SQL Incorrect syntax near '-' error, causing subsequent sync attempts to fail until the connector was deleted and recreated.

We fixed an issue where the web application did not set the HTTPOnly flag on cookies containing sensitive authentication information. A fix was applied to add the HTTPOnly flag.

We fixed an issue where instructions targeted at a large number of devices were not being reliably sent to all intended recipients. The fix ensures instructions are delivered reliably across all targeted devices.

We fixed an issue where the Catalog sync was failing when processing large datasets during resync with the Global Catalog. The sync mechanism has been updated, improving reliability for large catalog tables.

We fixed an issue where the ServiceNow CMDB Gateway Connector for device sync was failing with timeout errors in the Consumer API. New database indexes were added to optimise query performance, reducing execution time significantly.

We fixed an issue where long OS names caused device update failures during merging. This occurred because certain OS names (for example, Microsoft Windows Server 2025 Datacenter Azure Edition) exceeded the 50-character column limit in the Content Distribution stored procedure. The column size has been corrected to accommodate longer OS name strings.

We fixed an issue where announcements with management group filters failed to load engagement data. The fix ensures the dashboard correctly retrieves and displays response data for announcements scoped to Management Groups.