Crisis Track 4.9 Release Notes

These notes describe updates in the Crisis Track 4.9 releases for the desktop application scheduled on Tuesday, February 17, 2026. More information is available in this help center or by contacting the Juvare Support Center at +1 (877) 771-0911 or support@juvare.com.

New Features

Account Login: Case Sensitivity

When logging into the Crisis Track application, user names are no longer case sensitive unless there are established instances where there are multiple active users with a matching ID, due to the previous case sensitivity; for example, you can enter "jsmith", "JSmith" or "JSMITH". All new usernames will be validated without enforcing case sensitivity.

AI Image Description Generation

It is now possible to have AI generate an image description when uploading images to Entries for Public Damage, Commercial Damage, and Residential Damage forms. The Use AI button appears under the Damage Description field in the Assessment section.

This functionality is available on a client-by-client basis and is a limited access feature for early adopters. If you are interested in having this functionality enabled, contact your Client Success Manager (CSM). If this feature is enabled, settings for the AI output can be edited in the administrative Settings module.

For more information about creating entries, refer to Create Entries. For more information regarding the administrative Settings module, refer to Edit Settings.

Resident Self-Report Display

You can now view whether Resident Self-Reports are enabled for incidents by viewing the Self Report Enabled column in the Incident table. This allows you to quickly view whether or not the reports are enabled for the incident without needing to click through to the incident details.

For more information on editing the self-reporting status of an incident, refer to Manage Incidents.

Enhancements

  • Application improvements have been made when selecting a large number of structures via a polygon search.

  • When exporting a list of entries for an incident, the export options now have a unique value for each entry.

  • Several libraries have been updated, including the ArcGIS JavaScript library.

  • Application improvements have been made when exporting large numbers of entries to PDF, and the 1,000 entry limit has been removed.

  • Various remediations have been implemented to improve the overall security of the Crisis Track application.

Resolutions

  • Resolved an issue where map layers could be added without a type, preventing them from displaying properly.

  • Resolved an issue where map layers were not displayed properly after a refresh.

  • Resolved an issue where some new incidents were not properly created.

  • Resolved an issue where Guest User names were not properly sorted.

  • Resolved an issue where preconfigured tasks were not being created within Jurisdictions, and instead were created at the main account level.

  • Resolved an issue which did not clearly show when a user is logged out due to inactivity. Now, a user is properly taken back to the login screen and shown a message that clearly states they were logged out due to inactivity.

  • Resolved an issue which prevented statistics (total number of structures and structure value) from being displayed when an Area of Concern was uploaded via Shapefile.

  • Resolved an issue where Crisis Track allowed malformed or misconfigured map layers to be added to an account, resulting in misconfigured map layers that prevented other layers from being displayed.

  • Resolved an issue where the Timestamp field for entries did not export correctly to ArcGIS Online due to the time format being in 24-hour time.

Help Updates

The following help center pages have been added to collect and summarize important information:

Previous Versions

Release notes for previous versions are available here.