New Features

Department Location Selection on Login Screen

• What - Added a Department Location dropdown to the iOS login experience, allowing users to confirm or override the country environment the application connects to before signing in. Users can select either United States or Canada directly from the login screen, with the dropdown automatically pre-selected based on the device’s regional settings. The selected environment immediately updates authentication routing to ensure login requests are directed to the correct server regardless of VPN, MDM, or network routing conditions. FedRAMP builds continue using their specialized environment options and workflows.
• Why - This enhancement improves login reliability for responders operating on managed devices or networks that may route traffic through another country. Previously, users could experience generic authentication failures when network routing caused requests to reach the wrong regional environment. Allowing users to verify and manually adjust the selected region directly from the login screen reduces failed sign-in attempts, eliminates unnecessary troubleshooting, and improves operational readiness.
• How
  • Open the iOS application login screen.
  • Locate the Department Location dropdown.
  • Review the automatically selected country environment.
  • Select either United States or Canada if a different region is required.
  • Enter credentials and select Sign In.
  • The application automatically routes authentication requests using the selected environment.
  • FedRAMP environments continue using their existing environment selection workflow.
• Use Case - A responder connecting through a VPN while traveling or using a department-managed device may be routed through infrastructure in another country, causing login failures against the wrong environment. With the new Department Location selector, the responder can manually choose the correct region before authentication, avoiding delays and restoring immediate access to operational workflows.

Feature Enhancements

Fire Zone Display in Incident Details

• What - Enhanced the iOS incident details experience to display Fire Zone information for departments that receive zone data through their CAD integration. Fire Zone information now appears within both the incident details screen and the map incident callout using a highlighted layout consistent with the existing Fire Box display. The Fire Zone field is automatically hidden when no zone data is available, ensuring the interface remains clean and consistent for departments that do not use this information.
• Why - This enhancement improves situational awareness by making Fire Zone information immediately visible within the responder workflow without requiring users to switch modules or reference external systems. Matching the visual presentation of the existing Fire Box field also helps responders quickly interpret incident data under pressure while maintaining UI consistency across the incident experience.
• How
  • Open an active incident within the iOS application.
  • Navigate to the Incident Details screen or map incident callout.
  • Review the new Fire Zone field displayed above the Cross Street section when available.
  • Fire Zone information appears automatically for departments receiving zone data from CAD.
  • No additional configuration is required for supported agencies.
• Use Case - During an active response, responders reviewing incident information can immediately identify the assigned Fire Zone directly from the incident screen, helping crews coordinate operational areas, staging assignments, or mutual aid responses without leaving the responder workflow.

Fixes

Building Story Display for Unmatched Addresses

• What - Fixed an issue where the Building Story field incorrectly displayed “--” for dispatches associated with unmatched addresses, even when valid story information was returned from the API. The application now properly displays the Building Story text directly from the dispatch payload while preserving existing handling for null, empty, or missing values.
• Why - This fix ensures responders receive accurate building information regardless of whether the incident address is already matched within First Due records. Access to correct building story details improves operational awareness and reduces the likelihood of missing important structural information during dispatch review.
• How
  • Open an incident containing Building Story information.
  • Review the Building Story field within the incident details view or incident callout.
  • Valid Building Story data now displays correctly even for unmatched addresses.
  • Null or empty values continue displaying “--” as expected.
• Use Case - A responder dispatched to an address not yet stored in First Due records can still view valid Building Story information received from CAD, helping crews better understand the structure type and operational considerations before arrival on scene.

Training Video Conference Link Support in WebView

• What - Fixed an issue preventing Training video conference links from opening correctly inside the iOS embedded WebView experience. External meeting links such as Microsoft Teams or Google Meet now properly open through the device browser or installed native applications instead of displaying “Unable to load the page” errors.
• Why - This fix improves accessibility to online training sessions and external collaboration tools by ensuring responders can reliably launch meeting links directly from within the application. Removing navigation failures reduces interruptions during training workflows and improves overall WebView usability.
• How
  • Open a Training class containing a video conference link.
  • Select the meeting or camera button within the embedded WebView.
  • The external URL automatically opens using the appropriate browser or installed meeting application.
  • Existing internal WebView navigation behavior remains unchanged.
• Use Case - A responder attending a scheduled online training session can now launch Microsoft Teams or Google Meet directly from the Training module without encountering navigation failures or needing to manually copy meeting URLs outside the application.

WebView Battery Drain and CPU Usage Improvements

• What - Fixed a WebView navigation state feedback loop that caused significantly increased CPU usage and excessive battery drain during WebView-heavy workflows. Navigation state handling was restructured to prevent continuous rendering cycles while preserving form navigation safeguards and overall WebView functionality.
• Why - This fix improves application performance and device battery life during workflows that heavily rely on embedded web content, including Training, Fire Investigation, EMS Care Reports, and settings-related modules. Reducing unnecessary processing activity helps devices remain operational longer during active field use.
• How
  • Use WebView-based workflows normally within the application.
  • Navigation state handling now operates automatically in the background with optimized performance.
  • Existing form confirmation prompts and WebView navigation behaviors remain intact.
  • No user configuration is required.
• Use Case - A responder working through extended Training or EMS reporting workflows on an iPad or iPhone can now remain in WebView-based modules for longer periods without experiencing abnormal battery drain or device overheating caused by unnecessary background rendering activity.

iPad Map Hydrant and House Icon Rendering Improvements

• What - Fixed an issue on iPad devices where hydrant and house icons only appeared within the initial visible map area and failed to render correctly after panning or zooming. The map layer loading and visibility system was reworked to ensure icons continuously load as users navigate the map across both Google Maps and ArcGIS providers.
• Why - This fix improves situational awareness for responders relying on map-based hydrant, preplan, and location information while navigating large operational areas. Reliable rendering of map icons is critical for maintaining visibility into nearby resources during en-route and on-scene operations.
• How
  • Open the map view on an iPad device.
  • Pan or zoom across the map using either Google Maps or ArcGIS providers.
  • Hydrant, house, and related layer icons now load continuously as the visible map area changes.
  • The enhancement also supports viewport resizing during split-screen or rotation workflows.
• Use Case - A responder using an iPad during an active incident can now pan across surrounding operational areas and continue seeing hydrants, preplans, and related icons populate correctly without needing to reload the map or switch map providers, improving operational planning and resource awareness.