7.7.0 Release Notes
These Release Notes are for Firehouse® release 7.7.0, and provide a listing of the defects resolved and the enhancements implemented during this release. The changes listed in the Release Notes apply to both FH™ Standard and Enterprise.
When renumbering the records, users were able to edit the ID field of existing records to include an apostrophe or other special characters.
Example: If an apostrophe or other special character is saved in an ID field, when a user chooses Administration → Database Audit Log, clicks the Data tab, and then selects Invoicing & Accounts Receivable, the following error appeared: Error 102: [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near 'S'.
The issue has been resolved.
Apostrophes and special characters are no longer allowed when renumbering ID fields.
In the Administrative Options dialog box, on the Incident → EMS/Search & Rescue → NEMSIS tabs, in the Run XML Validation on Each Incident section, the default selection was Never.
The issue has been resolved.
The default is now Until, with the Incidents have validated successfully set to 100 days.
When a user saved a usage or vehicle extrication record, the incident's completion status is not updated. If there are requirements based on having a usage or extraction record , the incident's completion status remained incomplete, even though all requirements were met.
In fire and EMS incidents, sometimes the completion flag is not set to True, even though the incident is complete and full audit tracking was enabled.
The order of operations for a requery in the Incident and EMS modules can also cause the completion flag to be set incorrectly.
When a user completed an Incident of type 611 (Dispatched & cancelled en route), FH required any responding units to complete a Units Action Taken record.
Cancelled was selected automatically, and a time was required. If the user uncheck the option and recheck it, FH auto-completed Unit Actions Taken record. If the user did not check and recheck Cancelled , FH did not automatically complete the Unit Actions Taken record.
The issue has been resolved.
FH now auto-completes the Unit Actions Taken record with a code of 93 when the unit record is created.
The current NEMSISNM.FHz
file is missing the null values for medications and procedures, and the procedure code 154044 for Airway - BVM.
NemsisVA.FHz
file contained unmapped lookup codesThe NemsisVA.FHz
file contained unmapped lookup codes.
After filling out a NFIRS report and specifying authorizations on the Other tab in the NFIRS Incident Report dialog box, the user clicked the Additional Reports tab, and then EMS/Search & Rescue. In the EMS/Search & Rescue Report dialog box that appeared, the user clicked the Patients/Victims tab, and then clicked Add. In the Patient/Victim Information dialog box that appears, the user clicked the Other tab, and then clicked Copy from NFIRS Report.
If the FH login does not have an associated staff ID, the following message appeared:
One or more authorization type(s) may not be copied due to the reason(s) below:
1. Staff ID is not linked to user login
If the staff ID linked to a specific user security record has been disabled, the following message appeared:
1. User linked to Staff ID has been disabled.
Note: The same issue occurred when copying from EMS to NFIRS.
The issue has been resolved.
If a user is not linked to the quality control person and the user does not have access, the following message now appears:
1. QC 38-JTR Current user does not have Quality-Control Check Report rights.
When a user has EXPDFS installed and adds codes to the medical/surgical code, the <E12_10>Cancer</E12_10>
error appears.
Several codes for mechanism of injury needed to be removed from NemsisGA.FH
.
If certain rules for disabling fields are already established, when attendees are added in the Training module using the Add Group button, the following error message may appear:
error 152: Missing expression at line 55 of procedure/method TRN_GUPD.CTRCHKGROUPUPDATE5.SETRULEPROP
(FH Enterprise only) If data that was missing date values in required fields was imported into the Occupancy module, records which did not have a valid date did not appear in the Permits dialog box. These records did appear when a report or query for the number of permits per occupancy was run.
The issue has been resolved.
The list displayed in the Permits dialog box shows all data, even that which does not contain valid dates.
When the user attempted to delete an entry from the Journal module, the following table update error appeared:
1492 No key columns are specified for the update table "act_det". Use the KeyFieldList property of the cursor.
(FH Enterprise) In the Message module, when the user attempted to delete an inspection from the Daily Reminders dialog box, the following table update error appeared:
1492 No key columns are specified for the update table "act_det". Use the KeyFieldList property of the cursor.
When the user fills out a NFIRS Wildland Fire Report with the number of acres under 1000 acres, the total number of acres displayed when the report is run is incorrect.
Example: The user fills out a NFIRS Wildland Fire Report and specifies the number of acres as 160. When the NFIRS report is run, the total acres burned is reported as 60.
When the user chooses Reports → Occupancy Management Reports, and then in the Reports dialog box, selects Inspection Master Reports → Completed Inspection Checklist, and creates the report, the output in Notes or Corrections Below section causes the Labels and Fields to misalign.
summing totals correctly
When the user chooses Reports → Staff, Activity, and Training Reports, and then in the Reports dialog box, selects Training Classes Reports → Training Attendance by Rating Bureau Criteria, and creates the report, the totals in the Default Hrs
and the UnExc
columns are not summed correctly.
FHJWebEdtionServerSetup.exe
FH builds 7540-7584 have a 3.1.1.3520 version of
FHJWebEdtionServerSetup.exe
. This version is no
longer supported. Incompatibility errors with Ntoskrnl.exe
will be encountered if this outdated version is installed.
When a user tried to enter a new password or modify an existing password for reports and queries, the following error message appeared:
Error 13: Alias 'USERRECORD' is not found. at line 21 of procedure/method FRMSETPASSWORD.SAVE.
When a user clicked Ignore in the Report Password form, the following error message appeared:
The password you have chosen is not accecptable. It may be too long or contain a series of characters that are not crytographically secure. Please choose another password.
The following files have been added to or updated on the CD, in the State
folder:
NemsisVA.FHz
NemsisGA.FHz
NemsisNM.FHz
NemsisNM2.FHz
NemsisAL2.FHz
NemsisPatientExport.FHz
NemsisDemographicExport.FHz
You can now generate a report to find any unused or missing invoice numbers.
Note: Only invoices with a numeric invoice ID are reported.
To find the new report, do the following: