There are two types of tasks generated during the workflow process:
Approval Tasks: Approval tasks require the task owner to either approve or deny the business service request. There are two approval tasks generated during the workflow process: an Administrator approval task and a Sponsor approval task.
The Administrator approval task is generated for an administrator (Approver or Cloud Administrator) to provide IT approval. If the administrator approves the request, a Sponsor approval task is then generated for the Sponsor to provide financial approval.
Configuration Tasks: Configuration tasks require the task owner to complete the configuration of business service workloads. There are two configuration tasks generated during the workflow process: a pre-build configuration task and a post-build configuration task.
The pre-build configuration task occurs before the requested business service’s workloads are built, and a post-build configuration task occurs after the workloads are built. The tasks are generated for Build Administrators and Cloud Administrators.
Trigger Tasks: Trigger tasks require user input before performing an action, for example, a user can choose to immediately reboot a virtual machine as part of a change request, which could potentially lose data. Alternatively, a trigger task can be scheduled, allowing the user to delay a task to complete at a later time. For example, a user could schedule a VM reboot for midnight on a Saturday.
When a change request is made for a business service, the reboot trigger task occurs after the pre-build configuration task, and before the changes are applied to the workloads in the system build step. The trigger task is generated for the Business Service Owner and for Build Administrators and Cloud Administrators.