January 2026
Interactive Maps – Labels Enhancements
1. Label Types:
a. Interactive Maps now supports the following three types of labels, providing clear separation between user-defined and system-generated labels:
i. User Added Labels: Labels manually created by users on the map.

ii. Device Name Labels (Pipeline-Generated): Labels automatically generated by the system for device names.

iii. Detection / Landmark Labels (Pipeline-Generated): Labels generated by the Auto Label pipeline based on detection and landmark processing.

2. Labels List on Interactive Maps:
a. Added a Labels tool to the Interactive Maps page that displays all labels in a right-side panel.

b. Users can select any label from the list to automatically highlight the corresponding label on the map, making it easier to locate and manage labels.

3. User-Added Label Creation:
a. Introduced support for creating user-defined labels directly on Interactive Maps.
b. Users can double-click on the map while in Edit Mode with the Labels layer enabled to create a new label.

c. Newly created labels can be edited immediately by selecting the label and updating the text.

d. Saving the map triggers the Auto Label pipeline, and upon completion, a mask/color is automatically applied to the region associated with the new label.

4. Label Editing Behavior:
a. Users can edit text for User Added Labels and Detection Labels.
b. Device Name Labels cannot be edited. Attempting to edit them shows a toaster message: “Editing is Not Allowed.”

5. Moving Labels and Save Behavior:
a. Only User Added Labels can be moved using drag actions or toolbar directional controls.

b. Detection Labels and Device Name Labels cannot be moved.

c. Multiple User Added Labels can be selected and moved together.

d. Saving label edits triggers the Auto Label pipeline.

e. Label size and rotation changes are not supported.
6. Enhanced Editing for Devices and Labels:
a. Users can now edit devices and labels together in Interactive Maps while in Edit Mode.
b. Devices and labels can be selected, moved, and deleted simultaneously, with all changes saved in a single Save action.

c. Rotation and scaling controls are disabled when devices and labels are selected together.

d. Rotation and scaling become available only when labels are deselected, ensuring controlled transformations.

7. Label Deletion Behavior:
a. Users can now delete user-added labels using the trash icon while in Edit Mode.

b. Saving after deletion triggers the Auto Label pipeline.

c. Once the pipeline completes, the associated mask and color are removed when the mask file is regenerated.

d. Device name labels cannot be selected or deleted. Attempting to do so displays an “Editing not allowed” message.
8. Label Visibility Controls:
a. Enabled users to view labels on Interactive Maps through the Layers panel.

b. Users can display labels by expanding the Tools section and enabling the Labels layer.
c. Once enabled, all labels on the map become visible for easy reference.

9. Auto Label Pipeline Status Indicator:
a. Added a visual status indicator for the Auto Label pipeline on the Interactive Maps page.
b. While the pipeline is running after saving changes, the Toggle Mask icon blinks to indicate processing.

c. Hovering over the blinking icon displays a tooltip message: “Auto label pipeline in progress.”

10. Pipeline Overwrite and Device Update Behavior:
a. If a device location is changed, Detection Labels are regenerated, and any user edits to those labels are overwritten.
b. If the Auto Label pipeline completes while the user is still in Edit Mode, all interim changes are overwritten, and a toaster message is displayed: “AI Pipeline has made the changes to your map.”
c. Adding, updating, or deleting devices causes Detection Labels to regenerate, discarding any previous user modifications.

11. Toolbar and UI Improvements:
a. Updated the Toggle Map Mask icon on Interactive Maps for improved clarity.

b. Improved Label toolbar icons to be visually distinct, making each action easier to identify.
c. Enhanced tooltips for all Label icons, clearly describing the functionality when hovering over each icon.
12. Device Association Visualization:
a. Added a dotted-line visualization on maps to show associations between primary devices and related devices.
b. These lines appear when users hover over the map icon in UDC headers and are shown consistently across all UDC views.

13. Permission-Based Map Editing:
a. Enforced permission checks on the Interactive Maps page so that changes to maps, devices, and labels are saved only if the user has edit permission for the map.
b. Applied the same permission-based save behavior on the Maps and Locations page, ensuring map and device changes are saved only for authorized users.
AI Ticketing
1 AI Ticket Search Filter:
a. Introduced a dedicated filter view under the Tickets module.
b. Allows users to filter tickets by System Group, System, Facility, and Person.
c. Helps narrow down tickets based on organizational hierarchy and assigned personnel before viewing the ticket list.
d. Improves efficiency in locating relevant tickets, especially when handling large ticket volumes.
e. Includes a Create button to initiate ticket creation directly from the filter view.

2. Ticket List View:
a. Enhanced the Tickets list view with improved filtering capabilities for faster and more efficient ticket management.
b. Users can now filter tickets directly from the list page using Category, Subcategory, Priority, and SLA Policy.
c. Applied filters dynamically update the ticket list to display only matching tickets.
d. The ticket count updates automatically based on the applied filters.
e. The Search button applies the selected filter criteria.
f. The Clear Filters option resets all selections and reloads the complete ticket list.
g. These improvements enhance usability, accuracy, and speed, especially when working with a large number of tickets.

3 Ticket Details Sidebar:
a. Introduced a unified Ticket Details Sidebar that provides comprehensive ticket information without navigating away from the ticket view.
b. Added an Assigned To section displaying the assigned user’s name, role, and initials, along with a Reassign button.
c. Implemented SLA Compliance visibility, including response and resolution time targets, current status, remaining time, and visual progress indicators.
d. Integrated an AI Suggestions section to display AI-generated recommended solutions for faster resolution.
e. Added a Timestamps section showing Created, First Response, and Last Updated dates.

4. AI Ticket Comments:
a. Introduced an enhanced Ticket Comments section to allow users to add and view comments directly within a ticket.
b. Users can post new comments to communicate updates, notes, and resolutions in real time.
c. Added support for Internal and External comments to control visibility based on audience.
d. Each comment displays the user name, timestamp, and comment text for better context and traceability.

5. Ticket History Timeline:
a. Added a Ticket History Timeline displayed in a modal to view the complete lifecycle of a ticket.
b. The modal header shows the Ticket Number, providing clear context while reviewing history.
c. Displays all ticket events in a chronological order, including updates, assignments, and auto-classifications.
d. Each event includes user details, timestamps, and before/after values, with visual indicators for different event types.
e. Provides a “Close” button to easily exit the history view and return to the ticket details.

BluB0X AI Web
1. Building Oracle Selection:
a. Introduced support for Building Oracle selection within the Oracle configuration.
b. When Building Oracle is selected, users are presented with hierarchical dropdowns to choose Group, System, and Facility.
c. The dropdowns enable structured selection based on organizational and building hierarchy.
d. Improves accuracy and clarity when configuring oracles by guiding users through the correct selection flow.

2. AI Web Dashboard UI Enhancement:
a. Moved the prompt input component from the top of the screen to the bottom of the main panel for a more natural chat experience.
b. Ensured the prompt input remains easily accessible while viewing the full chat history.
c. Relocated the Mode and Model selection dropdowns to appear next to the Chat Stream title for better visibility and context.
d. Improved overall layout consistency to align with standard conversational UI patterns.
e. Enhanced usability by reducing visual clutter at the top of the screen and focusing attention on the chat stream content.
