As a cloud administrator, you must design resource approval workflows depending on the business requirements. When you design a resource approval workflow, you must consider the levels of approval, applicable organizations, types of resources, and user role of the approver at each approval level.
Figure-1 shows the resource approval workflow for an organization. In this workflow, common users are applicants, the organization administrator is the level-2 approver, and the cloud administrator is the level-1 approver.
Figure-1 Example of resource approval workflow design
The following information describes how the workflow system works:
Service request—A common user creates a resource approval workflow to request resources. The system provisions the requested resources as services after the request is approved by all levels of approvers.
Workflow status notification—The system sends a notification to the approver at a level when the workflow moves to that level. When the approver approves or rejects the request, the system sends a notification to notify the applicant of the result. The system sends the notification via email, SMS, WeChat, or system messaging, depending on the configuration.
Workflow approval—The approver at each level reviews the request, and then approves or rejects the request. If the request is approved, the system provisions the requested service. If the request is rejected, the system notifies the applicant of the result.