We have released today on semarchy.com this patch for Semarchy xDM 2024.1 LTS.
This patch solves the issues for customers such as Deutsche Bahn, CMA CGM, La Poste, Sanofi, Vetoquinol, Fortress, BPCE, Konecranes and ACCOS.
You can read the release notes (2024.1.12) for the public list of issues and JIRA for the full list.
New features
DM-496: xDM now supports Oracle Text capabilities to enhance search performance on Oracle databases. The following Oracle Text functions are now supported: CONTAINS, CATSEARCH, and MATCHES.
DM-512: The DETECT_DUPS validation now applies when editing existing records within a stepper, not just during initial record creation. This enhancement supports basic and ID-matched entities and is triggered on form exit. If a duplicate record is detected, an error or warning appears in the stepper interface. Duplicate resolution is limited to records created during the current transaction; merging or deletion must be done in the duplicate management interface.
MDM-15950: The delete phase of an integration job, specifically the Propagate Delete through References with Cascade Propagation step, has been optimized to reduce resource consumption, improve execution times, and ensure that jobs complete successfully.
MDM-17124: OAuth2 authentication is now supported in the SMTP notification server configuration to provide enhanced security.
Bug Fixes
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-16400: Clicking a hyperlink in a business view to navigate from a child entity record to a parent entity record may unexpectedly return users to the first tab of the parent record’s business view instead of the expected tab. This issue occurs when quickly returning to the parent record after opening the child record.
MDM-16443: When exporting records from a business object sorted by a specific attribute to XLSX format, fewer records than expected may appear if the display card uses the SQL expression ISNULL(F_ATTRIBUTE, '') and the export batch size is set smaller than the total record count. This issue affects SQL Server and PostgreSQL.
MDM-16480: Attempting to create the I1DL_COLLECTION_PREFERENCE index on Oracle databases configured with max_string_size=extended fails with the following error message: ORA-01450: maximum key length (6398) exceeded.
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-16623: Data export fails when attempting to export from a collection whose name contains non-ASCII characters. Export attempts in both Excel and CSV formats fail with the following error message: The Unicode character […] at code point […] cannot be encoded as it is outside the permitted range of 0 to 255.
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-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-17206: When using Azure OpenID Connect as an identity provider, logging out from an MDM application does not redirect users to the declared post-logout redirect URI.
The Docker image will be updated to this version in the following days.
Valentina ANTONOVA
New features
CONTAINS,CATSEARCH, andMATCHES.Bug Fixes
ISNULL(F_ATTRIBUTE, '')and the export batch size is set smaller than the total record count. This issue affects SQL Server and PostgreSQL.I1DL_COLLECTION_PREFERENCEindex on Oracle databases configured withmax_string_size=extendedfails with the following error message:ORA-01450: maximum key length (6398) exceeded.The Unicode character […] at code point […] cannot be encoded as it is outside the permitted range of 0 to 255.$..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.