How to Ensure a Successful TeamConnect Enterprise 8.0 Upgrade?

2a. Third Party Updates

Feature Overview & 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.

Check the Third Party Matrix for detailed information related to third party libraries.

2b. Application Servers

• Oracle WebLogic 15

• IBM WebSphere Liberty 25.x with Oracle JDK 21

• Tomcat 10.1 with Oracle JDK 21 

For more information, refer to the TeamConnect 8.0 – Application Server Configuration with Oracle JDK 21 document.

2c. What to keep in mind when going to 8.0 from an earlier version?

1. Manually upgrading to TeamConnect 8.0

• If you’re planning to manually upgrade to TeamConnect Enterprise 8.0 using the EXE installer, it is recommended to first upgrade to TeamConnect Enterprise 7.2 and then update all modules to the latest compatible version with TeamConnect Enterprise 7.2. This is a required step since there is a single manual upgrade path from the latest module version on TeamConnect Enterprise 7.2 to the latest module version on TeamConnect Enterprise 8.0.
   
• Note for Financial Management Installation in case on Financial Management 7.0 Patch 1: When upgrading from Financial Management 7.0 Patch 1 to Financial Management 8.0 using the “Available Updates” option in TeamConnect, the upgrade may fail due to a duplicate “CjbInvoiceBudgetScreen$10.class” file. This file is present in both the source version and the upgrade package. The DMT (Design Migration Tool) is designed to reference the base version folder (7.0.0.0001) during module upgrades and does not consider patch folders. As a result, this causes a conflict during the upgrade.
  Workaround: Before running the upgrade using the “Available Updates” option, manually delete the “CjbInvoiceBudgetScreen$10.class” file from the “Documents” section in TeamConnect. This prevents the duplicate file conflict and allows the upgrade to complete successfully.
  Note: This step is not required when performing the upgrade via the CLI (Command Line Interface) tool.

2. Financial Management Standard View in TeamConnect Enterprise 8.0:

• What was previously available (in TCE v7.2): In TeamConnect version 7.2, installing the Financial Management (FM) module would add the Cost Centers and Budgets sections to the standard Invoice View, which is a predefined system view.

• What has changed (in TCE v8.0 or later): Starting in TeamConnect 8.0, a new custom view called the “Financial Management Standard View” is available. When you install the Financial Management (FM) module, the Cost Centers and Budgets sections are now added to this custom view instead of the system-defined Invoice View. This view also includes Interactive Line Items, offering a more flexible and user-friendly way to review and manage invoice details.

• Reason for the change: This change was introduced due to updates in the DMT (Design Migration Tool), which now restricts changes such as import, export, delete, or update to predefined system views (such as the Invoice View). To support ongoing functionality and future maintainability, these sections are now added to a custom view instead.

Note: This change will not affect client upgrades and applies only to new implementations.

3. Using the CLI Tool to upgrade to TeamConnect 8.0 [Recommended]

• It is recommended to use the CLI tool to upgrade your TeamConnect environment, as the CLI tool will automatically build the relevant upgrade paths for all your modules.
• Check the CLI tool documentation for detailed information.

2d. Module Compatibility List

Check the module compatibility list below for details on previous and updated versions between TeamConnect Enterprise 7.2 and TeamConnect Enterprise 8.0.

3a. 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.

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 connected to TeamConnect. If you don’t have any, you can disregard the remaining steps. (See the FAQ section if you’re unsure whether you have custom integrations and check the package renamer section as well).

2. Determine Library Usage: Determine if any custom code uses libraries distributed within the TeamConnect deployment. Refer to the “Impacted Library Files” list for details.

3. Document Integration Details: Document the specifics of each integration, including the files it uses and the functions it performs. Share these details with your Mitratech Strategic Account Manager to determine the recommended remediation path.

4. Inform Your 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.

3b. The 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.

ℹ️ Important

• It is highly recommended to run the Package Renamer tool to make sure all the custom integrations and libraries have been updated to work with Oracle JDK 21 and Spring Framework 6.

• If you add any third-party JAR files to the library folder, they will also be affected by the Package Renamer Tool. To avoid potential issues, make sure to update those JAR files manually or create backups before running the tool.

