Documentum connector release notes
The respective releases of the Documentum connector feature the following enhancements. For more information about the connector, see About the Documentum connector.
Documentum Connector 3.2.0.0
System Enhancements
There are no system enhancements in this release.
Fixed issues
-
The Documentum connector was stacking all enumerated items before processing them. (BAI-17670)
-
The Documentum connector was incorrectly reporting that groups were changed, despite no changes occurring, each time a security sync Loads User and Group tables and executes the mapping based on the connector configuration. task was run. (BAI-17634)
-
In some scenarios, xml items in Documentum were failing to be crawled with a XmlException: Unexpected DTD declaration error. (BAI-17478)
-
After upgrading to the Documentum connector 3.1.0.0, in some scenarios the security sync was not showing any members in all groups. (BAI-17160)
Documentum Connector 3.1.0.0
System Enhancements
Feature | Description |
---|---|
D2 Rest API support | The Documentum connector now supports D2 REST API. For more information, see the Documentum documentation. |
Metadata Provides context with details such as the source, type, owner, and relationships to other data sets. Metadata provides details around the item being crawled by Connectivity Hub. enhancements | The Documentum connector can now retrieve the full path of all folders where a specific document is referenced. |
Configuration settings enhancements | You can now configure the delete, purge, and save audit events. Additionally, you can now specify multiple audit events. For more information see How to Set Up and Configure Documentum Connector. |
Fixed issues
-
After running a datastore types load Collects the types of data from your source system. Runs on a set schedule. Requires a log level which logs information or security sync job Loads User and Group tables and executes the mapping based on the connector configuration., an invalid URL error was shown in Test Bench. (BAI-13458)
-
During a crawl of the Documentum connector with Connectivity Hub 3.0, items were incorrectly being shown as deleted. (BAI-14514)
-
In certain scenarios during a crawl of the Documentum connector, an "Object reference not found" error would display due to a null property value. (BAI-15788)