Hi, Has anyone created a solution that allows for delegation of tasks?

Out of my experience and to add to other valuable suggestions, I would like to put forward few suggestions from the areas (so far I remember) where the chances of reassignment of tasks to the user (who has set his status to unavailable) occur :

1. What if the task is assigned using OOTB functionality 'Reassign Task' available in the left hand pane? For instance let's say an user has updated his availability status and alternate assignees. But if a reassignment is made by an other User in the system (to the user who has set his status to Unavailable) in the places where 'Reassign Task' is available in the left hand pane, I guess we don't have a control over this feature, neither in case of picker list nor in case of assignment(i.e. we can't capture the reassignment event and take an action accordingly). So still some tasks can be seen in the user's task list who has set his status to unavailable by using the Actions built by us.
Solution: A batch process against the unavailable users to check if they have tasks could be one of the solutions.
2. What if the task is assigned using OOTB functionality 'Reassign' available in the portal report? I guess we don't have a control over this feature, neither in case of picker list nor in case of assignment(i.e. we can't capture the reassignment event and take an action accordingly). Users who work on the Production support/ or the Super Users who takes care of the task delegations should have a knowledge that they should check the objects which lets them know about a User's status so that task reassignment is made carefully. Else this may lead to the tasks being assigned to the user irrespective of the status set by him.
Solution: Probably by educating the User about the entities that stores availability of the User or forcing the Users to work on a common SAIL interface which excludes the unavailable users in the pick list and thereby assigns the tasks to right person.
3. What about an user interface (SAIL interface (Tempo Tasks, Tempo Reports, Task Reports, Record Dashboards) or task forms) that re-assigns the tasks by using the Users available in the pickers? I guess we need to implement a platform level check in these cases so that the the User picker component excludes the users by making necessary checks against the objects that stores the availability status of the Users.
Solution: By implementing a check which is carried across the platform in case of User pickers

Out of my experience and to add to other valuable suggestions, I would like to put forward few suggestions from the areas (so far I remember) where the chances of reassignment of tasks to the user (who has set his status to unavailable) occur :

1. What if the task is assigned using OOTB functionality 'Reassign Task' available in the left hand pane? For instance let's say an user has updated his availability status and alternate assignees. But if a reassignment is made by an other User in the system (to the user who has set his status to Unavailable) in the places where 'Reassign Task' is available in the left hand pane, I guess we don't have a control over this feature, neither in case of picker list nor in case of assignment(i.e. we can't capture the reassignment event and take an action accordingly). So still some tasks can be seen in the user's task list who has set his status to unavailable by using the Actions built by us.
Solution: A batch process against the unavailable users to check if they have tasks could be one of the solutions.
2. What if the task is assigned using OOTB functionality 'Reassign' available in the portal report? I guess we don't have a control over this feature, neither in case of picker list nor in case of assignment(i.e. we can't capture the reassignment event and take an action accordingly). Users who work on the Production support/ or the Super Users who takes care of the task delegations should have a knowledge that they should check the objects which lets them know about a User's status so that task reassignment is made carefully. Else this may lead to the tasks being assigned to the user irrespective of the status set by him.
Solution: Probably by educating the User about the entities that stores availability of the User or forcing the Users to work on a common SAIL interface which excludes the unavailable users in the pick list and thereby assigns the tasks to right person.
3. What about an user interface (SAIL interface (Tempo Tasks, Tempo Reports, Task Reports, Record Dashboards) or task forms) that re-assigns the tasks by using the Users available in the pickers? I guess we need to implement a platform level check in these cases so that the the User picker component excludes the users by making necessary checks against the objects that stores the availability status of the Users.
Solution: By implementing a check which is carried across the platform in case of User pickers