7.17.28 Release Notes
These Release Notes are for Firehouse® release 7.17.28, 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.
Tip: You may want to also consult the Release Notes for 7.17.17, for a list of defects resolved and enhancements implemented during the previous release. These Release Notes are available as PDF files at 7.17.17 Release Notes, or as online help at 7.17.17 Release Notes .
The following issues were successfully resolved this release.
When you log into FH for the first time after an update, the remote folder loads automatically. If you upgraded to 7.16.07 or 7.17.04, the remote folder loaded with every login instead of only with the first login.
If your installation of FH is hosted on the FH Cloud, automated tasks did not stay running as expected, which impacted automatic synchronizations of data from FH Inspector.
(FH Enterprise) If you are not a user with administrative permissions, in the EMS module, if you opened a patient/victim record and clicked the Patient Narrative tab, a
1925 Unknown member CMDAPPEND appeared. This error also appeared in the NFIRS module if you clicked the Incident Narrative tab.
If you had an installation of FH on the FH Cloud, when users with normal permissions opened the EMS module and clicked Browse, FH was slow to open the record browser window.
If you created a PDF file in FH, a folder was automatically created using the file name. If you used the email feature in FH to email the PDF to another person, the email did not reach the person it was sent to.
In the Inventory module, if you created a user field and added a rule to require the field whenever a specific inventory ID is specified, then created a NFIRS record and tried to add an inventory usage/purchasing detail record to it, in the Usage/Purchasing Detail dialog box that appeared, the Other tab did not turn red to indicate that it is required. If you clicked the Other tab, the User Defined Fields dialog box did not appear, and a message that the user field is required appeared instead.
If you use an automated task to print reports to a PDF file, in the Automated Task Log Details dialog box, the PDF file was not generated and several error messages appeared on the Exceptions & Errors tab.
If you used FH Web to access FH Enterprise, when you logged in, an error message appeared stating that you need to give full control to the
FH.lic file to print; if you clicked OK, the message closed and you could print from within FH without a problem. This error message should not have appeared.
In the Incident module, on the Basic tab, if you clicked Supplemental Address, and then in the Supplemental Address dialog box that appears you clicked Find/Map Longitude/Latitude, the following error appeared.
Open of file "C:\users\russm\appdata\local\teamp\adashikmlexport.kml" failed. Parse error at line 126, column 40: not well-formed (invalid token)
If your NFIRS transaction file lists responding personnel in sequential numbers, and if you opted to automatically add staff ID numbers, unit ID numbers, and address components when you imported the transaction file, the import added all the responding personnel to the first unit, instead of to the correct units.
When you saved a report to a .PDF file, a folder with the specified file name was created instead, and the file itself was named using the date and time inside the folder.
In the accounting module, if a payment or an invoiced was voided, it still appeared in the Reconcile/Close Accounting Period dialog box with the original amount. If the amount was selected, the ending balance for the month changed and did not balance with the total billing and revenue received.
If you printed individual reports to individual PDF files, you were prompted to press OK for each report. FH now prints all the reports in the query with their individual names, without the prompt.
In the Inventory module, on an apparatus record, when you clicked Add Other, the default inventory browse dialog box appeared instead of a drop-down menu listing the equipment linked to the unit (based on its Inventory ID).
If you selected a new criteria as default, the new criteria selection did not save as expected.
In the Incident module, when you browsed for and selected a few incidents, then pressed Copy to Clipboard, all the files were copied instead to the clipboard instead of only the selected files.
If you installed the Michigan-specific NEMSIS lookup codes, the Complaint Reported by Dispatch field turned red and did not accept the codes provided.
When you start the
AutoRun.exe program, the FH installation or update dialog box appears. If you used it to install FH, and opted not to install the documentation near the end of the installation process, the installation wizard closed but the FH installation or update dialog box still appeared. If you clicked Exit in the dialog box, a message that the installation was not finished appeared.
When a new license with a new serial number was applied, FH did not remove the previous license first, and then did not allow the new serial number to be applied.
Unapproved third-party applications could be run through automated tasks.
In the Incident module, the List NFIRS Incidents Not Geocoded query returned records that have latitude and longitude records with values greater-than zero, and should not have.
If you have a hosted installation of FH and tried to print a report, the contents of the report were pushed to the right, and the right side of the report was cut off.