Semarchy xDM 2024.4 release notes

MDM-7254: With PostgreSQL, the application server hosting the xDM instance and the database server must be in the same timezone to avoid inconsistent dates in the integration loads.

MDM-7917: A boolean field default value is set to null when creating a record and to false when editing it.

MDM-7949: A model with a physical column name using a reserved name raises a validation error but can be deployed.

MDM-8034: When stopping xDM using the Tomcat Manager, a Severe message is logged with org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks…​. This message is a known Tomcat issue that can be ignored.

MDM-8703: Data import from Excel does not properly handle dates before February 28, 1900.

MDM-8977: Changing a reference to a fuzzy-matching entity while authoring a master record is not taken into account.

MDM-9184: Existing FS_ and FP_ reference column values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

MDM-10193: When a record in an entity is updated, records with the same ID in inheriting entities are also updated.

MDM-10269: Using the SEM_NUMBER_TO_CHAR function with a string argument does not raise a model validation error but fails with an invalid number error in the log.

MDM-10319: Authoring the same record in two different browser windows makes the second authoring fail with a java.lang.IllegalStateException: Current Step (products) should be a form step error.

MDM-10738: Duplicate flexElement error occurs at runtime when using a transition named like a form element (e.g., "field", "container") in a business view.

MDM-12415: Long-integer values higher than 9223372036854700 raise errors when authoring (Invalid ID for data type (longInteger)) or browsing (<entity name> not found) records.

MDM-13099: When moving an attribute from one group to another governed by a different survivorship rule, any overridden value within this attribute causes all other attributes in the new group to be considered overridden as well. Consequently, the values of these attributes may be nullified during the subsequent execution of the certification process, unless override values have previously been defined. To minimize potential negative impacts on data consistency and accuracy, designers should consider moving attributes with pre-existing overridden values to a group that does not include any other attributes.

MDM-16102: The SEQ_NEXTVAL function implementation for Snowflake leads to improper sequence value generation.

MDM-16107: When using Snowflake as the database system, paginated queries generated by DataPageJdbcHelper return inconsistent and unpredictable pagination results.

MDM-16120: In Oracle database environments, clicking the application icon on the xDM welcome page causes an infinite loading loop and triggers a java.sql.SQLSyntaxErrorException error.

MDM-7254: With PostgreSQL, the application server hosting the xDM instance and the database server must be in the same timezone to avoid inconsistent dates in the integration loads.

MDM-7917: A boolean field default value is set to null when creating a record and to false when editing it.

MDM-7949: A model with a physical column name using a reserved name raises a validation error but can be deployed.

MDM-8034: When stopping xDM using the Tomcat Manager, a Severe message is logged with org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks…​. This message is a known Tomcat issue that can be ignored.

MDM-8703: Data import from Excel does not properly handle dates before February 28, 1900.

MDM-8977: Changing a reference to a fuzzy-matching entity while authoring a master record is not taken into account.

MDM-9184: Existing FS_ and FP_ reference column values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

MDM-10193: When a record in an entity is updated, records with the same ID in inheriting entities are also updated.

MDM-10269: Using the SEM_NUMBER_TO_CHAR function with a string argument does not raise a model validation error but fails with an invalid number error in the log.

MDM-10319: Authoring the same record in two different browser windows makes the second authoring fail with a java.lang.IllegalStateException: Current Step (products) should be a form step error.

MDM-10738: Duplicate flexElement error occurs at runtime when using a transition named like a form element (e.g., "field", "container") in a business view.

MDM-12415: Long-integer values higher than 9223372036854700 raise errors when authoring (Invalid ID for data type (longInteger)) or browsing (<entity name> not found) records.

MDM-13099: When moving an attribute from one group to another governed by a different survivorship rule, any overridden value within this attribute causes all other attributes in the new group to be considered overridden as well. Consequently, the values of these attributes may be nullified during the subsequent execution of the certification process, unless override values have previously been defined. To minimize potential negative impacts on data consistency and accuracy, designers should consider moving attributes with pre-existing overridden values to a group that does not include any other attributes.

MDM-13817: Semarchy now supports Snowflake to host data locations. This feature is in preview and is not intended for production environments.

MDM-14021: The performance of named queries that contain single-record expressions has been optimized, with single-record expressions being executed in the same SQL query as the root entity, rather than generating separate queries for each expression. This results in faster response times for named queries. This optimization can be activated by setting the system property xdm.namedqueries.singlerecordexpressions.optimise to true.

MDM-14493: A new Call Procedure automation is now available to invoke predefined database procedures as part of a workflow’s execution process, enabling seamless integration of custom database logic into data-driven workflows.

MDM-15477: Specific validations can now be configured and applied during workflow transitions in data-driven workflows. Workflow designers can define custom validation rules for each transition, specifying whether validations should block, warn, or be skipped. When executing a workflow instance in an MDM application, a dialog displays validation results, providing clear feedback on failed checks and offering options to either proceed or cancel the transition.

MDM-15408: Security enhancement: SVG files.

MDM-15565: In a localized model using the translation bundle for attribute names, the advanced search filters fail to display certain translated attributes in search results as expected.

MDM-15604: Random database locks occur on instances running on SQL Server.

MDM-15611: The platform’s identity management system treats usernames with different cases (uppercase and lowercase) as distinct entries when using LDAP authentication, leading to duplicate user entries.

MDM-15622: Due to a browser limitation that restricts file sizes to 2 MB, trying to download or view binary files larger than 3 MB via a hyperlink in both legacy and data-driven workflows, as well as in steppers during direct authoring, results in a redirect to a blank page with the URL about:blank#blocked. To ensure consistent access to large files, all attachments exceeding 2 MB are now automatically downloaded, regardless of the browser.

MDM-15633: When attempting to filter data from a collection using the Form search type, the filter fails to return any records if the attribute value contains a [ or ] character in the primary text of the entity’s display card. This issue is observed specifically when using SQL Server or Azure SQL Database.

MDM-15634: Third-party component upgrade: Apache Tomcat.

MDM-15648: Third-party component upgrade: Microsoft JDBC Driver for SQL Server.
To take full advantage of the latest enhancements and improve connection resiliency, platform administrators may set the connectRetryCount and connectRetryInterval driver properties when configuring a datasource in xDM. Additionally, platform administrators are advised to review and explicitly configure the encrypt property for all SQL Server datasources following the upgrade, setting it to true to enable encryption or false if encryption is not necessary, as the JDBC driver defaults to interpreting the property as true if it is left unset.

MDM-15652: When two or more Browse Business View actions point to the same business view, selecting one causes all related actions in the navigation drawer to be highlighted, making them appear active.

MDM-15654: Attempting to install the xDM SDK version 2024.2.1 in Eclipse fails with the error message Cannot complete the install because one or more required items could not be found.

MDM-15660: The repository upgrade may fail to complete if an exception occurs during post-upgrade controls, leaving the platform in an unresolved state with no error or success status.

MDM-15661: When a step or workflow definition is renamed or deleted from the Workflow Builder, any attempt to display the task history in the My Completed Workflow Tasks view under History in the My Tasks interface fails, resulting in the following exception: Workflow definition <workflow definition name> missing for user task.

MDM-15663: When calling an AI-based classification enricher (either zero-shot or few-shot) to classify a product based on its description during record creation, a required field, despite being filled, displays an error indicating that the value has not been provided. In record editing, if a previously selected field is cleared before triggering the enricher, the field is correctly reselected, but Semarchy still displays an error incorrectly stating that the field is required, even though it has been populated.

MDM-15754: Third-party component upgrade: Apache CXF Core.

MDM-15755: Third-party component upgrade: Apache CXF Runtime HTTP Transport.

MDM-15764: Security enhancement: Semarchy Email enricher.

MDM-15823: Trying to open a workflow task from the My Tasks interface triggers an internal server error ( Missing named parameters: :<color>) when a background color is set on collection columns using SemQL.

MDM-15833: In the Image Libraries section of the Configuration interface, the non-editable, built-in image libraries have been removed from the list of options in the Target Library drop-down menu.

MDM-15850: When retrieving the platform status using the REST API, the API returns an HTML response instead of the expected JSON-formatted error. This occurs when an API key without administrator access is used, resulting in a 403 Forbidden error.

MDM-15868: After upgrading from version 5.3.26 to 2024.1.4, opening or editing forms in the Application Builder fails, resulting in a ClassCastException error recorded in the PDE log: jakarta.json.JsonException: Provider org.glassfish.json.JsonProviderImpl could not be instantiated.

MDM-15910: Third-party component upgrade: path-to-regex package.

MDM-15957: Third-party library upgrade: DOMPurify.

MDM-15963: Third-party library upgrade: Google Protocol Buffers for Java.

MDM-15986: Data-driven workflows with a Set Workflow Metadata automation step fail when the due date is set using the COALESCE function, with the error DUE_DATE resolved value '…​' is not valid (must be a Date) written to PDE log and displayed in the workflow administration section in My Tasks.

MDM-16073: After executing the create-azure-function-app.sh script to deploy the Microsoft Purview Connector, the scheduledxDMPurviewConnector function is not deployed to the Azure Functions app as expected.