Semarchy xDM 5.3 Release Notes

Feature Highlights

Integrated Authentication

Semarchy xDM version 5.3 brings considerable improvements for authenticating and managing users:

  • Users and Roles can now be managed into Semarchy xDM, reducing the dependency to the application server and facilitating user administration tasks such as provisioning, assigning roles, or resetting passwords. These tasks can be performed using the Semarchy xDM Configuration user interface of the administration REST API.

  • Built-in Identity Management supports all identity providers and protocols (for example, Microsoft Active Directory, Azure AD, Google, OKTA or Auth0, using OpenID Connect, SAML, LDAP, etc.), facilitating the implementation of Single Sign-On (SSO). Administrators can easily configure and test how users authenticate to the corporate identity provider, retrieve their roles, and synchronize their profile information.

Using these new features, administrators can simply set up and maintain users, roles, and Single Sign-On for the Semarchy xDM platform, in Cloud and on-premises infrastructures.

Integrated Datasources

Administrators can now configure in Semarchy xDM the Datasources to connect the databases storing the data hubs, as well as xDM Dashboard and xDM Discovery data. They can also limit the usages of these datasources to specific functionnalities to enhance data security.

The integrated datasources simplify setting up new database connections for data hubs, profiling and dashboarding, and streamlines deployment of Semarchy xDM across environments.

Secret Management

Secrets Management allows administrators to secure the Semarchy xDM platform’s sensitive configuration items such as credentials, API keys, or passwords.

  • Secrets may be stored in the repository, encrypted with a choice of methods, using a local key or third-party Key Management Services such as AWS Key Manager Service, Azure Key Vault or Google Cloud Key Management.

  • Semarchy xDM can also use secrets stored in third-party Secrets Managers such as AWS Secrets Manager, Azure Key Vault, or Google Cloud Secret Manager.

With this feature, administrators and designers can store and manage sensitive configuration items with the highest security and leverage corporate encryption or secret stores, on-premises, or in the Cloud.

Data Notifications

Data Notifications enable designers to easily automate data and change propagation from the data hub to consuming applications.

Data Notifications are delivered - on schedule or data change - to event streaming platforms (such as Apache Kafka) or applications via REST API calls and message services. Their payload is fully customizable, using Semarchy xDM’s named queries, and can contain any data change performed in the hub on golden data, master data, history, etc.

With Data notifications, the designers and integration team can simplify data integration and change propagation patterns from the data hub to downstream systems.

Database Views

Database Views allow designers to design logical views in the model and deploy them in the data hub schema as views, where they can be consumed by external applications or xDM Dashboard charts and dashboards.

Database Views use the full power of SemQL transformations, functions, and expressions to define each column’s content as well as data filters.

Using database views, developers can quickly design and deploy SQL APIs for their data hubs, aligned with the model structure and lifecycle.

Other changes

Integration

  • Delayed Continuous Loads prevents job contention with continuous loads by delaying load submission in the event of long-running certification job instances.

  • New REST API Mass Update action on the Manage Load endpoint allows updating multiple records in a single call, using literal or SemQL expressions.

  • The REST API Manage Load endpoint can be configured to limit the response payload to a summary of the changes instead of all records.

Application Builder

  • Compact Mode in Steppers. Application authoring form fields have been rewritten to support the compact mode.

  • New Markdown form field supports rich text editing.

  • A new reference is automatically added to the model diagrams containing both entities linked by the reference.

  • New Add Existing Reference actions in the model diagram palette to add existing references.

  • The properties view of the Collection Columns and Form Fields have been reorganized in the Application Builder. This view now appears in a vertical panel and supports multi-selection.

  • The Melissa Personator Enricher plugin is updated with the latest features of the Melissa API.

  • New Current Task Performer assignee available in workflow transitions.

  • New and updated design-time properties to Limit import to record creation or update in workflow transitions, stepper collection steps, and actions

  • In SemQL, The MasterRecords transition is now available on the GoldenDataWithErrors view.

