# Conflicts:
#	entity/Communication_entity/Communication_entity.aod
#	entity/Organisation_entity/Organisation_entity.aod
#	entity/Person_entity/Person_entity.aod

# Conflicts:
#	entity/DuplicateScanner_entity/entityfields/testactiongroup/children/testduplicatescanner/onActionProcess.js

Created Fallback on creation of an merge activity, if there is no current contact id, an empty string gets used

If a merge has been successful, a new acitivity gets created on the target record of the merge
This has been implemented on Person and Organisation

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.

bugfix: new activity/task in Person_entity did use wrong addtionalLink-ids for organisation-contacts

Fixed error where if no duplicate scan result on creation of a new person could be found, the code tried to access .lenght...
Data_alias.aod: The auditSyncConfig was configured to audit itself which resulted in an error. Fixed.

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".

If duplicates have been found while saving a new contact, a notification will be shown, alerting the user