Fire Reports Release Notes - v1.47 - December 16th, 2019

Fire Reports v1.47

December 16th, 2019

New in This Release

New Feature Highlight: 

The following new features are the most impactful for users, so we describe them here in greater detail:

New Features

The following features have been added in this release:

KeySummaryRelease Notes
FIRE-584Prevent Save of Empty Apparatus Data Previously, when users clicked "Add Apparatus" and forgot to enter any data, the information would save as empty data. This would affect reporting by showing as blank information. While it would not affect overall numbers, it made reports look cluttered. We have made a change that will exclude empty apparatus data from reporting.

Improved in This Release

The following issues have been addressed and resolved in this release:

KeySummaryRelease Notes
FIRE-615Passwords with Ampersand Cannot Sign Fire Incident Fixed an issue where passwords containing ampersands would not be able to sign fire reports. This issue resulted from new password security measures added on the sign offs tab.
FIRE-611When user clicks on any row of validation Summary for Apparatus Personnel, it should navigate to the related apparatus tab in Apparatus Personnel section. The validation summary was fixed to allow navigation to specific apparatuses. If you have multiple apparatuses with validation errors, you would previously be brought to the apparatus tab, but not necessarily the apparatus with the error.
FIRE-592Review Apparatus Tab Validation Timings Made numerous back-end improvements to the apparatus tab to increase performance and optimize custom validation rules. Further changes are pending.
FIRE-574Hazmat Which Occurred First Fixed an issue on the Hazmat tab with incident types in the 100 or 200 range.
FIRE-565Relational Edit 173 Fixed an issue on the Basic tab with incident types in the 113-118 range. There was an issue with the "Detector Alerted Occupants" field when the selection was changed after revisiting the basic tab.

Known Issues

The following issues have already been identified and will be addressed in a future release:

PDF Release Notes



Golden Hour