May 2025 Cumulative Release Notes

May 28, 2025

Bug Fixes

• Fixed an issue where Notification sounds would not play properly on iOS devices.
• Fixed an issue where entering a space before the Name or Description of a Cloud Node could cause unexpected problems.
• Fixed an issue where adding a Bluetooth Credential to an End-User who already has a Mobile App Credential could result in the Bluetooth Credential not being added to the End-User.
• Fixed an issue where changing the Device Type of an existing Device would not function properly.
• Fixed an issue where the IP Address for an Ethernet Connection could not be changed.
• Fixed an issue where a Primary Reader for an Elevator Device could not be added.
• Fixed an issue where attempting to create a new Person who will be assigned to multiple Groups, which are managed in different Partitions, would fail.
• Fixed an issue where deleting a Customer Account would not unregister any Cloud Nodes from the Customer Account.
• Fixed an issue where changing options in a Custom Field does not prompt to save the change.
• Fixed an issue where the on-screen keyboard would unexpectedly close when entering text into a Search field on iOS devices.
• Fixed an issue where an unclear error message is displayed when Characters that are not allowed are entered.
• Fixed an issue where Reader Type and Protocol Device options were not displayed when changing the Device Type from Generic IO to Premium IO on an existing Device.
• Fixed an issue where Integrations were not being displayed properly.
• Fixed an issue where migrating from a 1.0 Cloud Node to a 2.0 Customer Account would result in Mobile App Credentials no longer working.
• Fixed an issue where an error could occur when a Dealer Partner accesses the Billing portal.

May 22, 2025

Bug Fixes

• Fixed an issue where adding a Person to a Group containing over 100 People could remove existing People from the Group.

May 19, 2025

Bug Fixes

• Fixed an issue where a Device Filter could not be added to Event Reports.
• Fixed an issue where trying to access System Settings would produce an error after Migrating to 2.0.
• Fixed an issue where only numbers could be entered into a String field in Custom Fields, despite the Custom Field allowing non-number entry.
• Fixed an issue where an incorrect color was being displayed in a Custom Field dropdown menu.
• Fixed an issue where saving after entering data into a Custom Field would delete a previously entered Email for the Person.
• Fixed an issue associated with User Session Management.

May 09, 2025

New Features and Enhancements

• Partners with an Integrator Permission Role at the Dealer Level can now disable Bluetooth/Mobile App permissions for Customer Accounts.
• Migrated Customer Accounts now support Legacy Reports from multiple Cloud Nodes on a Customer Account.

Changes

• Added Description field to the “Custom Regular Expression” preset in Custom Fields.

Bug Fixes

• Fixed an issue when displaying Group Type in Custom Fields.
• Fixed an issue where Read Only Custom Fields could be edited.
• Fixed an issue where Custom Fields with spaces in the Field ID field were causing request failures.
• Fixed an issue where incorrect Search results occurred when a trailing space was included in the Search field.
• Fixed an issue where Partners with the Admin Permission Role couldn’t configure Integrations on a Customer Account.
• Fixed an issue that could occur when a Card Credential is entered with at least one zero before the number.
• Fixed an issue where the Export button for Custom Fields was not displayed in a Partition before creating a Custom Fields.
• Fixed an issue where submitting a Report without saving the Report first would cause an error.
• Fixed an issue where Devices could not be added to the Customer Account from the Discovery tab in Configuration.
• Fixed an issue where selected Devices in an Access Rule for a Group would not be saved when the Access Rule was edited.
• Fixed an issue where the ability to toggle visibility of Integrations did not work as expected in the Customer Account.
• Fixed an issue that could occur where incorrect information was displayed when editing the System Settings Time Zone setting on a Customer Account with multiple Cloud Nodes with different configured Time Zones.