Semarchy xDM 2023.1 Release Notes

This document provides the latest information about this Semarchy xDM version 2023.1, including new features and bug fixes.

Support Information

Semarchy xDM version 2023.1 is a long-term support (LTS) release.

LTS product versions are released annually, and include all changes introduced since the last LTS release. They are maintained and supported for an extended period with patches and fixes.

Alternatively, mainstream support (MS) versions offer the latest improvements and features, and are released more frequently.

For more details about our releases and support policies, see our Support and maintenance terms.

Feature Highlights

Version Naming

Semarchy xDM’s versions will now use the <year>.<quarter>.<patch> pattern. The current version will be the first to use this pattern and will be called 2023.1.0.

Data-Driven Workflows

Semarchy xDM version 2023.1 comes with a major enhancement to augment user collaboration for effective data management through data-driven workflows.

Workflow Builder

In the new graphical Workflow Builder module, designers can create rich data-driven workflows that allow divergent paths depending on record data, user data, or workflow metadata.

The building blocks for workflows are steps, linked by transitions to move the workflow from one step to the next. Workflows are initiated through a start event, which defines the overall parameters and metadata of the workflow. Workflows also support automations, such as Submit to publish record data into the hub.

User tasks allow users to view or modify data records through steppers. Designers can now configure the stepper’s action bar with more options and controls for both moving through the stepper as well as moving through the workflow itself.

Workflows are triggered using actions defined in data applications. These actions can be added to the navigation drawer, to folders, or to the actions menu of an entity. The workflow startup experience, including available or mandatory fields, can be configured at design time.

Simplifying and streamlining the building process enables true collaboration between architects, designers, and even business users in the design of workflows. The no-code approach to designing and building elaborate workflows leads to faster turnaround and implementation, with a more transparent understanding of the workflows across the organization.

Data-Driven with SemQL

There are a number of functionalities in workflows that can be carried out dynamically. Certain steps now support data-driven properties with a built-in SemQL editor, through which designers access workflow data and metadata, functions, and variables.

For example, routers allow designers to define data-driven rules using SemQL to control workflow behavior based on data.

SemQL may also be used to automatically assign tasks to a user or team.

Finally, SemQL is used to define the user associated with submitting records to the hub: the workflow initiator, the last person to have approved the record, or a data steward, for example.

Data-driven workflows are a powerful tool for designers to adapt processes to the intricacies of the business-directed solution they are providing and the data necessary for that solution. Further efficiency is also achieved by ensuring that the right information is available to the right people to accomplish a given task at the right time.

Parallel Blocks

Parallel blocks run simultaneous branches within the workflow, which may contain multiple steps, including user tasks and routers. With this capability, multiple teams and users can collaborate and work simultaneously on different parts of the records being modified in a workflow.

Parallel blocks allow workflows to meet any process optimization needs, and to respond dynamically to different or evolving business requirements across the organization, particularly when diverse business units are responsible for distinct aspects of data management.

My Tasks

In the navigation drawer, the Inbox has been replaced with My Tasks, providing an enriched view of all the user’s tasks and workflows in a single place. Users are able to quickly access and understand all their tasks and workflows with a single view that includes the data and metadata (such as status, current step, and assignees) attached to these tasks. Finally, users can also review past workflows that they initiated.

The workflow side panel provides users with a detailed view of a given workflow, whether in progress or completed. The history tab shows the user details of the selected workflow, allowing them to drill down into parallel blocks, see who has carried out previous steps, if they have made any comments or provided any attachments at each step.

My Tasks provides data stewards and business users with a bird’s-eye view of the workflows they are involved in, contributing to their day-to-day efficiency.

Notifications

When a task is to be carried out in a workflow, email notifications can be configured and sent automatically to the user or team to which the task is assigned. These notifications are dynamic in that they may contain record data and workflow details.

Automated notifications alert users when action needs to be taken, while their rich content provides details regarding the task. This combination of automation and informativity augments productivity.

Authoring and User Experience

Read-Only and Browsing Mode for Form Fields

