We have released today on semarchy.com this patch for Semarchy xDM 2025.1 LTS.
You can read the release notes (2025.1.8) for the list of issues.
New features
DM-762: Semarchy xDM supports PostgreSQL 17 across on-premises installations and cloud platforms, including Azure Database for PostgreSQL - Flexible Server, Amazon RDS for PostgreSQL, Amazon Aurora PostgreSQL, and CloudSQL for PostgreSQL.
DM-736: The Email notification enricher has been integrated into xDM, providing a built-in capability to automate and audit custom email notifications. Acting as a bridge between xDM and an SMTP notification server, this plugin collects and structures email notification data (such as recipients, subject, and content), submits it for delivery, and captures the outcome of each notification attempt.
Bug fixes
DM-908: Third-party component upgrade: Apache Tomcat for xDM preconfigured.
DM-907: Third-party component upgrade: Apache Tomcat for xDM preconfigured.
DM-906: Third-party component upgrade: Apache Tomcat for xDM preconfigured.
DM-842: In a record creation workflow, removing a record within a user task that runs inside a parallel block does not persist after the block completes. Updates made to the parent record are saved, but deleted child records reappear in subsequent tasks.
DM-801: In a workflow that includes a parallel block, adding a child record within a user task fails unless the parent record is also modified. This occurs when the parent and child entities share the same stepper, causing the error dataSetChanges is incompatible with targetDataSet if attempting to add a child record without editing the parent.
DM-780: When creating a new fuzzy lookup rule, clicking any SemQL editor button immediately triggers an error, which prevents users from adding the rule. The issue occurs in models where the fuzzy lookup rule involves entities connected through relationships that have different navigation directions depending on context.
DM-768: Third-party library upgrade: Spring Security Core.
DM-517: In a stepper that includes a collection step for linking records between entities in a many-to-many relationship, the deployed application does not respect the search configuration order defined in the model. When search types are reordered or disabled, the configured order is not reflected in the search dialog.
The Docker image and the Cloud releases will be updated to this version in the following days.
Valentina ANTONOVA
New features
Bug fixes
dataSetChanges is incompatible with targetDataSetif attempting to add a child record without editing the parent.