If no fields could be found in the pattern (or no pattern exists at all) no search for duplicates is excecuted any more in the selfDuplicates consumers in Person and Organisation

(cherry picked from commit ab461253)

(cherry picked from commit c16596fd)

(cherry picked from commit 8ad05a25)

#1048321 Berechtigungen greifen nicht bei Entity-Actions - fixed display bug in combination with field permissions

#1048321 Berechtigungen greifen nicht bei Entity-Actions - fixed a bug where creating permissions on entity actions was not possible

Reorganized changes in the duplicates related liquibase files. The files in folder 2019.2.1 have been reset to the version before the change from commit 50be8ae4 which is the same as in 2019.3.1.
Those changes have been moved to drop and alter liquibase scripts inside the folder 2019.3.2/Duplicates. Now an update from 2019.3.1 -> 2019.3.2 creates the correct liquibase structure.

Temporary Fix. When using dynamic(No fieldname as string(vars.get("$field.contactid")), instead automatic calling e.g. in a loop) vars.get on an entity field the static code analysis cant recognize that those fields are used. The values of those fields wont be loaded and thus not be available. To achieve a temporary fix, a manual call of get of the desired field will help.

[Projekt: Entwicklung - Neon][TicketNr.: 1048209][Telefonie: Ausgehender Anruf löst Benachrichtigung für eingehenden Anruf aus]

Removed all loggings
Changed the constraint on nullable=false on Column CLUSTERID in unrelatedDuplicates. This is necessary because of the live view of the duplicates. If the duplicates arent determined beforehand and sorted into clusters, the creation of a unrelated relation would fail because the used duplicate is not in a cluster

In the selfDuplicatesUncached consumer the parameter "ExcludedContactIds" is now filled.  All relations defined as "unrelated" are now excluded. This is because the duplicate list is now a live view instead of the cached one.

Consumer of uncached duplicates doesnt load all entity fields via project.getstructure, instead it only loads the fields mentioned in the configurated pattern