This document details the upgrade information, new features, resolved issues, and known issues that are included in TeamConnect 4.2.3.
1Upgrading to 4.2.3
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 2)
To upgrade to TeamConnect 4.2.3, 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.3 release. Each known issue is documented in the following format:
•A description of the issue
•Internal tracking code
•Case number, if applicable
Issue: After posting, invoice totals differed between the Account Summary and Invoice Total fields.
Tracking code: SUPPORTPRI-16897
Case number: 2016-0215-231929
Issue: Global search indexing of files with email attachments failed and reverted all correctly indexed items.
Tracking code: SUPPORTPRI-19034
Case number: 2016-0701-259842
Issue: Performance slowed after significant (~4GB) email uploads.
Tracking code: SUPPORTPRI-19779
Case number: 2016-0628-259139
Issue: Users with rights exclusive to Group records were able to view Category Rights.
Tracking code: SUPPORTPRI-20241
Case number: 2016-1025-280990
Issue: Native reports in Data Warehouse did not return all invoices and financials.
Tracking code: SUPPORTPRI-19999
Case number: 2016-0928-275474
Issue: Double-clicking results in left navigation panel is generating duplicate requests.
Tracking code: SUPPORTPRI-16850
Case number: 2016-0129-228805
Issue: User without rights for embedded objects could not edit the respective parent matter.
Tracking code: SUPPORTPRI-27601
Issue: Editing a matter with embedded objects as a user without rights to the respective objects resulted in the objects being deleted after saving.
Tracking code: SUPPORTPRI-17326
Case number: 2016-0407-242164
Issue: User could not add new custom fields on an involved party of a dispute to reports.
Tracking code: SUPPORTPRI-20301
Case number: 2016-1101-282330
Issue: Jmonitor logs were not created.
Tracking code: SUPPORTPRI-20255, SUPPORTPRI-20466
Case number: 2016-1021-280459, 2016-1103-282863
Issue: Refreshing the Data Warehouse did not update reports with the most recent approvers.
Tracking code: SUPPORTPRI-19020
Case number: 2016-0609-255666
Issue: Non-US taxes were included in total amount of invoices.
Tracking code: SUPPORTPRI-15621
Case number: 2015-1019-208819
Issue: Records with multiple groups assigned were not accessible via search if any group lacked permissions.
Tracking code: SUPPORTPRI-19791
Case number: 2016-0712-261056
Issue: Posted invoices could not be edited.
Tracking code: SUPPORTPRI-20279
Case number: 2016-1101-282371
Issue: After importing a CTU package, user could not revert to previous design snapshot.
Tracking code: SUPPORTPRI-19896
Case number: 2016-0920-273878
Issue: NullPointerException thrown after calling a Custom Action method on a custom wizard.
Tracking code: SUPPORTPRI-20397
Case number: 2016-1114-284789