Task Redirection:
Allows a Task to be directed to another User on the system. This entity also allows task allocation to be blocked for a specified User on the system.
This table allows a Task to be redirected from the User that they should normally be assigned to, to another User on the system
The records on this table may also stipulate that task allocation is blocked for a specified User on the system.
For task redirection, the redirect from user specifies the name of the user that the tasks will be redirected from while the redirect to user specifies the name of the user that the tasks will be redirected to. A start and end date time is specified to each task redirection record during which the tasks will be redirected. This also means that task redirections can be set up only for future dates.
For task allocation blocking, the redirect from user specifies the name of the user that the allocation of tasks will be blocked for. In this instance, a start and end date time is specified to each task allocation blocking record during which no tasks will be allocated to that User.
Example The following is an example of task redirection.
A User John Walsh has put in a request for annual leave for a specified week. His supervisor User Ronan Rooney then sets up a task redirection record for this specified period.
The start date time for the task redirection period is the first day of User John Walsh's specified week of annual leave. The end date and time is the last day of the specified week of annual leave.
The supervisor also specifies that the Task that were to be assigned to User John Walsh will be assigned to User Peter Johnson during this week.
During the period of time specified by the task redirection record, the Workflow Engine will assign any Task that were to be assigned to User John Walsh to User Peter Johnson.
The following is an example of task allocation blocking.
A User Peter Prior has been on sick leave for a week. His supervisor User Ronan Rooney realizes that there are now too many tasks assigned to Peter and sets up a task allocation blocking period to allow Peter to catch up with his workload.
The start date time for the task allocation blocking period is the current date and time. Ronan Rooney specifies that it should take Peter four days to catch up with his workload and so specifies the end date and time for the allocation blocking period to be four days from the current date and time.
During the period of time specified by the task allocation blocking record, the task allocation assignment algorithm will not allocate any tasks to Peter Prior. Once the end date and time of the task allocation blocking period expires, tasks will be allocated to User Peter Prior as normal.
|