> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.238/release-notes.md). # Release Notes ## Critical Updates & Actions Required MySQL versions earlier than 8.0 (e.g., 5.6 and 5.7) and Oracle versions earlier than 19c (e.g., 11g and 12c) are no longer supported by OIM, as they have reached end of life (EOL). **Actions:** * Upgrade MySQL to version 8.0 or later, or Oracle to version 19c. * Take a full backup of the OIM database and verify that it can be restored before upgrading. * Please refer to [Pre-Migration Checklist](https://docs.opshub.com/v7.238/pages/aNJ6cb19obZEir40YEKm#migrating-s-version-to-7.238-or-above) for more details. ## New Versions * Jira Zephyr Scale: 15.6.0 ## New Entities * DoorsNG: Module Artifact Format ## Enhancements ### Common * Added support for downloading usage reports for a configurable period of 1-12 months. * Added an optional **months** parameter to the UI, Admin API, and MCP tool to specify the reporting period. * By default, the report includes data for the last 6 months and the last 12 months. * Reference documentation: [Usage Reports](/v7.238/manage/advanced-utilities/usage-reports.md) ### Codebeamer * Added OAuth 2.0 (Client Credentials) authentication support using Microsoft Entra. ### Zendesk * Added automatic OAuth token renewal for Confidential OAuth client authentication, eliminating the need for manual token renewal. * Reference documentation: [Creating Confidential OAuth Client and Generating Client ID and Client Secret](/v7.238/connectors/zendesk.md#creating-confidential-oauth-client-and-generating-client-id-and-client-secret) ### MBSE * Improved MBSE synchronization when a very large number of elements (for example, over 100,000) have changed between two revisions. * Added support for MBSE remote links for model elements and projects, enabling synchronized links to open the corresponding element or project in the MBSE desktop client. ### qTest * Aligned qTest integration behavior with qTest Cloud by removing inline image support in Rich Text fields. Images are synchronized as attachments using the supported qTest functionality. ## Major Bug Fixes ### Common * Resolved a global failure that occurred after an OIM upgrade to versions 7.235, 7.236, and 7.237 on MS SQL Server that prevented users from viewing synchronization failures. * Resolved an issue where MBSE connectors could not be configured, or failed if already configured, under restricted systems licenses that included the SDK add-on. * Resolved an issue where integration dump export failed when an end system configured in the integration was inaccessible. * Resolved an issue where entities from ServiceNow, CASDM, Aras, Remedy, and Zendesk were synchronized to the first configured target project at the integration level instead of the correctly mapped project in integrations with multiple project mappings. ### Aha * Resolved a NullPointerException in Aha! integrations that occurred when a user entered incorrect metadata in the Aha system configuration, such as a value that does not exist in Aha or blank spaces. ### Doors * Resolved an issue where synchronization failed with a **NoSuchMethodError** due to outdated JAR files remaining in OIM after an upgrade to version 7.212 or later. ### Documentation * Enhanced Product Security documentation to improve vulnerability visibility across releases by listing open and resolved vulnerabilities with their severity, impacted area, reported release, and expected or actual fix release. * Updated the Azure DevOps connector documentation to mention that only revisions made within the work item's current project or entity scope are synchronized to the target. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.opshub.com/v7.238/release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.