Semarchy xDM 5.2 Release Notes

Feature Highlights

Intuitive Matching

Semarchy xDM version 5.2 introduces major additions to the matching engine to align more closely with the intuitive expectations of data stewards and business users:

  • Transitive Scoring is a new algorithm to compute the score of a group of matching records. It treats the score of each match pair as a probability of similarity and combines these probabilities for all possible paths in the group. Using this algorithm, designers can achieve more accurate scores for the groups without modifying existing match rules.

  • Multi-Iteration Grouping begins by creating groups using the highest confidence match rules. It then considers whether groups can be progressively expanded using other match rules. Designers obtain better golden records, dramatically reducing the time spent in manual match and merge.

The match graphs used to explain and manage the match groups are also enhanced to further increase the productivity of the data steward teams: Match links appear with a specific color defined by the designer for each match rule and a thickness that automatically reflects the match score. Both direct and transitive (computed) match links now appear in the graphs.

Master Record Deletion

Master record deletion is designed to propagate deletions performed in source applications or to remove from the hub records of a source application. When deleting one of the master records contributing to a golden record, the values consolidated in the golden record are updated to take into account this master record deletion.

Master deletion is triggered from the SQL and REST APIs, and from the data hub applications using a Delete action. This type of action in action sets now has two additional checkboxes to make it Available for Golden Data or Available for Master Data.

Enricher Caching and REST Clients

With REST Clients, designers define in a declarative way - with no code - external APIs that Semarchy xDM can use to enrich data. In a REST client, the URL, headers and request body are parameterized with inputs. The response body is parsed to extract outputs. Designers use REST clients like regular enrichers.
REST Clients simplify enriching data in the certification process using external services and data sources. With no code, designers can leverage any REST-enabled service.

Enricher Cache is a new feature for plugin and REST enrichers to cache the enriched data. For a given set of inputs, plugin/REST enrichers tap into the cache instead of running the plugin code or calling the external REST service.
With enricher caching, designers can improve the performance of the certification process and reduce the latency and cost of data enrichment using external services.

Application Documentation

Designers can now expose documentation from within the application, to help end-users better understand how the application works, the underlying data model as well as the rules that apply to the data.

This documentation is available at multiple places in the application. For example, contextually in forms and collection views, from the user menu or from an application action. The documentation exposes interactive diagrams of the model and displays in a user-friendly and visual way all the details of the diagrams, entities, attributes, enrichers, etc.

Using the application documentation, business-users and data stewards can better understand the information stored in the hub and how it is managed.

Applications Experience

Semarchy xDM version 5.2 adds new capabilities to further improve the data management applications experience. These include:

  • Customizable and translatable Validation Messages for all data quality checks defined in the model. These messages appear in the authoring experience to better explain quality rules that apply in the context.

  • A badge counter displays the number of items to do in the user’s inbox.

  • Badge counters on business views display the number of records in the business view.

  • Data import in applications now automatically handles new or modified records for entities with generated IDs (UUID, SemQL or Sequence).

  • Compact density mode configured in the user profile now applies to collection views and duplicate management collections.

Change Log

Version 5.2.11

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

Bug Fixes

  • MDM-12011: Records disappear from duplicate managers when saved for later.

  • MDM-12052: String search patterns including a % wildcard followed by digits result in filter loss and broken pagination.

Version 5.2.10

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

Bug Fixes

  • MDM-11882: Performance enhancement for the Refine Non Singleton Groups task in integration jobs.

  • MDM-11942: Expanding a data location having a high number of loads in the Application Builder causes excessive memory usage.

  • MDM-11944: Optimization of memory consumption for the Application Builder.

  • MDM-11996: Model import causes a java.io.IOException: Read-only file system on Cloud environments.

  • MDM-12012: Platform Configuration security enhancement.

Version 5.2.9

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

Bug Fixes

  • MDM-11497: The scrollbar of drill down data tables is not accessible with a mouse click.

  • MDM-11551: An incorrect error message is displayed when the duplicate ID rule is triggered on form data change.

  • MDM-11560: Using the Integration Job parameter PARAM_CHILD_POSTPROCESSING_JOB prevents from restarting a suspended job.

  • MDM-11708: Image library security enhancements.

  • MDM-11727: Application server logs security enhancements.

  • MDM-11728: Dashboard builder security enhancements.

  • MDM-11833: Unable to deploy applications from the /tmp directory using Tomcat Manager.

