7.25.28 Release Notes
These Release Notes are for Firehouse® release 7.25.28 and provide a listing of the enhancements and issues resolved since the 7.24.30 release. The changes listed in the Release Notes apply to both FH Standard and FH Enterprise editions.
The following enhancements were implemented this release.
The screen magnification feature initially released in FH 7.24.30 has been extended to include the User Fields dialog box for entering data in a module.
Example:Suppose in the EMS module, user fields are already defined, and you only need to enter data into them for the EMS record. If you open the EMS/Search & Rescue Report dialog box, click the Other tab, then click User Fields, the EMS/Search & Rescue Incident User Fields dialog box appears displaying the user fields already defined and arranged in the dialog box. In this dialog box, the screen magnification is applied. |
Note: Screen magnification is not applied to the User Fields dialog box that appears when you define and arrange the user fields for a module.
Example:If you have not created user-defined fields in the Occupancy module, when you open the Occupancy dialog box, click the Other tab, then click User Fields, a prompt appears asking whether you would like to create user fields. If you click Yes, the module_name User Fields dialog box appears, ready for you to being adding fields and arranging a layout for them. The screen magnification is not applied in this dialog box or to the associated User Fields Toolbar. Once you finish defining and arranging the fields, they are appropriately magnified in the "finished" (data entry) User Fields dialog box. |
[FHD-1177, FHD-1892]
According to the Codes & Standards, NFPA 1710 web page, the NFPA 1710 time standards for codes 5.2.4.1
, 5.2.4.1.1
, 5.2.4.1.2
, 5.2.4.2
, and 5.2.4.2.1
have changed from the 5–9 minute range to a 4–8 minute range. The NFPA 1710 EMS Detailed Report and NFPA 1710 Engine Detailed Report in FH have been updated accordingly.
[FHD-2074]
The following issues were successfully resolved this release.
In the Administrative Options dialog box, on the Incident > All Incidents > Resources, Units and Personnel tab, in the Requirements section, you can select Require resource detail (units and personnel), then select one or more of the Require units, Require personnel, and Require personnel info for each unit options. When you select these options, FH requires that units and/or personnel information is included an incident record.
In the Incident module, on the Response tab, under Resources, the Count from detail forms field is now selected and greyed out (disabled), and the Apparatus and Personnel columns in that section can not be filled out. Instead, FH will pull information about the number of apparatus and personnel deployed to the incident from values entered through the Units & Personnel tab, using unit response and personnel detail records.
If you had a month when no incidents occurred, then there would be no units and personnel information to export. However, when you exported a no-incident activity report, the following error message appeared, indicating that you had not completed resource records (unit response and personnel detail records).
Count from detail forms is specified on detail record, but resource records not completed.
[FHD-2163]
In the Workstation Options dialog box, on the General > Startup & Navigation tab, under Startup, you can select options to automatically load the Journal module and/or the Reminders dialog box when you log in to FH.
If you selected either of these options, the next time you logged in to FH, FH loaded the Journal module and/or Reminders dialog box before it loaded the FH toolbar. When the toolbar then loaded, it pushed the Journal module or Reminders dialog box down on the screen, and cut off the bottom half of the icons along the bottom edge of the module and dialog box.
[FHD-1885]
In Inventory module, on the Specs tab, for Inventory Type, when you chose Hose, the fields on the tab updated. Under Coupling Specifications, the field label Coupler Type was missing a space.
[FHD-1797]
In the Staff module, the Station field in the upper right corner identifies the primary station. You can still add additional stations to a staff record in the lower left corner, in the Other Stations section.
If you added the same station identified as the primary station in the Other Stations section and tried to save the staff record, an incorrect validation message appeared.
[FHD-557]
For the Incident module, in the NFIRS Incident Report dialog box, on the Units & Personnel tab, when you select a unit or personnel record in the respective lists and click Open, the Unit Response Detail or Participant Detail dialog boxes appear, respectively.
If you then dragged the window that opens over and that dialog box to a new position on the screen, a "trail" of dialog box edges was left across NFIRS Incident Report dialog box.
[FHD-16]
If you used the batch-report capability in FH to generate any reports outside the Incident module, the following error appeared.
Error 12: Variable 'INCI_ID' is not found. at line 166 of procedure/method RPTRUN.RPTSESSION.RUNCOLLATED.
[FHD-1109]
If you chose Administration > Administrative Options, in the Administrative Options dialog box that appears, on the Staff > Activities & Training tab, you can select Hide fields for public service (smoke detectors and safety seats installed) to hide specific fields in the Staff Activity module.
However, if you selected this option, not all of the fields were hidden as expected in the Staff Activity dialog box, on the Public Education/Service tab.
[FHD-1037]
If you created a new query for a report, when you ran it, the following error message appeared, and should not have.
Error 1560: Property value is invalid. at line 15 of procedure/method RPTRUN.QRYSESSION.SETVIEWPROPS."
If you clicked Ignore and continued running the report, the results appeared as expected.
[FHD-611]
In the Incident module, if you create a new incident, assigned it an incident type of 756 (Carbon monoxide detector activation, no CO)
, then in the Actions Taken section, you added an item of type 10 (Fire control or extinguishment, other)
, then tried to delete that item, the following error message appeared.
You cannot delete this required. 1 entries are required
The wording of this message has been improved to be a complete English sentence.
[FHD-589]
If you had a user-defined field with one character as the field name, the following error message appeared when you logged in to FH.
Variable 'VPARAM0' is not found
Note: From this release and in future releases, you can no longer create user-defined fields named with one character.
The issue has been for user-defined fields with one-character field names created in the past.
[FHD-47]
In the Administrative Options dialog box, on the Incident > All Incidents > Authorizations & Locking tab, an FH administrator can enable the necessary permissions for non-admin FH users to perform quality control checks on incident records,
An FH user who does not have administrative privileges can access the Incident module and open multiple incidents. The user can click the Other tab and, under Report Authorizations, click Add and use the Report Authorization dialog box that appears to add and save a new authorization as normal.
If the FH user used the VCR-style buttons in the lower left corner of the NFIRS Incident Report dialog box to advance to the next incident record, the Add button under Report Authorizations became disabled, and you could not add a report authorization to that record.
[FHD-1009]
You can access the Inspection Checklist dialog box from several places in FH. If you click New in this dialog box, a prompt appears asking if you would like to make a copy of an existing checklist as the basis for your checklist. If you click Yes, another Inspection Checklist dialog box appears, prompting you to select the checklist you want to copy.
When you copy a checklist, FH automatically adds the words Copy of
to the beginning of the name of the checklist you select for copying. If you selected a checklist that had over 42 characters in its current name, FH's 50-character name limit for inspection lists was exceeded, and the following error appeared.
Error 8152: [Microsoft][ODBC SQL Server Driver][SQL Server]String or binary data would be truncated
Now, the name of the new checklist is truncated at 50 characters.
[FHD-239]
In the Inspection dialog box, if you created or opened an existing inspection, clicked the Violations tab, and added 10 or more violations (enough to make scrolling up or down the list of violations necessary), then tried to select one of the violations, the cursor behaved erratically and would not highlight the record you were trying to select.
[FHD-1862]
In the Administrative Options dialog box, on the General > Display tab, in the Screen Magnification Settings section, you have the option to set screen magnification to Full or Intermediate.
If you changed the magnification, then added a system rule or default value to a field, when you verified the new rule or value, the verification results dialog box displayed behind the System Rule Expression dialog box, where it was hidden from sight. If you did not move the System Rule Expression dialog box to find the verification dialog box, FH appeared to be unresponsive and had to be manually closed through your Windows Task Manager.
[FHD-1922]
In the Administrative Options dialog box, on the General > Display tab, in the Screen Magnification Settings section, you have the option to set screen magnification to Full or Intermediate.
If you changed the magnification, then choose Administration > User-Defined Fields, the headings in the User-Defined Fields Setup dialog box that appeared were too large and the line and character spacing was too small. When you expanded the list under a heading, the fields listed under the headings were not magnified at all.
[FHD-1861]
In the Administrative Options dialog box, on the General > Display tab, in the Screen Magnification Settings section, you have the option to set screen magnification to Full or Intermediate.
If you changed the magnification, resized the main FH window, opened any module and an existing main record in it, then clicked Open or Add to access or add a child record to the main record, the field label text in the dialog box that appeared for the child record was not the same size as the field label text in the module's main dialog box.
Note: This issue is related to the physical size of your monitor, and can not be resolved in the FH application.
[FHD-1662]
If you choose Reports > Staff, Activity, and Training Reports, the Reports dialog box opens with the list of reports in this category already expanded. If you then expanded Staff Scheduling Reports, selected Exchanges/Reassignments NOT Approved, and clicked Run, the following message appeared even when there were unapproved exchange/reassignment records in the database.
There are no records in the main query for this report.
[FHD-1026]
If you ran the NFIRS Incident Report report and, in the Output Report To diaog box, you selected the New PDF option, in the resulting PDF file, the Narrative box did not expand in length as needed to accommodate the text entered in the FH Incident module. While the narrative text was not cut off, the bottom line of the Narrative box obscured one of the text lines where it overflowed the box.
[FHD-1024]
If you have user-defined fields defined in your Incident module, if only informational messages appeared in the Validation Results dialog box, and if you clicked Ignore for these messages, FH set the incident's status to Incomplete
instead of saving the record with a Complete
status.
[FHD-2089]
In FH 7.5.84 and higher, if you change the desktop color from the default gray to another color, a single gray pixel remains on the FH background
[FHD-2183]
If you tried to opened a Google map of a location in FH, the following error appeared in the browser window.
The Google Maps Platform server rejected your request. You must use an API key to authenticate each request to Google Maps Platform APIs.
Note: To resolve this problem, you must go to the Google console, generate an API key and a secret signing key, then enter those keys in FH. Instructions for generating and entering these keys are available in Generate and apply Google map keys.
[FHD-1842]