Released: September 2022
This release contains the following new features:
Matching and merge operations can be configured on multiple tables that comprise EBX® business objects.
The Manage group view is able to display records from multiple tables in a business object.
To improve the user experience, the progress bar was updated.
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 Apache Taglibs library was removed from this release.
This release includes the following closed issues:
[MAME-7661] The content does not display correctly when there are more than 50 errors in a validation report on the Consolidated view.
[MAME-7874] After rejecting a suspect record, users are navigated away from the Manage group screen and back to the tabular view.
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).