Administration

  • The Semarchy xDM Configuration user interface is moved to Material Design.

xDM Dashboard

  • xDM Dashboard charts now support Drilldown Data Export in Excel or CSV format.

  • New Dashboard Designer Privilege providing access to dashboards and charts but not to queries, datasource, and applications.

Change Log

Version 5.3.0

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 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 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-11731: Application startup logs a ResourceBundle not found warning, which should be ignored.

  • MDM-11923: Application startup logs startup configuration issues as verbose exceptions in catalina.out such as:

    [Blueprint Extender: 2] ERROR org.apache.aries.blueprint.container.ServiceRecipe - Error retrieving service from ServiceRecipe[name='.component-1']
    ...
    Caused by: java.lang.IllegalArgumentException: Missing required property xdm.repository.url (or env variable XDM_REPOSITORY_URL)
    ...

    Administrators should review the second exception to troubleshoot configuration issue.

  • MDM-11928: Application startup logs a sqlite-jdbc is not loaded warning, which should be ignored.

Features Removed and Changed

  • MDM-10591: SOAP Web Services are fully decommissioned.

  • MDM-10656: REST API now requires authentication with at least the SemarchyConnect role.

  • MDM-10658: Accessing the REST API Documentation requires an authenticated user.

  • MDM-10698: Checkbox Form Fields no longer support the Text Typography property.

  • MDM-10806: The B_OLDMATCHGRP column and OldMatchGroupID attribute are deprecated.

  • MDM-10891: Chart drill-down is disable by default in xDM Discovery dashboards.

  • MDM-10942: The REST API now only works in stateless mode to reduce server-side resource consumtion.

