5.3.27 Release Notes

If your FH CAD Monitor provided an interface for generic ASCII file processing, each time the FH CAD Monitor service started and stopped, CAD Monitor wrote to a text file. This file continued growing unless you manually deleted it from the FH CAD Monitor installation folder. This file is no longer created.

If your FH CAD Monitor provided an interface for Spillman CAD, on occasion a call was missed because the calls were being written to the Spillman database later than the date and time FH CAD Monitor was searching back for calls.

To resolve this problem the Poll Overlap Time field is now available in all CAD interfaces. Information on this field is available in the FH CAD Monitor online help, under Specify system settings.

(FH Standard) If your FH CAD Monitor provided an interface between Integraph CAD and FH 7 standard, and if you configured FH CAD Monitor to pull data from the Scheduling module with the steps below, when FH CAD Monitor processed calls, it added all the staff members on the roster for that shift to the incident, regardless of unit assignment.

1. At the bottom of the FIREHOUSE Software CAD Monitor dialog box, click Options.

   The FIREHOUSE Software CAD Monitor Options dialog box appears.

2. Click the System1 tab.

3. In bottom right corner of the dialog box, under Query Personnel, select From FH Schedule.

4. Click Save.

If you configured FH CAD Monitor to pull data from the Scheduling module with the steps below, when FH CAD Monitor tried to calculate the hours worked and hours paid for staff members assigned to a specific unit, a series of errors appeared concerning the QueryCalc_PersonnelHours procedure.

1. At the bottom of the FIREHOUSE Software CAD Monitor dialog box, click Options.

   The FIREHOUSE Software CAD Monitor Options dialog box appears.

2. Click the System1 tab.

3. In bottom right corner of the dialog box, under Query Personnel, select From FH Schedule.

4. Click Save.

If FH CAD Monitor processed a call and created an incident, then the incident was canceled while the unit was en route to the scene, in FHnet, in Action Taken List for the incident, the lookup code was not automatically set to the 93: Canceled en route.

If you created default and trigger rules in FHnet, they worked correctly for incidents created within FHnet, but were ignored for incidents created through an FH CAD Monitor import. Calculate rules were also initially ignored when the incident was created through an FH CAD Monitor import, but then were applied when the incident was opened in FHnet.

If FHnet imports data from FH CAD Monitor, the unit number, alarm time, arrival times, and cleared times did not import correctly. When you saved the incident record created in FHnet from the import, the incident record did not always validate as expected.

If you tried to configure FH CAD Monitor to process and export CAD vendor data to FHnet with the steps below, you were not able to specify the CAD tables or record types from the CAD vendor that should not overwrite existing FH records when processed from the CAD vendor.

1. At the bottom of the FIREHOUSE Software CAD Monitor dialog box, click Options.

   The FIREHOUSE Software CAD Monitor Options dialog box appears.

2. Click the Database or Data tab.

   During installation, if you selected a CAD vendor that uses an ODBCOpen Database Connectivity data source or text data files the tab is named Database. If you selected a CAD vendor that uses XML data files, the tab is named Data.

3. From FIREHOUSE Software Database, select Update FHnet database.

   If you select this option, the User Name, Password, FDID, and URL options appear in FIREHOUSE Software Database.

4. Specify the information necessary for integrating FH CAD Monitor with FHnet as described in the Installation and Upgrade Guide.

5. Click the General tab.

   The Don't Overwrite tab did not activate as expected, and you could not specify the CAD tables or record types from the CAD vendor that should not overwrite existing FH records when processed from the CAD vendor.