Skip to main content
Mitratech Success Center
Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

TeamConnect 8.0 Coming Soon!

TeamConnect 8.0 Upgrade Readiness Guide for Clients and SMEs

The following information pertains to the upgrade of TeamConnect to version 8.0. This document is intended to provide guidance to clients and Subject Matter Experts (SMEs) to ensure a smooth transition. While the information herein is subject to change, we will endeavor to finalize and formally publish this document by the end of July 2025.

Key Features & Enhancements

  • TeamConnect Document Automation (powered by HotDocs): The TeamConnect and HotDocs integration streamlines legal document generation by connecting TeamConnect data with HotDocs automation. This allows users on TeamConnect version 7+ to generate documents directly within TeamConnect using existing data, reducing manual entry and errors. Customers will benefit from increased efficiency, time savings, and improved data accuracy. Also available on TeamConnect versions 7.0+ (GA in August 2025).
  • ARIES Digital Assistant: TeamConnect 8.0 enhances the ARIES assistant's accessibility by integrating it as a widget across the entire user interface. This improvement makes ARIES a more useful productivity tool for daily tasks within TeamConnect.
  • TeamConnect Outlook Add-in on Mobile: TeamConnect 8.0 enhances the Outlook 365 Add-In by extending all desktop functionalities, including a new Invoice Approval feature, to the Outlook mobile app. This mobile expansion improves user convenience and efficiency by providing on-the-go access to key TeamConnect features.
  • TeamConnect 8.0 now supports & requires Oracle JDK 21: Upgrading to Oracle JDK 21 ensures TeamConnect utilizes a modern, supported Java Development Kit, enhancing security, and access to the latest Java features. This keeps the platform robust and aligned with current technology standards.
  • More Idea Portal Enhancements: Based on user feedback from the Idea Portal, TeamConnect 8.0 includes enhancements to logging (auditing and timer-based resetting of log levels) and improved filtering through Typeahead search linked to Involved Party/Custom Object custom fields.

Architectural Updates

Important: Impact and Required Actions Prior to Upgrading

TeamConnect clients with custom integrations need to review the architectural update in the 8.0 upgrade guide. While most custom Java code integrations are unlikely to be affected, some may require action for a seamless upgrade. This document details potential impacts and necessary preparation steps.

Key Areas of Review:

  • Custom Integration Code
  • Package Renamer Tool
  • SSO-SAML Update
  • DMS Connector Update
  • Office Suite Plugin Compatibility
  • TC 8.0 Module Compatibility Matrix
  • Impacted Libraries and other changes

Third-Party Platform & Integration Updates

Application Servers
  • Oracle Weblogic - TBD
  • Websphere Liberty 25.x with Oracle JDK 21
  • Tomcat 10.1 with Oracle JDK 21

Miscellaneous Updates

  • ElasticSearch 8.17.1
  • Data Warehouse with Oracle JDK 21
  • Screen Designer with Oracle JDK 21
  • SAML Update - now part of core TC
  • SOP-SOP 8.0
  • BO-Business Objects 4.3 SP4

Feature Overview and Client Benefit: Updating third-party libraries ensures compatibility with the latest versions of essential supporting software (like application servers and search engines). This enhances security by incorporating the latest patches, improves performance, and maintains supportability from vendors.

Detailed Architectural Updates

With the version 8.0 upgrade, the underlying Spring framework has been updated from version 5 to version 6.2. 

Feature Overview & Client Benefit: The Spring framework is a fundamental component of TeamConnect's architecture. Upgrading to Spring Framework version 6.2 ensures the platform remains current on support, benefits from the latest framework enhancements and reduces the risk of encountering vulnerabilities associated with older versions.

Important: Impacts and Actions for Custom Integrations

The TeamConnect platform supports custom integrations developed by Services, Partners, and Clients using custom java code. The update to the Spring library may necessitate updates to this custom code.

Note: It is unlikely that custom integrations rely on changed libraries. As a best practice, clients should upload library files to the TeamConnect system libraries folder when creating custom integrations.

However, if a custom integration utilizes library files deployed with TeamConnect, it may require updating as part of the version 8.0 upgrade.

💡 Recommended Actions (4 Months before starting the Upgrade process)

1. 
Identify Custom Integrations: Identify all custom integrations to TeamConnect. If no custom integrations exist, the remaining steps can be disregarded. (Please see FAQ section in case you don’t know whether you have custom integrations)
2. Determine Library Usage: Determine if any custom code uses libraries distributed within the TeamConnect deployment (see the "Impacted Library Files" list below).
3. Document Integration Details: Document the specifics of each integration, including the files used and the actions performed. Share these details with your Mitratech Strategic Account Manager to determine the recommended remediation path.
4. Inform Mitratech Contact: Prior to creating your upgrade plan, inform your Mitratech Strategic Account Manager and/or your Upgrades Included point of contact of these integration details. This will allow for inclusion of remediation planning in the upgrade project.

