Semarchy xDM 2023.4 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 and 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-matched 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 direct authoring in the user interface or by API.

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-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-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-14908: Third-party library upgrade: io.projectreactor.netty.

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

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 and 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 direct authoring in the user interface or by API.

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-14738: Support added for the Microsoft Build of OpenJDK.

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-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 form section is not displayed according to the Position form field property in the corresponding browsing form.

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

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-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-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-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 and 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 direct authoring in the user interface or by API.

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-6472: The maximum length for string entity attributes can be extended to 32,767 bytes by setting the com.semarchy.mdm.supportExtendedMaxStringSize system property in xDM. For Oracle users, the MAX_STRING_SIZE parameter must additionally be set to EXTENDED in the Oracle database settings.

MDM-6474: Row-level security is now supported when accessing data from the SE, AE, GX, GE, or MS views. At run-time, xDM automatically ignores the conditions from model privileges grant filters that use one or several unavailable attributes in the current view. A new -Dcom.semarchy.mdm.security.dataAccessAuthorizations.skipAdaptRowScopeToAvailableAttributes system property is available and must be set to true to disable this behavior and keep model privileges grant filters unmodified.

MDM-11973: When hovering over any item in the navigation drawer, a tooltip displays the item’s description, as well as its full label when the label text is ellipsed (i.e., truncated for being longer than the width of the navigation drawer).

MDM-14165: A new REST API endpoint (/app-builder/purge-deployment-history) now provides the ability to purge deployment history data.

MDM-14292: To prevent information overload in a data location, workflow metadata and workflow step data can now be included in scheduled data-purging jobs, in accordance with the retention policy applying to a specific workflow definition. The default retention policy will retain workflow metadata forever and can be configured for each workflow definition using retention type, time unit, and duration properties.

MDM-14341: In the Workflow Builder, data-driven workflows can now be configured to start from a selection of erroneous records, namely source authoring data with errors and golden data with errors.

MDM-14385: Semarchy xDM instance information and usage metrics can be downloaded and exported from the Manage license page for instances on which the automatic license synchronization has not been enabled.

MDM-14549: Data-driven workflows can now be triggered from a public REST API endpoint (/workflows/<dloc-name>/workflow-definitions/<workflow-name>/start), and can be configured to start either from a record selection or from an empty selection.

MDM-14550: Data-driven workflows can now be started from source authoring data with errors and golden data with errors through an entity action item in an Errors business view.

MDM-13941: Upon completing the first user task of a workflow, the due date specified in the workflow startup dialog is displayed minus one day in the subsequent transition dialog.

MDM-14166: Collection columns and browsing form fields show an empty value if their value expression returns data from SE, AE, GX, GE, or MS views and if a row-level filter is defined in model privileges grants for a role of the connected user.

MDM-14315: The task list in My Tasks is not refreshed correctly after selecting a workflow transition or closing a stepper.

MDM-14320: Triggering a workflow transition that is configured to revert data raises a Task not available—​This task has already been completed. non-blocking error to the user.

MDM-14355: With ID-matched entities, the absence of publisher ID for referenced records causes components such as browsing, named queries, enrichers, and validations to fetch incorrect references when several master records have the same ID with different publishers. A new -Dmdm.dataaccess.resolveIDMatchedRefsWithSamePubId system property allows bypassing this limitation by forcing the publisher ID to the same value as the child record’s. This property is set to false by default and must be set to true to enable this behavior.

MDM-14360: In My Tasks, the entity column header in a workflow user task view does not display the arrow icon to sort display cards by ascending or descending order.

MDM-14406: Basic-entity golden references to fuzzy-matched entities are temporarily reset to null in GD tables during the certification process. To fix this issue, the model must be redeployed after applying this patch.

MDM-14421: Workflow startup and transition dialogs show maximum attachment file size in MB instead of KB.

MDM-14431: Typo fixed in the tooltip that appears when you hover over the information icon next to the Maximum distinct values stored field in the Edit table properties dialog in xDM Discovery.

MDM-14436: Third-party library upgrade: Google Guava.

MDM-14453: In a Master Records view, boolean attribute values that survived in the corresponding golden record are not displayed on a blue background, as the other surviving values.

MDM-14480: SemQL Enrichers expressions containing complex attributes cause the Certify REST API to fail with an org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar error.

MDM-14481: When using the Select All action (and optionally after unselecting one or several records) while browsing a collection of records, the total number of selected records is missing in the header of the collection table. The same issue is observed when authoring an embedded collection of records.

MDM-14487: Attempting to display a model diagram in the application documentation returns a blank window.

MDM-14497: Third-party library upgrade: io.netty:netty-handler.

MDM-14512: Workflow instance fails to proceed past parallel block when two branches complete simultaneously.

MDM-14514: REST API calls raise a java.lang.IllegalStateException: Cannot create a session after the response has been committed error in the logs when the com.semarchy.xdm.rest.accesslog logger is set to DEBUG level.

MDM-14517: In a duplicate manager, the suggested final merge record is missing from the table view (replaced with a blank line in the top row) and is displayed in the graph view only.

MDM-14533: In the Workflow Builder, creating a custom parameter on an email automation step in a parallel branch returns a blank page.

MDM-14539: When multiple workflows are configured for the same entity and the start actions for these workflows are defined in distinct action sets, the resulting action menus in each concerned business view may not display the correct action label.

MDM-14565: When using an embedded collection transition to browse a business view that contains another embedded collection, the second collection appears empty on the target form.

MDM-14587: When nullifying the 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.

MDM-14594: Workflow instances running on SQL Server raise java.util.MissingResourceException: Can’t find resource for bundle java.util.PropertyResourceBundle, key Function_ATN2 and java.util.MissingResourceException: Can’t find resource for bundle java.util.PropertyResourceBundle, key Function_RADIANS errors in the PDE log.

MDM-14603: In the My Tasks or My Workflows side sheet, the display of certain user task dates does not adhere to the time zone settings configured by the user.

MDM-14622: File upload security enhancement.

MDM-14632: In the Application Builder, the tooltip of the Name field in the Create New Continuous Load wizard indicates that the field is optional, whereas it is mandatory.

MDM-14635: When setting the queryPotentialMatchesHighestScoreOnly parameter to true in a Certify One Record API request, the API returns all matches instead of just the one having the highest score as expected.

MDM-14645: In a data-driven workflow involving an ID-matched entity that references a basic entity, the execution of a Submit Data automation step fails with a PreparedStatementCallback; bad SQL grammar error after the basic-entity reference has been overridden on the ID-matched entity as part of a user task.

MDM-14671: After two user tasks have been processed in the course of a legacy workflow, the third user task is displayed as a duplicate entry in My Tasks, which prevents any actions from being taken on the task.

MDM-14677: The official xDM Docker image ships a Log4j default configuration file (log4j.semarchy.properties) instead of Log4j2 (log4j.semarchy.xml).

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

MDM-14687: When running a workflow on a specific entity for which a display card has effectively been created, exiting a user task raises a java.lang.IllegalStateException: Entity <entity_name> must have a Display Card error.