A new Authoring Mode property on form fields defines whether fields should display using their editable, read-only, or browsing variant. This property replaces the Read-Only property. In addition, a Form Fields Mode property on form steps within steppers enables forcing all fields in a step to the read-only or browsing variant.

Using these properties, designers have better control over the appearance of fields, and can quickly design display-friendly review steps.

Keyboard Navigation

Keyboard shortcuts in Semarchy xDM applications increases accessibility and efficiency in performing actions and navigating in user views.

Data Notifications

Data notifications benefit from several enhancements:

  • Configuration now supports filtering the propagated changes using timestamps in addition to batch IDs.

  • Configuration capabilities are enriched with new parameters to define a custom Connection Factory for JMS targets or Kafka key for Kafka targets.

Setup and Administration

Record-Type-Specific Retention Policy

Record-type-specific retention allows designers to control how long the different types of lineage and historical data (source data, source errors, history, or deletions, for example) are retained in the hub, globally or per entity.

Monitoring Execution Engine

New REST API endpoints (/appbuilder/execution-engine) are available to monitor, start and stop the execution engine and batch poller.

Other Noticeable Changes

Other noticeable changes include:

  • Configure the list of identity providers available per node in an Semarchy cluster using startup parameters.

  • A download link is automatically created in browsing forms for binary attributes' content that cannot be displayed by the browser.

  • Support for Snowflake as datasources for Dashboards

Change Log

Version 2023.1.9

Known Issues

  • 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-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 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-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.

Bug Fixes

  • MDM-14949: Basic authentication to the REST API returns a 500 error in the response and raises the following error in the PDE log: a java.lang.NullPointerException: Cannot invoke "com.semarchy.platform.accessmgmt.adapters.idm.IdmDetails.getIpAddress()" because the return value of "org.springframework.security.core.Authentication.getDetails()" is null.

Version 2023.1.8

Known Issues

  • 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-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 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-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.

Breaking Changes

  • 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.

Bug Fixes

  • 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-14623: Security enhancement: authentication mechanism.

  • MDM-14627: Security enhancement: logout page URL.

  • MDM-14629: Security enhancement: configuration module.

  • MDM-14764: After deploying a model, contextual menus do not open in the Application Builder until the browser is refreshed.

  • MDM-14774: In browsing forms, hyperlink fields configured to open in the same window open linked content in a new window or tab.

  • MDM-14823: Security enhancement: notification server.

  • 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).

Version 2023.1.7

Known Issues

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

New Features

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

Bug Fixes

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

  • 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.

Version 2023.1.6

Known Issues

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

Noticeable Changes

  • MDM-14428: PostgreSQL version 11 has reached end of life and is no longer supported.

In line with Azure’s announcement of extended support for PostgreSQL 11 servers, Semarchy xDM will maintain its support for Azure Database for PostgreSQL 11 in Single Server until November 9, 2024.

New Features

  • MDM-14684: 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.

Bug Fixes

  • 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-14524: Entering a number in an integer or long-integer field returns a format validation error when no thousand separator is set in the user profile.

  • 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-14622: File upload security enhancement.

  • MDM-14626: Security enhancement: error page content.

  • MDM-14630: Docker image security enhancement: Docker Compose sample file.

  • 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-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-14680: Third-party component upgrade: Apache Tomcat (xDM Preconfigured).

Version 2023.1.5

Known Issues

  • 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 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-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-12996: Login and SSO buttons only work when double-clicked on iOS phones and tablets.

  • MDM-13934: The Component Type drop-down list in the form editor of the Application Builder contains an unknown semDisplayCard_Label value that raises an Unhandled event loop exception when selected.

  • MDM-13937: Selecting one workflow definition using the table view in the Workflow Builder selects all instances.

Bug Fixes

  • 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 max. attachment file size in MB instead of KB.

  • 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-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-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.

Version 2023.1.4

Known Issues

  • 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 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-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-12996: Login and SSO buttons only work when double-clicked on iOS phones and tablets.

  • MDM-13934: The Component Type drop-down list in the form editor of the Application Builder contains an unknown semDisplayCard_Label value that raises an Unhandled event loop exception when selected.

  • MDM-13937: Selecting one workflow definition using the table view in the Workflow Builder selects all instances.

