This document details the upgrade information, new features, resolved issues, and known issues that are included in TeamConnect 4.2.6.
1Upgrading to 4.2.6
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 16)
•4.1 (including Update 1)
•4.2 (including any update from Update 1 through Update 5)
To upgrade to TeamConnect 4.2.6, 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.6 release. Each known issue is documented in the following format:
•A description of the issue
•Internal tracking code
•Case number, if applicable
•Additional detail, if applicable
Issue: When equal .doc and .docx files were present, .docx file types were not returned by custom searches.
Tracking code: SUPPORTPRI-30318
Case number: 2017-0222-345605
Additional detail:
Steps to Reproduce |
Expected Results |
---|---|
1.Setup a TeamConnect instance with a SQL server database. 2.Upload two files with the same contents (one .doc and one .docx file type) 3.Perform a custom search with a filter criteria on Document Body 4.Enter content from test files and search |
Both files will be returned |
Issue: Custom searches on Relations did not return all correct results.
Tracking code: SUPPORTPRI-30326
Case number: 2016-0315-237549
Additional detail:
Prerequisites |
Actual Results |
Expected Results |
---|---|---|
Two Custom Objects |
Search enforces a two-way relationship, and only returns results that match both left and right relations |
Search should return results that match left OR right relations |
Custom Objects have a Relations block with at least one Project Relation type |
Issue: Approval request remained in Pending status after final approval.
Tracking code: SUPPORTPRI-30681
Case number: 2017-0525-374590
Additional detail:
Steps to Reproduce |
Expected Results |
---|---|
1.Cancel Approval Request 2.Update Matter and put the phase to Approval 3.Observe how Approval Request remains as Pending
|
Upon approving the request, the approval request will not display as Pending. Note: Scheduled action was being updated after deletion. Update did not occur is scheduled action ran independently; the error occurs when in tandem with workflow approval. |
Issue: For custom searches with mass edit view results rendered in a tiny column width, making the results difficult to view despite preset column widths.
Tracking code: SUPPORTPRI-29808
Case number: 2017-0518-372965
Issue: After a design change, CTU export package did not include all necessary XML (.scr) files, resulting in an error upon load for the recently created screen.
Tracking code: SUPPORTPRI-30334
Case number: 2017-0228-346625
Additional detail:
Steps to Reproduce |
Expected Results |
---|---|
1. Create a new screen with screen designer and publish to TC instance 2. Create a new block with that screen 3. Add that block to an object view 4. Create a CTU package for all updates 5. Import to TC instance |
The imported design should import successfully with all the necessary files to build the design change from its original environment that it was created in. |
Issue: Error thrown when searching on Custom Field date type.
Tracking code: SUPPORTPRI-30342
Case number: 2017-0301-346814
Additional detail:
Prerequisites |
Steps to Reproduce |
Expected Results |
---|---|---|
Instance setup with datasource |
1.Open a Custom Search 2.Choose a custom field (date type) as filter for e.g. Creation Date 3.On the Operators choose BETWEEN / OLDER THAN / NEWER THAN 4.Add values for the dates 5.Search |
Search completes successfully. |
.war file updated to not use a direct connection to the database |
||
Date type custom fields |
Issue: Scheduled actions could not complete due to concurrency errors on commit.
Tracking code: SUPPORTPRI-30366, SUPPORTPRI-30358
Case number: 2017-0406-363968
Additional detail:
Steps to Reproduce |
Actual Results |
---|---|
1. Take the DebugScheduledAction.java and edit the primary key in that Java file. 2. Compile this Java file in JDK7 to a class file 3. Add the DebugScheduledAction.class to the schedule action section of TCE. 4. Run the DebugScheduledAction.class as a scheduled action 5. While it is running for 15 seconds, go to the record and modify it 6. Check the logs. |
OptimisticLockException and NullPointerException errors shown in logs. |
Issue: Memo field could not be resized for Internet Explorer 11 users.
Tracking code: SUPPORTPRI-30562
Case number: 2016-1219-334420
Issue: Templates for Multi-Value List fields with prerequisite custom fields froze screen when configured.
Tracking code: SUPPORTPRI-19798
Case number: 2016-0912-272121
Issue: Global search (Elasticsearch) stopped indexing new entries after a NullPointerException was encountered in Elasticsearch logs.
Tracking code: SUPPORTPRI-30813
Case number: 2017-0619-379654
Issue: Post-commit rules designed to print a debug statement included an extra statement which resulted in executing the post-commit action twice.
Tracking code: SUPPORTPRI-29885
Case number: 2017-0619-379621
Issue: TeamConnect crashed with an OutofMemory error after approving a Budget Request received via CSM.
Tracking code: SUPPORTPRI-30095
Case number: 2017-0606-376963