New Features

  • MDM-5736: Form fields now support the background color property in authoring.

  • MDM-6863: Designers can select and update properties for multiple Collection Columns/Form elements at the same time in the Property Inspector.

  • MDM-8081: New Markdown form field supports rich text editing.

  • MDM-7067: Compact Mode is available in Authoring Forms.

  • MDM-7743: Improved look and feel for multi-valued list of values.

  • MDM-8113: Named Query parameters can be sorted alphabetically in the Add Properties dialog.

  • MDM-8488: New Default Limit property in named queries to limit the number of root records returned.

  • MDM-8834: New Dashboard Designer platform privilege available to only allow designing charts and dashboards.

  • MDM-9019: xDM Dashboard charts now support Drilldown Data Export in Excel or CSV format.

  • MDM-9376: Interacting with non-existing dashboard applications using the REST API now raises clearer error messages.

  • MDM-9488: Better error message logged at application startup when the repository is not created.

  • MDM-9560: The state of the xDM Dashboard application slicer panel is saved with the user profile.

  • MDM-9756: PostgreSQL 11 Stored Procedures are now supported in stepper triggers. A new usePostgreSQLFunctionsAsProceduresInStepperTriggers system property is available to keep the previous behavior and use functions as stored procedures.

  • MDM-9819: The Batch Update Size properties of enricher plugins defaults to 1000 when empty.

  • MDM-9921: Database Views allow designers to design logical views in the model and deploy them in the data hub schema as views.

  • MDM-10094: Delayed Continuous Loads prevents job contention with continuous loads by delaying load submission in the event of long-running certification job instances.

  • MDM-10104: A new Select All button is available in the Add Properties dialog when configuring a Named Query.

  • MDM-10190: SQL exceptions are now displayed in Dashboard Builder’s Query Editor.

  • MDM-10194: Enhanced UX for unparsable dates and number value in authoring fields.

  • MDM-10253: New and updated design-time properties to Limit import to record creation or update in workflow transitions, stepper collection steps, and actions.

  • MDM-10329: Datasources are now configured in Semarchy xDM configuration and no longer in the application server.

  • MDM-10339: Reduced loading times for Model Documentation diagrams.

  • MDM-10341: Named queries properties appear in the REST API documentation with their datatype.

  • MDM-10367: New Current Task Performer assignee available in workflow transitions.

  • MDM-10461: Support the IP Address, SSN, and other inputs in the Melissa Personator enricher plug-in.

  • MDM-10500: The AWS Marketplace AMI and Azure Quickstart VM now allocate more memory to the Application Server based on the virtual machine size.

  • MDM-10503: New Add Existing Reference actions in the model diagram palette to add existing references.

  • MDM-10537: The Semarchy xDM Configuration user interface is moved to Material Design.

  • MDM-10584: The Properties view of the Collection Columns and Form Fields has been reorganized in the Application Builder.

  • MDM-10678: Dashboard Pivot tables now support the right alignment for numeric values.

  • MDM-10696: Image Form fields now support the Text Color property.

  • MDM-10727: Semarchy xDM product documentation reorganized with a different format supporting local search.

  • MDM-10754: The application folders and actions use by default a Sort Method by position instead of alphabetical.

  • MDM-10764: The REST API Manage Load endpoint can be configured to limit the response payload to a summary of the changes instead of all records.

  • MDM-10765: New REST API Mass Update action on the Manage Load endpoint allows updating multiple records in a single call, using literal or SemQL expressions.

  • MDM-10778: Payload samples in the REST API Documentation are now specific to the data models.

  • MDM-10790: Apache Tomcat upgraded to version 9 in the xDM - Preconfigured with Apache Tomcat package.

  • MDM-10801: User variables are updated after each update of the user profile.

  • MDM-10804: In SemQL, The MasterRecords transition is now available on the GoldenDataWithErrors view.

  • MDM-10857: The Melissa plug-ins now support TLS (Transport Layer Security) versions 1.2 and 1.3.

  • MDM-10867: Data Notifications enable designers to easily automate data and change propagation from the data hub to consuming applications.

  • MDM-10889: Secrets Management allows administrators to secure the Semarchy xDM platform’s sensitive configuration items such as credentials, API keys, or passwords.

  • MDM-10927: Notification Server properties can be defined as secrets.

  • MDM-10928: Users are now managed from the Platform Administration.

  • MDM-10937: Semarchy xDM now supports Identity Management Providers for authentication.

  • MDM-11087: The documentation now indicates that SQL Server’s Common Table Expressions (CTE) are not supported in Dashboard Queries.

  • MDM-11327: Variable Provider parameters can be defined as secrets.

  • MDM-11347: The documentation has been updated HTTP cookie security recommendations.

  • MDM-11348: HTTP Cookies security enhancements.

  • MDM-11350: The Workflow Notification Server property is renamed Default Notification Server

  • MDM-11382: Documentation update for system and sizing requirements.

  • MDM-11449: New roles and privileges for identity providers, User, and Role Management.

  • MDM-11450: The Setup and Upgrade processes have been modified and now require a security token during the first login.

  • MDM-11557: The repository connection (formerly SEMARCHY_REPOSITORY application server datasource) is now configured as two datasources set in the startup configuration.

  • MDM-11646: The User Profile Timezone property is now mandatory.

  • MDM-11836: Cloud Virtual Machine images have been updated with new memory management settings to improve performance on medium and large cloud instances.

  • MDM-11882: Refine Non Singleton Groups certification job task performance optimization.

