Task Assignment
Business analysts and developers can control the distribution of tasks based upon both static and dynamic information associated with the task type. For example:
One example of a static task attribute is the task type itself; suppose a task type is named Setup_Computer, and is used to ensure that a computer is set up and ready for a new employee. In this case, all tasks started from this task type can be assigned to the IT Support group.
An example of a dynamic task attribute is an order amount. Each time an order approval task is triggered in an automated process, the order amount is likely to be different. In this case, orders over a certain amount can be assigned to a specific role.
A task type can also be designed to enable a My webMethods user to assign a task to another user, group, or role, or to delegate a task to another user. Some other key points about task assignment:
Each task instance contains a list of assigned principals (users, groups, or roles). The task may be assigned to more than one principal at a time or not assigned to anyone at all.
Conditional assignments (assignment rules) associated with the task type can control when and to whom a task is assigned. Also, a task instance can be assigned or re-assigned manually from the Task List Management page.
The owner of the task is the user who started (queued) the task. The task owner is always implicitly assigned to the task
Tasks can also be delegated to users with automatic scheduled delegations or manually from the My Inbox or Task List Management pages. Each task instance tracks who tasks are delegated from and to whom they have been delegated.