Remediation will be handled on a case-by-case basis, depending on the integration code and the files used.

Mitratech Support: Mitratech is committed to ensuring a smooth upgrade process. Please contact your Strategic Account Manager with any questions or concerns.

Package Renamer Tool

Feature Overview & Client Benefit: This tool automates a necessary technical update (javax to jakarta package renaming) required by the move to Oracle JDK 21. It simplifies the upgrade process for clients with customizations by handling these changes automatically, reducing manual effort and potential errors.

This tool will be released along with TeamConnect 8.0 to alleviate issues related to custom integrations in Java files.

SSO-SAML Update

Feature Overview & Client Benefit: Integrating Single Sign-On (SSO) using SAML directly into TeamConnect core streamlines the authentication architecture. Clients benefit from potentially lower costs (by eliminating a separate application), simplified configuration management within TeamConnect itself, enhanced security & flexibility with support for multiple Identity Providers, and customizable login experience.

Previous Architecture (TeamConnect 7.2 and earlier):

  • SSO-SAML was separate from TeamConnect core.
  • SSO-SAML configuration was maintained in a separate file.

New Architecture (TeamConnect 8.0+):

  • SSO-SAML is now integrated into core TeamConnect.
  • SSO-SAML now supports multiple Identity Providers.
  • Each SSO-SAML integration with an Identity Provider has its own redirect URL (e.g., "/login/SAML/{identity}").
  • Clients can customize their login experience based on their authentication selections.
  • SSO-SAML configuration is now located under Setup > System Settings > Authentication.

Impacts During Upgrade

  1. Existing SSO-SAML configurations will not be compatible.
  2. Any existing standalone SAML login applications must be disabled.
  3. All configurations must be migrated to TeamConnect Setup > Tools > SAML Setup Tool.
  4. New certificates must be generated and uploaded to System SAML Configuration.
Note: The SSO-SAML configuration migration and certificate generation are one-time setup procedures requiring coordination between the Hosting Team, the Client's IT administrators, and TC Admins/Upgrades Team.


DMS Connector Update

(The following information applies to SharePoint integrations only.)

  1. The SharePoint CLASS file has been updated.
  2. The new CLASS file must be checked in to replace the existing CLASS file in client environments.
  3. The application server must be restarted.
  4. New certificates must be generated for the DMS SharePoint Integration.
Important: The Sharepoint certificate generation(s) are one-time setup procedures requiring coordination between the Hosting Team, the Client's IT administrators, and TC Admins/Upgrades Team.


Office Suite Plugin Deprecation

Beginning with TeamConnect 8.0, the Office Suite Plugin is deprecated and will be fully replaced by the Outlook 365 Add-In. Clients using TeamConnect versions 7.2 and below will receive continued support for the Office Suite Plugin for critical issues only.

The TeamConnect Outlook 365 add-in is built on Microsoft’s modern web-based framework, replacing the legacy COM-based plugin model. As Microsoft phases out support for COM add-ins—especially in New Outlook—this transition ensures long-term compatibility and aligns with how modern enterprise tools are expected to function. The add-in is fully supported on both Classic and New Outlook, making it easier for organizations to adopt the latest Microsoft innovations, including features like Copilot.

Major features from the legacy plugin—such as appointments, tasks, matter creation, and document interactions—are available in the add-in, along with new capabilities in TeamConnect Enterprise 8.0 that include mobile compatibility and invoice approvals. By moving to the add-in, organizations are not only positioned for better maintainability and security, but also fully aligned with Microsoft’s future roadmap.


Frequently Asked Questions (FAQs)

Q: What is the primary reason for the TeamConnect 8.0 upgrade?

A: The upgrade to TeamConnect 8.0 includes an update to the underlying Spring framework (from version 5 to version 6). This update ensures that TeamConnect remains current with supported technologies and reduces the risk of security vulnerabilities.

Q: Will this upgrade affect my custom integrations?

A: It is unlikely, but possible. The upgrade may impact custom integrations that utilize specific library files distributed with TeamConnect. See the "Impacted Library Files" section for a list of potentially affected libraries.

Q: What do I need to do to prepare for the upgrade?

A: If you have custom integrations, please follow these steps:

  1. Identify all custom integrations to TeamConnect.
  2. Determine if any custom code uses libraries distributed within the TeamConnect deployment.
  3. Document the specifics of each integration.
  4. Share these details with your Mitratech Strategic Account Manager.

Q: What do I do to identify custom integrations or what if I don’t know whether there are custom integrations?

A: Please connect with your Mitratech Strategic Account Manager and they will assist you in connecting with our Upgrades Included team. The Upgrades team will help you in identifying the custom integrations and resolving any potential issues that may arise.

