TeamConnect 5.2 provides users with seamless integration to external document management systems for robust, user-friendly control over your documents. Documents uploaded to and removed from your Document Management System will be reflected in TeamConnect (and vice versa).

Global Search and DMS

TeamConnect users leverage Elasticsearch as the driver for full global search across their documents. TeamConnect's global search feature will return results from DMSes linked to TeamConnect, but these connections will not be indexed by Elasticsearch. Searches will thereby utilize the searching system of the respective DMS. To help manage these results, the results page will have tabs for each DMS. The External DMS field works similar to any other multi-value field in TeamConnect as a custom, searchable, matter-level field.

Currently Supported DMSes

Along with these out-of-the-box integrations, TeamConnect is structured so that users can implement their own DMSes as well. For more information on setting up a new DMS or a custom integration, please see Setting Up a New DMS.

By navigating to the DMS Connector under Tools in TeamConnect, administrators can add new DMS connections as well as set the default DMS for their team's document storage. The documents are fully integrated into TeamConnect global search (upon indexing), and accessible via API and within the Screen Designer module.

DMS Troubleshooting

•Users must have rights to Documents to select a DMS Integration.

•If a client is using a DMS that doesn't support document versioning, but versioning is enabled in TeamConnect, an error message will be thrown when trying to open a previous document version. Only the latest version of the document will be viewable.
 

•In order to leverage Sharepoint Online DMS integrations, users must ensure that the Baltimore CyberTrust Root certificate is installed in their application's truststore. This certificate is key to enabling utility of many Microsoft web services applications.

•The default DMS cannot be deleted. External DMS integrations cannot be deleted if records or documents are associated with that DMS.

•WebLogic users may see something similar to the following error when testing their DMS:

I/O error on GET request for "https://myURL.com/": Hostname verification failed: HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier

To resolve this issue, navigate to Servers > Server Name > Configuration SSL > Advanced and change the Hostname Verification dropdown to None. This setting will allow TeamConnect to consume external webservices.

•For Tomcat users, please ensure that your Tomcat classpath is pointing to jdk/lib and not jre/lib.