November 2021 Sprint 64

Release Date

November 5, 2021 (Sprint 64) Release

This version is comprised entirely of minor bug fixes and improvements.

There are no new features to report in this release.

None.

The following issues have been resolved in this release.

ID	Component	Description	Ticket #
64103	Core	Fixed an issue where Destruction Certificate is incorrect if using multiple approval groups on a Record Class.	00011667
64205	SharePoint Online Connector	Added general optimization: Retention job and inactive sites.
64220	SharePoint Online Connector	Added general optimization: Configurable timeout for RM Client used for sending a batch.
63937	Core	User interface fix: Title field extends outside of Records Class Records dialog.
61507	Core	User interface fix: Clicking the ellipsis in Inbox as a User causes error message.
63534	SharePoint Online Connector	Added general optimization: Folder query LVT optimization.
63953	SharePoint Online Connector	Resolved, unhandled exception while fetching pending action items while performing retention.	00011680
62869	Physical Records Management	Fixed PRM bug where menu options are missing from Container Dropdown.
61159	SharePoint Online Connector	Fixed bug where @folder token was not properly listing nested folders in SharePoint Online.
62800	Physical Records Management	Fixed ambiguous reference to security object. Build error corrected. No functional change.
63154	SharePoint Online Connector	Added logging to tenant controller and job control creation.
62369	SharePoint Online Connector	Fixed issue with SPO Site Registration via API.	00011287

The following issues are known to exist at this time.

ID	Component	Description	Workaround
65433	Core	Manage Record log in "refused to connect" from Chrome browser.	This issue does not currently occur in Firefox or Microsoft Edge. If using Chrome, workaround is to log into Gimmal Records first and then navigating to the Manage Records button.
65408	Core	User can remove their own access which prevents them from logging in.	Gimmal Records users should use care to accidentally revoke their own access. Workaround would have a System Administrator restore the Users access.