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

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

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.

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

If a person is added, a scan for duplicates is triggered automatically. if a matching cluster exists the new record gets added, otherwise a new cluster gets created
The field, which is currently used by the demo duplicatescan (firstname) is now another type because the phonetic matcher creates seemingly wrong searchresults. If the scan for duplicates or the indexsearch results in seemingly unrelated results, set the indexFieldType to TEXT_NO_STOPWORDS.

refactorings

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)