New Features

  • 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.

Bug Fixes

  • MDM-13876: HTTP connections are not closed by REST data notifications.

  • MDM-14164: File upload security enhancement. The maximum number of files that can be uploaded at once in Configuration and in the Application Builder is now set to 100 files. A new -Dcom.semarchy.mdm.maxImportFileCount system property allows customizing this value.

  • 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. See MDM-6474 (New Features).

  • MDM-14407: Third-party module upgrade: Apache Tomcat for xDM Preconfigured.

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

  • 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-14399: Attribute values of type Date set in a workflow user task are not persisted after triggering a transition requiring stepper completion.

  • MDM-14404: The certification endpoint raises an Unexpected Error when using an enricher with a filter on an FID attribute.

  • MDM-14420: Duplicate email notifications are sent on workflow user task assignment.

  • MDM-14470: REST client authentication combining basic authentication and a custom header fails with a 401 HTTP response status code.

Version 2023.1.3

Known Issues

  • 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 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-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-12996: Login and SSO buttons only work when double-clicked on iOS phones and tablets.

  • MDM-13934: The Component Type drop-down list in the form editor of the Application Builder contains an unknown semDisplayCard_Label value that raises an Unhandled event loop exception when selected.

  • MDM-13937: Selecting one workflow definition using the table view in the Workflow Builder selects all instances.

Breaking Changes

  • MDM-14236: To increase security, the X-Forwarded-For,Forwarded, and X-Real-IP HTTP headers are now ignored by default. A new allowXForwardedHeaders system property is available to process these headers, which should be activated when the Semarchy instance is only accessible through a reverse proxy.

Bug Fixes

  • MDM-12395: Leading and trailing spaces are removed from attribute values in browsing forms and collections.

  • MDM-14114: Reference fields do not show the selected record after selection when using a reference picker.

  • MDM-14209: The Always Authored in the MDM Override Strategy defined for an attribute does not allow editing its value on authoring forms.

  • MDM-14235: Form fields in sections with vertical layout use the entire vertical space available instead of being top-aligned.

  • MDM-14236: API keys security enhancement.

  • MDM-14268: Default user settings defined in the configuration of the internal identity provider are not taken into account when creating a new user.

  • MDM-14361: Starting a workflow instance from the browsing form of a record having a UUID primary key fails with an unexpected server error.

Version 2023.1.2

Known Issues

  • 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 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-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-12996: Login and SSO buttons only work when double-clicked on iOS phones and tablets.

  • MDM-13934: The Component Type drop-down list in the form editor of the Application Builder contains an unknown semDisplayCard_Label value that raises an Unhandled event loop exception when selected.

  • MDM-13937: Selecting one workflow definition using the table view in the Workflow Builder selects all instances.

Bug Fixes

  • MDM-13946: Duplicate manager performance improvement.

  • MDM-14151: Clicking a row in My Tasks, My Workflows, or the Administration UI unexpectedly refreshes the table and scrolls it to the top of the page.

  • MDM-14205: Column Values histograms in xDM Discovery show duplicate value counts.

  • MDM-14206: Authoring fields do not reflect model privileges grants in the context of workflow user tasks.

  • MDM-14212: Starting a workflow instance from a record having a UUID primary key fails with an unexpected server error.

  • MDM-14221: Duplicate manager performance optimization.

  • MDM-14240: Model documentation export fails when the Semarchy instance runs with JDK 17.

  • MDM-14245: Third-party module upgrade: Apache Tomcat (xDM Preconfigured).

Version 2023.1.1

Known Issues

  • 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 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-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-12996: Login and SSO buttons only work when double-clicked on iOS phones and tablets.

  • MDM-13934: The Component Type drop-down list in the form editor of the Application Builder contains an unknown semDisplayCard_Label value that raises an Unhandled event loop exception when selected.

  • MDM-13937: Selecting one workflow definition using the table view in the Workflow Builder selects all instances.

  • MDM-14240: Model documentation export fails when the Semarchy instance runs with JDK 17.

New Features

  • MDM-13972: Semarchy xDM is now certified with Java 17.

  • MDM-14020: Semarchy xDM is now certified with Eclipse Temurin Open JDK.