Bug Fixes

  • MDM-8878: FDN attributes are not colorized for master records lineage table view if they match the golden record value.

  • MDM-9251: Changes to an entity primary key attribute sequence Start With are 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-10346: Repository creation fails with an ORA-01450: maximum key length (6398) exceeded error on an Oracle database configured with MAX_STRING_SIZE=EXTENDED.

  • MDM-10383: Using the PostgreSQL driver version above 42.2.11 causes unexpected exceptions with timestamp datatypes.

  • MDM-10439: Using the Most Frequent Value consolidation strategy for the default rule should raise a model validation error.

  • MDM-10466: Batch poller crashes if two root data models have the same name in a deployment environment.

  • 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-10492: Integration Job generation optimizations.

  • MDM-10507: The model documentation export misses the Allow publishing as user in API, Allow Enrichment Documentation, and Allow Data Quality Documentation model privilege grants.

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

  • MDM-10535: A user filter deletion is not effective if refreshing the page.

  • MDM-10556: The EntityNames job notification property does not list all the entities processed by the integration job in the Test Values tab.

  • MDM-10572: The model validation does not identify two attributes with the same name as an error.

  • MDM-10575: Using a Named Query parameter of type UUID on entities with UUID primary keys can raise Unexpected errors with PostgreSQL.

  • MDM-10600: Custom Translations using a single space or an empty string are not taken into account. The documentation now indicates that they need to be replaced by the notation \u0020.

  • MDM-10605: Dashboard charts are truncated after opening and closing the fullscreen mode.

  • MDM-10608: Custom translations used by the class DefaultMessageBundleLoader are ignored for languages other than English and French.

  • MDM-10638: An embedded dashboard' slicer panel has no title.

  • MDM-10663: Server error pages security enhancements.

  • MDM-10680: An object component with an URL source type automatically downloads the targeted file when opening an authoring or browsing form.

  • MDM-10695: Date picker do not use the Text Color property in authoring forms.

  • MDM-10697: The Click to upload action is not working on an Object form field if it is associated with a binary attribute.

  • MDM-10703: Form and Collection validation errors are not redirecting the user to the root cause of the error.

  • MDM-10708: The Import and Import-Update workflow actions have the same label in the user action menu.

  • MDM-10726: The confirmation message to delete selected records in a stepper is not accurate.

  • MDM-10753: Boolean checkboxes do not use properly the theme secondary color in an authoring form.

  • MDM-10762: Importing master records with a fuzzy-matched entity using a sequence for master ID generation can cause duplicate records in the SD table if the Import ignoring errors option is used.

  • MDM-10780: Using a PostgreSQL function with numeric parameters in a step procedure trigger raises a function does not exist error.

  • MDM-10785: The right sidesheet is truncated in applications with a Safari browser.

  • MDM-10795: The REST API should prevent creating a model without a name.

  • MDM-10796: The Density Mode profile setting is not translated to French.

  • MDM-10823: Saving a job a filter using Include Only cause Incorrect syntax near 'OFFSET' error with a SQL Server repository.

  • MDM-10829: Using comments in a SemQL expression can cause NoSuchViewAttributeException errors in an authoring form.

  • MDM-10868: In an authoring form, a text field associated with a number or decimal attribute removes incorrect characters automatically with no error message displayed.

  • MDM-10880: Missing recommendation in the documentation to use UTF-8 collations with SQL Server 2019 or Azure SQL Database.

  • MDM-10904: Users can by bypass the Max Character Length validation on a text field by entering the correct number of characters, pausing, and then adding more characters to exceed the max length.

  • MDM-11008: The workflow Reassign Task dialog now show user first and last names instead of the username.

  • MDM-11017: Inconsistent labels for the attribute data type and form/collection default data type in the Application Builder.

  • MDM-11038: HTTP-500 error pages security enhancement.

  • MDM-11042: The Phone Extractor plug-in fails to run when the optional input Accepted Region is not set.

  • MDM-11099: On SQL server, using the entity ID in the display card causes an Error converting data type nvarchar to numeric error with the Explain Record action on suggestions.

  • MDM-11100: On SQL server, using the entity ID in the display card causes an Error converting data type nvarchar to numeric error with the Review Duplicate Suggestion action on suggestions.

  • MDM-11176: The PARAM_AGGREGATE_JOB_PLUGIN_ENRICHERS parameter causes the integration job deployment to fail with a value too large for column error if a plugin enricher uses an input expression longer than 128 characters.

  • MDM-11239: A named query property with a coalesce expression on date fields returns a timestamp.

  • MDM-11245: Specifying an unexisting validation or enricher in the integration REST API causes an Unexpected Error response.

  • MDM-11256: Accessing the REST API with an API key from an IPv4 address fails with a Failed to parse address IP:port if the port is specified.

  • MDM-11259: Listing Job Notification Policies using the REST API causes an Unexpected Error if one of the policies has the Job Name Pattern property set to an empty string.

  • MDM-11321: A Date Picker field is not filtered correctly by the Min Date and Max Date properties in an authoring form.

  • MDM-11332: Job notifications using an HTTP notification server with the POST method ignore the PARAM_PARAMS notification properties.

  • MDM-11337: HTTP-400 error pages security enhancement.

  • MDM-11340: With a long integer value, a search criterion autocomplete field does not always show the value matching the user input, depending on the global application configuration Autocomplete Max Results property. If a value matches exactly the user input, it now appears first in the autocomplete search field.

  • MDM-11364: Reference selection in authoring forms that use a search on open do not take into account the search criteria if the search form is submitted too quickly.

  • MDM-11383: A missing ID attribute in a REST API call causes an Unexpected Error response.

  • MDM-11408: The REST API documentation is only accessible to users with the semarchyAdmin role.

  • MDM-11420: Workflow transitions triggers do not run on cancel events.

  • MDM-11463: Sorting a collection on the ID (Golden ID) attribute fails on SQL Server with an error code [169]; A column has been specified more than once in the order by list. Columns in the order by list must be unique. error

  • MDM-11479: Datasources are not listed in the Dashboard Builder if at least one datasource configuration is invalid.

  • MDM-11517: Accented characters do not carry over properly when exporting and importing models through the REST API.

  • MDM-11545: A REST Client Enricher can suspend an integration job if it processes invalid data with the settings Behaviour On Error set to Skip Record and Behaviour On Absent Value set to Use default value.

  • MDM-11559: Object and Image fields now always use the Height property, even when there is no content in the preview zone.

  • MDM-11561: Selecting two previously split golden records found using an advanced search with two criteria on the same attribute, and then performing any action on these records fails with a Conflicting binding name error.

  • MDM-11600: Unable to export data from business views with a custom sort that uses a lookup on date fields.

  • MDM-11619: A new user accessing an application for the first time receives an unexpected database error when opening the inbox.

  • MDM-11643: The user variable :V_USER_COUNTRY used in an enricher makes the integration job fail if the user profile has no country defined.

  • MDM-11726: Login page security enhancements.

  • MDM-11741: Performance improvements for complex Named Queries.

  • MDM-11795: Export data from a business view might be erroneous when a sort is applied on columns containing empty values.

