This release contains the following enhancements:
Viewing record lineage: |
|
Performance enhancements | Updates in this release have reduced redundant matches when processing tables that have many duplicate records. This speeds up matching, grouping, and merging, and results in fewer records in the Matching results table. |
Automated purging | The add-on now supports automated purging of outdated matching metadata through the EBX® Task scheduler. This enhancement reduces manual maintenance and helps prevent performance degradation over time. For more information, see Scheduling matching metadata purges. |
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.
As the add-on UI is under development, some images in the documentation might not exactly match those in the UI.
This release contains no changes in functionality.
Take the following into account if you upgrade TIBCO EBX® Match and Merge Add-on:
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.
If upgrading from any version prior to 6.2.0, a performance improvement was made to better balance the weights of fields that participate in matching. The automatic balancing occurs during the pre-processing phase. This helps mitigate issues that might occur when fields include many values. As a result of this update, matching operation results might be impacted. To mitigate any negative impacts, you can test and adapt your existing weights to achieve the desired matching outcome. Alternatively, you can set the ebx.clustering.balance property to false in the ebx.properties file to restore the legacy behavior.
The following third-party libraries were updated:
Jackson Core was updated to version 2.21.1.
Spring Framework was updated to version 6.2.14.
Jakarta Servlet was updated to version 6.0.
This release contains the following closed issues:
MAME-9523 When matching with business objects, group management is inaccessible after deleting the center record.
MAME-9904 Records matched through transitive relationships are not grouped correctly when matching is executed in batches.
MAME-9914 The tooltip description for the Any duplicates merge mode should be rephrased and clarified.
MAME-9930 An error occurs when importing the add-on's metadata (_MDS dataset).
MAME-9933 The add-on's logs are throwing an error in EBX® Container Edition.
MAME-9952 When a matching policy is set to execute after submission, it is not triggered when creating a new record from a workflow.
MAME-9959 When the merge policy is set to Auto create new golden and the mode is Only duplicates, any customized source value that should only apply to new golden records is getting incorrectly assigned to unique golden records.
This release contains the following known issues:
The following workaround is for a known issue in EBX® (CP-27860). When child dataspaces or snapshots are created before enabling the EBX Match and Merge Add-on on a data model, some operations can fail after the add-on is enabled. For instance, child dataspace merge might not work correctly, or snapshots might have errors.
Workaround: Disable the add-on before performing the dataspace merge, or creating a snapshot; enable the add-on after completing the operation:
Open the data model, navigate to Configuration > Add-ons.
To disable the add-on, tic the box next to Match and Merge and select Delete from the Actions menu.
Publish the data model.
After performing the desired operations, enable the add-on by re-creating the Match and Merge record in the Add-ons table.
Publish the data model.
[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).