FDCMS Change Log
 
Drag a column header here to group by that column.
 
ID
App Name
Version
Description of Change
Date Changed
6376
ADI
ADI
10.22
Notification User Detail Unit IDs field now allows up to 250 characters.
5/14/2019 8:54:55 PM
7376
ADI
ADI
10.22
Changed: Full installer updated to auto start ADI after Microsoft changed the way the Startup folder works in Windows 10.
5/19/2019 7:59:38 PM
6375
ADI
ADI
10.21
Updated the ADI File Transport utility to use TLS1.2 as it is now required in order to upload incident data to Emergency Reporting.
3/21/2019 9:12:12 PM
6373
ADI
ADI
10.21
Updated TCP/IP Winsock control routines so that any failure of the WinsockListen process will cause ADI to attempt to change the control state to open.
2/7/2019 9:47:09 PM
6374
ADI
ADI
10.21
Madison, NY - Fixed: Incident location may not be parsed correctly if location is missing a comma between address and municipality.
3/18/2019 9:45:17 PM
6372
ADI
ADI
10.20
An option to have ADI ignore all units in the Station and Unit Configuration table was added. It is called 'Disable Station Unit Filtering' and is located on the Troubleshooting tab.
1/27/2019 4:12:15 PM
6371
ADI
ADI
10.20
Livingston, NY - Updated parsing routines to adapt to changes made in the incident template by the county. Prior to this update, unit times were not being properly calculated and the Final report was not being properly processed.
1/26/2019 9:26:29 AM
6370
ADI
ADI
10.19
Chester, PA - Fixed: A rare condition when a unit went AQ before the next unit was dispatched would cause an error #13 when processing a Close report.
11/12/2018 8:45:26 AM
6369
ADI
ADI
10.18
Montgomery, PA - Changed - Some radio receivers would cause ADI to deviate from full incident processing and generate a license violation.  This was a result of the way the receivers were configured. Going forward, ADI will only process when it sees a Form Feed character or when the Maximum Connect Time is exceeded.
11/1/2018 2:49:28 PM
6368
ADI
ADI
10.17
Chester, PA: Fixed - Some incidents would fail to process and report  the following message: Error #13 Type mismatch - [EvaluateData] even when all due units were properly listed in the Station and Units Table. This would happen if an AQ time was accidentally stamped for the unit in CAD prior to the unit's AR time.
10/14/2018 1:43:36 PM
Records per page:
1
|
2
|
3
|
4
|
5
Records: 1 - 10 of 373 - Pages: 


Legacy Revision History