Version 5.2.8

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

New Features
  • MDM-11243: The AWS and Azure Cloud images base operating system is changed to Ubuntu 20.04 using Apache Tomcat 9.0.31 and PostgreSQL 12.

Bug Fixes

  • MDM-11237: The Application Management (Read) platform privilege incorrectly allows canceling jobs in the Execution Engine editor.

  • MDM-11363: Logout does not redirect to the login page when the Semarchy xDM application is deployed on the root context.

  • MDM-11410: Model validation checks reserved names on complex attribute physical prefixes and definition attribute physical column names instead of using the generated physical column names.

  • MDM-11434: Model reverse-engineering of an MDS schema in SQL Server fails with a Duplicate Map Key Value Attribute (Type) error.

  • MDM-11457: Copying a record with a populated longtext attribute fails with the following error: ` Value for attribute xxx cannot be stored: Unexpected type for value LongText(4 char), expecting class java.lang.String, got class com.semarchy.mdm.datahub.services.query.datamgr.impl.LongText`.

  • MDM-11465: Clicking to open a record with a UUID primary key from an embedded collection is ineffective.

  • MDM-11470: Accessing an application without having the application required role is possible with a direct URL.

Version 5.2.7

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

Bug Fixes

  • MDM-10924: API Key Origin IP Addresses or ranges property does not accept a comma-separated list of IP addresses.

  • MDM-11090: Accessibility: The application pages' lang attribute is not set. The default language can not be programmatically determined by screen readers.

  • MDM-11117: The record representing the current batch is randomly missing from the DL_BATCH table during job execution.

  • MDM-11118: Application Builder fails to load with an Action Global.ImportModelEdition not found error if the repository contains a profiling datasource with a large number of tables.

  • MDM-11186: Dashboard Builder fails to load with a TypeError: Cannot read property 'dateTimeFormat' of null error if the connected username contains a '\' character.

  • MDM-11180: Transitive match scores appear in the Explain Record graph even if they are not activated.

  • MDM-11198: Business views using Search on Open do not take into account the search criteria if the search form is submitted too quickly.

  • MDM-11217: Accessibility: The user is trapped while navigating into the Hierarchy view using a keyboard.

  • MDM-11227: Model Documentation Diagrams fail to load with a 'Diagram false' error if Semarchy xDM is deployed on Tomcat root context.

Version 5.2.6

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

Bug Fixes

  • MDM-11036: Security enhancement on collection browsing.

  • MDM-11072: Stepper hangs after clicking on "Back" within a stepper containing a collection.

  • MDM-11031: Resources declared in semarchy.xml using Tomcat ResourceLink elements are not recognized as valid datasources by xDM Dashboard and xDM Discovery.

  • MDM-11025: Dashboard queries executed on Apache Hive datasources fail with a java.sql.SQLException: Method not supported.

  • MDM-11006: Workflow transition notifications configured with the "Members of Next Tasks’s Role" recipient are sent to the role’s emails instead of the users' emails or raise a Cannot send notification when no recipients are defined error when no email is configured.

  • MDM-10996: The REST API documentation raises a NumberFormatException if a Named Query parameter of type Number has an empty default value.

  • MDM-10989: In a Named Query, recursive multi-record properties do not loop over records.

  • MDM-10916: In Dashboard Applications, the "Show in drilldown" query attribute property masks column headers but not values in the drilldown table.

  • MDM-10811: Excel export fails with a SqlObject cannot be cast to java.lang.String error when the collection includes a SemQL child lookup returning a Date or Timestamp value.

  • MDM-10917: In Dashboard Applications, query attributes with "Show in drilldown" disabled are not resolved in the Query Action URL.

Version 5.2.5

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

