Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

These release notes cover AdvanceGuard AdvanceGuard® V4.8 and above.

Note

This version of AdvanceGuard requires a new certificate to issued by NavtechPlease note that version 4.8 of AdvanceGuard® requires a new licence when upgrading from earlier versions. To create the new licence ensure you use the equivalent version of the Licencing Tool.

Panel
borderColorsilver
borderWidth1

On this page:

Table of Contents
maxLevel3
indent16px

Version 4.8.0 Build 528 - 27 April 2020

Tracker 4.8.0.142 Release Notes

New Features

  • TUN-3672 - Added a title bar to the Entity configuration panel so you can always see which object is selected and being changed

  • TUN-3637 - Added the ability to show track history of live tracks when they are selected. The track path will show from the original sighting and will only show when the track is selected

  • TUN-3675 - Added optional basic target data to video viewer overlay

  • Installer can now install services using proper FQDN (fully qualified domain name) credentials

  • TUN-3626 - Added sighting classification and reclassification status to every track sighting. This data is visible in the Track History dialog

  • TUN-3621 - Moved the UI panel layout configurations to the database as part of the user settings so each setup is user specific

  • TUN-3640 - Added an additional UI Track Filter Option to user settings so tracks can be displayed based on one or more severity settings

  • TUN-3636 - Added disk space stats to the Topology Manager view in the UI. This reports consumed and available disk space for all the servers

  • TUN-3683 - Add new System Configuration profile option. This allows operators, based on user group permission, to select system configuration profiles. In response to these changes, rules can undertake any number of actions in order to adapt the current system setup

Improvements

  • Services will now by default be installed using TLS for service to service communication

  • Trackers will now by default be configured from new to use TLS for onboard communication

  • TUN-3676 - Reduced minimum size of video viewer and added automatic aspect ratio resizing

  • TUN-3698 - Ensured only an administrator can import a system license through the UI

  • TUN-3688 - Enhanced UI track filter to allow selection of all threat types

  • TUN-3632 - Added check for image DPI in background image importer to prevent errors when importing very large, high resolution images

  • TUN-3644 - Ensured both AG and CW will have the same default threshold window size

  • TUN-3645 - Change size and position of Web UI notifications to be larger

  • TUN-3664 - Ensured the User and Engineer accounts will be disabled by default on a new system

  • TUN-3671 - Ensured that default mechanical delay is 800ms for all cameras

  • TUN-3659 - Forced custom empty rules to be disabled when created because they can never be valid on creation

  • TUN-3673 - Ensured the cameras PTZ controls can be hidden via a video viewer config option

Fixes

  • TUN-3669 - Fixed issue with selecting items in the Web UI as a result of a ordering issue

  • TUN-3696 - Fixed issue with the camera lock mechanism going home after time out

  • TUN-3695 - Fixed Web UI not handling the situation when an area is disarmed while in alarm

  • TUN-3691 - Fixed track tag severity handling and associated setup of the configuration in the system settings

  • Fixed camera/target selection logic to correctly choose the closest target to a camera

  • TUN-3701 - Made sure that the area and breach lines show correct severity colour when in alarm for the Web UI

  • Fixed ML Classification configuration not appearing in global settings

  • TUN-3643 - Fixed bug with track left behind on Web UI when the expire period of track is reached

  • TUN-3645 - Made sure that arm/disarm message in the Web UI uses correctly logged in user name

  • TUN-3666 - Ensured a selected Rule schedules Where Used list will be updated post selection when a relevant change is made in another UI client

  • Fixed for rule engine so we don't load or run invalid rules yet still load disabled rules which we need for rule to rule interaction

Info

Due to the layout settings for the UI now being stored in the users settings in the database, the UI layout may reset to defaults after an upgrade


Related information

Filter by label (Content by label)
showLabelsfalse
cqllabel in ( "tungsten" , "advanceguard" )