This release contains the following new features:
It is now possible to use the replication feature on Business objects.
Data comparison nodes now have the option to use operators or algorithms to determine how to values are compared.
The following user experience enhancements were made:
The display order of fields in merge policies was updated so that Auto create new golden is now at the top. This is more intuitive as this value can impact the availability of other options.
The explanation for the evaluation of matching execution now includes additional parameters to better explain the results.
Performance was improved when changing the state of selected records to [Unset].
When upgrading from version 3.0.0, 3.1.0, or 3.1.1 you must update existing matching configurations. After updating configuration settings, you should re-execute matching to ensure that matching related metadata is up to date.
This release contains no changes to functionality and behavior.
The FasterXML jackson-databind library was updated to version 2.15.2.
This release contains the following closed issues:
[MAME-8983] [JAVA API] An exception is thrown when no duplicates are found in a group.
[MAME-9210] All records display in the Merged association tab when opening a record that is not golden.
[MAME-9289] A different method should be used to detect whether a table belongs to a Business object, or individual table configuration.
[MAME-9311] After being deleted in the Matching fields tab, fields in a data comparison node cannot be re-created that use a range data type (Date, Time, Date and time, integer, decimal).
[MAME-9358] When using staging to import the matching configuration, it fails if the decision tree in the source environment uses Predicate.
[MAME-9390] The decision tree result is incorrect when: 2 or more matching fields are used, one field is from a related table, and it's values are null due to being excluded by the Exclude related records where setting.
This release contains the following known issues:
Foreign key alignment of recursive foreign keys is not possible.
[MAME-7434] Linked records are duplicated in the link table when one of the foreign keys is not part of the primary key.
[MAME-9049] A manual merge operation cannot be performed on more than 400 records.
When matching using the foreign key option, you can only specify a single hop foreign key. In other words, it cannot be a foreign key to a foreign key.
The Validation service in the Consolidated view runs as expected when first executed, but slow on subsequent executions.
In order to accurately track record lineage, table history must remain activated over time. If the table's activation status repeatedly changes, the lineage data will be inconsistent.
Severe errors occur when multiple datasets based on the same model exist and a table from one of these datasets is activated in an add-on matching configuration. As a workaround, you can create another data model publication using the Manage publications service in the Data Model Assistant. After creating a dataset for the new publication, you can follow the normal procedures to configure a matching policy for tables in the new dataset.
For foreign key alignment, the FKs that are multi-value fields cannot be aligned (either manually or automatically).