Bug Fixes

  • MDM-10716: An entity with a large number of attributes and using the Until Consolidation Change override strategy fails the "Reset override values for UntilConsoChanges rules with changed values" job task with an Internal error: An expression services limit has been reached error on SQL Server. After applying this patch, the model should be re-deployed to fix this issue. Note that on SQL Server, due to the internal limits of this database engine, such a survivorship rule should be configured to process less than 80 attributes.

  • MDM-10884: Import Fails with an incorrect Invalid SemQL Query. Error while parsing expression error when importing child records with missing parent records and checking the parent reference.

  • MDM-10910: Enabling the SecurityManager in Tomcat 9 prevents the application to start with BundleException: Could not resolve module …​ errors.

  • MDM-10913: Memory leak caused by caching in the GroovyEvaluatorService (DefaultRuntimeTemplate).

  • MDM-10946: Named Query Parameters of type Number incorrectly appear with a String datatype in the REST API documentation.

Version 5.2.4

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

New Features

  • MDM-10341: Datatypes are now indicated in the REST API Documentation for named query properties.

  • MDM-10750: AWS Quickstart VM configuration is updated to prevent issues with too many open files.

Bug Fixes

  • MDM-10645: Validations configured on a single step stepper still raise issues after resetting the fields to null.

  • MDM-10834: Email Enricher setup fails on Azure DB for PostgreSQL with a relation "ext_email_domains" already exists¬†error.

  • MDM-10837: Continuous Loads cause table locks on SD and SA tables with large data loads on SQL Server.

  • MDM-10838: CXF temporary files are not cleaned up by the internal API, causing an excessive number of open files on the application server.

  • MDM-10839: A No matching enum value for [509] error is raised during a REST API call with a "Skip record" behavior on error.

  • MDM-10865: An Unexpected Error is raised by the named-query-count REST API operation when filtering with query parameters.

  • MDM-10872: The copy of an entity within a stepper fails with Unexpected server error: Unrecognized field selection

Version 5.2.3

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

New Features

  • MDM-10461: Include IP Address, SSN & other inputs in Melissa Personator Enricher

  • MDM-10758: Melissa Personator Enricher now supports all available Melissa outputs

Bug Fixes

  • MDM-10707: Read-only fields can be edited within a workflow

  • MDM-10724: Performance enhancement for Transitive closure

  • MDM-10745: Integration job fails with NullPointerException when using GoogleMaps Enricher Cache

  • MDM-10747: The application cannot start when a global application server datasource is used as repository datasource under Wildfly

  • MDM-10757: Consulting the job execution log for a job log entry that was suspended and then resumed will raise a null pointer exception.

  • MDM-10786: During authoring, Form Fields/Columns for which user is not authorized are throwing a DataPermissionDeniedException instead of being hidden

  • MDM-10787: Performance enhancement for REST API calls using API Key

  • MDM-10792: Performance enhancement for Transitive closure

  • MDM-10814: Lookup value form field on MasterRecords throwing Invalid SemQLAttribute error

Version 5.2.2

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

Bug Fixes

  • MDM-10618: Deletions are not processed by continuous loads

  • MDM-10620: Deleting with the REST API a golden record with a UUID primary key fails with a RECORD_NOT_FOUND error status.

  • MDM-10637: Data management applications perform an excessive number of requests to the global-search-config?historySearch=false URL.

  • MDM-10639: Embedded collections configured with Allow List only do not appear in popup forms, with a TypeError: Cannot read property 'tableColumns' of undefined error message in the browser console.

  • MDM-10642: Integration jobs should analyze the statistics of the GH/MH tables when the PARAM_ANALYZE_STATS parameter is set.

  • MDM-10653: During model deployment, an error dialog appears with the "Errors found during database schema merge:" message and no error details.

  • MDM-10654: JNDI security enhancements.

  • MDM-10655: User information API security enhancements.

  • MDM-10656: REST APIs require SemarchyConnect role.

  • MDM-10660: System URL security enhancements.

  • MDM-10661: Listing of available services security enhancements.

  • MDM-10672: A pivot table breaks the chart and the dashboard when all its data is filtered out by a slicer.

  • MDM-10679: Attribute documentation markdown content no longer supports opening a URL in a new tab. This feature is reintroduced, with a forced rel='noopener noreferrer' to avoid reverse tabnabbing security issues.

  • MDM-10706: Querying existing loads filtered with the PROCESSING status in the REST API returns an empty list.

  • MDM-10721: A Browse action with a built-in filter using columns for which the user has no privilege breaks the application with a java.lang.IllegalStateException: Browse action error in the log

Version 5.2.1

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

  • MDM-10527: Configuring a decimal attribute with a scale greater than the precision should raise a model validation error.

