8.0 Known Issues
This article provides the information about the Known Issues reported at the time of release.
This is a living document that will report Known Issues at the time of a release and add new issues as they are reported. This document will also share the patch plan for reported issues.
How to Use this Document
This document does not reflect all client cases submitted through Support and recorded in Salesforce. This lists reflects the cases that have been escalated to Engineering for further action. Client cases that have been escalated to Engineering will be in one of four categories:
SOH - Support Office Hours - tickets that are escalated where Support needs assistance from an Engineer to find a solution. Some SOH cases are moved into the queue for a bug fix. Some are closed through other means like a workaround, configuration change, etc.
QAQ - these are tickets escalated from Salesforce or SOH that likely need a bug fix. In this stage, Engineering is vetting the ticket information and verifying a bug fix is the right solution.
SUPPORTPRI - QAQ tickets get escalated to the SUPPORTPRI bucket when we’ve determined that a fix is required to solve the problem, the ticket information is good and we can reproduce the issue.
TC - Regression bugs logged by internal teams for a fix. These are typically low priority otherwise they would have been fixed before the release went out.
NOTE: If you, the Client, do not see one of your cases here that you believe needs to be escalated to Engineering, please reach out to your Support representative.
Issues Reported against TCE 8.0
(if reported on a 8.0 patch, it will be listed under the tracking code)
| Tracking Code | Reporter | Issue | Patch / Update | Release Date | Status |
|---|---|---|---|---|---|
| TC-58793 | Internal | TeamConnect logs continuously loop and overflow when it cannot connect to ElasticSearch due to invalid server settings. This occurs because the global search indexing task retries connection attempts at a fixed interval defined by the elasticsearch.index.frequency setting in the teamconnect.properties file, causing repeated connection attempts and log entries. Workaround: None |
To Do | ||
| SUPPORTPRI-67542, TC-58469 | Internal | Reports generate incorrect results when filters are applied using custom fields with the ‘Has No Value’ operator. Specifically, child records and their respective custom field values are expected to display based on the filters applied, but they are missing from the report. Workaround: None |
To Do | ||
| TC-58382 | Internal | Users with just the “View Admin Settings” can still change the logger level or set a timed override. Workaround: To prevent users from modifying logger settings, such as changing the logger level or configuring a timed override, do not assign the “View Admin Settings” permission. |
To Do | ||
| TC-57950 | Internal | When Single Logout (SLO) is configured in SAML settings (for example, with Okta or Azure), logging out of the SSO session does not terminate the TeamConnect session as expected. After logging out from the SSO provider, the TeamConnect session remains active. This occurs even if the Single Logout URL is correctly configured in both the SAML settings and the application. Note: The fix for this issue will be available in TeamConnect Enterprise 8.0 Patch Bundle 2. |
To Do |
Known Issues marked as Won't Fix
These issue were deemed low user path/low priority. If you see an issue in this list that affects your team, please contact TeamConnect Support.
| Tracking Code | Reporter | Issue | Patch / Update | Release Date | Status |
|---|---|---|---|---|---|
| TC-58744 | Internal | When upgrading from Financial Management 7.0 Patch 1 to Financial Management 8.0 using the “Available Updates” option in TeamConnect, the upgrade may fail due to a duplicate “CjbInvoiceBudgetScreen$10.class” file. This file is present in both the source version and the upgrade package. The DMT (Design Migration Tool) is designed to reference the base version folder (7.0.0.0001) during module upgrades and does not consider patch folders. As a result, this causes a conflict during the upgrade. Workaround: Before running the upgrade using the “Available Updates” option, manually delete the “CjbInvoiceBudgetScreen$10.class” file from the “Documents” section in TeamConnect. This prevents the duplicate file conflict and allows the upgrade to complete successfully. Note: This step is not required when performing the upgrade via the CLI (Command Line Interface) tool. |
Won't Fix | ||
| TC-57959 | Internal | When creating a new connection in the DMS Connector tab, TeamConnect may use DMS class files from the application cache instead of the selected integration folder. As a result, replacing class files in an existing folder may not be reflected until the TeamConnect cache is cleared from Setup or a new folder is created. Workaround: Clear the application cache in Setup after updating the latest class files to ensure TeamConnect loads the latest versions. |
Won't Fix |