7.17.04 Release Notes

The following NEMSIS files have been updated on the FH installation CD in the State directory, and on the FIREHOUSE Software web site.

• NEMSISOH2.FHz
• NEMSISOH3.FHz
• NEMSISOH3.FHz
• NEMSISAK2.FHz
• NEMSISOK.FHz
• NEMSISOK2.FHz
• NEMSISSD2.FHz
• NEMSISSD3.FHz
• NEMSISGA2.FHz
• NEMSISGA3.FHz

An option has been added to the automated task Run a Query, so that you can now choose to export all the fields to a spreadsheet, or only updated fields.

To find this new option, do the following.

1. Choose Administration → Automated Tasks.

   The Automated Task Setup dialog box appears.

2. Click New.

   The Automated Task Properties dialog box appears.

3. Under Task to Perform, select Run a Query, and then click Setup Task Parameters.

   The Queries dialog box appears.

4. Select the query you want to run as an automated task, and then click Select.

   Depending on the query you select, the Query Parameters dialog box may appear. If the query does not require additional parameters, the Output Query To dialog box appears.

5. (If the Query Parameters dialog box appears) Make selections in the dialog box as necessary, and then click Run Query.

   The Output Query To dialog box appears.

6. Select Other File Type, and then from the menu below it, select one of the Spreadsheet options.

   The Output All Fields option now appears. If you select this option, all the fields are exported; if you clear this option, only the updated fields are exported.

   

If you installed FH and then tried to launch FH, the following error appeared.

1426 (OLE error code 0x80040154: class not registered.) at line 297 of program STARTUP.

When you created an add personnel exchange and the activity record was created through an auto task, if you then you changed an end time or start time, a new activity record was created the next time the automated task ran, instead of updating the existing activity record.

A number of group names in the Wildland Federal Agencies lookup table were not correct, and two more missing.

If you were working with the Training module, and you attached and compressed a Microsoft Word .DOCX file with the steps below, when you later tried to run the file in FH, an Unable to execute error appeared.

1. Open the Training Class dialog box as normal.
2. Click the Other tab.

3. Click Attachments & Signatures.

   The Attachments & Signatures dialog box appears.

4. Click Add.

   The Attachment dialog box appears.

5. Navigate to and select a Microsoft Word .DOCX file as normal.
6. In the lower left corner of the dialog box, click Compress data on server.
7. Click Save, and then click Close.

8. In the Attachments & Signatures dialog box, select the attachment that is the Word .DOCX file, and then click Run It.

   An Unable to execute error appears.

If you specified FH database permissions that allowed information to be appended to incident notes and narratives after an incident record was locked, and assigned with the steps below, and then locked an incident record, you were not always able to unlock the narrative portion of the incident as expected.

1. Set the database security option to only allow information to be appended to the narrative of an incident record, after the record is locked.

   1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

   2. Click the Database tab, and then click the Data Security tab.
   3. Under Append-Only in Notes & Narratives, expand Incident Records Management → NFIRS Incident Reports, and then select the tables you want users to be able to append notes and narratives to after the incident record is locked.
   4. Click OK.
2. Set the individual user's permissions to be able to unlock narrative and override record lock status setting on locked incident records.

   1. Choose Administration → Administrative Options.

      The Administrative Options dialog box appears.

   2. Click the Incident tab.

      A series of sub-tabs appears.

   3. Under the All Incidents sub-tab, click the Authorizations & Locking sub-tab.

   4. Select Automatically Lock Incident Reports.

      The options below it activate.

   5. Select Disallow changes ___ hours after initial report entry.
   6. Click OK.
3. Lock the incident record you want to only have narrative information appended to.

   1. In the main FH toolbar, click Incident, and then open an existing incident record as normal.
   2. In the NFIRS Incident Report dialog box, click the Other tab.

   3. Click Record Lock Status.

      The Record Lock Status dialog box appears.

   4. Select Lock Record, and then click OK.
4. Select the incident record to override the locked record, to the degree that the user is allowed.

   1. In the NFIRS Incident Report dialog box, in the upper right corner, select Override Lock.

      Because you have administrative permissions to append note and narrative information to NFIRS incident reports, this setting lets you override the record lock for the incident enough to append information on the Incident Narrative tab.

   2. Click Save, and then click Close.

5. Reopen the incident record you just locked, and then click the Incident Narrative tab.

   Sometimes the Append button was disabled, when it should have been enabled.

If you ran the Activity & Training Hours/Points Detail report with any filter other than Activity/Training Date with the steps below, a box flashed in the background on the screen, but the report did appear on the screen as expected.

1. Choose Reports → Staff, Activity, and Training Reports.

   The Reports dialog box appears, with the Staff, Activity, and Training Reports section expanded.

2. Choose Activity & Training Hours/Points Detail, and then click Run.

   The Output Report To dialog box appears.

3. Under Select Output Type, select Screen, and then click OK.

   The Query Parameters dialog box appears.

   If you specified any filters in any row in this dialog box other than the Activity/Training Date row, and then click Run Query, a box flashed in the background on the screen, but the report did appear on the screen.

If you have a lot of users, the first time you opened the Users and Security dialog box and clicked a user name past the first page of users with the steps below, the user name that was highlighted was a name near the top of the list of users, instead of the name you clicked lower in the list.

1. Choose Administration → Users and Security.

   The Users and Security dialog box appears.

2. Scroll down the list of users until all the user names that were displayed when you initially opened the dialog box have scrolled off the top of the list.

3. In the list, click a user name.

   The list resets to the top of the scrollable list, and the user name selected is near the top of the list (not the user name you clicked further down in the list).

If you created an occupancy inspection and marked it as complete with no violations, then tried to print the violation report with the steps below, an error appeared stating that there were no records in the query.

