New Features

Evaluations Module

• What - Added the Evaluations module to the iOS mobile application, providing authorized users with access to two new evaluation destinations directly from the application's main navigation. The new module follows existing mobile navigation and permission patterns so evaluation options are available only to users with the appropriate access.
• Why - Adding Evaluations to the mobile navigation provides users with more direct access to evaluation workflows from the field without requiring them to navigate separately through the web platform.
• How
  • Open the Main Menu.
  • Select Evaluations.
  • Choose the appropriate evaluation submenu.
  • Available options are displayed based on the user's assigned permissions.
• Use Case - A supervisor who needs to complete or review an evaluation can access the appropriate evaluation workflow directly from the mobile application's main navigation while working away from a desktop computer.

Log Training Mobile Navigation

• What - Added a new Log Training submenu to the Training module and renamed Training Classes to Scheduled Training. The updated navigation provides authorized users with direct access to mobile training logging while using clearer terminology to distinguish scheduled training activities from the process of recording completed training.
• Why - Separating scheduled training from training logging makes the mobile Training menu easier to understand and provides users with faster access to the workflow appropriate to the task they need to complete.
• How
  • Open the Main Menu.
  • Navigate to Training.
  • Select Log Training to access the training logging workflow.
  • Select Scheduled Training to access the functionality previously labeled Training Classes.
  • Available Training options continue to respect assigned permissions.
• Use Case - After completing a training exercise, an authorized user can select Training → Log Training to document the activity, while personnel looking for upcoming classes can select Scheduled Training.

Feature Enhancements

Fire Investigation Navigation Updates

• What - Updated the mobile application's Fire Investigation web navigation to use the latest Fire Investigation routes, ensuring supported workflows open the correct current web pages from the iOS application.
• Why - Keeping mobile navigation aligned with current web routes helps prevent broken or outdated links and provides a consistent experience between the mobile and web platforms.
• How
  • Navigate to the applicable Fire Investigation option from the mobile application.
  • Select the desired Fire Investigation workflow.
  • The application automatically opens the corresponding current Fire Investigation page.
  • No configuration changes are required.
• Use Case - An investigator accessing a Fire Investigation workflow from an iOS device is automatically directed to the current version of the applicable page without encountering an outdated route.

Mobile Web Navigation Alignment

• What - Updated multiple mobile web navigation paths to match the current server-defined routes used by the web platform. This improves consistency when users launch web-backed modules and workflows from the iOS application.
• Why - Maintaining alignment between mobile and web navigation helps ensure menu selections consistently open the intended destination as web routes evolve.
• How
  • Continue accessing web-backed modules through the Main Menu and other existing mobile navigation options.
  • The application automatically uses the updated server-aligned paths.
  • No user configuration is required.
• Use Case - A responder selecting a web-backed feature from the mobile menu is taken directly to the correct current page without being affected by differences between legacy mobile paths and current web routes.

Safer Offline Data Pack Updates

• What - Improved offline data reliability by introducing a safer replacement process for downloaded offline packs. Updated packs are now temporarily downloaded and validated before replacing the existing pack, reducing the possibility of incomplete or invalid data replacing a working offline dataset.
• Why - Responders may depend on offline information when network connectivity is unavailable. Validating replacement data before activating it helps protect existing offline information and provides a more reliable update experience.
• How
  • Download or update supported offline data using the existing workflow.
  • The application downloads and validates the replacement data before making it active.
  • The existing offline pack remains protected during the update process.
  • No additional user action is required.
• Use Case - A responder updating offline data before operating in an area with limited connectivity can have greater confidence that the existing working dataset will not be replaced until the newly downloaded information has been successfully prepared.

Offline Data Connection Reliability

• What - Improved offline data handling by refreshing cached database connections after an offline data pack is replaced. This helps ensure the application begins using the newly installed offline dataset rather than retaining connections associated with the previous pack.
• Why - Properly refreshing database connections reduces stale-data conditions and improves reliability after offline information is updated.
• How
  • Update an offline data pack using the existing workflow.
  • The application automatically refreshes applicable offline database connections after replacement.
  • Newly installed offline information is then used by supported workflows.
  • No user action or configuration is required.
• Use Case - After downloading updated offline information, a responder can immediately use the new dataset without the application continuing to reference information from the previously installed pack.

Account Switching and Logout Reliability

• What - Improved session safety during logout and account switching by adding protections that stop applicable in-progress native operations when a session ends or the active account changes.
• Why - Preventing work associated with a previous session from continuing after logout or account switching reduces the possibility of stale information or account-specific activity carrying into another session.
• How
  • Use Logout or switch between configured accounts normally.
  • Applicable in-progress operations associated with the previous session are automatically stopped.
  • New operations begin using the currently authenticated account.
  • No additional configuration is required.
• Use Case - A user working with multiple accounts can switch from one organization to another with improved assurance that background activity associated with the previous account does not continue into the new session.

WebView Session and Reload Improvements

• What - Enhanced the application's newer SwiftUI-based web experience with improved handling for push-triggered page reloads, new browser windows, and session timeout behavior. These workflows now more closely match the behavior available through the previous web experience.
• Why - Consistent WebView behavior helps users move between web-backed workflows without experiencing differences in refresh, navigation, or session handling as the application transitions to its newer web architecture.
• How
  • Continue using web-backed modules normally.
  • Push-triggered reloads are handled automatically where supported.
  • New-window navigation follows the updated WebView behavior.
  • Session timeout handling occurs automatically when authentication expires.
  • No user configuration is required.
• Use Case - A responder working in a web-backed module can continue receiving expected page updates and authentication handling while using the application's newer web experience.

Web-Based Map Workflow Modernization

• What - Updated remaining map-based web workflows to use the application's newer WebView hosting experience, providing greater consistency with other modernized web-backed areas of the iOS application.
• Why - Moving map-related web workflows onto a common web framework helps improve consistency and supports more predictable navigation and session behavior across the application.
• How
  • Continue accessing supported web-based map workflows normally.
  • Applicable pages now automatically use the updated web hosting experience.
  • Existing user workflows remain available without additional configuration.
• Use Case - A responder opening web-based information from a map continues using the familiar workflow while benefiting from the same underlying web experience used elsewhere in the application.

Web Form Navigation Consistency

• What - Improved consistency across SwiftUI web-based forms by standardizing how shared form destinations are handled throughout the application.
• Why - Consistent form navigation reduces differences between web-backed workflows and provides a stronger foundation for reliable navigation as additional areas of the application transition to the updated web experience.
• How
  • Continue opening supported web-based forms through existing application workflows.
  • Form destinations are handled automatically using the standardized navigation behavior.
  • No user configuration is required.
• Use Case - A user moving between different web-based forms receives more consistent navigation behavior regardless of which mobile workflow opened the form.

Database Lifecycle Reliability Improvements

• What - Improved the application's database lifecycle management by introducing a more consistent method for determining when local database information is ready for use and updating critical application workflows to use the unified database lifecycle behavior.
• Why - More consistent database readiness handling helps reduce timing-related issues during application startup and other workflows that depend on locally stored information.
• How
  • Continue launching and using the application normally.
  • Database readiness and lifecycle transitions are handled automatically.
  • Supported workflows wait for the appropriate database state before accessing local information.
  • No user configuration is required.
• Use Case - A responder launching the application can access locally stored operational information with reduced risk of a workflow attempting to use the database before it is ready.

Fixes

Dispatch Details Crash

• What - Fixed an issue that could cause the iOS application to unexpectedly close while opening Dispatch Details and rendering incident information.
• Why - Reliable access to dispatch details is essential during active response operations. Eliminating this crash reduces interruptions when responders are reviewing incoming incident information.
• How
  • Open an incident using the normal responder workflow.
  • Navigate to Dispatch Details.
  • Incident information now renders without triggering the identified crash.
  • No configuration changes are required.
• Use Case - A responder receiving a new call can open its dispatch details immediately and review the available incident information without the application unexpectedly closing.

Responder Status Stability

