5.12.05 Release Notes

These Release Notes are for FH CAD Monitor release 5.12.05 and provide a listing of the enhancements implemented and defects resolved during this release.

Note: FH CAD Monitor requires FIREHOUSE Software 7.21.27 or later.

The following enhancements were implemented during this release.

On the System1 tab, options are now available to let you choose whether to calculate the last-cleared time using the en route to destination times, or to calculate it using the last-unit cleared time.

Additional information on these new option is available in Specify system settings.

For the TriTech VisiCAD, Spillman, and Tiburon interfaces, field mapping changes were made to let the ESO support staff better-assist customers when setting up the necessary configuration files for FH CAD Monitor on the FH Cloud, when it is in receiver mode.

The following issues were resolved during this release.

If you used FH 7.21.27 or older and the FH CAD Monitor VisiCAD interface with an ODBC database, the following error message appeared.

ODBC Error 207 ([Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'CAD_FDID'.)Error executing FH Database command

For the ESO EHR XML interface, on the General tab, on the Process sub-tab, the Authorization Type check box did not appear, and should have.

If you used the Generic XML interface and if your XML data file contained a District value greater than five characters in length, the following validation error appears.

"NB DI" is not valid for lookup category "Districts".

If you used the Generic XML interface and, on the System2 tab, under Incident Numbering Method, you had selected Calendar Year and imported XML data files, the imported records contained only the alarm date, FDID and incident number. If you imported CAD files containing unit codes that did not match any unit codes in FH, and in FH CAD Monitor, in the CAD Data Filters dialog box you had selected Exclude incidents where no units are dispatched, blank incident records were created.

If you used the Generic ASCII interface, and if in the CAD Data Filters dialog box you had selected Exclude incidents where no units are dispatched and created a filter for responding units to not-import a unit if its unit code was a specific value, incidents with no units were imported.

If you used the TriTech VisiCAD interface and imported an incident in FH, then later a unit number in that incident was changed and the incident was imported again, the following error appeared.

ODBC Error 2627 ([Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint