RecordPoint 4.06

Release date: October 2017

RecordPoint 4.06 brings new features, enhancements and bug fixes to improve your Records Management platform.

For guidance on installing or upgrading to RecordPoint 4.06, see Installation, Upgrade and Configuration.

New Features in this release


Export to Azure Storage file service

RecordPoint now support exporting to an Azure Storage file service. This allows for flexible and secure records export to an enterprise cloud storage location.

To enable exporting to Azure Storage, enter your Storage Account details in the General Settings page.

For more information, see Exporting Records, File and Boxes.

Barcode Scanning - File Return

A new barcode scanning action has been added to return files that are on loan, reducing overhead and complexity in managing file transfers.

The Return File action will locate any File Request for the scanned item with a status of On Loan and complete the request.

For more information, see Barcode Scanning Actions

Configuration options for Finalising content with minor versions

Previously, RecordPoint would not allow finalising SharePoint content when minor (draft) versions were present in the Active Site.

New configuration options are now available for this scenario, granting increased flexibility in finalising content where minor versions are present.

The new options allow the Finalise process to publish the last minor version when finalising, revert to the last major version, or prevent the finalise.

For more information, see Finalise and Finalise Archive in the Active Site.

Bugs fixed in this release

Release version 4.06 includes all bugs resolved since version 4.05, including:

  • Search performance improvements
  • Search results inaccurate when special characters present
  • Access denied message when recipient opens shared document set from the Active site
  • Improved handling of audit logs

Considerations for Administrators

There are no additional requirements or considerations for RecordPoint 4.06. Before deploying this release, we recommend following a best practice deployment process, which includes thorough testing in a non-production environment.