The new delegation feature is useful however, we are aren't able to enable it due to some sensitive use cases.
Some tasks/approvals can be sensitive in nature and should only be directed to the intended stakeholder where we wouldn't want the task/approval being generically delegated to someone else.
I.e. if there is a employee contract or payroll type task form that gets assigned to an employee, if the current delegation function is enabled, this will route through to another employee that will have access to possible personal information.
We are currently running more of a custom built function that allows us to pick and choose which tasks inherit a delegation rule:
1. Employees can fill out a delegation form
2. Form writes to an Azure SQL data source that stores delegation information incl. start and end dates
3. Depending on the workflow, an action set is implemented before a particular task is assigned to query this Azure SQL data source to determine if there is a delegation in place based on the current date being between start and end date for the delegation record and if so, will add the delegate to the task assignment
Would be great to see this flexibility on task and workflows OOTB.
Thanks for your consideration,
RB