Release Notes

Document Issue Level: Date Issued:
1.0 September, 2020
Product: Version Issued:
Symmetry CONNECT & GUEST 1.27.0

We are now providing Visit Notification Settings by Visit Type. GUEST administrators can find the new and migrated settings in ‘Visit configuration’ > ‘Add/Manage Visit Types’. All existing Visit Notification Settings will be migrated to each Visit Type by default.

If you do not wish to utlize the new ‘Auto Check-in’ feature then you will not need to amend or change any settings.

ON PREMISE Customers who wish to use the new Wallet Pass Integration will be responsible for generating their own Google /Apple Wallet Acounts and Environment Variables.

Customers using Symmetry are strongly advised to upgrade their AMAG.Symmetrty Clients to the latest version.

The version of python used in GUEST/CONNECT has been upgraded to python3. In order to downgrade to any version of Symmetry GUEST/CONNECT prior to 1.27.0, the application must be manually changed back to use python2. See below for steps to do this (Instructions for Installers only):

  • Connect to Docker using SSH
  • Type ‘cd connect.deployment’
  • Type ‘vi ansible.cfg’
  • Type ‘i’ to enter insert mode, then use the arrow keys to locate the following: ‘interpreter_python = /usr/bin/python3’
  • Change: ‘interpreter_python = /usr/bin/python3’ to: ‘interpreter_python = /usr/bin/python2’
  • Press Esc, then type “:wq” to save and exit the file
  • Continue with the downgrade as planned.

Introduction

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

New Functionality

Installer

  • The installer has been updated to provide users with the ability to add Google/Apple Wallet environement variables, to enable wallet integration with GUEST. Users will be prompted in the upgrade to 1.27.0.

GUEST

  • Visit Settings and Visit Notification Settings have been migrated to Visit Type Definitions in Visit Configuration.
  • A new Automatic ‘Check-in’ feature has been added the the GUEST module that will allow Visitors who are subject to Access Control to Scan their recieved QR credential on or after the scheduled arrival time.
  • Visitors now have the ability to receive and save a QR credential to either Google Pay or Appple Wallet via the Welcome email, subject to Visit Notification Settings.
  • Increased control over notifications including the ability to enable and disable by visit type as well as define who receives them.
  • GUEST Reports have been enhanced to display when a Visitor was Automatically checked in by the System.

Issues Addressed

  • FP151181 - We have an addressed an issue with CAC Reports occaisonally producing unknown errors in the application. This has now been resolved.
  • We have a addressed an issue with multiple notifications being received at the start of Audit Campaigns. This has now been resolved.

Known Issues

  • 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