This release contains the following updates focused on performance improvements:
Foreign Key alignment during the merging phase was optimized.
Instead of relying on snapshots, a new method is used to check the differences between transactions.
The API was updated to improve performance when getting lists of suspects or records contained in a group.
This release contains the following enhancements:
New rules are applied to survivor record selection for the instances where no records, or multiple records satisfy required conditions.
When running the Purge old results service, out-of-date matching selections are now also purged.
Foreign key alignment of composite primary keys during automatic merge was improved.
The relationship between selected records is now removed for any suspect record that is accepted as a match when managing groups.
The readability of information written to the logs regarding foreign key alignment was improved.
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 the following changes to functionality and behavior.
If a field configured to participate in matching meets either of the following criteria, it is automatically disabled during the pre-processing phase to improve performance:
The field's type is boolean.
The entire column is null.
Special characters are now preserved when using the add-on's distance matching algorithms.
The Spring framework was updated to version 5.3.29.
This release contains the following closed issues:
[MAME-6368] The Merge and Purge old results legacy services still display on the Merged Record Association screen.
[MAME-8332] Field values that satisfy the merge policy requirements are still preselected when the survivor record is read-only.
[MAME-8656] A NullPointerException occurs in log4J2 during Liberty startup.
[MAME-9352] The incorrect survivor field value is used when multiple records satisfy merge function conditions.
[MAME-9383] When auto-merging, do not select the smallest primary key to be the survivor record when no records satisfy the Record selection function.
[MAME-9418] The inline matching is marked as Deprecated in the breadcrumb when running the service.
[MAME-9420] For Auto-merge, result of aligning some foreign and primary keys are incorrect if the keys are set to read-only on dataset permissions.
[MAME-9421] For Auto-merge, alignment of foreign and primary keys is incorrect when a related table has a primary or foreign key, and auto-incremented primary key, and one of those keys is read-only by dataset permission.
[MAME-9422] For Auto-merge, alignment of foreign keys does not work for all related tables if one FK field from any related tables is set to Read-only.
[MAME-9423] For Auto-merge, alignment of foreign and primary keys is incorrect when a related table has a primary or foreign key, and auto-incremented primary key, and one of those keys is read-only by Access rule.
[MAME-9466] The align foreign key function (in another dataspace) does not work correctly when the merge service runs in a child of the referenced dataspace configured on the data model.
[MAME-9505] Medium and large numbers of merged records cannot be modified (changed to <unset>).
[MAME-9519] The selected auto-Golden records in Related tables incorrect after merged several auto-created records by selecting each record.
[MAME-9536] The result column in the decision tree explanation popup disappears when using an evaluation method which other than Average.
[MAME-9539] A blank Merge related screen when creating a new golden on a business object.
This release contains the following known issues:
[MAME-8084] The Evaluate matching service returns inconsistent results for related matching fields that have the DateTime data type.
[MAME-8857] It is not possible to accept or reject suspects in groups that contain a large number of records.
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).