Q: Where can I find a list of the library files that may be impacted?

A: See the "Impacted Library Files" section of this document.

Q: My organization uses SSO-SAML. What changes should I expect?

A: SSO-SAML is now integrated into the core of TeamConnect 8.0. Existing SSO-SAML configurations will not be compatible, and you will need to migrate your configurations to the new SAML Setup Tool within TeamConnect. Please see the "SSO-SAML Update" section for detailed instructions.

Q: We use the Office Suite Plugin. What are our options?

A: The Office Suite Plugin is deprecated in TeamConnect 8.0 and will be replaced by the Outlook 365 Add-In. If you are using TeamConnect 7.2 or earlier, support for the Office Suite Plugin will be limited to critical issues only.

Q: Who should I contact if I have questions or need assistance with the upgrade?

A: Please contact your Mitratech Strategic Account Manager.


Impacted Libraries and Other Changes
iText Library Update

The iText library is being replaced by the OpenPDF library. While the old iText library will remain accessible under system libraries, any client or service customizations must be updated to reference the new folder directory for the OpenPDF library.

CustomBlock API in Enterprise 4.x

The CustomBlock API in Enterprise 4.x has been updated. While existing runtime functionality will not be disrupted, source control systems will need to be updated to incorporate these API changes.

Incorrect WebService URLs

If you encounter "400 bad request" errors in TeamConnect SOAP or REST web service calls, ensure your request URLs do not contain double slashes. Spring 6 and later versions have enhanced URL parsing for improved security, which now flags double slashes as invalid.

Impacted Library Files
Note: The most commonly used libraries for such integrations include Apache POI and CXF, so any integrations using those are at highest risk.  We believe it is unlikely any custom java code would utilize the remaining library files, but it is good to check the whole list.

 

Dependency Old Version New Version Change Type

org.apache.maven.resolver:maven-resolver-api

-

2.0.1

Added

jakarta.servlet:jakarta.servlet-api

-

6.1.0

Added

jakarta.el:jakarta.el-api

-

6.0.1

Added

jakarta.transaction:jakarta.transaction-api

-

2.0.1

Added

org.gwtproject:gwt-servlet-jakarta

 

2.11

Added

org.gwtproject:gwt-user

 

2.11

Added

org.gwtproject:gwt-dev

 

2.11

Added

com.google.inject.extensions:guice-assistedinject

-

6.0.0

Added

com.google.inject:guice

-

6.0.0

Added

org.apache.commons:commons-dbcp2

-

2.12.0

Added

org.sitemesh:sitemesh

-

3.2.1

Added

org.springframework.security:spring-security-config

 

6.3.3

Added

org.springframework.security:spring-security-web

 

6.3.3

Added

jakarta.servlet.jsp.jstl:jakarta.servlet.jsp.jstl-api

-

3.0.2

Added

org.glassfish.web:jakarta.servlet.jsp.jstl

-

3.0.1

Added

org.apache.maven.plugin-tools:maven-plugin-annotations

-

3.15.0

Added

com.fasterxml.jackson.jakarta.rs:jackson-jakarta-rs-json-provider

-

2.18.1

Added

jakarta.ws.rs:jakarta.ws.rs-api

-

4.0.0

Added

org.apache.cxf:cxf-rt-rs-security-jose

-

4.1.0

Added

org.powermock:powermock-api-mockito2

-

2.0.9

Added

jakarta.xml.soap:saaj-api

-

1.3

Added

jakarta.enterprise:jakarta.enterprise.lang-model

-

4.1.0

Added

jakarta.annotation:jakarta.annotation-api

-

3.0.0

Added

jakarta.servlet.jsp:jakarta.servlet.jsp-api

-

4.0.0

Added

jakarta.xml.bind:jakarta.xml.bind-api

-

4.0.2

Added

xml.ws :jakarta.xml.ws-api

-

4.0.2

Added

org.glassfish.jaxb:jaxb-runtime

-

4.0.5

Added

jakarta.xml.soap:jakarta.xml.soap-api

-

3.0.2

Added

org.eclipse.persistence:org.eclipse.persistence.jpa

-

4.0.4

Added

javax.servlet.jsp:jsp-api

2.2

 

Removed

javax.servlet:javax.servlet-api

3.0.1

-

Removed

javax.servlet:jstl

-

-

Removed

javax.ws.rs:javax.ws.rs-api

2.1

-

Removed

spring-ldap:spring-ldap

-

-

Removed

com.sun.xml.parsers:jaxp-ri

1.4.2

-

Removed

info.solidsoft.mockito:mockito-java8

1.0.0-beta

-

Removed

org.powermock:powermock-api-mockito

1.6.6

-

Removed

javax.xml.soap:saaj-api

1.3

-

