5.3.76 Release Notes

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

Note: FH CAD Monitor requires FH 7.9.14 or FHnet 2.0.18.08 or later.

The following enhancements were implemented during this release.

Note: These enhancements are available only in integrations between FHnet and FH CAD Monitor.

(Generic ASCII interface) If your CAD vendor does not provide an EMS record as part of the data file that FH CAD Monitor reads, you can now configure FH CAD Monitor to write an incident report that contains a NEMSIS-coded reason for dispatch.

To find and use this new feature, do the following.

  1. At the bottom of the FH CAD Monitor interface, click Options.

    The FIREHOUSE Software CAD Monitor Options dialog box appears, set to the General tab.

  2. On the Process tab (within the General tab), select EMS Incident Report.
  3. Click the Database tab.
  4. For FIREHOUSE Software Database, select Update FH.Net database.
  5. Specify the rest of the values on the Database tab as appropriate for your implementation of FH CAD Monitor.

  6. Click the Filters & Data tab, and then click Field Mapping on the tab.

    The Field Mapping dialog box appears.

  7. For Show Field Mappings for Table, select EMS Incident Report.

    The fields listed in the dialog box update to list the Reason For Code (NEMSIS) row.

  8. In the Maps to CAD Data Element cell for the row, choose Specify literal value or expression.

    The Specify Literal Value or Expression dialog box appears.

  9. In the dialog box, type cad_incidents.INCI_FLD_30, and then click OK.

    The value you specified appears in the Maps to CAD Data Element cell.

  10. Click OK.
  11. Click the System2 tab.

  12. Select Force Creation of EMS Record.

    This is the new option which creates the EMS record from the incident record.

  13. Click Save.

Information on using this option is available in the FH CAD Monitor User's Guide, in Specify system settings.

(FH CAD Monitor using the generic ASCII interface) On the System2 tab, the Bypass unknown unit record option has been added to let you choose whether or not a unit record with an unrecognized unit code is imported into FHnet. If you select this option, no unit record is created if the unit record's unit code does not exist in FHnet. If you clear this option, the unit record imports with a blank unit code.

To find this new feature, do the following.

  1. At the bottom of the FH CAD Monitor interface, click Options.

    The FIREHOUSE Software CAD Monitor Options dialog box appears, set to the General tab.

  2. Click the Database tab.
  3. For FIREHOUSE Software Database, select Update FH.Net database.
  4. Specify the rest of the values on the Database tab as appropriate for your implementation of FH CAD Monitor.

  5. Click the System2 tab.

    The new Bypass unknown unit record option appears on this tab.

    Information on using this option is available in the FH CAD Monitor User's Guide, in Specify system settings.

Using the generic XML file interface, you can now indicate whether or not you want to create incident authorization records in FHnet when the CAD data file does not contain specific data for them.

  1. At the bottom of the FH CAD Monitor interface, click Options.

    The FIREHOUSE Software CAD Monitor Options dialog box appears, set to the General tab.

  2. Click the Database tab.
  3. For FIREHOUSE Software Database, select Update FH.Net database.
  4. Specify the rest of the values on the Database tab as appropriate for your implementation of FH CAD Monitor.

  5. Click the System2 tab.

    The new Create default authorization records option appears on this tab.

    Information on using this option is available in the FH CAD Monitor User's Guide, in Specify system settings.

Using the generic XML file interface, FH CAD Monitor now creates incident action records in FHnet, when the incident action data exists in the CAD file.

The following issues were resolved during this release.

If the CAD data for the Incident Type field is over 10 characters long, FH CAD Monitor was not able to convert the field.

When lookup codes from the CAD system were converted to FH lookup codes, only the first 30 characters were displayed in FHnet. Lookup codes are now displayed up to 75 characters.

If you used a user-defined field to contain the incident number, when FH CAD Monitor processed two or more files, the incident numbers were swapped and did not import into the correct record.

If you tried to import a time and date as a user defined field in the unit record, FH CAD Monitor put the last unit's user field in the first unit's record, and no user field in any other units.

(TriTech and Intergraph) When using FH CAD Monitor to import personnel records from a CAD system, the values for the Hours Worked and Hours Paid fields did not import as expected.

The master incident and responding unit records imported as expected, but staff activity and personnel records did not. When importing staff activity and personnel records, the following ODBC errors appeared.

ODBC Error 8152 ([Microsoft][ODBC SQL Server Driver][SQL Server]String or binary data would be truncated.)

ODBC Error 44446 ([Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert record because no matching record exists in ACT_MAIN)

When using FH CAD Monitor to import personnel records from a CAD system, the values for the Hours Worked and Hours Paid fields were not calculated as expected, and the following errors appeared.

Error 107 (Operator/Operand type mismatch) Error occurred at line 47 of method QUERYCALC_PERSONNELHOURS

Error 12 (Variable (CSQL' is not found.) Error occurred line 49 of method QUERYCALC_PERSONNELHOURS

Error 13 (Alias_46POQNWSF is not found.) Error occurred at line 50 of method QUERYCALC_PERSONNELHOURS

CAD data for the Census Tract field was not being imported through FH CAD Monitor as expected.

If you had multiple departments in FHnet and multiple FH CAD Monitor sessions running, when FHnet imported generic ASCII files from the concurrent FH CAD Monitor sessions, a duplicate incident number was occasionally created in FHnet. As a result, you had to manually edit the incident number to make it unique before you could save the incident record in FHnet.

If you used FH CAD Monitor to send incident data to FHnet, FHnet created a new unit record every time a file with the same unit was processed, instead of updating the existing unit record.

Importing CAD data through FH CAD Monitor created new incident records, but did not trigger user-defined default rules for fields.

When processing data from the CAD vendor, the following error appeared in the event log.

NullReferenceException DataItemStringQuery.cs:line 92

System.NullReferenceException: Object reference not set to an instance of an object.

at ACS.FH.Query.QueryPresenter.GetData(QueryDto query) in d:\Svn checkout\UPBuildCode2.3.0.0\QueryGlobal\QueryPresenter.cs:line 73

at ACS.FH.Global.DataItem.DataItemStringQuery.CheckUnique() in d:\Svn checkout\UPBuildCode2.3.0.0\Global\DataItem\DataItemStringQuery.cs:line 92

When importing multiple files with multiple FH CAD Monitors with different departments, on rare occasions, the following FHApp Server error Method errors appeared.

FHnet Result: Error - See CAD Transaction Import log in FHnet for details.

FH App Server Error - Method GetCodeDescriptFromGuid Cannot find table 0.

FH App Server Error - Method GetCodeDescriptFromGuid Method GetCodeDescriptFromGuid failed, dtLookup = nullfor category UNIT.

When FH CAD Monitor imported a large number of incidents into the FHnet database, all other FHnet services stopped processing logins, and an error message appeared.

When files were being processed, the following error appeared and the record was rejected by FHnet.

An error occurred in CADIncidentProcessor.CreatePoIncident method.There is no row at position 1.

When files were imported from FH CAD Monitor, if the Arrival Time field did not have a value in the first file processed, the Arrival Time field did not populate for the rest of the files imported, even if they contained a value for the field.

City, state, and zip code values did not import from CAD records as expected.

When you imported data from FH CAD Monitor into the Journal module, any location that included a street direction (N, S, SE, and so forth) did not validate as expected and returned an error of No Matching Record.

The incident Cleared date/time field was populated with the first unit's Back In Service field date/time value, instead of the last unit's cleared date/time.