What was the issue: When creating a new Person and assigning a brand new card number at the same time in the Classic Client, a duplicate card number error was being displayed even though the card number did not already exist in the system. This prevented users from saving the new Person record with their intended card assignment. The issue was isolated to the Classic Client — the same action completed successfully in the Unified Client.
What has been fixed: Creating a new Person and assigning a unique card number at the same time no longer produces a duplicate card number error. New card numbers that do not already exist in the system are now accepted and saved correctly.
What was the issue: When applying a Badge Type to a Person record in the Classic Client, the Access Levels associated with that Badge Type were not being automatically added to the Person. This affected all Badge Types configured with associated Access Levels, meaning cardholders were not receiving the correct access permissions upon having a Badge Type applied.
What has been fixed: Applying a Badge Type to a Person record now correctly and automatically assigns all configured Access Levels to that Person, as expected.
This maintenance release contains bug fixes and other improvements. Full release notes can be found at https://acre.my.site.com/knowledgearticles/s/article/acre-Access-Control-Release-Notes.
For further information about this release, or for clarifications, please contact your account representative.