1. Perform and complete the inspection as normal, and indicate that there are no violations.

2. In the Inspection dialog box, on the Basic tab, in the lower left corner of the dialog box, click Print Violation Notice.

   The Output Report To dialog box appears.

3. Select the options you want for printing the violation report, and then click OK.

   FH attempts to run the no-violation report, and and then the error stating that there are no records in this query appears.

If you ran the Staff Member Participation Report report with the steps below, the following error message appeared.

Error 1429: OLE IDispatch exception code 0 from SWbemServicesEx: Generic failure .. at line 30 of procedure/method RPTPARTICIP.RPTSESSION.SETFRXVALUE.

1. The Reports dialog box appears, with the Staff, Activity, and Training Reports section expanded.

2. Choose Staff Member Participation Report, and then click Run.

   The Staff Participation Report dialog box appears.

3. Under Date Range, change the dates as needed for the time span you want in the report and then click OK.

   The Output Report To dialog box appears.

4. Under Select Output Type, select Screen, and then click OK.

   The error message appeared.

If you were importing your fire incidents from FH CAD Monitor and had specific administrative options set in FH, when you opened an incident through the Incident module or the Department Journal, the incident was already locked when it opened and you were not able to edit it.

1. Choose Administration → Administrative Options.

   The Administrative Options dialog box appears.

2. Click the Incident tab.

   A series of sub-tabs appears.

3. Under the All Incidents sub-tab, click the Authorizations & Locking sub-tab.

4. Select Automatically Lock Incident Reports.

   The options below it activate.

5. Select Allow only the user who entered the report or a system administrator to modify.
6. Click the Restrictions & Ownership sub-tab.
7. Under Ownership of Records Imported from CAD or External Data, select Automatically prompt to take ownership of unassigned records when the record is selected for edit.
8. Click OK.
9. Access the Department Journal as normal, and find a fire incident from FH CAD Monitor .

10. Double-click the journal entry to open the incident.

    A message appears asking if you want to take ownership of the incident.

11. Click Yes.

    The Validation Results dialog box appears.

12. Click Ignore All.

    The Assign Report dialog box appears.

13. Click OK.

    A prompt for confirmation of ownership assignment appears.

14. Click Yes.

    A confirmation dialog box appears.

15. Attempt to enter or edit data in the incident record.

    The record is still locked, and you are not able to enter or edit the data.

If you were using FH Enterprise 7.15.32 or 7.15.37, and you created an automated task to update activities in the Schedule module with the steps below, the date and time fields in the resulting activity records appeared to be populated in the FH interface, but did not have valid date and time values in the FH database. If you then tried to run an activity report using a date/time filter, an error message appeared stating that no records were found.

1. Choose Administration → Automated Tasks.

   The Automated Task Setup dialog box appears.

2. Click New.

   The Automated Task Properties dialog box appears,

3. Under Task to Perform, select Update Scheduling Activity, and then click Setup Task Parameters.

   The Query - Schedules by Name dialog box appears.

4. Select the schedule you want to automatically update the activities for, and then click OK.

   The Automated Task Properties dialog box becomes visible again.

5. Fill out the rest of the fields in the dialog box as normal, and save and close the automated task dialog boxes.

   When the automated task runs, the new records were created in the schedule, and in the FH interface, in the Staff Activity dialog box, the Start Time and End Time fields appeared to be populated as expected in those records.

   However, if you tried to run a staff activity report and filter the report based on activity date/time, an error message appeared stating that no records were found.

If you updated to FH Enterprise 7.15.32 and you have custom user-defined fields, when you try to open FH, or open an incident, activity, or journal record, the following message appeared.

Unable to open <table name> tables in exclusive access mode.

An automatic internal process in FH for installing state-specific .FHz files did not install all the necessary .FHz files as expected.

If you set up an automated task for a custom data export, the task would run, but the export file was not created and the following error message appeared instead.

Failed.
NEMSIS Demographic Output XMO is NOT valid according to <path> EMSDEMOGRAHICDATASET.XSD

If you are using the Ohio NEMSIS code set and you indicated that a patient had an injury with the steps below, an option for patient safety equipment did not disable automatically.

1. Start an EMS incident record as normal.
2. Click the Patients/Victims tab.

3. Click Add.

   The Patient/Victim Information dialog box appears.

4. Click the Scene tab.

5. From Injury or Illness, select Yes.

   In the lower right corner of the dialog box, under Patient Safety Equipment Worn or Deployed, the N/A options remains active, when it should have been disabled.

If you tried to run the custom NEMSIS Demographic Data Export for Ohio, the following error message appeared.

Failed
The local copy of the EMSDemographicDataSet.xsd file is missing.
NEMSIS Compliance testing can not be performed.

1. Choose File → EMS/Search & Rescue Reporting → Export EMS Transaction File.

   The Select EMS Export dialog box appears.

2. Select NEMSIS Demographic Data Exort, and then click OK.

3. Fill out the rest of the screen in the export wizard as normal, and then click Finish.

   The error message appears.

(FH Database Tools) If you were running FH Enterprise and using SQL Server 2012 for your FH database, when you try to clear the inactive logins with the steps below, the following error message appears.

ODBC Error 2812: [Microsoft][ODBC SQL Server Driver][SQL Server] Could not find stored procedure 'sp_dboption'

1. Choose Start → All Programs → FIREHOUSE Software 7 → FIREHOUSE Software Database Tools.

   The Database Tools dialog box appears.

2. In the lower left corner of the dialog box, click View Active Logins.

   The Active Logins dialog box appears.

3. In the lower left corner of the dialog box, click Attempt to Clear Invalid Logins.

   The error message appears.