TeamConnect Version 7.0 is now Available!

We are delighted to announce the release of TeamConnect version 7.0.  Included below is a summary of key features.

We also want to let you know about an architectural update which, though very unlikely, could impact any custom java code integrations and therefore may require some action when you are ready to upgrade. We have created the below, detailed  page to outline the possible impacts and steps to prepare you for the version 7.0 upgrade.

Key Enhancements & Features

• InvoiceIQ:  Invoice Review powered by Machine Learning: Improve invoice review timelines and provide potential adjustment opportunities through machine learning recommendations on line items; activity categorization; custom rules; GC, AGC and compliance dashboards using TCBI.

• Joint Timekeeper + Rate Approvals: Streamline the onboarding of new firms and timekeepers by combining the approval of Timekeepers and Rates in a single-step; validations in Collaborati prior to Timekeeper submission.

• Invoice Review Improvements:  Direct client-based usability enhancements, that include easier vertical and horizontal scrolling to review invoices faster and configuring of custom fields for My Approvals with regards to invoices.

• Heartbeat:  This feature transmits TeamConnect enterprise and module versions and environment (ex:  database vendor and version) information back to Mitratech.  This feature is defaulted on to streamline the Upgrades Included process for you.

• Spring Update:  As part of Mitratech maintenance processes, component libraries are periodically updated for performance, sustainability, and security reasons.

• Support for Websphere Liberty 21.

Architectural Update

With the version 7.0 upgrade, the underlying Spring framework upon which TeamConnect is built has been updated from version 3 to version 5, which keeps us current on support and reduces risk of encountering vulnerabilities when performing application scans.  

Important: Impact and Action Needed Prior to Upgrading

Any client who has a custom integration with TeamConnect should follow the plan below to ensure a smooth upgrade to version 7.0.

The TeamConnect platform provides extensibility by allowing Services, Partners, and Client developers to create custom integrations through use of custom java code.  It is this custom code that may need updates due to the Spring library updates.

NOTE:  It is highly unlikely that custom integrations will rely on libraries that have been changed.  Best practice is to upload library files to the TeamConnect system libraries folder when creating custom integrations.  However, it is possible a custom integration was written that may leverage the library files deployed with TeamConnect.  If this has been done, then the integration may need to be updated as part of the version 7.0 upgrade plan.

Please review your custom integration code and note the following recommendations:

1. Identify any and all custom integrations to TeamConnect.  If none exist, then the remaining activities can be ignored.

2. Determine whether any of the custom code utilizes libraries that are distributed within the TeamConnect deployment (see Impacted Library Files list, below).

3. Take note of the details of the integration (what files are used, what actions are performed) and then reach out to your account manager so that we can determine a recommended path for remediation.

4. Prior to creating your upgrade plan from your TeamConnect current version to TeamConnect version 7.0, inform your Mitratech contact (Account Manager and/or your Upgrades Included point of contact) of these integration details so that remediation planning can be included into the upgrade Project.  Remediation will be handled on a case by case basis, depending on the integration code and the files used.

We are here for YOU and to make this a smooth upgrade.  If you have any questions at all, please reach out to your Account Manager to arrange a call.

Impacted Library Files 

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.

Here is the full list: