fix #1045256: filtering in jdito does work again when no custom checker funciton is defined for a column

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

# Conflicts:
#	process/Email_lib/process.js

Permissions - refactoring lib, updating role, fixing detail

See merge request xrm/basic!69

Sophia Leierseder authored 5 years ago and Johannes Goderbauer committed 5 years ago

(cherry picked from commit 52870197)

Sophia Leierseder authored 5 years ago and Johannes Goderbauer committed 5 years ago

(cherry picked from commit 775617d2)

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

This has been integrated into the action to rebuild person and org duplicates

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.

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