The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
An approval, via email, by a supervisor or manager can be set up as a policy for infrastructure provisioning requests made by end users. Approvals allows your administrator to give visibility to supervisors and to manage exceptions often needed to meet business policies while automatically provisioning infrastructure. Your administrator can define two approval groups (primary and secondary). Primary or secondary approvers must approve the service request at the first or second level. Your administrator can also specify if approval is required from all users. Once a service request is created, a service request notification email is sent to the approvers. You can view all requests that require your approval, or your service requests that are pending approval from either primary or secondary approvers on the Approvals screen. Once the service request is approved, the next step, infrastructure provisioning, is initiated.
The Approvals screen displays all approved, pending, and rejected service requests and the following information for each service request:
Service Request ID
Request Type
Initiating User
Group
Catalog Name
Initiator Comments
Request Time
My Comments
My Approval Status
You can view additional details about a service request by clicking the row with the service request and clicking View Details.
If you are assigned as an approver for your VDC, pending service requests that require your approval appear on the Approvals screen.
Rejecting a pending service request in your approval list denies the request, and the request appears in your approval list as rejected.
You can cancel a pending or approved service request. Canceling the request denies the request and removes it from your approval list. The workflow for a pending approval stops in a failed state at the approval task. You can cancel an approved service request that you may want to resubmit later. If you resubmit a service request for a cancelled request that was previously approved, the workflow starts from the approval task.
You can resubmit a rejected or failed service request. A service request can fail for the following reasons:
Budget limit (if defined by your administrator) is exceeded for the group under which the VM is being provisioned.
Resource limits (if defined by your administrator) are exceeded for the group under which the VM is being provisioned.
Provisioning could fail if relevant information is not provided when creating a service request.
When a service request is resubmitted, you can choose the task in the workflow from which you want to start the service request. For example, if a service request fails in the Resource Allocation workflow, you can resubmit the service request to start from this step.
On the Approvals page, choose and approve the service request.
You can archive a service request for future use. Archiving a service request removes it from your approval list. Once you archive a service request, contact your administrator if you want to reinstate the service request.
You can add notes to a service request, to provide information for yourself, the requestor, or other approvers.
You can undo all or part of an executed workflow by rolling back a service request. You can roll back tasks that executed successfully. Exceptions include:
Some tasks are designed such that they cannot be rolled back.
Rollback can be disabled for a task within a particular workflow.
Any changes made by tasks that are not selected to be rolled back are not undone. For example, if the task for creating virtual resources is not selected, virtual resources are not removed when the service request is rolled back. If you choose to roll back an entire successful service request, all of its workflow tasks are rolled back with the exceptions of those that are disabled.
On the Approvals page, choose and approve the service request.