This function enables a user to define delegates, in other words, users likely to:

  • replace them in signature processes when they are not available.
  • receive a copy in signature processes.
  • exceptionally sign in their place.

Prerequisite

See also Refer to documentation Implementation

Screen management

Entry screen

The following elements are entered in this screen:

  • in the header, the code of the user for whom delegates need to be defined.
  • on each line, a rule defining a delegate.

The order in which the delegates are defined is taken into consideration when searching a delegate for a Workflow rule that needs to look for the first available one.

Block number 1

User code (field USER)

It corresponds to the code of the user for whom delegates are defined.

Email address (field USEREML)

The messaging address of the previously entered user is displayed for information purposes.

Grid

Delegate no. (field NUMDEL)
User delegate (field USRDEL)

It corresponds to the code of the user who receives the delegation for the main user.

Type (field NATURE)

When this field is entered, the delegate defined on the line can only be taken into account if the Workflow event to be processed has a nature equal to the value of the field.
Email address (field USREML)

The messaging address of the previously entered user is displayed for information purposes.

Type of delegate (field TYPDEL)

This field can take three different values:

  • Copy for information only: the user will receive notifications sent to the main user, but they will have no signature authority.
  • With signature authority: a delegate of this type can sign instead of the main user. It should be noted that if there are several delegates of this type, and if, according to the rule, a Workflow notification should be sent to all these delegates, only the first one having decided to sign will be able to do so (the other delegates will be informed that the notification has already been signed).
  • Exceptional: a delegate of this type does not receive the notifications of the main user, but they can display the notifications of the user for whom they act as delegates by accessing the workbench and selecting the code of the main user. They are then in a position to sign in their place. Usually, an exceptional delegate is a hierarchical superior who is authorized to view the pending elements of their subordinates in order to sign for them.
Validity start date (field VLYSTR)

When a delegation is temporary, the start date of the delegation is entered here. If this field is left empty, the delegation is valid as early as it has been entered.
Validity end date (field VLYEND)

When a delegation is temporary, the end date of the delegation is entered here. If the field is not entered, the delegation is not limited in time.

Error messages

The only error messages are the generic ones.

Tables used

See also Refer to documentation Implementation