New Features

  • MDM-10567: New defaultCacheMaxAge property of the OpenIdConnectAuthenticator valve enables configuring the document cache expiration in seconds when the identity provider does not serve expected cache headers.

Bug Fixes

  • MDM-9839: A value selected in a search form value picker appears as the bound value and not as the primary text.

  • MDM-10516: The helper text appears with an incorrect color (black) in authoring form fields.

  • MDM-10526: HTML tags are not correctly escaped in collection display card columns.

  • MDM-10528: HTML tags are not correctly escaped in chart tooltips (dashboard applications).

  • MDM-10529: HTML tags are not correctly escaped in pivot table headers (dashboard applications).

  • MDM-10533: REST API query potential matches returns no results for an entity with Sequence or UUID primary key.

  • MDM-10577: Data location upgrade to version 5.2.0 fails with an Unable to save or commit changes to the database. Changes canceled. error message. This problem occurs when a fuzzy-matched entity references a basic entity with a long entity name.

  • MDM-10578: Unable to restart a data location upgrade that has failed during the integration job update phase.

  • MDM-10580: Performing a Direct Confirm action from a form view does not start the associated job.

  • MDM-10595: Azure Solution Template deployment and management scripts should fail when a SQL Server command fails.

  • MDM-10596: Azure Solution Template az-xdm-instance-reset-admin.sh management script sometimes raises a useless mount error(16): Device or resource busy error.

  • MDM-10598: Job fails on the Notify Referencing MI task with a NullPointerException when the PARAM_CHILD_POSTPROCESSING_JOB parameter is set to true.

Version 5.2.0

Known issues

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

  • MDM-7917: A boolean field default value is null when creating a record and 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 the Semarchy 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 handle properly dates before Feb 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 columns values in a basic entity are overwritten by an enricher when this record is modified by the API or by authoring.

  • MDM-9251: Changes to a sequence Start With property is not taken into account after the first deployment.

  • MDM-9801: Duplicate manager is broken with a wrong editor title when resuming an obsolete suggestion.

  • 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED. This Oracle feature is currently not supported, and the database should be configured with MAX_STRING_SIZE=STANDARD.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes. As a workaround, downgrade to version driver version 42.2.10.

  • MDM-10439: Using the most frequent value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10470: An entity can have more than one default collection.

  • MDM-10472: In the form and collection editors, the configuration column does not use all the available space.

Features Removed

  • MDM-9630: GBGroup Matchcode Global Plug-in is decommissioned.

  • MDM-10084: Removed support for Oracle 11g Release 1, Oracle 11g Release 2, Oracle 12g Release 1 and PostgreSQL 9.5.

