Updated version of DuplicateScanner_lib

Changed liquibase files accordingly.

Temporarily added view to Organisation which calculates duplciates on each main-view-open and doesnt cache the results. Same as on Person

Temporarily added a new Tab in the Persons main view. It calculates the duplicates for the specific person on the fly. Results arent cached.

Removed the block size configuration from the client. Default value is 5000. All scanners now use the same value, it can be changed via designer custom setting in the preferences
2 fields in the person entity have been added, now the firstname and the lastname fields exist as phonetic and text_no_stopwords
Refactorings

- neue Projekt-Version 6.0.2
- neue EntityModel-Version 1.3.12
Cherry Pick from stable/2019

It's now possible to have a scanner configuration without any prefilters. No threshold logic is applied, only the configured fields are used to search.
On the other hand is it now possible to have a scanner with only a prefilter.

New field BLOCK_SIZE which specifies the bulk size of data which gets loaded. This is used in the case of a cache rebuild, the data to scan for duplicates gets loaded in the thru BLOCK_SIZE specified size.

Feld DB_FIELD_NAME removed
Created fields for defaultvalues city,zip,... to use in duplicatesearchconfig
Custom fields added in subProcess to have them added to the index

(cherry picked from commit 42dd4194)

S.Listl authored 5 years ago and Sebastian Listl committed 5 years ago

(cherry picked from commit caac232e)

S.Listl authored 5 years ago and Sebastian Listl committed 5 years ago

(cherry picked from commit c708b72d)

The Cache rebuilding has been changed. The values to check for duplicates are now loaded using the entities api instead of pure sql. If the cache for all duplicates of a scanner gets rebuilt, it's now done in blocks. This ensures that even while wokring on huge recordsets, the ressources are enough. It sure may take some time to check huge recordsets...
The flag "Use external Webservice" has been removed from the view because no native api to a duplicate scanning service exists, therefore this is unnecessary right now. The config of the resultfields has been removed aswell, if no external service is used, it's enough to work with the id which is always in the index's response.
The configuration of the indexfields has been changed, no manual connection between entity and db field is necessary because no sql is used any more. Instead, the fields can be selected via dropdown which offers the entity fields to select.
Some refactoring
Changes on the docks to reflect the changed datastructure of some arrays