Introduction
These release notes cover AdvanceGuard V4.4 and above.
Contents
Version 4.4.0 Build 403 - 09 November 2019
Tracker 4.4.1.114 Release Notes
Fixes
Fixed issue local tracker connections failing
Version 4.4.0 Build 397 - 04 November 2019
Tracker 4.4.1.114 Release Notes
Improvements
Improved the track correlation to ignore distance and speed checks when we know that the track is being updated by the same underlying input track. This fix should improve several situations where tracks currently de-correlate, including when vehicles accelerate rapidly
Fixes
Fixed issue with HikVision camera plugin files not being digitally signed correctly
Version 4.4.0 Build 395- 01 November 2019
Tracker 4.4.1.114 Release Notes
New Features
Fixed issue with tracker TLS handling causing high CPU usage on Track Engine servers
Version 4.4.0 Build 388- 08 October 2019
Tracker 4.4.1.114 Release Notes
New Features
TUN-3189 - Added ICD-001 command to enable external system to change the system profile
TUN-3217 - Added support for TLS 1.2 encryption and authentication to ICD-001 plugin
TUN-3200 - Added system profile status report which can inform external systems when the system profile changes
TUN-3204 - Added an area status report which can inform external systems when any of the area states have changed
TUN-3202 - Added new area status information to the ICD-001 status report
TUN-3199 - Added new system profile status information to the ICD-001 status report
TUN-3187 - Added a new Alarm Dashboard to show a recent alarm activity summary
TUN-3216 - Added new permission option to control whether user roles can clear alarms
TUN-3183 - Added new permission option to control whether user roles can acknowledge alarms but also added user account permission to override role permission so specific users can be given acknowledge rights if required
TUN-3118 - Added new rule action that can change a camera mode between Manual and Automatic - designed to be used with schedules
TUN-3133 - Added new user role permission to control whether the Playback tab is visible to the user
Updated the MongoDb version to V4.0
TUN-3248 - Added New Integration Client
TUN-3208 - Added rule node to set camera home position
Improvements
TUN-2830 - Improved the Where Used links to show the correct relationships to radar and tracking parameters
TUN-3121 - Added a locate button to the rule Area Check node so that the selected area can be easily located on the map
TUN-3130 - Improved system alarm translations to cover built in alarm descriptions not previously covered
TUN-3137 - Switched off UI track position prediction by default but added it as a user setting if required
TUN-3140 - Added rule enabled status column to the rule order dialog
TUN-3154 - Added classification confidence and drone classification check to Echodyne plugin
TUN-3182 - Added camera group behaviour description to each camera group
TUN-3171 - Improved the animation on static sensors to enhance emphasis
TUN-3250 - Improved classification selection
TUN-3268 - Added UI notification when ICD-001 requests camera override
TUN-3269 - Enabled Helvellyn main window resizing from any edge
TUN-3209 - Adjusted camera logic so a 0s dwell time will prevent the camera returning home
TUN-3244 - Added ability to playback tracks with non-sensor source types (i.e. IFF and Drone)
Fixes
TUN-3190 - Fixed Alarm Quick reports which were not querying the database correctly
TUN-3198 - Fixed an issue with camera lock where, in specific conditions, the lock failed and the camera moved home after the dwell period
TUN-3218 - Fixed issue where user settings were not correctly reflecting the state of the background image after using the import wizard
TUN-3219 - Improved the image size check when importing a large background image so it reports a more sensible error message
TUN-3155 - Fixed the rule node copy and paste function so that using copy and paste in a test field does not interfere
TUN-3161 - Fixed an issue that caused the UI to hang if there were no camera plugins installed and a user tried to add a camera
TUN-3168 - Fixed an issue when resetting the system to defaults and restoring a backup which caused a number of database duplicate entry errors
Note that due to the database upgrade, this version must only be installed after upgrading to V4.3.0 first.
Related Information
-
Rules (Witness 4.0)
-
Breach Lines (Witness 4.0)
-
Entity Timeouts (Witness 4.0)
-
UI Recording (Witness 4.0)
-
AdvanceGuard® System Design (Witness 4.0)
-
AdvanceGuard® Alarm Panel (Witness 4.0)
-
AdvanceGuard® Configuration (Witness 4.0)
-
Track Correlation (Witness 4.0)
-
Quick Reports (Witness 4.0)
-
AdvanceGuard® Settings (Witness 4.0)
-
AdvanceGuard® Track Queries (Witness 4.0)
-
AdvanceGuard® Alarm Queries (Witness 4.0)
-
AdvanceGuard® Queries (Witness 4.0)
-
Navigating AdvanceGuard® (Witness 4.0)
-
Technical Manuals - AdvanceGuard (Products)