7.19.17 Release Notes
These Release Notes are for Firehouse® release 7.19.17, and provide a listing of the issues resolved during this release. The changes listed in the Release Notes apply to both FH® Standard and Enterprise editions.
The following enhancements were implemented this release.
In the Incident module, you can now save incomplete incidents, even if user fields do not have valid data in all of them. This capability lets you save a NFIRS report without filling in every required field, which can be useful if data entry is interrupted by other fire station duties.
To find the new feature, do the following.
You can now filter the NFPA Yearly Experience Survey Report to exclude specific unit types from the report.
To find this new filter, do the following.
- Choose Reports > Incident Reports.
- In the Reports dialog box that appears, expand Incident Reports > NFIRS Incident Reports > Incident Statistical > Incident Statistical Summary.
Select NFPA Yearly Fire Experience Survey, and then click Run.
The NFPA Yearly Fire Experience Survey dialog box appears, containing the new TYPE field.
Any units you specify in the TYPE field are excluded from the report.
For Ontario customers, the Incident Type Report (Summary) report can now query groups in the incident type lookup that are grouped by letters followed by numbered values.
The following issues were successfully resolved this release.
In the Incident module, if you made changes to the fields and clicked Cancel, a prompt appeared asking if you wanted to save, discard, or cancel the changes. If you clicked Save, the changes were saved, even if you had only view permissions for the module.
In the Administrative Options dialog box, on the Incident > EMS/Search & Rescue > Privacy and HIPAA tab, under Information Privacy, List all matching patient record names when starting a new patient record is selected by default.
If you cleared this option and saved the change, then in the EMS module, when you began to add a new patient/victim to a record, if under Last Name, you typed a last name and pressed the Tab key on your keyboard, the lookup dialog box that appeared listed records in FH with matching record patient names. These names should not appear when List all matching patient record names when starting a new patient record is cleared.
In the Incident module, on the Units & Personnel tab, under Units, if you clicked Open All, in the Response Detail dialog box that appears, time values in the table were highlighted red and the Basic tab was red, and should not have been.
In the Schedule module, when you double-click a staff member identified as OD ( on-duty), the Shift Personnel Exchange or Exception dialog box appears. On the Basic tab, for Covering Staff, if you select No covering staff necessary, click the Assigned tab, then click the Activity Code lookup button (), select VC (Vacation) and click Edit, the Code for Staff Activity Types dialog box appears.
If you changed the value in Default Hrs Paid to
24 and clicked Save, the value for VC in the Def Hpd column updated to
24 as expected. If you selected VC and clicked OK, in the Shift Personnel Exchange or Exception dialog box, on the Assigned tab, in the Hours Paid field, the value did not correspondingly update to
24 as expected.
If you use AVG anti-virus software and installed FH 7.18.18 or 7.18.19, messages appeared stating that viruses existed in the
updateuser.exe files in the
C:\firehouse software folder. The files did not contain viruses, and were erroneously reported by AVG.
While installing FH on a Windows 10 computer, a blue screen appeared, and Windows shut down and rebooted the computer. If you install the Windows 10 Anniversary Update, FH installs without this issue.
If you updated to FH 7.18.18 and had automated tasks for generating a PDF file or running a report, the scheduled tasks did not run as expected, and no errors appeared in the log file.
In FH Enterprise, in the Administrative Options dialog box, on the General > Security tab, if you selected Allow individual user preferences, some global options for Length of Service Award Programs (LOSAP) reports and macros were incorrectly overridden by user preferences.
In the Administrative Options dialog box, on the Database > Field Captions tab, you have the ability to change the default FH field labels to something else.
If you had changed the field labels and then updated to FH 7.17.17, the custom field labels were removed and the fields reverted to their default names. The custom field labels should remain during a software update.
In FH Inspector, when you completed a scheduled inspection that had no violations, then synchronized it with the FH database, FH created an unnecessary reinspection for the occupancy or hydrant.
The National Emergency Medical Services Information System (NEMSIS) codes for Iowa departments were missing some of the E9.14 (Other Associated Symptoms) lookup codes.
If you added a user-defined field as normal, when you clicked Save in the User Fields dialog box, the following error message appeared, where DatabaseName is the name of the SQL database.
Error # 515
Description of Problem: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert the value NULL into column 'category', table 'DatabaseName
.dbo.uf_form'; column does not allow nulls. INSERT fails.
When updating from FH Enterprise 7.14.19 (using FH Web) to 7.18.19, the following error message appeared.
odbc error 515 cannot insert value NULL into the column 'total_amt' table fh_sjfd2.dbo.acc_invc; column does not allow nulls. Update fails.
If you choose Tools > Workstation Options, then in the Workstations Options dialog box that appears, on the Scheduling tab, you can use Default Schedule to specify what type of schedule is opened by default in the Scheduling module.
However, when you opened the Scheduling module, it did not open with the default schedule you had specified in the Workstation Options dialog box.
In new installations of FH 7.19.04, when you opened the Scheduling Console, the following error message appeared.
The demo version of SftTree/OCX has expired.
If you edited an occupancy's contact information in FH Inspector on the iPad and completed the occupancy's inspection, then synchronized FH Inspector with the FH database, some of the occupancy's contact records were duplicated.
In the Incident module, in the NFIRS Incident Report dialog box, on the Incident Narrative tab, when you click Auto-Generate in the lower right corner, the Narrative Generation dialog box appears. If you then click Generate Narrative, SQL expressions and the FH template appeared instead of text for the alarm date, incident type, or requested fields from the report.