Creating component manual tasks
A component manual task interrupts a component process until manual intervention is done. To create a component manual task, add a manual step to a component process, and select a notification template.
A process that is interrupted by a manual task remains suspended until the targeted user or users respond. During new process testing, use manual tasks to test the results of steps. After testing, use manual tasks for tasks that are too complicated to automate. Remove manual tasks after testing or when processes are automated.
Similar to approvals, triggered tasks notify targeted users. Affected users can accept or reject the task by using the Work Items pane (see Responding to approval requests). Unlike approvals, component manual tasks are incorporated within a component process. Do not use a component manual task in place of an approval process. To obtain approval for an entire component, create an approval process instead of a component manual task (see Creating an approval process).
- Open a component process in the process editor.
- From the Utility Steps folder, add a Manual Task step to the process.
- In the Edit Properties window, specify
the following properties for the step:
- Specify a name for the step.
- Notification Template
- Specify a notification template. These templates map to the notification scheme that the application uses. (See Creating Notifications in a Notification Scheme.) If a scheme is not specified, the default scheme is used.
- Optionally, add one or more properties to the task. You can use these properties later in the process just like output properties from other steps.
- Who can approve this task
- Any User
- Any user can approve the task.
- Role Member By Environment
- Specify an environment role that can approve the task.
- Role Member By Application
- Specify an application role that can approve the task.
- Click Save to save the properties for the step.
- Include the manual task in the process as with any other step.
- Save the process.