Released: April 2023
The matching operation triggers can now be paused on business objects.
This release contains no changes in functionality.
The SnakeYAML library was updated to version 2.0.
This release includes the following closed issues:
[MAME-8622] Hidden field values are not updated after the merge process finishes.
[MAME-8623] An inconsistent matching result is shown in the diagram when evaluating matching results.
[MAME-8624] The record order in when managing a group in the Consolidated view is incorrect.
[MAME-8626] Incorrect matching results are returned when using light relationships (FK from matching table to target table OR over a link table).
[MAME-8628] The State is duplicated in the Identified as false positives tab.
[MAME-8629] The back button does not work as expected after completing a merge.
[MAME-8630] Some text is not translated into French.
[MAME-8632] A false positive relationship is not created after merging records in the inline screen.
[MAME-8634] [UI] When hovering over the False positive icon in the Manage group screen, the cursor displays as a hand.
[MAME-8635] Records are not sorted correctly when accessing the Merge view when managing a group.
[MAME-8636] The warning banner does not display when accessing a group that includes at least one hidden record.
[MAME-8637] The matching field is changed when duplicating a matching policy.
[MAME-8638] [BO] There is no new golden record but the Apply merge policy button is still enabled.
[MAME-8640] When managing relationships during a manual merge, it takes a long time to display records.
[MAME-8646] An incorrect error message displays when manually merging and the main table's primary key is not auto-incremented.
[MAME-8670] All add-on services still display in the Actions menu after pausing the corresponding matching configuration.
[MAME-8678] Matching cannot be evaluated for selected records when using a matching policy without having a merge policy defined in the related table.
[MAME-8884] Unexpected information is included in the log file.
[MAME-8891] An error displays after unmerging an auto-created golden record that had been merged multiple times.
[MAME-8894] The login page displays when executing any action in the Actions menu in the Manage group screen after accessing the group from a workflow.
[MAME-8920] The decision tree result is inconsistent when evaluating matching for a URI field through a relationship.
[MAME-8932] An error occurs when running manual merge if the primary key is a String and includes an apostrophe in the data value.
[MAME-8936] An error displays when applying sort criteria for false positive records or when viewing records in the Manage group screen.
This release contains the following known issues:
A field configured for use in matching operations cannot be configured for other relationships. For example, in a Person table the Address field is configured through matching by foreign key. This field cannot be configured in another instance with a different relationship (over linked table, or none).
[MAME-7434] Linked records are duplicated in the link table when one of the foreign keys is not part of the primary key.
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).