We have released today on semarchy.com this patch for Semarchy xDM 2025.1 LTS.
You can read the release notes (2025.1.5) 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.
Bug fixes
DM-368: Unexpected XML validation errors are logged when starting an MDM application or performing an offline installation without internet access. These warnings reference missing external schema files but do not prevent the application from starting normally.
DM-414: When a procedure fails to execute within a stepper trigger, xDM does not log the underlying SQL exception. As a result, the cause of the failure cannot be identified from the error logs.
MDM-16596: When restarting the application server during an integration job, the job recovers, but triggers two empty data notifications instead of a single notification with the processed data. This behavior occurs even for jobs processing valid records, especially with high data volumes (over 10,000) and when notifications are configured to trigger on empty datasets.
MDM-17116: Third-party library upgrade: Apache POI OOXML.
MDM-17134: An inefficient SQL query causes significant performance degradation for the Compute SA.F_ from SA.FP_ & SA.FS_ where F_ is null for {ParentEntity} reference task within integration jobs.
MDM-17140: Third-party library upgrade: Spring Security Crypto.
MDM-17153: When upgrading an SQL Server data location to version 2025.1.4, the upgrade process fails with a dependency-related error stating: com.microsoft.sqlserver.jdbc.SQLServerException: The index '<index_name>' is dependent on column '<column_name>'.
MDM-17157: During SAML login, valid identity provider (IDP) names are incorrectly rejected, despite conforming to the expected format. This issue triggers an unhandled IllegalArgumentException with the message: IDP name should only contain letters, numbers, dashes and underscores. Consequently, an HTTP 500 error occurs immediately after attempting to log in, which prevents access to xDM application components for users authenticating via SAML.
MDM-17169: Deleting a validation rule from the data model does not automatically remove its references from workflow transitions. No warning or error message is displayed during model or workflow validation, leading to a runtime error when the workflow attempts to evaluate the missing validation.
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.5) for the list of issues.
Breaking changes
Bug fixes
com.microsoft.sqlserver.jdbc.SQLServerException: The index '<index_name>' is dependent on column '<column_name>'. IllegalArgumentException with the message:IDP name should only contain letters, numbers, dashes and underscores.Consequently, an HTTP 500 error occurs immediately after attempting to log in, which prevents access to xDM application components for users authenticating via SAML.The Docker image and the Azure Solution Template will be updated to this version in the following days.