FourEyesPrincipleHandler

This ActionHandler is used to make sure that two different tasks are not completed by the same user (e.g. approvals). The ActionHandler must be set on NODE-LEAVE of the second activity and the other activity name is used as a parameter. It is possible to add this ActionHandler multiple times on the same activity so that more than two activities can be checked.

Class

com.dooris.bpm.actionhandler.FourEyesPrincipleHandler

Reference	Attribute	Description

Reference	Attribute	Description
1	`FourEyesPrincipleHandler`	The FourEyesPrincipalHandler modal opens, and it displays all the fields it contains, providing a clear view of the required information.
2	Event Name	The event name field should display the name of the actionhandler you intend to complete next.
3	Description	Enabling the description toggle button will reveal a brief overview of the modal and its functionality.
4	`activity` MANDATORY	The name to be entered in the ‘Name of the Activity’ field should be that of the activity (ie. Fill Employee Information) that makes sure that the current task (i.e. Account Setup) is not finished by the same person who did the other task (Fill Employee Information).
5	`checkAllLoops` OPTIONAL	The (checkAllLoops) which is optional and default false. if set to true, the actionhandler checks all loops of the given activity, and if one of those tasks was finished by the same user, it throws the error.
6	Save Changes	The ‘Save’ button enabled and saved the changes

The error message is shown when the user is unable to complete the mentioned task after enabling the Foureyesprinciplehandler. This means that the same user that completed the task “Fill Employee Information” and tries to complete also Account Setup.