Version 5.3.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 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 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.

New Features

  • MDM-10498: Azure Solution Template VM updated to use JDK 11.

  • MDM-11471: Reference, Menu, and Chips components usability enhancements to update an existing value.

  • MDM-11499: Markdown browsing component updated for consistency with the authoring component.

  • MDM-12020: LDAP identity provider new bind as User authentication mode.

  • MDM-12025: Active Directory identity provider new Search filter and RootDN properties.

Bug fixes

  • MDM-10715: The display card column width is not configurable for business view transitions.

  • MDM-11024: Dashboard charts are zoomed-in with Chrome version 75.

  • MDM-11235: The record action menu appears with extraneous menu items that disappear after few seconds.

  • MDM-11351: Data access SQL errors security enhancements.

  • MDM-11464: Match detection fails when using a matcher on a basic entity by a user who does not have permission to view all of the attributes in the entity.

  • MDM-11845: Unnecessary Hikari driverClassName warning is logged when starting Semarchy xDM on Tomcat.

  • MDM-11880: Adding a new column to a collection in the Application Builder raises a NullPointerException.

  • MDM-11892: Entity forms with a large number of references generate large HTTP responses.

  • MDM-11913: Tomcat manager is not restricted to localhost access on Azure Solution Template VM.

  • MDM-11936: Exporting the content of an embedded collection fails with a Multiple entries with same value error if the sort expression uses one of the exported fields.

  • MDM-11942: Expanding a data location node in the Application Builder cause excessive server memory consumption when the data location has numerous loads.

  • MDM-11944: Excessive server memory consumption caused by retained TreeItems in the Application Builder.

  • MDM-11946: Incorrect label for the Confirm Password field in the Setup & Upgrade wizard.

  • MDM-11948: Startup information is no longer displayed in the System & Repository Information.

  • MDM-11952: The setup & upgrade wizards are not translated according to the browser locale.

  • MDM-11961: Unable to authenticate on a passive instance with a SAML or OpenID Connect identity provider.

  • MDM-11969: Repository upgrade fails with a DDL: EXEC sp_RENAME 'PDS_DATASOURCE.CONFIG', 'POOL_CONFIG', 'COLUMN' error on a case-sensitive SQL Server database.

  • MDM-11978: Documentation updated better explain the Active Directory Domain property for the Active Directory identity provider.

  • MDM-11979: Configuring an LDAP identity provider with an empty User DN Pattern raises a NullPointerException.

  • MDM-11980: The welcome page displays as HTML source code under certain conditions.

  • MDM-11988: The Encryption Public Key and the Signature Public Key can not be reset to null for a SAML identity provider.

  • MDM-11990: Creating a user with an empty email address fails with an email address must not be empty error.

  • MDM-11996: Importing a model on a QuickStart VM instance (Azure and AWS) fails with an Upload canceled because an error has occurred error message.

  • MDM-11998: Using a SAML identity provider with an incorrect private key format raises an org.bouncycastle.asn1.pkcs.PrivateKeyInfo cannot be cast to org.bouncycastle.openssl.PEMKeyPair error.

  • MDM-12001: Secrets Management usages fixed to support true or false values.

  • MDM-12002: Excessive number of network requests due to Inbox badges.

  • MDM-12006: Built-in roles are not available in the API Key configuration.

  • MDM-12012: Image Library Import security enhancements.

  • MDM-12040: Incorrect email validation in the user creation dialog prevents emails with multiple "." characters.

