Release Notes

Document Issue Level: Date Issued:
1.0 November, 2020
Product: Version Issued:
Symmetry CONNECT & GUEST 1.28.4

There is now a new version of the amag.Symmetry.Client 4.0.5.309

Introduction

This bulletin provides technical information on product improvements for Symmetry CONNECT & GUEST for both hosted and on-premise deployments, available in production from November 2020.

Technical Information

  • On-Premise Customers who wish to upgrade Elastic Search via the installer, MUST remove all plugins (if utilised) prior to upgrade. The plugins can be reinstalled after the upgrade is complete. If Customers are not using plugins then no further action will be required to upgrade ElasticSearch.
  • Customers who wish to use the new Data Export flag to populate dbo.DataExportTable in multiMAXExport, will need download the latest AMAG.Symmetry.Client version 4.0.5.309. Customers will also need to update the settings.config file to include;
    • ReportChangesToSymmetryDataExport::True

New Functionality

Installer

  • We have added an option in amag.sh to allow users to gracefully shutdown/startup the application as well as the backend.
  • We have added a new option in amag.sh > advanced options, to allow users to update values in datacenter.config and rotate the application secrets.
  • We have improved the order in which applications are built on the initial installation.

REDIS

  • We have added optional password protection to the REDIS servers.

GUEST

  • FP154833 - We have addressed an issue with Signatures not appearing on the Check In screen. this has now been resolved.

CONNECT

  • We have added the ability to create double-sided badge templates in CONNECT.
  • We have added the ability to print double-sided badges from CONNECT
  • We have added additional database fields for ‘Credential Expiration Date’, ‘Department’ and ‘Title’ for use in the CONNECT badge template editor.
  • We have added the ability to define CONNECT badge templates by Department. This can be done through the ‘Settings’ menu when editing a badge template.
  • We have created an optional update to the amag.Symmetry.Client to allow for CONNECT data to populate the dbo.DataExportTable in multiMAXExport. Customers will be able to set a flag in the settings config file or alternatively re-install the Amag.Symmetry.Client. The instructions to add in the parameter manually can be found in the Technical Information section of this document.

Issues Addressed

  • FP155765 - We have addressed an issue with mapped UDF fields in UDF not getting truncated in Symmetry - This will require users who wish to see utilise this fix, to update their Amag.Symmetry.Cleint to the latest version.
  • FP156888 - We have addressed an issue where Host Delegates could not schedule visits. This has now been addressed.
  • FP154103 - We have addressed an issue with Cardholders appearing in the incorrect Symmetry instances where Access is mapped to a specific Company. This has now been addressed.
  • FP155240 - We have addressed an issue whereby stale UIOLI data was appearing in the CONNECT Dashboard after the Rule was turned off. This has now been resolved.
  • FP155587 - We have addressed an issue with multiples of the same Identity were being displayed in CONNECT. This has noe been resolved.
  • FP155640 - We have addressed an issue with the ‘Identity without Credential Report’ displaying all Identities as opposed to Identities who do not have Credentials. This has now been resolved.
  • FP155919 - We have addressed an issue with Symmetry Clients failing to Sync on remote message upload failures. This will require users who wish to see utilise this fix, to update their Amag.Symmetry.Client to the latest version.
  • FP153598 - We have addressed an issue with Unknown Cardholders that have been deleted from Symmetry are still appearing in the CONNECT Dashboard widget. This has now been resolved.
  • FP154833 - We have addressed an issue with Signatures not appearing on the Check In screen. This has now been resolved.
  • We have addressed an issue whereby unmapped UDFs in IDM were getting deleted after an Identity was updated via the IDM Importer. This has now been resolved.
  • We have addressed an issue with the Access Report > Access Group dropdown was not displaying all Access Groups. This has been resolved.
  • We fixed a number of issues regarding reporting in grafana for On-premise Customers.
  • FP153178 - We addressed an issue to remove ACRM/ACRs from the ‘Deleted ACRM/ACRs to process’ dashboard widget once reinstated.
  • We addressed an issue with multiple emails being distributed on Access Requests. Only the relevant amount of emails will be distributed on Access Requests.

Known Issues

  • Maximum advance pre-registered or Maximum visit length should not be set to 0 as this will stop Visits from being scheduled and Visitors from being checked in in from Self Registration.
  • After completion of ‘Define New Visitor’ from the Unknown Visitor link (Calendar Integration) the user is not automatically re-directed to the default GUEST view. The work around is to manually navigate back to GUEST until a fix is put in place in a future release.
  • PDF pagination numbering does not change when cycling through (x) pages for Policies.
  • ACRM/ACR proxy by admin is displaying exceptions when selecting Audit Pie charts from CONNECT Dashboard. ACRM/ACR retain functional behavior for Audit pie chart selection.
  • ACRM/ACR proxy by admin will throw exceptions when navigating between GUEST and CONNECT.
  • Identity Credentials Report attributes will be deleted from fields if drop-down is selected during editable phase of report generation. Ensure that report is generated before selecting the Drop down icon.
  • If a receptionist’s base building/company combination has a visit configuration without visit types, all the self registration kiosks activated with a code generated by the receptionist won’t be able to create any visits. This is a limitation of the current design of the kiosk and will be fixed in a future release. The work around for this issue is to either change the building/company of the receptionist to a combination that has a visit type, or to add a visit type to the current building/company combination used by the receptionist.

Please refer to Amag Technology Software License Agreement which is available from the following link: https://www.amag.com/software-licence-agreement

© G4S Technology Limited 2020