Home > New Features and Improvements from Previous Versions > AvePoint Cloud Records July 2020

    Export to PDF

    AvePoint Cloud Records July 2020

    Release Date: July 12, 2020

    • For Cloud Records, a classic SharePoint Online site is scanned into the SharePoint Sites container and it will be scanned into the Microsoft 365 Groups container for management after it connects with a Microsoft 365 Group.

    • You can now use the Records app to scan barcodes of physical records and then perform operations to manage the physical records via a mobile device.

    • You can now create template suites for storing customized templates.

    • You can now search for a SharePoint Online tree node using the Search feature on the Content Repository Management page.

    • You can now import customized document level term settings to Cloud Records using a template.

    • You can now manage documents using the Parent Folder Name rule criterion.

    • You can now use Cloud Records via the Microsoft Edge based on Chromium browser.

    • A Type column is added to the Records for Review table to help identify the type of the object that is waiting for approval.

    • The dd-MM-yyyy date format is now supported in general settings.

    • You can now choose whether to archive content to a storage location before removing it from SharePoint Online.

    • You can now choose whether to skip the Remove content and destroy rule action when running Enforce Rule Actions jobs.

    • You can now directly sign into Cloud Records without going into AvePoint Online Services.

    • End Users now are able to manage related records in Physical Records Explorer.

    • You can now choose a hold conflict resolution when moving folders to a new location if both the source folders and the destination box are already on hold.

    • You can now use the legend to identify the status of each physical box/folder/record in Physical Records Explorer.

    • The Team name is now added to the text of a private channel tree node on the Content Repository Management page to indicate the team where the private channel exists.