Release Notes

Document Issue Level: Date Issued:
1.0 April, 2021
Product: Version Issued:
Symmetry CONNECT & GUEST 1.33.1

Customers are advised to update their Amag.Symmetry.Clients to the latest version 5.0.3.370 for the meaningful error messages added as part of FP159761 detailed below.

Introduction

This bulletin provides technical information on product improvements for Symmetry CONNECT & GUEST for both hosted and on-premise deployments

New Functionality

Installer

On Premise Customers (Online) Only.

  • Now only officially released versions of GUEST/CONNECT will be displayed by default in the installer to prevent accidental upgrades to versions still under test.
  • Connect.deployment will now use versioning based on branch names, but new code will be pulled automatically by the installer. The process is as follows:
    • Connect to docker using SSH
    • Type in cd connect.deployment
    • You will initially be asked for your Bitbucket Credentials which will be stored for future use.
    • Switch to the branch of your desired release by typing in git checkout version/<Version Number>.
    • Run the installer by typing in bash ./amag.sh. From here, the installer will automatically pull the latest changes from the branch, and the upgrade/install can continue as normal.

Issues Addressed

  • FP159561 - We have fixed an issue with card transactions that have no identityID from Symmetry not appearing in CONNECT reports. The CONNECT Card Activity report was updated to display transactions that have no direct link to a CONNECT Identity. These card transactions will now appear in the report without any CONNECT-specific information such as building, company, etc.
  • FP159761 - We have addressed an issue with reporting in CONNECT showing “unknown error” against certain terminated records. We have improved the Symmetry Integration Support Report to replace “Unknown error” with a more meaningful error message. These include:
    • “Execution Timeout Expired”
    • “Object reference not set to an instance of an object”
    • “SqlDateTime overflow”
    • “SqlTransaction has completed”
    • “Transaction was deadlocked”
    • “An error was raised during trigger execution”
    • “Could not allocate space for object”
    • “Invalid column name”
    • “String or binary data would be truncated”
    • “Card Holder already exists for this card number”
    • “This Card Number is already in use”
  • FP160321 - We have fixed an issue with bulk assigning access codes to identities, where some of the identities were not receiving all access codes assigned.
  • FP160482 - We have fixed an issue where creating a visit and then editing it would cause the visit to be displayed as “Pending” instead of “Approval Not Required” on the “My Visits” page.
  • FP160549 - We have addressed an issue where attempting to import recently deleted employees with the IDM importer would cause an error saying “X is not a unique employee number”. It is now possible to re-import recently deleted identities with the Importer.
    • To ensure proper processing, we advise waiting an hour between same employee additions if the employee is to be deleted in between.
  • Guard assist will now correctly load in RTL languages.

Known Issues

  • GUEST Search field will only allow Users to search on a maximum of two searchable words. In the future we will provide Users with the ability to search three search words. The work around at this time is to enter an ‘AND’ operator between each word to exceed a 2 word search.
  • 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 behaviour 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 2021