• What - Fixed a production crash associated with processing and encoding responder status information.
• Why - Responder statuses are used throughout operational workflows, and improving their processing reliability reduces the possibility of application interruptions as statuses change.
• How
  • Continue using responder status workflows normally.
  • Status information is processed using the corrected handling automatically.
  • No user action is required.
• Use Case - Responders can update and receive operational status information during an active incident without encountering the previously identified application crash.

Google Maps Background Stability

• What - Improved Google Maps stability by strengthening protections around background map snapshots and graphical rendering, particularly during background transitions and on iPad devices.
• Why - Responders frequently move the application between foreground and background states while using maps. Improving map rendering safety reduces unexpected crashes when returning to active responder workflows.
• How
  • Use Responder Map normally.
  • Background or return to the application as needed.
  • Google Maps rendering and snapshot handling now operate using the updated protections.
  • No configuration changes are required.
• Use Case - A responder using an iPad can move between the Responder Mobile App and another application and return to the map with reduced risk of a rendering-related crash.

Map Marker Teardown Stability

• What - Improved map stability by ensuring Google Maps markers are properly detached when a map view is closed or dismantled.
• Why - Properly releasing map elements reduces the possibility of rendering and memory-related issues when users repeatedly enter and leave map workflows.
• How
  • Open and close map-based workflows normally.
  • Map markers are automatically removed from the previous map instance when it is dismantled.
  • No user action or configuration is required.
• Use Case - A responder repeatedly moving between incident details and map views during an active response experiences more reliable map behavior without stale map elements contributing to application instability.

Verdugo CAD Response Button Accuracy

• What - Fixed an issue in Verdugo CAD workflows where non-incident response buttons could be displayed when a CAD status update was received without the original dispatch event. The application now presents response controls that more accurately reflect the current incident state.
• Why - Showing controls that do not match the active CAD state can create confusion and lead users to believe an action is available when it does not apply to the current response.
• How
  • Receive and process Verdugo CAD status updates normally.
  • The application automatically evaluates the current dispatch state.
  • Applicable responder controls are displayed based on the available incident information.
  • No user configuration is required.
• Use Case - A responder receiving a CAD status update without the original dispatch event sees controls appropriate to the actual incident state rather than unrelated response options.

Unit Availability After Dispatch Closure

• What - Fixed a bidirectional CAD workflow issue where a unit could fail to return to Available after its dispatch was closed. Unit availability now updates appropriately when the dispatch lifecycle ends.
• Why - Accurate unit availability is important for resource awareness and subsequent dispatching. Units remaining in an incorrect state after an incident closes can create confusion about whether they are ready for another assignment.
• How
  • Complete the applicable dispatch workflow.
  • Close the dispatch using the normal process.
  • The associated unit automatically returns to Available when appropriate.
  • No additional user action is required.
• Use Case - After completing an incident, a unit's status returns to Available, allowing personnel to immediately see that the resource is ready for another response.

Active Incident View Continuity

• What - Fixed an issue where an incident currently being viewed could unexpectedly refresh when a new dispatch was received. The open incident now remains stable while the application processes incoming calls.
• Why - Unexpectedly refreshing an incident can interrupt users who are actively reviewing operational information. Preserving the current view helps responders maintain focus while still allowing the application to receive new dispatches.
• How
  • Open an incident and review Incident Details.
  • If another dispatch arrives, the currently open incident remains in place.
  • New dispatch information continues to be received through the normal responder workflow.
  • No configuration changes are required.
• Use Case - A responder reviewing pre-arrival information for one incident can continue reading that information when another call is dispatched instead of having the current screen unexpectedly refresh.

Station and Location List Freshness

• What - Fixed an issue where station and location changes could remain stale during an active application session. Updated station information now appears more reliably within the To Station workflow and Default Station settings without requiring the user to restart the application.
• Why - Keeping station information current ensures users are working with the latest available operational locations and reduces unnecessary logout or restart steps after configuration changes.
• How
  • Access the To Station workflow or Default Station settings.
  • Station additions, changes, and removals are refreshed during the active session.
  • Continue using the updated station information without restarting the application.
  • No additional configuration is required.
• Use Case - When a station assignment or location is updated, a responder can see the change during the current application session and select the updated station without signing out or restarting the app.