Released: January 2023
Instructions were added to the documentation that describe how to prevent library conflicts when deploying on WebLogic. See the Preventing library conflicts on WebLogic heading in the index.html file that is located in the following folder in the 4.5.16 Add-on Bundle: documentation > daqa_<xxx>.
This release contains the Changes in Functionality:
You can now configure the State filter property for a target table to execute a crosswalk matching operation.
The API's new SurvivorField.getConditionFieldValueSurvivorship() method allows you to get the condition for a field value that can be merged.
This release contains no changes in third-party libraries:
[DAQA-3949] A security issue was fixed.
This release contains the following known issues related to matching functionality:
The EBX® session lifetime is limited for security reason, meaning the user is logged out automatically after a certain amount of time passes without activity. In some situations, this can open the login EBX® screen inside a frame of the EBX® Match and Merge Add-on views. To exit from this type of situation, select any action outside the frame, and then EBX® full login screen will appear. This limitation has no consequence on data integrity or security issues. This is an ergonomics known limitation.
When the search panel is active on the EBX® tabular view, it will be inherited in the matching views. Then, it is no longer possible to remote it at the level of the matching views. It is mandatory to remove it from the EBX® tabular view.
All EBX® Match and Merge Add-on services and triggers are deactivated on children data-sets.
If you want to use old configuration archive files from a previous version, after importing them, you must restart the system.
Search option on matching views is disabled for searching on foreign key which is configured as matching field with multi hop links.
Multi occurrence field and foreign key field with multi hop are not supported when executing 'Exact match at once' operation.
You should avoid matching with inherited fields or value functions because they are not indexed in EBX® and can lead to performance issue.
Matching is not enabled on D3 slave delivery dataspaces.
The enumeration fields are not taken into account when matching.
Only single-occurrence fields at the first level of a multi-occurrence group are considered when matching.
Match at once parallel does not support 'Data life cycle context' in Matching policy.
Exact match at once in memory does not support 'Matching policy context' in Matching policy.
In a surrogate matching, complex fields, foreign key fields, multiple-value fields and enumeration fields cannot be taken as alternative matching fields.
When changes are made to the configuration while the 'Match at once' service is running, the add-on reloads the index and executes matching with the new configuration.
When data referenced by foreign keys, or contained in linked tables, is modified during a matching operation, the system automatically clears and reloads the cache.
If a related table's foreign key is in a list, you cannot run the Align foreign key of merged record service on the golden, or pivot record.
The Restore from history service is not available on tables containing the DaqaMetaData group.
This release contains the following known issue related to cleansing functionality: The cleaning procedure 'Foreign key fixing' does not support multi-valued FK. It is not possible to fix a FK that is a part of a primary key.
This release contains the following known issue related to the crosswalk feature: The crosswalk function does not support matching on foreign keys.