This release contains the following new features:
The add-on was adapted to ensure compatibility with the EBX® staging feature.
A page loading indicator now displays when performing a manual merge.
When configuring inline matching for a workflow, it is now possible to use the Matching policy parameter to specify a matching policy other than the default policy configured for the table. The default policy is used when this parameter is undefined.
All snapshots related to the add-on now include a MAME_ prefix.
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:
The Search before create service no longer needs to be enabled by an administrator. Additionally, when running the service, the matching policy is selectable. The chosen matching policy will determine which fields are available to search and the criteria used to locate potential matches. The Search before create service is still available from the matching policy configuration, however it is marked as deprecated.
When a matching table configuration is deleted, now all related replications are also removed.
The following default options were changed in comparison node configurations:
The default value for Comparison function is now All fields match.
For the Full text, Fuzzy, and Hybrid fuzzy algorithms, the Minimum score now defaults to a value of 100.
The Consolidated view was deprecated. It is still available to access, but it is planned to be removed in a future release.
The Spring framework was updated to version 5.2.24.
This release contains the following closed issues:
[MAME-5690] The screen does not display correctly in a data workflow when the matching field of the default matching policy is deleted.
[MAME-6629] Color properties are not applied correctly.
[MAME-8088] The tooltip for 'Enable Matching' is not localized in the Administration pane.
[MAME-8104] Records that include the '+' character in the primary key cannot be viewed when accessing their group.
[MAME-8807] Some records are incorrectly grouped after running a matching operation.
[MAME-8848] The undo option is still clickable for values where it should not be available.
[MAME-8864] The Manage group screen does not display correctly after changing the view.
[MAME-8931] Records' false positive icons are not removed in the Manage group screen after deleting the records from the metadata service.
[MAME-8934] The Search before create service cannot be executed when the Matching fields tab includes invalid matching fields.
[MAME-8935] In workflows, the Search before create screen cannot be re-accessed after performing an inline merge and updating a record in list of potential duplicates.
[MAME-9016] The add-on's manage group feature cannot be accessed when primary keys include a foreign key.
[MAME-9038] Redundant rows can display in the Manage group screen.
[MAME-9059] A foreign key field can be configured to use other algorithms besides the Exact algorithm.
[MAME-9061] The error message from previous phase is not cleared after changing field.
[MAME-9205] Nothing happens when clicking the Preview button on primary key or foreign key field in the Lineage screen.
[MAME-9206] Display ALL services under Actions menu in the association of Merged records.
[MAME-9225] The screen does not display correctly after previewing a record in the Manage group screen.
[MAME-9248] Matching results are provided using the light relationship instead of the strong relationship when both are configured on a business object.
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.
[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).