Bug Fixes

  • MDM-13355: A dashboard query using the PATINDEX function fails on SQL Server with an Unable to retrieve data from the server error.

  • MDM-13892: Some cells are not correctly aligned in data tables.

  • MDM-13901: In the Dashboard Builder, a Missing mandatory value in databaseType error is issued when validating a newly created datasource.

  • MDM-13926: With Safari, the Primary Text of entity Display Cards is not visible.

  • MDM-13950: ID form fields set with the auto or force-readonly authoring mode display an empty value on authoring forms when the related entity attribute is a UUID.

  • MDM-13972: Semarchy xDM version 2023.1.0 fails to start with Java 17 JDK.

  • MDM-14022: Duplicates manager performance enhancement.

  • MDM-14038: After an upgrade to 2023.1.0, the SEMARCHY_REPOSITORY_READONLY datasource is not available as a Dashboard datasource.

  • MDM-14044: After an upgrade to 2023.1.0, the upgraded SemQL in the Authoring Mode form field property is incorrect and raises an ORA-00932 error in Oracle.

  • MDM-14054: Object form fields fail to display content from a URL when browsing.

  • MDM-14070: A form section configured with a horizontal layout incorrectly uses a vertical layout.

  • MDM-14071: The Object form field displays the raw content when configured with a SemQL visibility condition.

  • MDM-14076: Reference fields defined with a non-writable expression are not displayed in authoring forms and prevent other fields in the same container from being displayed.

  • MDM-14093: Object form fields fail to display content from a URL when authoring.

  • MDM-14096: In Dashboard applications, the Cancel button of the Export Records dialog is not localized.

  • MDM-14108: The priority set while performing a transition in Data-Driven Workflows is not saved on the workflow instance.

  • MDM-14116: A newly created Dashboard Query raises an unexpected error when validated under certain conditions.

  • MDM-14117: Unexpected margins cause the content of collection columns to be truncated.

  • MDM-14124: The Workflow Builder link incorrectly appears on the Welcome Page for users with no sufficient privileges.

  • MDM-14125: Third-party library upgrade: Kafka Client.

  • MDM-14127: Third-party library upgrade: Commons File Upload.

  • MDM-14138: When a form is opened in a stepper, a nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'order' is raised with SQL Server under certain conditions.

  • MDM-14146: Enabling the Tomcat security manager causes server startup and integration jobs to raise a java.security.AccessControlException: access denied error.

  • MDM-14163: Master records cannot be moved to an existing golden record in Merge or Split duplicate managers using the graph view.

  • MDM-14171: Email notifications are not sent by Data-Driven workflows if the entity’s display card has no secondary text.

  • MDM-14204: Email notifications are not sent by Data-Driven Workflows if the primary or secondary text of the entity’s display card contains user-dependent variables.

  • MDM-14210: Third-party library upgrade: net.minidev and nimbus-jose-jwt.

Version 2023.1.0

Breaking Changes

  • MDM-6475: Following the replacement of the Read-Only form field property with Authoring Mode, fields containing computed expressions (SemQL) will display as Read-Only authoring fields when Authoring Mode is set to auto. Such fields were previously displayed as browsing fields. To display computed fields as browsing fields on authoring forms, designers should set their Authoring Mode to force-browsing in the Application Builder after migrating this version.

  • MDM-13565: Support for Java 8 has been discontinued. Only Java 11 is supported.

Known Issues

  • 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 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-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-12996: Login and SSO buttons only work when double-clicked on iOS phones and tablets.

  • MDM-13901: Datasource validation in the Dashboard Builder returns an error for wrongly missing Database Type property after creation.

  • MDM-13934: The Component Type drop-down list in the form editor of the Application Builder contains an unknown semDisplayCard_Label value that raises an Unhandled event loop exception when selected.

  • MDM-13937: Selecting one workflow definition using the table view in the Workflow Builder selects all instances.

