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
| Feature | Description |
|---|---|
| Support for media policy URL configuration |
You can now specify the value of your media policy url for your Documentum instance. For more information, see configure your Documentum connector using web.config. |
| Support for Documentum sub-queries in filters |
The Documentum connector has added a new <tablesWithoutObjectId> configuration setting to allow you to specify sub-queries in your custom filters, without making the custom filter check result in an invalid DQL statement. For more information, see Set up and configure the Documentum Connector. |
| Support for ignoring r_is_public attributes |
In the Documentum connector, the r_is_public attribute is used as a flag to skip permissions on a document and mark it as public. As a result, a new <ignoreR_is_Public> configuration setting has been added to allow you to ignore this attribute on your documents, and enforce permission processing. For more information, see Set up and configure the Documentum Connector. |
Fixed issues
-
In some scenarios, the Documentum connector was not removing duplicate users and groups during a security sync Loads User and Group tables and executes the mapping based on the connector configuration.. (1775831)
-
The Documentum connector was not preserving user access for documents that were set as public in Documentum. (1751283)
-
The Documentum connector was stacking all enumerated items before processing them in Connectivity Hub, which resulted in exceedingly long crawl times. (1729445)
-
In some scenarios, crawl tasks with the Documentum connector were failing with an "XmlException: Unexpected DTD declaration" error. (1712166)
-
In some scenarios, after upgrading to the Documentum connector 3.1.0.0, the security sync was not showing any members in all groups. (1678194)
-
In some scenarios, the Documentum connector was reporting that groups were modified during an incremental security sync task, despite no modifications to groups occurring on the source system Your Source System is the repository where your data is stored (data to be indexed). This repository is managed by applications such as: - SharePoint O365 - SharePoint 2013/16/19 - Documentum - File Share - OpenText - Lotus Notes - etc. Your Source System repository can also be a database such as SQL or Oracle..
-
Documentum connector crawls were failing when multiple FROM clauses were used in the DQL statement.
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)