Nintex workflow provides a feature to delegate your tasks for a period of time, i.e. when you go on leave. This feature can be enabled by enabling long term delegation in through the Nintex Global Settings in Central Administration.
One issue with this is if assigned approvers in workflows do not delegate their tasks prior to becoming unavailable, the process will stall until the task is delegated by a site collection administrator or the approver returns to the office.
Options
To address this issue, there are two options to consider:
-
Ad-hoc Delegation
The individual tasks will need to be manually delegated by a site collection administrator.
Advantages
Advantages of this option would include:
- This can be a feasible solution if requests to a site collection administrator or site owner to delegate tasks occur infrequently and in small numbers.
Disadvantages
The following disadvantages can include:
- If a large amount of tasks are required to be delegated, this can be a time consuming process for the site collection administrator.
- Delegates may be required to submit a Help Desk request if they require a task to be delegated to them and the assigned Approver is not present to do so.
-
Long Term delegation
There is the ability to turn on Long Term delegation through the Nintex Global Settings in Central Administration , which will allow a site owner to delegate on behalf of others for a set period of time for sites they have full control access to only.
Advantages
The Advantages to this option would include:
- This can reduce the burden on system administrators as delegates with the correct permissions can set up long term delegation for any required tasks without the need to request assistance.
Disadvantages
The following disadvantages can include:
- Enabling Long Term delegation allows the site owner to turn on long term delegation on behalf of another issue. This could potentially result in a site owner delegating tasks for a senior manager (for example) and then approving these tasks without the manager being aware. Considerations
- Implementation of this solution involves an IIS reset, therefore would cause an outage to your SharePoint environment.