Resolved Issues
Connect
Software version: 25.2
The following issues were resolved in this release. No configurations changes are required unless explicitly stated.
| Key | Summary |
| OCTCR17W1703115, SC:02899125 | Resolved an issue where an invalid fallback user configuration could disrupt the communication layer with the database. |
| OCTCR17W1347745, SC:01839350 | Fixed the issue by improving the email format to ensure that individual error messages are now clearly separated by new lines (CR/LF). |
| OCTCR17W1793762 | Fixed the issue in utilities by ensuring consistent UTF-8 encoding for reading and writing files in mfcDataSourceUser and mfcUserMap, resolving encoding inconsistencies across different utilities. |
| OCTCR17W1780178, SD00491317 | Fixed an issue where stopping Connect while connections were starting or running, changing the server GUID, and then restarting Connect could cause connections to become stuck and unresponsive. |
| OCTCR17W1813226, SC:03024852 | Fixed a compatibility issue with Dynatrace OneAgent that could prevent database initialization in certain environments. |
| OCTCR17W1797579, SC:03016639 | Fixed an issue in mfcAudit utility where notifications were not sent for specific Skipped items. |
| OCTCR17W1716606, SC:02926431 | Failing calculated values are now highlighted in the audit log. |
| OCTCR17W1803432, SC:03024852 | Improved logging for upgrade procedure. |
| OCTCR17W1824099, SC:03090964 | Resolved an issue where multiline JavaScript expressions were not correctly parsed in calculated values. |
| OCTCR17W1780178, SD:00491317 | Resolved an issue that prevented users from starting or stopping connections. |
| Key | Connector | Summary |
| OCTCR42D414005, SC:01962351 | Jira | When a connection contains multiple Jira projects and one is archived, the entire connection would stop. This issue is now resolved by skipping the sync set for the archived project instead of halting the entire connection. |
| OCTCR17W1811345, SC:03081401 | SDP/SDM | Resolved an issue where business rules were not correctly parsed when using the 'Modify lookup list' action with a custom list specification. |