We have released today on semarchy.com this patch for Semarchy xDM 2025.1 LTS.
You can read the release notes (2025.1.4) for the list of issues.
Breaking changes
MDM-16712: An upgrade to the Spring framework in xDM 2025.1.3 has introduced incompatibility between the new Spring Security version and Tomcat 9. To ensure proper functionality, migration to Tomcat 10 or 11 is required.
New features
MDM-10809: The integration process now uses the UPDATE_WHILE transitive closure by default to improve performance, rather than requiring an opt-in system property. This change preserves the -Dmdm.integjob.defaultTransitiveClosureMode=UPDATE_WHILE system property, allowing users to revert to the previous behavior if needed.
MDM-14938: xDM now supports Oracle 23c (including Oracle 23ai). After upgrading to version 2025.1.4, platform administrators must grant additional permissions to the repository schema user to ensure the system can execute cryptographic functions required for the consolidation process.
MDM-16068: The integration process now supports single-step consolidation by default to improve performance for large volumes of data, using the new property xdm.integjob.useSingleStepConsolidation=true, which applies to all integration jobs unless a specific job parameter overrides it. This change retains the system property, allowing integration designers to revert to the previous behavior if necessary.
Bug fixes
MDM-16798: When configuring an identity provider, a misconfigured role mapping with a null role entry (provider or mapped) causes an unexpected error and prevents the configuration from being saved. No clear error message is shown in the user interface, and the only indication of the issue is a ValueInstantiationException: Cannot construct instance of com.semarchy.platform.idm.core.config.idp.RoleMapping$MappingEntry written to the PDE log.
MDM-16800: When using the JSONPath selector $..Attribute in REST client tests, users may encounter unexpected behavior, where only a single object is returned instead of multiple objects. This change in behavior results in incomplete or inaccurate data being fetched, as visible in the REST client test dialog.
MDM-17040: When using a custom search form to filter records in a collection view, the corresponding value picker does not show any available options, preventing users from selecting filter values.
MDM-17099: When attempting to install Semarchy xDM 2025.1.3 on-premises (preconfigured with Apache Tomcat) or via Docker, platform administrators encounter a 403 Forbidden error during the setup token validation step. This error prevents further progression in the installation process.
MDM-17101: When attempting to import a model via the Application Builder, the Finish button in the import dialog remains grayed out. This issue also affects the import of image libraries and custom translations.
The Docker image and the Azure Solution Template will be updated to this version in the following days.
Valentina ANTONOVA
We have released today on semarchy.com this patch for Semarchy xDM 2025.1 LTS.
You can read the release notes (2025.1.4) for the list of issues.
Breaking changes
New features
UPDATE_WHILEtransitive closure by default to improve performance, rather than requiring an opt-in system property. This change preserves the-Dmdm.integjob.defaultTransitiveClosureMode=UPDATE_WHILE system property, allowing users to revert to the previous behavior if needed.xdm.integjob.useSingleStepConsolidation=true , which applies to all integration jobs unless a specific job parameter overrides it. This change retains the system property, allowing integration designers to revert to the previous behavior if necessary.Bug fixes
nullrole entry (provider or mapped) causes an unexpected error and prevents the configuration from being saved. No clear error message is shown in the user interface, and the only indication of the issue is aValueInstantiationException: Cannot construct instance of com.semarchy.platform.idm.core.config.idp.RoleMapping$MappingEntry written to the PDE log.$..Attributein REST client tests, users may encounter unexpected behavior, where only a single object is returned instead of multiple objects. This change in behavior results in incomplete or inaccurate data being fetched, as visible in the REST client test dialog.403 Forbiddenerror during the setup token validation step. This error prevents further progression in the installation process.The Docker image and the Azure Solution Template will be updated to this version in the following days.