Check the Package Renamer tool documentation for detailed information.

3c. SSO (Single Sign-On)-SAML now integrated into TeamConnect Enterprise

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.

TeamConnect Enterprise 8.0 introduces native support for SAML-based Single Sign-On (SSO), which is now integrated directly into the core platform. All configuration is now managed within TeamConnect under Setup → System Settings → Authentication.

Before You Begin

• If you are configuring SAML for the first time with your Identity Provider (IdP), view the Setting up SSO-SAML in TeamConnect 8.0.

• If you are upgrading from an earlier version of TeamConnect and previously configured SAML authentication, you must remove the legacy configuration before setting up the new SAML authentication in TeamConnect version 8.0. For more information, see How to upgrade from SAML Server to Integrated SAML-SSO in TeamConnect.

Key Enhancements

This integration provides several key improvements:

• Support for Multiple Identity Providers (IdPs): You can now configure connections to several IdPs, each with its own unique redirect URL (e.g., “/login/saml2/sso/{RegistrationID}”).

• Customizable Login Experience: The login process can be tailored based on the authentication method selected.

• Improved Security: A native integration reduces maintenance overhead and enhances overall security.

⚠️ Upgrade Impact: Action Required

Due to this architectural change, your existing SSO-SAML configuration requires manual migration during the upgrade.

• Existing SSO-SAML configurations are not compatible with the new version.

• Any existing standalone SAML applications must be disabled.

• All configurations must be migrated using the TeamConnect Setup → Settings → SAML Authentication Settings.

• New certificates must be generated and uploaded to the System SAML Configuration.

3d. DMS Connector Update for SharePoint Online Integration

Upgrade Impact: Action Required

To ensure your SharePoint integration continues to function after the upgrade, you must perform the following steps:

1. Update the CLASS file: The SharePointOnlineIntegration.class file has been updated. You must check in the new file to replace the existing one in your environment.
2. Restart the application server: After the file is updated, a server restart is required.
3. Generate new certificates: New security certificates must be generated for the DMS SharePoint integration.

For more information, refer to the TeamConnect DMS Connector SharePoint Online Integration v2.0 Release Notes.

Coordinated Setup Process

Please note that the SharePoint certificate generation is a one-time setup procedure. It requires coordination between the Hosting Team, your organization’s IT administrators, and the TeamConnect Admins/Upgrades Team.

3e. CustomBlock API in TeamConnect Enterprise 4.x

Important

• Update your source control systems and integrations to use these methods if you need to modify these dates programmatically.

• Existing runtime behavior is not affected. These changes apply only to systems using the API for automation or external updates.

Ability to Update OOTB Opened On and Closed On Dates for Matters

• Symptom: You cannot programmatically set the “Opened On” or “Closed On” dates for Matters using the CustomBlock API in TeamConnect Enterprise 4.x.

• Cause: In TeamConnect Enterprise versions prior to 8.0, the API did not include methods to update the Out-Of-The-Box (OOTB) date fields for Matters.

• Solution: From TeamConnect Enterprise 8.0 onward, the following methods have been added to the CustomBlock API:

  • void setOpenedOn(Date date);

  • void setClosedOn(Date date);

3f. Strict URL Updates in Spring Framework 6.2

1. Incorrect WebService URLS: Resolving “400 Bad Request” Errors from Double Slashes in URLs

• Symptom: You are receiving 400 Bad Request errors in your TeamConnect SOAP or REST web service calls.
   