Removed

com.google.gwt:gwt-servlet

2.11.0

-

Removed

com.google.gwt:gwt-user

2.11.0

-

Removed

com.google.gwt:gwt-dev

2.11.0

-

Removed

javax.transaction:jta

1.0.1B

-

Removed

javax.servlet.jsp:jsp-api

2.2

-

Removed

org.json:json

20140107

-

Removed

javax.ws.rs:javax.ws.rs-api

2.1.1

-

Removed

org.apache.maven:maven-project

2.0.11

-

Removed

org.apache.abdera:abdera-core

${abdera.version}

-

Removed

com.sun:tools

1.5

-

Removed

javax.servlet:javax.servlet-api

3.0.1

-

Removed

org.springframework.security:spring-security-ntlm

6.3.3

-

Removed

org.springframework.security:spring-security-catalina

2.0.4

-

Removed

opensymphony:sitemesh

2.5.0

-

Removed

org.jdom:jdom

1.1.3

-

Removed

commons-dbcp:commons-dbcp

1.4

-

Removed

com.google.gwt:gwt-incubator

2.3.0

-

Removed

org.glassfish:javax.el

3.0.1-b11

-

Removed

com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider

2.8.8

-

Removed

org.hibernate:hibernate-entitymanager

${hibernate.version}

-

Removed

org.springframework.security.extensions:spring-security-saml2-core

1.0.0.RELEASE

-

Removed

com.sun.xml.bind:jaxb-impl

2.2.11

-

Removed

com.sun.xml.bind:jaxb-core

2.2.11

-

Removed

javax.annotation:javax.annotation-api

1.2

-

Removed

javax.xml.bind:jaxb-api

2.2.12

-

Removed

xml.ws :jaxws-api

2.3.1

-

Removed

javax.xml.soap:javax.xml.soap-api

1.4.0

-

Removed

jdom:jdom

-

-

Unchanged

net.sf.oval:oval

1.9

1.90

Unchanged

netty:netty

-

-

Unchanged

org.apache.commons:commons-fileupload

1.4

-

Unchanged

org.apache.taglibs:taglibs-standard-jstlel

-

-

Unchanged

org.apache.taglibs:taglibs-standard-spec

-

-

Unchanged

org.dom4j:dom4j

2.1.3

2.1.4

Unchanged

org.jdom:jdom2

 

 

Unchanged

org.mindrot:jbcrypt

-

-

Unchanged

poi.version:poi.version

5.2.0

-

Unchanged

spring.version:spring.version

5.3.20

6.1.12

Unchanged

tinymce:tinymce

5.10.3

-

Unchanged

elastic.version

7.1

8.17

Updated

aspectj.version

1.8.4

1.9.22.1

Updated

com.google.code.gson:gson

2.9.0

2.10.1

Updated

com.rometools:rome

1.18.0

2.1.0

Updated

com.thoughtworks.xstream:xstream

1.4.19

1.4.20

Updated

cxf.version:cxf.version

3.5.0

4.1.0

Updated

elasticsearch.version:elasticsearch.version

7.10.0

8.2

Updated

hibernate.version:hibernate.version

5.4.32.Final

6.6.0.Final

Updated

jackson.version:jackson.version

2.10.5

2.18.0

Updated

jaxen:jaxen

1.2.0

2.0.0

Updated

org.apache.commons:commons-text

-

1.10.0

Updated

jakarta.persistence:jakarta.persistence-api

2.2.3

3.2.0

Updated

org.eclipse.persistence:eclipselink

2.7.13

4.0.4

Updated

xml.ws :jaxws-ri

2.2.10

4.0.3

Updated

com.sun.mail:jakarta.mail

1.6.7

2.0.1

Updated

com.googlecode.mvp4g:mvp4g

1.3.1

1.6.0

Updated

org.dom4j:dom4j

2.1.3

2.1.4

Updated

jaxen:jaxen

1.2.0

2.0.0

Updated

com.sun.xml.messaging.saaj:saaj-impl

1.3.14

3.0.4

Updated

org.apache.cxf.xjc-utils:cxf-xjc-runtime

3.1.0

4.0.1

Updated

org.apache.cxf.services.sts:cxf-services-sts-core

3.1.0

4.0.1

Updated

com.fasterxml.jackson.jaxrs:jackson-jaxrs-base

2.8.8

2.18.0

Updated

org.apache.jackrabbit:jackrabbit-webdav

2.20.0

2.22.0

Updated

org.mockito:mockito-core

1.10.19

5.13.0

Updated

javax.xml.parsers:jaxp-api

1.4.2

1.4.5

Updated

xml-apis:xml-apis

1.3.04

2.0.2

Updated

com.microsoft.graph:microsoft-graph-core

2.0.20

2.0.19

Updated

  • Was this article helpful?