New Features

  • MDM-1585: Unified proxy configuration for all components in the platform (REST clients, enricher/validation plugins, notification server, licensing) acting as HTTP clients.

  • MDM-3569: All validations now support customizable and translatable error messages defined in the model. These messages appear in applications' authoring UI and the REST API response payloads when raising validation errors.

  • MDM-5698: Database reverse engineering now supports selecting the entity type for each table.

  • MDM-5843: An badge counter can be configured on the inbox application actions to display - in the navigation drawer and folder item - the number items to do in the user’s inbox.

  • MDM-6851: In the Form and collection editor, the datatype of the fields and columns is now displayed after their name.

  • MDM-6925: Designers can now disable the first login experience (welcome) popup dialog for all applications.

  • MDM-7319: Import now supports new or modified records for entities with generated IDs (UUID, SemQL or Sequence).

  • MDM-7485: Mandatory list of values should not propose the "None" value in authoring.

  • MDM-7529: New empty state editors in applications when browsing an unexisting record, a record that was deleted or an error that was fixed.

  • MDM-7577: The fuzzystrmatch package functions available in PostgreSQL (levenshtein, levenshtein_less_equal, dmetaphone, metaphone, soundex, etc) are now exposed in SemQL.

  • MDM-8010: Compact density mode configured in the user profile is now supported in browsing collection views.

  • MDM-8198: The default entity type is set to Basic in Database reverse engineering.

  • MDM-8343: The new Channel parameter in the Google Maps enricher plugin allows tracking usage in the Google Maps usage reports.

  • MDM-8461: A default Image for Null Values can be defined for the lists of values.

  • MDM-8660: Oracle Database versions 18c and 19c are now certified.

  • MDM-8740: REST Clients can now be defined in the platform and used in enrichers to use external REST APIs.

  • MDM-8833: Dashboard Builder now supports filtering, sorting and table view in lists of charts, dashboard, and queries.

  • MDM-8940: Data import for entities with a SemQL-generated ID now supports mapping a subset of the attributes involved in the ID generation if applicable.

  • MDM-9009: The attribute creation wizard in the application builder allows defining the attribute documentation.

  • MDM-9084: Form tabs and child transitions in business views fallback on the icon of the entity by default.

  • MDM-9100: Fediz tooling (PingFederateSamlRequestBuilder) support for configurable NameID format and optional SPNameQualifier.

  • MDM-9136: The New Model and New Model from import actions are added to the Model Administration node in the application builder Management view.

  • MDM-9146: New SEM_EQUAL_OR_ONE_NULL and SEM_EQUAL_OR_BOTH_NULL built-in SemQL functions for null-save equality conditions.

  • MDM-9160: Automatically-generated workflow transitions to the Cancel task should have the same Cancel label.

  • MDM-9329: New Show in drilldown property on query attribute in Dashboard Builder to define whether they are visible in data drilldown.

  • MDM-9390: New REST API Get platform version endpoint (/admin/version) returns the product version.

  • MDM-9413: New distinct_string_agg lookup type in the SemQL Lookup syntax returns a concatenation of distinct values.

  • MDM-9472: Better advertisement of slicer filtering in dashboards, in the dashboard title, and the slicer panel.

  • MDM-9540: New V_DATALOCATION variable returns the deployment data location name.

  • MDM-9579: Plug-in and REST enrichers now support caching to avoid redundant calls. The cache configuration is defined in the model.

  • MDM-9580: Matchers now support a transitive match score computation method to treat each match pair scores as a probability. Combined probabilities are computed for the entire group to compute a more accurate score.

  • MDM-9582: Matchers now support iterative grouping to process sub-groups of records and create golden iteratively by decreasing match scores.

  • MDM-9585: TRIM function added to the SemQL function list for SQL Server.

  • MDM-9668: Compact density mode configured in the user profile is now supported in duplicate management collections.

  • MDM-9676: Image libraries icons updated to the latest material design icon set.

  • MDM-9698: The Phone Enricher plugin now supports the E123_NATIONAL & E123_INTERNATIONAL values for the Phone Format parameter. These formats comply with the ITU-T E.123 recommendation (no hyphens) for national and international phone numbers.

  • MDM-9713: OpenID samples and explanations removed from the installation guide.

  • MDM-9723: Transitive match scores appear in duplicate manager and explain record graphs as grey match links.

  • MDM-9725: New in-application generated model documentation configurable by applications.

  • MDM-9778: PostgreSQL version 12 is now certified.

  • MDM-9789: Clearer messages and action buttons in license and auto-sync dialogs.

  • MDM-9864: An badge counter can be configured on the Browse Business View application actions to display - in the navigation drawer and folder item - the number of records.

  • MDM-9877: In xDM Discovery, the following metrics are now persisted in the PRF_COLUMN table and no longer computed: Unique Count, Duplicate Count, Unique Values, Duplicate Values.

  • MDM-9886: Link thickness in duplicate manager and explain record graphs reflect the match score.

  • MDM-9890: Microsoft Azure SQL Database is now certified.

  • MDM-9900: New Color property on the match rule configures the color of the match links in the duplicate manager and explain record graphs.

  • MDM-9901: New built-in Melissa Plug-ins provides enrichers to fix and complete contact data for US/Canada using the Personator service, and to validate international addresses in 240 countries using the Global Address Verification service.

  • MDM-9910: Support for self-signed for all components in the platform (REST clients, enricher/validation plugins, notification server, licensing) acting as HTTP clients. This feature is configured using the com.semarchy.xdm.ssl.trustCertificates system property. Set it to selfSigned to accept self-signed certificates, and to all to accept all certificates.

  • MDM-9916: In xDM Discovery, the Row Sampling property is deprecated and replaced by the Maximum Distinct Values Stored and Maximum Patterns Stored properties with default values of 50.

  • MDM-9936: The certification process, REST API and applications now support master record deletion with golden record re-consolidation.

  • MDM-9947: Compact density mode configured in the user profile is now supported in Semarchy drilldown tables.

  • MDM-9996: New REST API name-query-count to count the number of records using a name query.

  • MDM-10017: The SemQL Lookup syntax supports expressions as separators in the separated by clause.

  • MDM-10058: Database functions declared in the model now allow any case for their Name and Schema. A model validation prevents having two functions with the same qualified name and a different case.

  • MDM-10061: New Documentation property on entities, displayed in the application documentation. This property is set to the value of the entity’s description during the upgrade.

  • MDM-10065: New Icon property on model diagrams. This icon appears in the list of diagrams displayed in the application documentation.

  • MDM-10108: New Referenced Role Documentation and Referencing Role Documentation properties on reference relationships, used in the application documentation.

  • MDM-10110: LDAP authentication should return the user found in the directory and not the login, for case where user lookup in the directory is case-insensitive.

  • MDM-10149: The list of detected matches (potentialMatches) returned by the PERSIST_DATA action in the publish data Rest API is now sorted by descending match score.

  • MDM-10154: In the application builder, editor tables supporting inline editing now support tabbing to move to the next cell of the row.

  • MDM-10177: Binary hyperlink component now supports the display text property consistently in browsing and authoring.

  • MDM-10218: Microsoft SQL Server version 2019 is now certified.

  • MDM-10246: The PostgreSQL JDBC driver is updated from version 42.2.9 to version 42.2.10. The SQL Server JDBC Driver the updated from version 7.4.1 to version 8.2.1.

  • MDM-10292: The global search icon no longer appears in the application toolbar when no global search is available for the connected user.

  • MDM-10297: Validation custom error messages now appear in the REST API PersistRecord response payload.

  • MDM-10337: Form field documentation sidesheet is available in the explain record and duplicate manager editors.

  • MDM-10338: Match and merge documentation sidesheet is available in the explain record and duplicate manager editors.

