A component task is used to interrupt a component process until some manual intervention is performed. A task-interrupted process will remain suspended until the targeted user or users respond. Typically, component tasks are removed after the process has been tested or automated.
Like approvals, triggered component tasks alert targeted users. Alerts are associated with component-, environment-, or resource-defined user roles. Unlike approvals, component tasks can be incorporated within a component process.
The person alerted for the task can indicate that it is complete by approving the step from the request's log in Approval Requests. See Approving Requests.
Create and use tasks as follows: