Semarchy xDM 2024.1 release notes

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-14021: The performance of named queries that include 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-15408: Security enhancement: SVG files.

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-15754: Third-party component upgrade: Apache CXF Core.

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

MDM-15810: When using the Mass Update action in an MDM application, users with read-only access to an entity can still modify or remove data from its attributes, despite receiving warnings that indicate insufficient permissions.

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-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-15907: In an MDM application, when a hyperlink field is configured with a string datatype, using URL as the link source and set to open in a new window, the Display Text value is rendered incorrectly in the collection view, appearing cut off from the bottom. This issue occurs specifically when there is only a single-line value in each column of the collection.

MDM-15935: In versions 2024.1.7 and 2024.1.8, the encrypt driver property has been set to false by default on existing and new SQL Server datasources. Platform administrators should review their datasource configurations after the upgrade and assess the encrypt property setting to ensure it aligns with their intended database security practices.

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

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

MDM-16092: Third-party library upgrade: Apache Commons IO.

MDM-16125: With the optimization parameter xdm.namedqueries.singlerecordexpressions.optimise enabled, calls to named queries fail in the following scenarios: when a named query of type Single Record Expression includes a reference relationship that targets a foreign attribute with a name differing from that of the referenced entity; and when a SemQL expression is specified at a non-root level within the query, which triggers an invalid SemQL request error.

