Released: November 2022
This release contains the following new features:
The UI was updated for manual merge operations on the tables that comprise business objects.
The stewardship UI was updated so that lineage and metadata can be viewed for a business object's related tables.
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 in functionality.
The FasterXML jackson-databind library was updated to version 2.13.4.2.
This release includes the following closed issues:
[MAME-7953] The manual merge view is slow to load if the table has a merged records association.
[MAME-8157] The Align foreign keys step does not display when a merge policy attribute is defined and Use for manual merge is set to No.
[MAME-8201] Hidden field values are still highlighted when selecting a survivor field by merge function.
[MAME-8265] Matching state is cascaded to child levels when unmerging even though the child records are excluded.
[MAME-8283] When using matching fields from related tables with the Exact algorithm and Both value are null = Match, there are inconsistent matching result between Evaluate Matching and See details.
[MAME-8286] An HTML block is displayed instead rendering the Decision tree and Business object activation.
[MAME-8318] Deleted records display in the Data selection view of the Supersede survivorship service.
[MAME-8326] The Manage group screen should be reloaded after a successful manual merge operation.
This release contains the following known issues:
[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).