Version 5.3.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 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 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-12166: Authentication on Azure Active Directory through HTTPS fails because of incorrect reply URL.

  • MDM-12266: Authentication with a SAML Identity Provider fails with Saml2AuthenticationException{error=[malformed_response_data] No assertions found in response.} error when EncryptedAssertion is signed but the response is not signed.

New Features

  • MDM-11513: Configure the authentication request signature algorithm for SAML identity providers.

  • MDM-11596: New REST API Certify endpoint runs the certification process for a record without persisting data.

Bug fixes

  • MDM-10923: Double-clicking the column separator in collection column headers does not resize the column automatically.

  • MDM-11202: Nested attributes from referenced entities having a model privilege grant of None are visible on browsing. The fix hides the values of nested attributes when the referenced entity or its attributes are not read-authorized.

  • MDM-11406: The inputs of REST clients having numerous output parameters are not visible on the test dialog.

  • MDM-11552: Explain Record displays inconsistent confirmation status.

  • MDM-11731: Application start logs show a ResourceBundle not found warning.

  • MDM-11964: Loading all images from image libraries causes xDM Configuration to freeze.

  • MDM-11982: xDM Configuration cannot open after the upgrade to version 5.3 if unsupported access modes have been set on platform privileges.

  • MDM-12003: The first attempt to edit the arguments of a step trigger fails with a java.lang.NullPointerException and the dialog cannot be resized.

  • MDM-12034: The Service Provider Metadata URL of SAML identity provider is not accessible while the IDP configuration is incomplete or invalid.

  • MDM-12052: String search patterns that include a % wildcard followed by numeric digits cause filter loss and bad pagination.

  • MDM-12079: Calling a procedure within a step trigger or stepper trigger on SQLServer raises an org.springframework.jdbc.UncategorizedSQLException.

  • MDM-12083: Date field causes the REST API to fail while sending response with a com.fasterxml.jackson.databind.exc.InvalidDefinitionException.

  • MDM-12084: Embedded collections cannot be sorted on attributes that also exist in the parent entity.

