This document details the upgrade information, new features, resolved issues, and known issues that are included in TeamConnect 4.0.16.
1Upgrading to 4.0.16
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 15)
To upgrade to TeamConnect 4.0.16, 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.
2Changes and Enhancements
The following changes and enhancements have been added as of 4.0.16. Each enhancement is documented in the following format:
•A description of the enhancement
•Internal tracking code
•Additional detail
Enhancement: Users are able to include CSM logs in email notifications. A Download button has been added to the Logging page for a .zip file download of the instance’s logs.
Tracking code: SUPPORTPRI-30111
Additional detail: In order to include the CSM logs in Email Notifications, users will need to leverage an added API call. Refer to the image below for information on how to use the new API.
3Resolved Issues
The following items have been resolved in the 4.0.16 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: Users were able to log into or stay logged into TeamConnect. BadCredentialsException was thrown upon accessing the TC site.
Tracking code: SUPPORTPRI-28680
Case number: 2017-0317-350399
Additional detail:
Prerequisites |
Expected Results |
|---|---|
Clustered TeamConnect instance |
Users are able to log into the application normally. |
SAML Authentication |
Issue: Triggering a workflow approval upon invoice posting caused error when viewing the Workflow Process Manager tool.
Tracking code: SUPPORTPRI-30623
Case number: 2017-0502-369167
Additional detail:
Steps to Reproduce |
Expected Results |
|---|---|
1.Create a normal user “x” 2.Have/create an approval rule where invoice posting initiates workflow approval 3.Login as “x” and go to Approvals 4.Error is thrown |
Approval rule will fire upon invoice posting as designed. |
Issue: Corrupted rule qualifier existed due to incorrect DMT import of a primary key.
Tracking code: SUPPORTPRI-16374
Case number: 2015-1221-220886
Issue: Custom searches on Relations did not return all correct results.
Tracking code: SUPPORTPRI-17027
Case number: 2016-0315-237549
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-29877
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 Note: This error was not reproducible across all matters in all instances. |
Upon approving the request, the approval request will not display as Pending. |
Issue: Custom field date type returned paged search result error.
Tracking code: SUPPORTPRI-28620
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: Error thrown due to concurrency issues when updating invoices via scheduled action.
Tracking code: SUPPORTPRI-29766
Case number: 2017-0406-363968
Additional detail:
Steps to Reproduce |
Expected 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, modify the record. 6. Check the logs. |
No error should occur. |
Issue: OptimisticLockException occurs after updating invoices through scheduled actions due to either customizations or user edits between the update and commit.
Tracking code: SUPPORTPRI-29774
Case number: 2017-0406-363968
Issue: Line Items could not be sorted as per the ‘Date’ criteria as set on Default Sort Order.
Tracking code: SUPPORTPRI-30615
Case number: 2015-0423-131327
Issue: Updating a vendor contract matter could not be saved without throwing Oracle error.
Tracking code: SUPPORTPRI-19064
Case number: 2016-0711-260914
Issue: The "Adjusted" and "Total Adjustment" fields are updated based on the displayed value every time the user clicks away from the Adjustment field.
Tracking code: SUPPORTPRI-29782
Additional detail:
Steps to Reproduce |
Expected Results |
|---|---|
1. Create an Invoice with a Fee Line Item and post it into workflow Make sure the approval rule has "Updates to record pending approval" set to allow 2. Navigate to Summary Breakdown 3. Click on the Net Amount 4. Make an Adjustment 5. Click away from the Adjustment field 6. Click on and away from the Adjustment field several more times. |
Adjustment and Total Adjustment fields are updated based on value when window is first opened. |