Bug Fixes

  • MDM-2833: Export Excel should support exporting zero records as a template.

  • MDM-4913: New master records do not correctly join partially confirmed golden records.

  • MDM-6258: Integration job fails for an entity with only a primary key attribute.

  • MDM-7872: Exporting the graph view fails silently when avatar images are located on a different server.

  • MDM-9153: Platform variable V_USER_DEPARTEMENT should be spelled V_USER_DEPARTMENT.

  • MDM-9159: Data import should check field values (data type, length, etc) and raise more accurate messages.

  • MDM-9300: Importing master records with references to fuzzy-matched entities fails with a java.lang.NullPointerException at com.semarchy.mdm.dataui.domain.dataimport.impl.RowProcessor.isExpressionMapped(RowProcessor.java:550)

  • MDM-9379: The Browse Entity application action fails with an HTTP-400 response for an entity with a large number of attributes.

  • MDM-9596: Profiling fails with a PRIMARY KEY violation PK_PRF_COLUMN error when the connected database user has access to multiple tables with the same name in different schemas.

  • MDM-9601: The job log count appearing in the subtitle of the Executions editor is incorrect when filtering the job logs.

  • MDM-9619: Dashboard builder prevents creating two measures on the same query attribute in a chart.

  • MDM-9624: In xDM Discovery, the Create Profiling Application dialog should automatically fill the name from the title.

  • MDM-9636: Propagating split leaves broken relationships on Fuzzy matched → Fuzzy matched → ID matched _ and _Fuzzy matched → Fuzzy matched → Fuzzy matched entity chains.

  • MDM-9646: User preferences are not saved for the table view in duplicate managers.

  • MDM-9655: The "splitting all the master records from golden record" SQL sample provided in the documentation is incorrect.

  • MDM-9678: A custom ranking survivorship rule using NULLS LAST generates incorrect SQL code for SQL Server.

  • MDM-9719: A notification server should use the authentication of the application server’s mail resource when it is configured.

  • MDM-9722: Missing privileges when accessing Dashboard Builder or xDM Discovery should lead to the global error page.

  • MDM-9779: Using the CONCAT function in SemQL with SQL Server raises an Unknown function error.

  • MDM-9793: Tomcat server fails to start with a GBK default encoding and raises a jdk.nashorn.internal.runtime.ParserException: Unclosed character class near index 3 exception.

  • MDM-9795: Using a number in the display card primary text with no avatar defined causes empty display cards to appear in the graphs.

  • MDM-9800: Form view fails to appear with a com.semarchy.mdm.datahub.services.query.datamgr.BadSqlGrammarException when a user-defined sort is active.

  • MDM-9802: The list of queries should be sorted alphabetically in the chart creation dialog of Dashboard Builder.

  • MDM-9805: The "Initializing and External Load (SQL Server)" SQL sample provided in the documentation is incorrect.

  • MDM-9806: The "Canceling an External Load (SQL Server)" SQL sample provided in the documentation is incorrect.

  • MDM-9807: In xDM Discovery, the following column metrics are incorrect when sampling a subset of the table: Unique Count, Unique Values, Duplicate Count, Duplicate Values.

  • MDM-9815: Value pickers in filters do not show validation errors.

  • MDM-9816: Changes made on workflow triggers do not reflect in the application builder editor.

  • MDM-9829: The sample logging configuration installation documentation is not up-to-date.

  • MDM-9830: Excel export fails if an export column is a list of values.

  • MDM-9833: Unable to perform an advanced search with the ConfidenceScore = 0 condition.

  • MDM-9835: An application fails to load with a Model for data location: xxx is not valid error when attributes invalid for a given view are used in a collection.

  • MDM-9836: The text color property does not work for chips in authoring forms.

  • MDM-9837: Querying an entity with the REST API fails if the primary key attribute name contains an underscore character.

  • MDM-9846: The profile created for a user with a french browser locale contains an invalid Datetime format pattern.

  • MDM-9863: The update/help buttons in the manage license window use incorrect colors.

  • MDM-9874: Installation guide should mention support for OpenJDK.

  • MDM-9883: The SEM_NGRAMS_SIMILARITY function runs slowly on SQL Server.

  • MDM-9891: Table view indentation is incorrect for master records in duplicate managers.

  • MDM-9902: Incorrect MESSAGE No user principal found in security context. Reject request error logged with an authenticated user.

  • MDM-9909: A reference picker using non text values in the primary/secondary texts fails to load values when typing ahead with BadSqlGrammarException errors on PostgreSQL.

  • MDM-9929: The field documentation side sheet should remain on the same tab when navigating to another record.

  • MDM-9949: Due to JEE constraints, custom (not built-in) notification servers cannot load libraries embedded in their plugin jar, and fail to process job notifications with java.lang.NoClassDefFoundError errors. To bypass this limitation, set the following system property on the server startup command -Dcom.semarchy.xdm.notification.keepPluginClassLoader=true.

  • MDM-9963: Review duplicate suggestion runs slowly. To fix this issue, a new data consolidation method (using nested analytical functions) is now used by default for all databases in the integration job and the applications (for duplicate managers).

  • MDM-9969: Golden authoring is not possible for a user having a row-level filter for read/write on an entity. Authoring fails with a Default data are not readable, you are probably trying to create a record, without privileges to read default data error.

  • MDM-9976: The vertical spacing is inconsistent between text and value picker fields in custom search forms.

  • MDM-9977: A DETECT_DUPS validation triggered on stepper finish should not propose the record being created and should allow selecting one of the duplicates found.

  • MDM-9978: Tables should be sorted alphabetically in the database reverse-engineer dialog.

  • MDM-9989: The date picker fails to update multiple records in a mass-update.

  • MDM-10009: The search type pickers in the Global Search Configuration editor show multiple similar Full-Text search configurations.

  • MDM-10020: License management page reports "License Synchronized" even when the synchronization has failed.

  • MDM-10042: Database reverse-engineering fails while deploying a model to SQL Server with a StringIndexOutOfBoundsException error if a custom procedure was renamed with the Management Studio or with SP_RENAME.

  • MDM-10043: No error is raised when the reverse-engineering phase fails while dropping a data location on SQL Server.

  • MDM-10049: All past install jobs & purge job appear attached to the latest deployment history of a data location.

  • MDM-10050: With SQL Server the default repository name should use the database name instead of the schema name.

  • MDM-10053: In authoring forms, a mandatory validation fails to detect a value reentered after clearing a field.

  • MDM-10080: When editing multiple tables of a datasource in xDM Discovery, empty and multiple values are not correctly handled.

  • MDM-10081: Workflow task for editing records does not start when there is no record to edit.

  • MDM-10093: The Javamail notification server fails to send workflow notifications with an Unable to instantiate a notification server error.

  • MDM-10097: Lookup enricher fails with a NullPointerException if the lookup column contains null values and the Cache Lookup Data parameter is set to LOAD_ON_START.

  • MDM-10101: The Add Properties wizard in the named queries should generate valid unique names when creating nodes.

  • MDM-10109: Minimum Waffle version to download (2.2.1) now indicated in the documentation.

  • MDM-10124: Tooltips appear misplaced on all the graphs (in the explain record editor, a duplicate manager or a graph view).

  • MDM-10147: API Key storage is enhanced to follow OWASP recommendations and uses BCrypt. Existing keys are automatically upgraded to the new storage.

  • MDM-10161: Using a binary attribute with a hyperlink component type in an authoring form prevents removing its value.

  • MDM-10185: The form tab icon in a browsing form does not support images from the image library in PNG or JPG format.

  • MDM-10189: Authoring records do not track the golden history when the entity inherits from another one.

  • MDM-10208: In an authoring form, a component' icon overlaps the next component when they are arranged horizontally.

  • MDM-10224: The httpHeaderSecurity filter is configured with blockContentTypeSniffingEnabled in the preconfigured Tomcat to enable the X-Content-Type-Options: nosniff header by default and prevent browser content sniffing.

  • MDM-10227: Dashboard application name should be validated in the backend to prevent script injection.

  • MDM-10228: The API documentation endpoint returns YAML content with an incorrect JSON content type when no format is explicitly specified.

  • MDM-10230: The httpHeaderSecurity filter is configured with xssProtectionEnabled in the preconfigured Tomcat to enable the X-XSS-Protection: 1; mode=block header by default and stop pages from loading when they detect reflected cross-site scripting (XSS) attacks.

  • MDM-10231: All external links in the product tooltips now use rel="noopener noreferrer" when opening on a _blank target.

  • MDM-10232: Hyperlink components now use rel="noopener noreferrer" when opening the link on a _blank target.

  • MDM-10233: The clusters and queues list in the Execution Engine editor should be sorted alphabetically.

  • MDM-10244: The V_USERNAME variable should be available in a workflow transition when selecting User name from a variable for the candidate assignees.

  • MDM-10254: The navigation menu of the REST API documentation remains on the top of the page with Chrome.

  • MDM-10256: The platform now starts by default in clustered mode to automatically propagate configuration and model deployments on all nodes.

  • MDM-10266: Defining a number value as the display card avatar causes collections using it to partially appear, with startsWith is not a function errors in the browser console.

  • MDM-10285: Filtering or sorting a named query with attributes not available in all views prevents generating the REST API advanced documentation.

  • MDM-10314: A SemQL validation fails to run when the validation is named like the entity or the constraint type, or when the entity is named like a constraint type.

  • MDM-10315: Checkbox text in application authoring forms is too large.

  • MDM-10304: Viewing a dashboard generates ag-grid: invalid colDef property 'name' errors in the browser console.

  • MDM-10318: FID attributes to fuzzy-matched entities should be available in the basic entities' enrichers.

  • MDM-10326: An incorrect number of records indicated in the duplicate issue selection dialog when that number exceeds 49.

  • MDM-10329: Sorting the potential matches using the match rule name or the match score fails in the stepper’s resolve duplicate issue selection dialog.

  • MDM-10349: Business view "search on open" dialog does use not theme color.

  • MDM-10369: In a workflow transition, the Previous task performer value for candidate assignees incorrectly returns all the users who have acted on the task and not the last one.

  • MDM-10371: Default application menu items are not taken into account in platform custom translations.

  • MDM-10372: Field documentation side nav does not refresh when changing record.

  • MDM-10373: Duplicate management actions should not be available to users without full write privileges on an entity.

  • MDM-10374: Custom Translations are unable to serve special characters outside the Latin 1 range.

  • MDM-10435: Integration job fails for golden record override when a binary attribute uses the most frequent value survivorship strategy.

  • MDM-10473: The Oracle reverse-engineering process taking place during the deployment to detect existing objects is optimized to use simpler queries and a RULES hint.