Chat now with support
Chat with Support

Sensitive Content Manager 2.2.3 - Release Notes

Metalogix® Sensitive Content Manager 2.2.3

Release Notes

January 2023

These release notes provide information about the Metalogix Sensitive Content Manager 2.2.3 release. Metalogix Sensitive Content Manager uses a micro-service architecture and can be integrated with Microsoft SharePoint, Metalogix ControlPoint and Metalogix Essentials.

·About Metalogix Sensitive Content Manager 2.2.3

·New features

·Resolved issues

·Known Issues

·Version History

·System Requirements

·Notes and Notices

·Product Licensing

 

 

About Metalogix Sensitive Content Manager 2.2.3

Metalogix Sensitive Content Manager (SCM) provides a reliable, accurate and flexible solution for detecting sensitive information within enterprise content management systems. SCM ships with pre-built analysis profiles such as General Data Protection Regulation (GDPR), Personally Identifiable Information (PII), Protected Health Information (PHI), Payment Card Information (PCI) in addition to the detection capabilities with customizable analysis profiles.

 

New features

This version of Metalogix Sensitive Content Manager introduces the following features and improvements:

General

·Messaging resiliency improvements in the different web and background services.

·Low disk space throttling and checks on Document Processing, Extraction and File Upload services.

 

Resolved issues

The following is a list of issues addressed in this release.

Description

Work Item

Case No.

Reliable Publisher stops publishing after a channel exception

387469

01825803

Dead-letter-added notifications cause an infinite loop and results in a large log message

390819

01825803

Incorrect message order processing on the FileSubmittedHandler can cause the system to heavily slow down

399444


Fixed FileStorage Retry Behavior reporting partial results when disk is full

399439


Implement Low Disk Space Throttling in Upload, DPS and Extraction Services

402711


FileResult records can be incorrectly deleted when the Windows Front End (running the SCM services) server locale (UK date format) is different to the SQL Server locale (USA date format)

392148


 

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating