This document details the upgrade information, new features, resolved issues, and known issues that are included in TeamConnect 5.0.2.
1Upgrading to 5.0.2
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 4.1.1)
•4.2 (including any update from Update 1 through Update 3)
•5.0 (including 5.0.1)
To upgrade to TeamConnect 5.0.2, run the TeamConnect Installer as described in the TeamConnect Enterprise Installation Guide.
Important: Users upgrading from 5.0 with a SQL Server database should run the upgrade scripts with the database in autocommit mode if their instance contains a large number of line items with adjustment types other than ‘NONE’.
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.
2Changes and Enhancements
TeamConnect 5.0.2 does not include any net new changes or enhancements. However, users upgrading from versions prior to 5.0.1 are encouraged to read the TeamConnect 5.0.1 Release Notes for changes carried forward from that release.
3Upgrade Considerations
TeamConnect 5.0.2 supports both JDK 1.7 and 1.8. Similarly, the 5.0.x line supports WebLogic 11g as well as 12c.
4Resolved Issues
The following items have been resolved in the 5.0.2 release. Each known issue is documented in the following format:
•A description of the issue
•Internal tracking code
•Case number, if applicable
Issue: Memo field size could not be increased for Internet Explorer 11 users.
Tracking code: SUPPORTPRI-27903
Case number: 2016-1219-334420
Originally fixed in: TeamConnect 4.0.15
Issue: Logging logs were unable to be viewed.
Tracking code: SUPPORTPRI-19483
Case number: 2016-0122-226739
Originally fixed in: TeamConnect 4.0.15
Issue: The teamconnect.properties file now allows for clients with clustered enviroments to prepend their JVM process ID.
Tracking code: SUPPORTPRI-28448
Originally fixed in: TeamConnect 4.0.15
Issue: Lookup table was corrupted after installing update.
Tracking code: SUPPORTPRI-17812
Case number: 2016-0420-245197
Originally fixed in: TeamConnect 4.0.15
Issue: Users without rights to the respective embedded objects of a dispute could not edit the parent dispute.
Tracking code: SUPPORTPRI-28462
Originally fixed in: TeamConnect 4.0.15
Issue: Project type could not be changed in custom search.
Tracking code: SUPPORTPRI-27877
Case number: 2016-1216-294287
Originally fixed in: TeamConnect 4.0.15
Issue: Updated amounts for invoice summary values on line items were not updated in real-time.
Tracking code: SUPPORTPRI-28274
Case number: 2017-0120-339644
Originally fixed in: TeamConnect 4.0.15
Issue: LookupItemParameter returned checklist rather than drop-down list as intended.
Tracking code: SUPPORTPRI-28515
Case number: 2017-0302-347170
Originally fixed in: TeamConnect 4.0.15
Issue: Changes to groups were not logged and exported in CTU package exports.
Tracking code: SUPPORTPRI-20053
Case number: 2016-1007-277203
Originally fixed in: TeamConnect 4.0.15
Issue: Error thrown when attempting to launch document generator from Documents tab of an Involved Party record.
Tracking code: SUPPORTPRI-27835
Case number: 2016-1216-294246
Originally fixed in: TeamConnect 4.0.15
Issue: Invoice versioning checked only for calendar year difference and ignored 12-month difference on dates.
Tracking code: SUPPORTPRI-28545
Case number: 2017-0224-346150
Originally fixed in: TeamConnect 4.0.15
Issue: Screen froze when adding Detail List qualifier to Rule Qualifier for Custom Objects.
Tracking code: SUPPORTPRI-20663
Case number: 2016-1205-291851
Originally fixed in: TeamConnect 4.0.15
Issue: API call Project.getDisplayString() did not format the string as expected.
Tracking code: SUPPORTPRI-28330
Case number: 2017-0207-342884
Originally fixed in: TeamConnect 4.0.15
Issue: Instances deployed on WebSphere 8.5 cluster experienced hung threads at persistence layer.
Tracking code: SUPPORTPRI-28301
Case number: 2017-0203-342198
Originally fixed in: TeamConnect 4.2.3 Patch 2, TeamConnect 4.2.4
Issue: Global search did not index and return newly added records as designed.
Tracking code: SUPPORTPRI-28434, SUPPORTPRI-28383
Case number: 2017-0208-343094
Originally fixed in: TCE 4.2.3 Patch 4, TeamConnect 4.2.4
Issue: Error thrown by using Project Search for line items during manual invoice creation.
Tracking code: SUPPORTPRI-28374
Case number: 2017-0120-339659
Originally fixed in: TCE 4.2.3 Patch 4, TeamConnect 4.2.4
Issue: Searching by City did not return relevant contacts in global search.
Tracking code: SUPPORTPRI-19524
Case number: 2016-0816-267472
Originally fixed in: TeamConnect Enterprise 4.2.4
Issue: Database indexing for global search required improvement for performance speed.
Tracking code: SUPPORTPRI-20181
Case number: 2016-0829-269791
Originally fixed in: TeamConnect Enterprise 4.2.4
Issue: Password expiration date did not function with Office and Notes integration.
Tracking code: SUPPORTPRI-28634
Case number: 2017-0302-347194
Originally fixed in: TeamConnect Enterprise 4.2.4
Issue: Security enhancements were made in regard to cross-site scripting.
Tracking code: SUPPORTPRI-28776
Originally fixed in: TeamConnect Enterprise 5.0.1 Patch 1
Issue: TeamConnect has been improved to support IBM Lotus Notes integration.
Tracking code: SUPPORTPRI-28142
Case number: 2016-0920-273835
Issue: Users without rights to upload a document still received upload confirmation message.
Tracking code: SUPPORTPRI-28840
Case number: 2017-0404-363405