MDM-16129: After upgrading to version 2024.1.8, validation rules using square brackets in LIKE statements may fail in SQL Server environments, potentially resulting in valid data being incorrectly rejected. This issue is associated with the fix for MDM-15633, which is disabled by default for SQL Server in version 2024.1.9. To apply the MDM-15633 fix and escape square brackets in LIKE expressions, platform administrators can set the com.semarchy.xdm.sqlserver.escapeSquareBracketsInLikeExpressions system property to true.

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-15604: Random database locks occur on instances running on SQL Server.

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-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-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-15601: Workflow tasks assigned to users with an apostrophe (') or left single quotation mark (‘) in their username—​or to a role including such users—​do not appear in the My Tasks interface. Instead of displaying the assigned tasks, a Generic.UnexpectedError error page is shown.

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-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 library upgrade: Azure Identity.

MDM-15648: Third-party component upgrade: Microsoft JDBC Driver for SQL Server. This upgrade ensures compatibility with JDK 17. To leverage the latest enhancements and improve connection resiliency, platform administrators may set the connectRetryCount and connectRetryInterval driver properties when configuring a datasource in xDM.

MDM-15764: Security enhancement: Semarchy Email enricher.

MDM-15965: Models containing validation errors cause xDM to fail during startup with the following error message: Unable to start Semarchy xDM platform caused by: NullPointerException.

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-14786: Even after data locations are deleted, xDM continues to send information regarding these data locations to the license server.

MDM-14797: When attempting to publish records that reference a data-entry-based golden record related to a fuzzy-matching entity, despite the F_ column being appropriately populated in the SD table, the certification process fails in referencing the parent record, with the resulting golden record exhibiting a null value in the F_ column. The fix for this issue will only take effect after the model has been redeployed.

MDM-15302: Within the Workflow Builder, the attribute list in the SemQL editor’s Assignment Condition view remains empty when the related model includes entities that inherit from other entities.

MDM-15374: Security enhancement: internal API access control.

MDM-15375: Within an MDM application, the Explain Record action encounters an unexpected exception when the current user lacks access to one or more attributes due to the model privilege grants defined for their role(s). Specifically, if a fuzzy-matching entity’s attribute is granted None access but included in the Explain Record view, the following error occurs: com.semarchy.mdm.datahub.security.datapermission.DataPermissionDeniedException: READ for expression [<attribute>] on entity <Entity> is not authorized.

MDM-15449: The initial attempt to call the REST API or application readiness probe endpoints results in a 503 error, with subsequent identical attempts returning a 204 response. Starting with version 2024.1.6, the model cache for these endpoints is loaded at startup to prevent the initial 503 error. This change may increase startup times for applications with large models. Platform administrators can revert to the previous behavior by setting the system property xdm.api.rest.model.unsecured.cacheEagerLoad.enable to false, delaying the model cache loading until the first call to the probe API endpoints.

MDM-15476: When accessing a dashboard application incorporating multiple dashboards that exceed the visible area in the navigation drawer, the scroll bar is missing from the side navigation panel, which makes it challenging to navigate beyond the dashboards immediately visible in the list.

MDM-15531: When drilling down into a dashboard chart, rearranging the column order using the Select Columns action does not result in the expected modification of column order in the displayed table view.

MDM-15541: When trying to assign a legacy workflow task in My Tasks, the list of candidate assignees shows usernames instead of first and last names.

MDM-15574: When configuring a user task step in the Workflow Builder, if the primary text expression of a display card from the relevant entity contains an FDN_ attribute from a parent entity, editing the task’s Assignment Condition property causes the SemQL editor to crash. Consequently, an Invalid SemQLAttribute qualified name exception occurs, and no SemQL attributes are displayed in the attribute list.

MDM-15597: Third-party library upgrade: Azure Identity.

MDM-15598: Third-party library upgrade: Azure Identity.

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-15029: Security enhancement: image library file upload.

MDM-15156: Under specific conditions when configuring a stepper in the Application Builder, a discrepancy arises in the display of the DETECT_DUPS validation, with it appearing multiple times for one entity but not at all for other entities in the Validations table.

MDM-15298: When navigating the Explain Record view within an MDM application, the Value tab exclusively displays the golden record column, while the master record columns remain empty, showing no labels or values.

MDM-15310: The Semarchy Email enricher does not return the expected cleansed domain names in both online and offline modes, specifically when the domain extension is missing from the input email address.

MDM-15373: Forms configured to open within an MDM application that uses a color theming scheme including css: green as a secondary color appear blank upon opening in the application interface.

MDM-15401: Despite configuring a form field as read-only in a legacy workflow, records remain editable in the corresponding stepper, including binary fields marked as read-only.

MDM-15403: When attempting to save a space character as a thousand separator within SAML identity providers, the save functionality remains inactive, preventing the application of the space as intended.

MDM-15420: When using a SemQL expression that incorporates the ClassName attribute for ID generation and trying to persist records via a POST request in a REST API environment, two distinct errors arise: omitting the ClassName attribute from the JSON payload prompts an error message indicating java.lang.IllegalArgumentException: Some attributes required to compute the id are missing from inputAttributes: [ClassName]; conversely, including the ClassName attribute in the JSON payload triggers a different error, specifically com.semarchy.mdm.runtime.data.InvalidDataAccessAPIUsageException: Attribute Adde.ClassName not allowed in persist calls.

MDM-15448: When creating a child record through the REST API, if the parent is an instance of a fuzzy-matched entity, the FP_ and FS_ values provided in the source record are overwritten with values from another existing parent master record, resulting in a loss of information and incorrect associations between the child and parent records.

MDM-15454: Upon importing or publishing master records for a fuzzy-matched child entity through a workflow designed to handle erroneous golden records of this entity, the workflow encounters a failure while attempting to update multiple columns within the child entity table referencing the parent. This failure results in a multiple assignments to same column "parent" error message in the PDE log.

MDM-15487: When trying to assign a legacy workflow task, the list of candidate assignees is not sorted alphabetically in the transition dialogs, making it difficult to efficiently locate users and assign tasks.

MDM-15489: Within an MDM application, binary fields remain editable in read-only forms, allowing modifications that persist inconsistently based on entity type and previous overrides.

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-15189: To facilitate immediate comprehension of asset relationships in Purview, the display name for physical tables published by the Purview connector now reflects the name of the respective table instead of the table type (e.g., se_person instead of Source Errors).

MDM-15421: To prevent notifications from being indefinitely delayed due to connectivity issues with remote servers, a default timeout duration of 30 seconds is applied to SMTP and SMTPS notification servers using mail.smtp.* and mail.smtps.* timeout properties, respectively, when platform administrators do not specify any value.

MDM-14820: Security enhancement: authentication mechanism.

MDM-14975: While configuring identity management in the Configuration module, removing the value from the Synchronize from column of an LDAP attribute results in a failed validation test and throws an unexpected exception: java.lang.IllegalStateException: java.lang.IllegalArgumentException: Attribute ID must not be empty.

MDM-15156: Under specific conditions when configuring a stepper in the Application Builder, a discrepancy arises in the display of the DETECT_DUPS validation, with it appearing multiple times for one entity but not at all for other entities in the Validations table.

MDM-15313: Upon initializing a data-driven workflow, delays are encountered in reaching the first user task step due to a large number of potential candidates, despite configuring the initiator role as 'none' and enabling any user to claim the first task.

MDM-15315: While configuring a SAML identity provider, trying to access the service provider metadata URL results in an internal server error and writes a java.lang.IllegalStateException error to the PDE log. This prevents the download of the SAML service provider metadata in XML format.

MDM-15320: Third-party component upgrade: Apache CXF.

MDM-15326: In the table view of a duplicate manager, columns defined with a SemQL expression containing golden record attributes show empty values for master records. This missing data prevents the calculation and display of the edit distance between master and golden records.

MDM-15337: The Save button on the Identity Management page remains disabled even after modifications have been made to the configuration settings.

MDM-15347: Third-party component upgrade: Netty.

MDM-15354: Third-party component upgrade: Markdown-it.

MDM-15358: Attempting to delete master records from the Master Records tab within a business view fails with an Insufficient privileges error message, resulting in the deletion process being aborted.

MDM-15376: When multiple transitions are available from a user task in a workflow, the Assignee drop-down menu for selecting the next task’s assignee in the transition dialog consistently and exclusively shows the candidate list for the task targeted by the first transition configured in the current user task’s settings.

MDM-15377: Third-party library upgrade: Bouncy Castle.

MDM-15400: Upon completing a user task in a workflow where the next task is automatically assigned to the user’s team, the completed user task stepper does not redirect to My Tasks as expected.

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-14604: An unexpected backslash character (\) is observed at the end of the line just before a bullet-point list in bold formatting when inputting content into a long text field using a Markdown component.

MDM-14714: Attempting to apply row-level filter privileges to an entity with a SemQL condition involving an attribute of a parent entity and the IN operator fails with a java.lang.IllegalArgumentException error in the PDE log.

MDM-14800: X-Forwarded-For headers are available despite the allowXForwardedHeaders system property being set to false, potentially causing undesired header handling. For enhanced control and security, the default (false) behavior of the allowXForwardedHeaders property now removes X-Forwarded headers from requests.

MDM-14805: In the Configuration module, the Identity Provider Test side sheet fails to display logs when testing a SAML connection, regardless of whether the connection is made over HTTP or HTTPS.

MDM-14824: Security enhancement: REST API documentation.

MDM-15064: Applying row-level filter privileges to an entity, specifically when the condition references a child entity through a SemQL lookup expression, raises a java.lang.IllegalArgumentException error in the PDE log and makes the application inaccessible to users with restricted privileges.

MDM-15159: The execution engine’s performance has been optimized by reducing the number of database queries required to identify running loads in the continuous load process. For enhanced performance, platform administrators should create a custom database index on MTA_INTEG_LOAD(LOADID) to optimize queries that involve filtering or sorting by load ID.

MDM-15196: Third-party library upgrade: Apache Commons Compress.

MDM-15204: Third-party component upgrade: PostgreSQL JDBC driver.

MDM-15214: Third-party library upgrade: Apache Commons Compress.

MDM-15226: Attempting to create a replica datasource through the user interface when the original datasource was initially created using the REST API fails with the following JavaScript error message: Error: Minified React error #31.

MDM-15302: Within the Workflow Builder, the attribute list in the SemQL editor’s Assignment Condition view remains empty when the related model includes entities that inherit from other entities.

MDM-15308: When attempting to access a workflow user task from the My Tasks interface, a generic unexpected error occurs if the associated collection configured to display in My Tasks references a model variable, and the following error message is logged: com.semarchy.datahub.runtime.workflow.service.WorkflowEngineException: Missing named parameters.

MDM-15312: Security enhancement: datasource configuration.

MDM-15314: Security enhancement: login page content.

MDM-15317: Third-party component upgrade: Apache Tomcat for xDM preconfigured, Docker image, and cloud images (QuickStart VM and Azure Solution Template).

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-14723: Semarchy xDM supports PostgreSQL 15 across on-premises installations and cloud platforms, including Azure Database for PostgreSQL - Flexible Server, Amazon RDS for PostgreSQL, Cloud SQL for PostgreSQL, and Amazon Aurora PostgreSQL.

MDM-15092: Platform administrators can deactivate the default security enforcement that temporarily blocks users after a certain number of unsuccessful login attempts by setting the xdm.idm.maxloginattempts.enable startup property to false.

MDM-14970: Despite setting a display text for hyperlinks in form fields, the full URL is displayed instead of the specified text on browsing forms.

MDM-14987: Custom translations are not supported for the My Task interface.

MDM-14988: Special characters are not encoded correctly when incorporated through a SemQL custom parameter in an email subject line configured within the properties of the Send Email workflow automation.

MDM-15091: When attempting to edit the value of a hyperlink field in an authoring form and intervene in the middle of a URL, the cursor unexpectedly jumps to the end of the edit box upon typing.

MDM-15105: When validations are disabled for a reference relationship and a record contains a broken reference, the corresponding form field’s Value tab displays <null> instead of the expected value indicating the broken reference.

MDM-15151: Attempting to override a reference on a record that originates from a fuzzy- or ID-matched entity within a workflow’s user task causes the subsequent Submit Data automation step to fail with a PreparedStatementCallback; bad SQL grammar error.

MDM-15152: When testing REST APIs set up in Semarchy xDM REST clients to receive data from an external API, an unexpected error occurs due to misconfigurations in the JSONPath library.

MDM-15167: When creating a dashboard, despite successful completion, an unexpected error page appears within the Dashboard Builder with no corresponding entry in the PDE log.

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-14989: When attempting to open a dashboard application from the welcome page, a blank screen is displayed in the browser.

MDM-14997: Attempting to open the Configuration module results in an unexpected error in the browser, along with a 404 not found message when opening the Dashboard Builder or Workflow Builder.

MDM-15025: Attempting to view profiles associated with datasources in the Discovery module or to open a profiling application from the welcome page results in an unexpected application error and a 404 not found message.

MDM-15066: When creating a new user and enabling the Ask for a password change at the next login setting, subsequent user attempts to log in result in an application error with a 404 not found message.

MDM-7254: With PostgreSQL, the application server hosting the Semarchy 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 Semarchy 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-9782: When browsing records with errors, the Error Details tab in a business view now displays meaningful and detailed error messages for each listed error—​in addition to the constraint type and constraint name for built-in errors—​and provides the ability to switch between list and table views for comprehensive error details.

MDM-9988: SEM_CAST_NUMERIC SemQL function available on SQL Server for converting numeric strings to integers.

MDM-9993: When querying error views using the REST API, the API response now includes a ConstraintErrorMessage attribute that contains either the customized or default error message associated with the error records.

MDM-12576: SEM_CAST_INTEGER SemQL function available on PostgreSQL for converting numeric types to integers.

MDM-13980: The REST API documentation explicitly specifies golden record IDs as 64-bit integers instead of numbers.

MDM-13998: In the workflow administration view, a new Workflow Instance Details panel presents general information on a selected workflow instance (including its start, end, and due date, progress status, initiator’s name, and more) to complement the existing step details panel.

MDM-14173: When executing invalid SQL queries in the Dashboard Builder, the query editor prompts detailed error messages to help pinpoint and rectify syntax mistakes or logical errors.

MDM-14217: The REST API documentation provides more specific summaries and descriptions for each endpoint, incorporating details such as entity name, for improved clarity in external API management tools.

MDM-14303: In the xDM official Docker image, the default Log4j configuration has been updated with the addition of the Console appender to the root logger, allowing platform administrators to retrieve logs effectively through the command line in Kubernetes environments.

MDM-14536: The REST API documentation has been updated to better handle large models, now organizing data location sections by entity. This improvement introduces a submenu for entity selection with enhanced search functionality and facilitates YAML downloads for specific entities.

MDM-14585: The toast message that is displayed after closing a duplicate manager now acknowledges situations where no changes have been made.

MDM-14611: The contrast ratio in read-only fields has been heightened, enhancing text visibility across all authoring fields in the user interface of xDM applications.

MDM-14729: The date picker in workflow startup and transition dialogs now restricts users from choosing a date prior to the current date when defining the due date.

MDM-14738: Support added for the Microsoft Build of OpenJDK.

MDM-14822: An allowlist mechanism now restricts the classes permitted in Groovy conditions or scripts to enhance security within Semarchy xDM. To modify the default allowlist without compromising security, platform administrators are invited to contact our Technical Support team.

MDM-12278: During a Review and Confirm Matches operation using a duplicate manager, the table view presenting details of the master records suggestions for the golden record is not scrollable—​both horizontally and vertically—​unless the scrollbars are clicked first.

MDM-13911: Missing translation keys result in java.util.MissingResourceException errors in the PDE log when exporting model documentation.

MDM-14269: Within the Application Builder, selecting the Directed Graph mode and clicking Auto Layout in the diagram of a model that contains a self-referencing inherited entity throws a java.lang.RuntimeException: Cycle detected in graph error.

MDM-14297: Processing entities inheriting from the same parent entity in separate queues may cause the certification jobs to produce discrepancies or errors in the data, as jobs performed on one child entity can incorrectly update the batch IDs of another child entity’s records and disrupt job completion.

MDM-14338: Configuring the Authoring Mode property of a form field using a SemQL expression while the Visible property is unselected causes a display error on authoring forms.

MDM-14348: In a workflow startup or transition dialog, users can input workflow instance descriptions without length limits despite the 128-character database restriction. This results in a value too long for type character varying(128) error after closing the dialog.

MDM-14386: Values copied from dashboard charts and from the Users and Roles tables in Configuration using the Control+C (or Command+C on macOS) shortcut are not available in the clipboard for pasting.

MDM-14388: In the Application Builder, configuring the value of a new form field with a primary-key or list-of-values attribute returns a non-blocking error with the following message: java.lang.NullPointerException.

MDM-14443: When using the responsePayloadRecordsExpressions parameter in a model’s REST API, the expected name for the defined expression is not reflected in the response payload; instead, the calculation expression itself is used as the attribute name.

MDM-14613: After customizing the header border color in an xDM application, the default color theme reverts upon refreshing the application.

MDM-14614: An ix_integ_load_loadid native index has been added to the loadid column in the MTA_INTEG_LOAD repository table to alleviate contention and prevent deadlocks in SQL Server.

MDM-14623: Security enhancement: authentication mechanism.

MDM-14625: Security enhancement: login process.

MDM-14626: Security enhancement: error page content.

MDM-14627: Security enhancement: logout page URL.

MDM-14629: Security enhancement: configuration module.

MDM-14630: Security enhancement: Docker Compose sample file.

MDM-14641: When setting a date and time in an authoring form using a date-and-time picker, the value displayed in the field does not reflect the current user’s timezone settings.

MDM-14642: Using invalid decimal values such as ,,, or . in an authoring form field does not trigger an error message, and results in the attribute value being processed as null.

MDM-14643: When using a SemQL condition to configure the Visible property of a section within a horizontal form container, the label of the attributes included in the browsing form section is not displayed as defined by the Position form field property.

MDM-14649: When exporting records, the Attribute Name and Label option can be selected in the advanced formatting options so that attribute names and labels are concatenated in the column headers of the exported file.

MDM-14679: When generating application components and opting for the default display card instead of creating a new one, an extra display card is systematically generated.

MDM-14685: Workflow user tasks based on entities having a UUID primary key cause the My Tasks screen to turn gray and unresponsive.

MDM-14686: External application links configured in object form fields cannot be previewed in xDM’s applications and fail to display with the following error message: Access to fetch at '<target URL>' from origin '<origin URL>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

MDM-14708: Users who have been assigned a workflow administrator role cannot access the workflow administration view in My Tasks unless they have been granted full access to the model.

MDM-14717: Typo in a label in the French localized version.

MDM-14719: Third-party library upgrade: Apache Commons Compress.

MDM-14734: Multi-step steppers do not hinder users from entering pre-existing primary keys while creating new records, resulting in the potential overwrite of existing golden records. This behavior exclusively affects golden records created after opening such steppers.

MDM-14754: Embedded Javascript content—​such as Google Maps—​is not displayed in an object form field when initially opening a browsing form, and appears after navigating to another tab and returning.

MDM-14756: In the Datasources view of xDM Configuration, the chips in the Datasource Usages column are not horizontally aligned with the content of the adjacent columns.

MDM-14757: In the Workflow Builder, the value of a drop-down menu cannot be reset to None after a different value has been selected.

MDM-14776: When nullifying child references to a record from a self-referencing entity that is soft-deleted in a load, the certification process may revive the record previously flagged for deletion. This behavior occurs regardless of the child records' level in the record hierarchy. To fix this issue, the model must be redeployed after applying this patch.

MDM-14791: Resizing columns in the My Tasks view causes the application’s web page to become unresponsive.

MDM-14793: Third-party library upgrade: Azure Identity.

MDM-14794: Third-party component upgrade: Apache Tomcat (xDM preconfigured).

MDM-14823: Security enhancement: notification server.

MDM-14834: Workflow user tasks that have been configured to display task items from a collection containing a binary attribute column cause the My Tasks view to throw an exception without showing the list of task items.

MDM-14870: Third-party library upgrade: io.projectreactor.netty.

MDM-14898: File uploads in the Application Builder and in the Configuration module fail in AWS environments, specifically with Semarchy xDM versions containing the MDM-14622 fix.

MDM-14907: When using a lookup SemQL expression in the Condition on Selection property of a workflow start event, triggering it prompts an unexpected error message and writes an error to the PDE log (com.semarchy.datahub.runtime.workflow.service.WorkflowEngineException: This attribute builder should not be called), disrupting workflow execution.

MDM-14908: Third-party library upgrade: io.projectreactor.netty.

MDM-14909: Third-party module upgrade: Apache Tomcat (xDM preconfigured).