• Cause: For improved security, Spring 6 (used in TeamConnect Enterprise 8.0) and later versions have enhanced URL parsing, which no longer permits double slashes (//) in request URLs.
   
• Solution: Review your integration’s request URLs and ensure you remove any double slashes.
   
• Example:
  • ✔️ Correct URL: https://.../TCE_TOMCAT_OLR_04/webser...oryTableSource
  • ❌ Incorrect URL: https://.../TCE_TOMCAT_OLR_04//webse...oryTableSource

2. Change in Login URL Case Sensitivity for Email Notifications

• Symptom: After upgrading to TeamConnect 8, users clicking on login hyperlinks in email notifications may encounter the following error:

Error 404: jakarta.servlet.ServletException: java.io.FileNotFoundException: SRVE0190E: File not found: /standardlogin

• Cause: TeamConnect 8 introduced an upgraded Spring framework that enforces case sensitivity in URLs. As a result, previously valid links such as /standardlogin (all lowercase) are now invalid. The login URL must now use the correct case: /standardLogin (with a capital “L”).
   
• Solution: 
  • Review all email templates and automated system notifications containing login links.
  • Update any instance of /standardlogin to the correct casing: /standardLogin.
  • Ensure the full login URL in templates follows this format: https://your-instance-url/standardLogin
  • No action is needed if you are already using /login or /standardLogin.
     
• Example: 
  • ✔️ Correct URL: https://.../standardLogin
  • ❌ Incorrect URL: https://.../standardlogin
     
• Read more about the Mixed-Mode Authentication here.

3g. Back Navigation updates in the Setup

• Symptom: When attempting to navigate back in setup, the page returns blank and displays the following error message: “This webpage requires data that you entered earlier in order to be properly displayed. You can send this data again, but by doing so you will repeat any action this page previously performed.”

• Cause: TeamConnect does not support browser-based back navigation in setup. In earlier versions, this limitation was not visible because browser caching allowed the page to reload. Starting in TeamConnect Enterprise 8.0, cache-control headers are set to no-cache, which prevents cached pages from being reused and results in the error.

• Solution: Do not use the browser’s Back button in setup. Use only the navigation controls provided within the setup interface to proceed.

3h. Office Suite Plugin Deprecation

Legacy Office Suite Plugin Replaced by Outlook 365 Add-in

Beginning with TeamConnect Enterprise 8.0, the legacy Office Suite Plugin is deprecated and is fully replaced by the modern 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.

Why We’re Making This Change: This transition to the Outlook 365 Add-in ensures long-term compatibility and security by aligning with modern technology standards.

• Modern Framework: The TeamConnect Outlook 365 Add-in is built on Microsoft’s modern web-based framework, replacing the legacy COM-based plugin model.

• Microsoft Roadmap Alignment: As Microsoft phases out support for COM Add-ins, especially in the “New Outlook,” this transition ensures your integration remains fully compatible with Microsoft’s future roadmap.

• Future-Ready: The TeamConnect Outlook 365 Add-in is fully supported on both Classic and New Outlook, making it easier for your organization to adopt the latest Microsoft innovations, including features like Copilot.

What’s New in the Outlook 365 Add-in

Major features from the legacy plugin – such as managing appointments, tasks, matter creation, and document interactions – are available in the new Add-in, along with new capabilities.

• Mobile Access: The Outlook Add-in is now available on mobile devices to enhance productivity and team collaboration. You can streamline workflows on-the-go with features like document uploads and matter creation. This is targeted for release in November 2025.

• Invoice Approvals: You can now approve invoices directly within the Outlook Add-in on both web and mobile devices. This feature allows attorneys to review key invoice details and perform single or bulk approvals within their email workflow, which eliminates delays and streamlines the process. This is also targeted for release in November 2025.

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.

For more information, refer to the TeamConnect Outlook 5.0 Release Notes.

3i. iText Library Replaced by OpenPDF

Action Required: iText Library Update

The iText library has been replaced by the OpenPDF library. This change affects all custom JAVA or CLASS files that include functionality for creating or modifying PDFs.

Upgrade Guidance and Recommendations:

• To minimize the immediate impact on your existing customizations during an upgrade, you have the option to temporarily add the old iText library back into your system under Documents → System → Libraries.

• It is strongly recommended that you test all PDF-related customizations without the legacy iText library to ensure long-term compatibility.

• If you encounter breaking changes, you must update the methods in your custom files to use the correct syntax from the OpenPDF library.

For more information, refer to the iText Library Updates guide.

3j. Library updates in TeamConnect Enterprise 8.0

Custom integrations that rely on the Apache POI and Apache CXF libraries are at the highest risk of being impacted by the upgrade. While it is unlikely that your custom Java code utilizes other bundled libraries, we recommend reviewing the complete list of changed libraries to confirm. For more information, see the complete list of the TeamConnect Enterprise 7.2 to TeamConnect Enterprise 8.0 library changes.