New Features

  • MDM-6475: A new Authoring Mode property on form fields allows designers to define whether fields should use their browsing or read-only variant, or if their mode should be determined automatically depending on the attribute’s type and content. Similarly, a new Form Fields Mode property on stepper steps allows designers to force all fields for a given step to use their browsing or read-only variant.

  • MDM-8148: Data retention policies can be configured at a finer level for source data, source errors, history, and deletions. This is possible for the default retention policy as well as for individual policies for entities.

  • MDM-10690: A new Address.City attribute is now available in the OpenStreetMap enricher’s outputs.

  • MDM-11013: Object fields on browsing forms now show a download link when their content cannot be previewed instead of triggering an automated download.

  • MDM-11111: Object and Hyperlink fields on browsing forms now support Long Text attributes and data URLs.

  • MDM-11122: A new Quotation Character parameter in the import wizard options allows end-users to specify the quotation character used in the imported file.

  • MDM-11458: Reference fields now show More values available - type to filter at the bottom of the drop-down list when more than 50 records are available.

  • MDM-11469: Invalid datasources are now visible and available for selection in Discovery. An error message is displayed when an invalid datasource is selected.

  • MDM-11570: The app-builder/data-locations/<data-location-name>/ REST API endpoint now restarts the installation job in the case where the data location is in INSTALL_JOB_FAILED status.

  • MDM-11716: A new Time (HH:mm:ss) column in the job logs export shows task durations in hours/minutes/seconds.

  • MDM-12140: New NOTIFICATION_TRIGGER_TIMESTAMP, HIGH_BATCH_TIMESTAMP, and LOW_BATCH_TIMESTAMP built-in variables are available for data notifications to filter data depending on the notification firing timestamp and/or batch executions timestamps.

  • MDM-12170: A new Connection Factory property allows configuring a custom connection factory for JMS data notification targets.

  • MDM-12256: The app-builder/data-locations/<data-location-name>/set-status REST API endpoint now returns an HTTP 409 response with a specific message when the data location is in a status that is not compliant with the requested status change.

  • MDM-12310: Oracle 21c is now supported for Semarchy xDM repository and data locations.

  • MDM-12352: The page informing users about HTTP 500 errors now shows a log reference that can be retrieved in logs.

  • MDM-12411: The REST Request URL property for REST data notifications can now be more than 128 characters long.

  • MDM-12436: Snowflake is now supported for creating datasources for dashboards.

  • MDM-12546: New REST API endpoints allow monitoring, stopping, and starting the batch execution engine.

  • MDM-12271: Different groups of identity providers (authentication methods) may be enabled per Semarchy xDM node. The xdm.idp.availableidps property in the startup configuration can be used to configure the list of identity providers for a given node.

  • MDM-13373: Third-party library upgrade: kafka-clients.

  • MDM-13455: The official xDM Docker image now runs Tomcat with a semarchy_user non-root user.

  • MDM-13532: AWS Aurora PostgreSQL versions 14.x are now supported for Semarchy xDM repository and data locations.

  • MDM-13857: A new Kafka Message Key property allows defining a custom value for the Kafka key used in data notifications sent to a Kafka target.

