This document details the upgrade information, new features, resolved issues, and known issues that are included in TeamConnect 4.2.5.

1Upgrading to 4.2.5

You must be using one of the following TeamConnect versions in order to upgrade:

•3.0 SP1

•3.0 SP1 Update 1

•3.1

•3.1 Update 1

•3.1 SP1 (including Update 1 and  Update 2)

•3.2 (including Update 1 and Update 2)

•3.3 (including Update 1 and Update 2)

•3.3 SP1

•3.3 SP2

•3.3 SP3 (including any update from Update 1 through Update 18)

•3.4 (including any update from Update 1 through Update 8)

•3.4 SP1 (including any update from Update 1 through Update 20)

•4.0 (including any update from Update 1 through Update 14)

•4.1 (including Update 1)

•4.2 (including any update from Update 1 through Update 4)

To upgrade to TeamConnect 4.2.5, run the TeamConnect Installer as described in the TeamConnect Enterprise Installation Guide.

Note: These release notes assume that users are upgrading from TeamConnect 4.0.9 or later. If you are upgrading from a TeamConnect version prior to 4.0.9, please see the TeamConnect 4.0.9 Release Notes for information necessary upgrade changes and module dependencies.

2Resolved Issues

 

The following items have been resolved in the 4.2.5 release. Each known issue is documented in the following format:

•A description of the issue

•Internal tracking code

•Case number, if applicable

 

Issue:  TeamConnect did not load as expected when accessed through SAML.

Tracking code: SUPPORTPRI-28680

Case number: 2017-0317-350399

 

Issue: Full-text searching on Documents did not return matching results.

Tracking code: SUPPORTPRI-28786

Case number: 2017-0222-345605

 

Issue:  Searches on Relations did not return full results as designed.

Tracking code: SUPPORTPRI-29758        

Case number: 2016-0315-237549

 

Issue: XML file for newly created screen was not successfully migrated via CTU.

Tracking code: SUPPORTPRI-28522

Case number: 2017-0228-346625

 

Issue:  Custom Searches on custom date type fields generated search result error.

Tracking code: SUPPORTPRI-28620

Case number: 2017-0301-346814

 

Issue:  OptimisticLockException thrown due to concurrency errors when updating invoices via scheduled actions.

Tracking code: SUPPORTPRI-29208

Case number: 2017-0406-363968

 

Issue:  Each click after adjusting the Net Amount on the Summary Breakdown of an invoice replicated the adjustment.

Tracking code: SUPPORTPRI-29315

 

Issue: DMT import resulted in corrupt rule qualifier.

Tracking code: SUPPORTPRI-16374

Case number: 2015-1221-220886