New Features

Feature Enhancements

What - Enhanced the Android push notification structure by adding the sound attribute directly within the FCM data payload, leveraging the same sound selection logic currently used for iOS to ensure consistent notification behavior across platforms and removing dispatch type–based sound-matching logic from the Android application.
Why - Previously, Android relied on in-app dispatch-type logic to determine which sound to play, creating inconsistencies and added complexity compared to iOS; centralizing sound selection in the payload ensures users hear the correct configured tone for dispatch and chat notifications while improving maintainability and cross-platform alignment.
How
- Configure notification tones under Settings → Sound Settings
- Assign sounds for relevant Incident Groups and chat notifications
- Receive a dispatch or chat notification
- Confirm the correct configured tone plays automatically
- Note: Sound selection is now determined by the payload sent from the server.
- Note: No additional configuration is required for this enhancement.
Use Case - A responder configures a distinct audible tone for dispatch alerts and a separate tone for chat messages; when a dispatch notification is received, the correct alert tone plays, and when a chat message arrives, the designated in-app tone is triggered—without relying on device defaults or inconsistent matching logic.

What - Corrected a configuration issue within the Canada Rabbit setup by adding a previously missing key required for proper auto-update functionality, restoring event publishing from Rabbit to Centrifugo so connected clients receive real-time updates as expected when auto-update is enabled.
Why - Without the required configuration key, events were not being forwarded properly, preventing clients from receiving live updates despite having auto-update enabled; this fix ensures reliable real-time data synchronization and restores expected system responsiveness.
How
- Ensure Auto-Update is enabled within the applicable system configuration
- Perform an action that triggers a real-time update (e.g., status change or new event)
- Confirm the update appears automatically without manual refresh
- Note: No action is required for environments not using the Canada Rabbit configuration.
- Note: No user-facing configuration changes are necessary.
Use Case - When auto-update is enabled, a change made to an incident or responder status is immediately reflected across connected devices without requiring a manual refresh, ensuring personnel have the most current operational information in real time.

What - Fixed an issue where custom Base Map layers added via ArcGIS were stored in the database but did not appear in the Base Map/Layers menu for certain users, restoring consistent visibility across roles, browsers, and environments.
Why - Inconsistent layer visibility prevented users from managing or selecting configured basemaps, impacting mapping workflows and administrative control. Ensuring proper rendering across roles improves reliability and user confidence in map configuration.
How -
- Navigate to Responder > Map View
- Open the Base Map/Layers menu
- Confirm custom ArcGIS basemaps are visible
- Select a basemap to activate it
- Use available options to Edit or Remove layers as needed
- Ensure ArcGIS public resource URLs are valid when saving new layers
Use Case - A GIS administrator adds a custom ArcGIS basemap for wildfire operations. After the fix, all authorized users can see and select the basemap from the menu, ensuring consistent mapping during incident response.

What - Standardized page header titles across 13 affected pages following the new navigation rollout by applying the updated shared header component, relocating misplaced titles, and removing duplicate page headings to ensure consistent layout and styling.
Why - Inconsistent or missing page titles created confusion and visual inconsistency across the platform. Aligning all pages with the standardized header component improves navigation clarity and user experience.
How -
- Navigate to any updated module page
- Confirm the page title appears within the standardized Header Component
- Verify no duplicate titles appear within page content areas
- Resize the browser window to confirm responsive behavior across breakpoints
Use Case - A user navigating between Messaging, Responder, and Dispatch modules now experiences consistent title placement and styling, reducing confusion and improving usability across workflows.

What - Addressed a low-severity security finding related to lack of input validation by implementing centralized server-side validation, schema enforcement, sanitization, and contextual output encoding across impacted API endpoints while preserving legitimate special character usage.
Why - Consistent validation and sanitization reduce the risk of malformed or unsafe payloads, including cross-site scripting (XSS) vulnerabilities, while maintaining support for valid operational data entry requirements.
How -
- Input submissions are automatically validated against defined Schema Rules (type, length, format, required fields, ranges)
- Invalid or malformed requests are rejected with generic error responses
- Allowed special characters are processed using an allow list approach
- User-supplied data is safely encoded before rendering in the UI
- Administrators can review detailed server logs for validation failures
Use Case - A user enters notes containing approved special characters in a responder record. The system accepts valid input while blocking malformed or unsafe payloads, maintaining both usability and security integrity.

Related to