Delegation Overview

A key concern for Executives is ensuring their responsibilities are appropriately delegated in their absence. OneList allows managers to maintain their own delegation (or substitution) rules. These are often required during periods of vacation absence, for example.

Importantly, OneList ensures that delegations activated in OneList are synchronised back to the originating source systems. Where a source system supports scenario-based delegation, individual workflow scenarios can be delegated. If the source system workflow does not support fine-grained delegation (substitution) rules, all approval scenarios handled by that source system will need to be redirected to the delegate (substitute). The delegations micro-app lists both outbound and inbound delegations.

Delegation Rules

The following delegation rules are available within OneList:

• Time based rule – this rule can be configured to specify the maximum delegation duration.
• Required claims rule – this rule can be configured to ensure that the delegate has suitable authorisation claims.
• Delegation chain rule – this rule can be configured to specify the maximum length of a delegation chain eg if persona A delegates to B, and B delegates to C, we have in effect set-up a 2-link delegation chain, and may result in unintended delegation of authority by the delegator
• Reporting line rule – this rule can be configured to specify the reporting relationship between the delegator and delegate eg you can enforce upward delegation only.
• Inbound limit rule – this rule can be configured to specify a limit on the number of delegators that can assign tasks to a single delegate eg your delegation policy could be that any person can only be the assigned delegate of no more than one other person.
• Reason code rules – this rule can be configured to provide the list of delegation reasons, and specify which reason codes require additional explanation.
• Custom rule - using this rule, custom delegation logic can be specified (within constraints).