Release 4.2.5
Added a REST API endpoint that returns information about the candidate records by blocking round identified by the blocking algorithm for evaluation given a record
Enhanced the concatenation transformation function to allow for sorting of the values of the fields to be concatenated thereby increasing the effectiveness of the custom field in identifying matching records
Performed some optimizations to the blocking service to reduce the potential duplicate evaluation of record pairs by the matching algorithm
Fixed a bug where the dates associated with an entity in the UI were not being displayed properly
Fixed a bug with the import of an exported entity schema where custom fields were not being imported correctly
Fixed an issue in the creation of entity indexes where the naming convention of the indexes were causing confusion to the the database parser in the interpretation of the command
Upgraded the versions of various libraries including Artemis and GSON among others that are utilized by OpenEMPI to eliminate security vulnerabilities that have been identified
Upgraded the version of the Postgres driver to eliminate a security vulnerability present in an earlier version
Release 4.2.4
Fixed a bug with the generation of a Data Profile based on a file where the job was not completing successfully if the data file was not formatted properly
Added an option to the user profile page on the UI to allow the user to specify a blank value for the state field
Replaced the use of log4j-1 with reload4j to eliminate any concern regarding the vulnerabilities detected in log4j-1
Upgraded the version of the Postgres driver used by the application to a more recent version that is free from security vulnerabilities
...