Portal

Hello Team,

We have released today on semarchy.com this patch for Semarchy xDM 2025.1 LTS.

You can read the release notes (2025.1.1) for the list of issues.

Bug Fixes

• MDM-16211: On SQL Server, attempting to import more than 2100 records using a data-driven workflow results in the workflow instance failing with the following error message: The incoming request has too many parameters. The server supports a maximum of 2100 parameters.
• MDM-16506: Third-party component upgrade: Apache MINA Core.
• MDM-16572: Attempting to delete a large number of records (e.g., 40,000 or more) from a business view in an MDM application does not trigger a deletion load to process the records.
  This failure results in delays, unresponsive behavior, or failed deletions.
• MDM-16580: The User Task Instances REST API endpoints fail with a 500 Internal Server Error when accessed with an API key assigned to a workflow administrator role.
• MDM-16581: The User Task Instances REST API endpoint returns both KILLED and STARTED steps when filtered on userTaskStatus=STARTED, instead of only showing STARTED steps.
• MDM-16597: Workflow notifications for candidates and assignees may fail or show incomplete information when the root entity’s FDN attribute includes a lookup and no corresponding child entity exists. In this case, the lookup returns a null value. If the lookup is not enclosed in a COALESCE function, the notification fails without recording an error in the PDE log. If the lookup is wrapped in COALESCE, the notification is sent successfully, but the display card in the email does not include the lookup value.
• MDM-16600: When exporting data in batches using the -DexportBatchSize=N system property, queries may gradually increase in size due to the accumulation of batch filters. While unlikely, this behavior could affect performance or reach database limitations, such as SQL Server’s 2100-parameter limit.
• MDM-16613: Workflow notification emails do not correctly embed the application logo if the logo file name contains a blank space. Instead, the logo is sent as an attachment.
• MDM-16624: Upgrading a data location to version 2025.1.0 fails on SQL Server databases with the following error message: A SQL exception was caught while processing SQL statement: alter table (…) alter column (…) bitNULL.
• MDM-16639: When an enricher nullifies an attribute upon opening a form, re-entering the same value that the attribute previously had results in the attribute being treated as null.
• MDM-16656: When creating a child record, using a parent foreign display name (FDN) in the form may cause the form to load incorrectly, resulting in hidden fields or a blank form after entering the parent FDN value. This issue occurs during any transition that accesses the parent FDN.

The Docker image and the Azure Solution Template will be updated to this version in the following days.

Hello Ajay,

2025.1.1 version is compatible with 

• Apache Tomcat 9.0.x

• Apache Tomcat 10.1.x

• Apache Tomcat 11.0.x

This is listed here in our documentation for your reference https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Install/system-requirements.html#_supported_application_servers

Please pay attention to the fact that starting 2025.1.3, tomcat 9.0.x is no longer supported.

I hope this helps.

Best regards,

Stéphanie.