Skip to content
Snippets Groups Projects
  1. Nov 14, 2019
  2. Oct 08, 2019
    • David Büchler's avatar
      New processes to run the scans for duplicates serverside have been created. · 6cebec77
      David Büchler authored
      RebuildAllDuplicateCaches_serverProcess.aod takes both person and organisation scanner (currently hard coded) and runs them. This is ought to be executed via the manager/other serverside ways
      RebuildDuplicatesCache_serverProcess on the other hand should be used via code because this process expects the filterName and TargetEntity as parameters. The usages are commented out for the time beign becaus of incompatibilities in the process.execute* methods...
      If a person or organisation is merged, the standardcommunication ways of the old record are reset to "no standard".
      6cebec77
  3. Oct 07, 2019
  4. Oct 02, 2019
  5. Sep 27, 2019
    • David Büchler's avatar
      The function ScanForDuplicates has been refactored and is now much more easy... · c664b39b
      David Büchler authored
      The function ScanForDuplicates has been refactored and is now much more easy to use because it does much more stuff inside to have an easier api.
      "RebuildDuplicatesCache" and "ScanForDuplicates" have been refactored.
      The fields used in the prefilter don't have to be configured manually by the user. Instead, the fields defined by the prefilter now get added automatically to the list of fields to be used. In the case, that the field has been added via the users config anyways, it doesn't get added by code to ensure that each field is mentioned exactly once.
      To reflect these changes, the javadoc including the example of ScanForDuplicates and RebuildDuplicates has been updated.
       Until it's possible to load values from a consumed entity dynamically via code, the possibility to select entity fields from consumed entities via ui has been removed. See ticket #1044577. Now only "native" fields directly from the base entity can be selected.
       Since the entity fields are now used in the configuration of the duplicate search, no db fields have to be configured any more. The field has been removed from liquibase
      c664b39b
  6. Sep 25, 2019
    • David Büchler's avatar
      The Cache rebuilding has been changed. The values to check for duplicates are... · ca57d1a0
      David Büchler authored
      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
      ca57d1a0
  7. Sep 24, 2019
Loading