Bug Fixes

  • MDM-11129: Duplicate Management entity actions have no default label.

  • MDM-11255: Opening the filter panel of a child business entity and navigating back to the parent business entity using the breadcrumb prevents opening any record in the parent business view until the page is refreshed.

  • MDM-11664: Submitting a record that uses a LoV with no values causes the integration batch to fail.

  • MDM-11935: The Add Datasource dialog does not contain a Close button if no Discovery-compliant datasource is found.

  • MDM-11941: Sessions do not timeout when badges are enabled on application actions.

  • MDM-11974: Pressing any key opens the drop-down list for Reference, Chips, and Menu form fields, which prevents using the shift and tab keys for backward navigation.

  • MDM-12120: The $EntityNames job notification property is empty for deletions.

  • MDM-12148: The web.xml file provided with the xDM Preconfigured version prevents using à, é, or ç characters in passwords.

  • MDM-12163: SemQL validation on ID field keeps rejecting after modification of the erroneous value that was initially provided.

  • MDM-12198: Search-field drop-down list unexpectedly shows on the results page when the search form is submitted using the keyboard.

  • MDM-12245: Merge or Split action on SQLServer fails with a SQLException if a Golden Record has over 500 master records.

  • MDM-12299: Keyboard navigation improvements.

  • MDM-12309: Form field documentation is not shown in the side panel for form fields with SemQL computed values.

  • MDM-12393: Zip file upload security enhancement.

  • MDM-12408: The Override and Reset Override buttons are still available for form fields set to read-only.

  • MDM-12432: Object form fields set to read-only still allow uploading a file on authoring forms.

  • MDM-12539: Field label color set to theme:accent is not applied.

  • MDM-12543: Validations for boolean fields in steppers are not triggered.

  • MDM-12549: Special characters / \ ; % in username cause user creation with the REST API to fail with a javax.ws.rs.ClientErrorException: HTTP 404 Not Found error. These characters are now authorized but /`and `\ require additional setup:

    • To allow the slash / character to be used in usernames, the encodedSolidusHandling property must be set to decode for every Connector in the server.xml file of the xDM instance.

    • To allow the backslash \ character, a new org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH must be set to true when starting xDM.

  • MDM-12564: UUID field values are shown as NaN in advanced filter drop-down lists.

  • MDM-12677: The Min. Date value set on a Date Picker field is rejected with a validation error when entered by a user on an authoring form.

  • MDM-12720: Values of long text attributes are not retrieved when entering an advanced filter criterion.

  • MDM-12821: Optimization of CPU and memory usage for model deployment on data locations containing large user-defined functions.

  • MDM-12900: The field timeline on browsing forms shows values from failed integration batches.

  • MDM-13045: Third-party library upgrade: AngularJS.

  • MDM-13075: Using environment variables in the named query attributes of a data notification makes instances of this notification fail with a com.semarchy.mdm.datahub.datanotif.DataNotificationException$QueryRecordsException error.

  • MDM-13112: In Configuration, values in the Latest Authentication Date column are sorted alphabetically instead of being sorted in chronological order.

  • MDM-13171: Relative width between containers is ignored on authoring and browsing forms when the user reduces the width of browser window.

  • MDM-13179: Application theming color defined with notation different from hexadecimal RGB (#rrggbb) prevents fields from being displayed on authoring forms.

  • MDM-13224: Match rules using the SEM_EDIT_DISTANCE_SIMILARITY function with PostgreSQL raise an org.postgresql.util.PSQLException: ERROR: division by zero error.

  • MDM-13263: Background color on Reference collection columns is displayed as gradient instead of solid color.

  • MDM-13287: Checkbox authoring fields with long helper text are not displayed and cannot be selected.

  • MDM-13343: Checkbox authoring fields do not show their full helper text in a tooltip.

  • MDM-13357: In Dashboard Builder, renaming a dashboard without actually changing its name removes it from the list of dashboards.

  • MDM-13417: Clicking the value of a Hyperlink column in a collection that contains several columns with this type always opens the content of the first Hyperlink column.

  • MDM-13459: Drop-down lists on form filters do not open after saving a filter.

  • MDM-13475: Zipped SVG images are not imported into image libraries.

  • MDM-13481: The horizontal scrollbar is not available on collections accessed with Firefox.

  • MDM-13495: On the Users collection in Configuration, the Select All functionality ignores the filter previously set by the user.

  • MDM-13505: Third-party module upgrade for xDM Quick Start virtual machines on AWS, Azure, and GCP and Azure solution template: Apache Tomcat.

  • MDM-13518: Third-party library upgrade: d3-color.

  • MDM-13640: Starting xDM on a Mac M1 CPU using an arm64 JDK fails with an org.osgi.framework.BundleException: Could not resolve module: com.semarchy.engine.plugins.convergence.email error.

  • MDM-13643: Saving the target properties of a Kafka data notification fails with a java.lang.NoClassDefFoundError: Could not initialize class com.semarchy.mdm.datahub.datanotif.producers.KafkaMessageProducer error.

  • MDM-13669: In the datasource editor, clicking the header of the Driver Properties section after entering a property value as a secret raises an Error: Minified React error #31 error in the user interface.

  • MDM-13771: The French label of the Kafka Topic data notification property is incorrect.

  • MDM-13864: Third-party library upgrade: SnakeYAML.