Version 5.3.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 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 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-12266: Authentication with a SAML Identity Provider fails with Saml2AuthenticationException{error=[malformed_response_data] No assertions found in response.} error when EncryptedAssertion is signed but the response is not signed.

Bug fixes

  • MDM-12166: Authentication on Azure Active Directory through HTTPS fails because of incorrect reply URL.

  • MDM-12185: Calling a Named Query that contains an optional FDN raises an org.springframework.jdbc.UncategorizedSQLException with PostgreSQL if there is no parent record to return.

Version 5.3.4

Breaking Changes

  • MDM-12142: This release no longer includes the javax.json library to avoid possible conflicts with other libraries (JMS drivers) or application server-provided implementations.
    Tomcat does not provide a built-in implementation of javax.json. When deploying Semarchy xDM in an existing Tomcat server, make sure to copy the org.glassfish.jakarta.json_*.jar file from the mdm-server/additional-libraries/ folder to the Tomcat lib/ folder.

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 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 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-12161: The form preview fails to appear with a [http-nio-8088-exec-1] WARN org.apache.cxf.phase.PhaseInterceptorChain - Application {http://designtime.md.platform.semarchy.com/}DesignTimeController has thrown exception, unwinding now org.apache.cxf.interceptor.Fault exception when Semarchy xDM run with a JDK 8.

  • MDM-12254: The documentation side nav fails to appear with a NullPointerException error when Semarchy xDM run with a JDK 8.

  • MDM-12266: Authentication with a SAML Identity Provider fails with Saml2AuthenticationException{error=[malformed_response_data] No assertions found in response.} error when EncryptedAssertion is signed but the response is not signed.

New Features

  • MDM-9290: The Persist Data and Mass Update actions in the Publish Data API now support running all enrichers/validations in addition to a list of enrichers/validations.

  • MDM-10055: Azure instance upgrade script supports customizing the backup resources name suffix.

  • MDM-10332: Semarchy xDM QuickStart VM offer is available in the Google Cloud Platform marketplace.

  • MDM-10740: "Select All" added to the list of records in the many-to-many reference picker.

  • MDM-10948: The REST API OpenAPI documentation now exposes the description for the named queries.

  • MDM-11123: The application action description appears added as a tooltip on the corresponding navigation drawer item.

  • MDM-11146: The Persist Data and Mass Update actions in the Publish Data API now support responsePayloadRecordsBaseExpressions and responsePayloadRecordsExpressions options to configure the records returned in the response.

  • MDM-11738: New REST API probe endpoints to monitor the platform, REST API, and applications liveliness, startup, and readiness.

  • MDM-11903: Semarchy xDM certified with PostgreSQL 13.

  • MDM-11925: New startup logging to capture clean startup logs. See Startup Logging for details.

  • MDM-11994: Mass-update UI performance improvements.

  • MDM-12046: The Persist Data and Mass Update actions in the Publish Data API now support queryPotentialMatchBaseExpressions and queryPotentialMatchExpressions options to configure the potential matches returned in the response.

  • MDM-12061: The Persist Data and Mass Update actions in the Publish Data API now support configuring the rules used to query potential matches, as well as returning only the potential match with the highest score.

  • MDM-12076: Preview in the Form editor enhanced with more accurate layout and rendering.

  • MDM-12090: REST API Certify endpoint supports running validations.

  • MDM-12117: SAML Identity Provider configuration editor properties reorganized.

  • MDM-12180: New Replicas feature in platform datasource configuration allows administrators to define distinct database connection parameters per environment and to specify in the startup configuration the environment to use.

  • MDM-12197: Platform startup correctly captured and reported in the log.

Bug fixes

  • MDM-10797: Form search should set the focus on the "Find field by name" field when opening.

  • MDM-10798: Full-text search should focus on the "search text" field when opening.

  • MDM-10911: The Value tab of the Explain Record editor loads indefinitely when the form contains embedded collections.

  • MDM-11156: Import fails to parse a file and does not display the preview to configure the separator.

  • MDM-12213: Focus jumps to the first field in a search form after the user clicks fast on another field.

  • MDM-11549: The Reference Selection dialog does not display an empty state in the table view.

  • MDM-11760: Creating a function with an incorrect category in the model prevents using any SemQL editor.

  • MDM-11925: Incorrect sqlite-jdbc is not loaded errors reported in the platform startup log.

  • MDM-12032: Job enricher aggregation wrongly applies the filter to all the enrichers involved.

  • MDM-12045: Editors appear broken after an application refresh with a TypeError: Cannot read property 'hasGlobalSearchConfigLink' of undefined in the browser console.

  • MDM-12068: Missing detailed stack trace for SSL errors when testing identity providers.

  • MDM-12070: Discovery and Dashboard Builder do not translate correctly/immediately when a French locale is used.

  • MDM-12094: Security hardening for identity management REST API.

  • MDM-12101: Job log export fails with a NullPointerException due to a missing end date.

  • MDM-12110: Chart based on a query with a trailing semicolon fails. The query editor now raises an error for such queries.

  • MDM-12111: Multiple concurrent logins with a named account and the internal IDP cause an HTTP-500 error.

  • MDM-12141: Login fails with a net.minidev.json.JSONObject cannot be cast to java.lang.String error when the "address" additional scope is configured for an OpenID Connect IDP.

  • MDM-12146: Seeding a language that is not in the known values breaks the user profile editor with a Cannot read property 'label' of undefined error.

  • MDM-12151: Using SQL Server windowing functions in dashboard queries prevents drilling down.

  • MDM-12158: Security enhancement for logging configuration.

  • MDM-12159: Reinforced checks of YAML content in Dashboard application.

  • MDM-12167: The SEM_NGRAMS_SIMILARITY function used with the ngrams length parameter raises a conversion error on SQL Server.

  • MDM-12174: The date picker component "Cancel" button is not translated to French.

  • MDM-12187: When browsing, special characters cause truncation of the rendered string in long text form fields.

  • MDM-12211: A NullPointerException is raised when no group is returned in the response token of an IDP test.

  • MDM-12216: Step transition returns an unexpected The date must be later than Invalid date validation error when min or max date format is set to 'YYYY-MM-DDTHH:mm:ss.sssZ' on a Date Picker form field.

Version 5.3.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 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 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.

Bug fixes

  • MDM-12161: The form preview fails to appear with a java.lang.NullPointerException error when Semarchy xDM runs with a JDK 8.

  • MDM-12208: Testing a notification server fails with a java.lang.NullPointerException error if the optional username and password properties are not set.

  • MDM-12253: The selected value is not visible in reference fields after modification during a mass update.

  • MDM-12254: The documentation side nav fails to appear with a java.lang.NullPointerException error when Semarchy xDM runs with a JDK 8.

  • MDM-12266: Authentication with a SAML Identity Provider fails with a Saml2AuthenticationException error when EncryptedAssertion is signed but the response is not signed. A new -Dxdm.idm.saml.unsafelyDecryptAssertionsInUnsignedResponse system property is available to keep the previous behavior and support encryption in unsigned responses (unsafe).

  • MDM-12293: Receiving a HTTP 201 response status code for a job notification raises a java.lang.IllegalStateException.

  • MDM-12296: Performance improvements for Named Queries.

  • MDM-12311: The Identity Provider Entity ID and Web SSO Endpoint properties cannot be set on SAML identity providers.

  • MDM-12314: Diagram documentation fails to open with a com.semarchy.engine.extensionpoint.NoSuchRowTransformerException error for entities using a Custom Plugin Validator.