vRealize Automation Approval Service API 7.3
Approval Service API Specification
What is the Approval Service REST API?
The approval service provides features for managing and tracking the human approval tasks associated with a service process/artifact in a provider realm. It also provides a record of the approval process when it completes.
The goal of the approval service is to provide a generic approval mechanism that any provider can use for any artifact, such as as a service or a resource action (which follows its own provider specified approval process).
Approval is agnostic to the business artifact it is attached to. There is no representation of the artifact within the approval service. The provider (client of the approval service) stores an identifier of an approval to manage the approvals associated with their artifact.
Typical Use Cases
You can use the approval service REST API to implement approval policies for your service or resource action. You can:
- Define multiple approval levels in which actions must be approved.
- Define approval policies that determine how an artifact is approved.
- Query information about the state of specified approvals and the values of data fields in schemas associated with the service or resource action.
A level of approval that you define for your service. For each level, you can specify approval criteria.
Each level supports two modes of approval:
- ANY - If any ONE of the users approves, the approval step is complete and the process moves to the next step; for example, from Level 1 to Level 2. After one approver has approved, the remaining approvers are not allowed to approve that level.
- ALL - All the approvers for the level need to approve. Each approver is assigned a workitem. The approval flow can only move on to the next step after ALL the approvers have approved.
Approval criteria are specified in a JSON string of a
Criteria should be set up based on the context that is defined by the corresponding
The properties used in the criteria expression must be those of the client side object identified by the
CatalogItemRequest client object provides an example of how criteria are specified. A
CatalogItemRequest has a criteria expression based on Request fields such as
CatalogItem, and so on, which are direct properties of the
How the Approval Service Works
Overall High Level Flow
The approval process involves a simple chain of approval steps:
- Currently, the approval service supports only a single series of approval steps.
- Each step in the sequence can contain one or more users.
- Approval flows from level1 to level2 to level3, and so on. The approvers in level2 do not receive an approval request until level1 is approved, and so on for other steps in the series.
- If approvers in ANY level reject the request, the whole approval is rejected. This essentially short circuits the approval process.
- When the final approval step is approved, the Approval instance goes into the APPROVED state.
Notes About Approval Level
- These are referred to as Level N Approval. Each step is activated in sequence, i.e., Level1 Approval is active first, and after it is done, Level2 Approval is active, and so on.
- The users in an approval step can be defined (during approval policy creation/definition) using three different methods, by referring to:
- One or more actual users (hard coding the user ID).
- One or more AD groups (static) and dynamic groups (composed of multiple AD groups and actual users).
- The users from contextual data such as $request.owner or $request.owner.manager, and so on.
- When a step is active, the users in that step are resolved, i.e., groups are expanded and contextual data expression is evaluated. The users in a step are not materialized until that step is active.
- All the users within the step are notified of the pending approval.
- If one of those users reject it, the Approval is short circuited and goes into the REJECTED state.
- A level supports two modes of approval:
- ANY - if any ONE of the users approves, then after the approval step is complete, the the process moves to the next step; for example, from Level1 to Level2. After one approver has approved, the remaining approvers are not allowed to approve that level.
- ALL - All the approvers resolved in this level need to approve. Each approver is assigned a workitem. The approval flow can only move on to the next step after ALL the approvers have approved.
Notes About Criteria Associated with a Level
- Each level has its own criteria that triggers approval from that level.
- Criteria of every level will be evaluated in sequence.
- Criteria is essentially a JSON string of a
- Criteria should be set up based on the context which is defined by the corresponding
- The properties used in the criteria expression must be those of the client-side object identified by the
typeFilter. An example is the
CatalogItemRequestclient object, whose criteria expression is based on Request fields such as
CatalogItem, and so on, which are direct properties of the
- The list of concrete Clauses are:
Related Sample Code
- vRealize Automation - Approval ServicevRealize Automation - Approval Service The approval service provides features for managing and tracking the human approval tasks associated with a service process/artifact in a provider realm. It also ...api_vra_approval vRealize Automation POSTMAN Collection
- vRealize Automation - WorkItem ServicevRealize Automation - WorkItem Service The work item service provides a standard way for services to present work items to users. It manages the life-cycle of a work item and passes events back to the ...api_vra_approval api_vra_workitem vRealize Automation POSTMAN Collection
- vRealize Automation API Samples for PostmanvRealize Automation API Samples for Postman Overview The vRealize Automation REST API provides consumers and administrators access to all services in its service catalog that support the vRealize Auto ...vRealize Automation POSTMAN CollectionDownload
Updated 6 months
- vRealize Automation - Catalog ServicevRealize Automation - Catalog Service The catalog service REST API is designed to be used by the consumers of the service catalog; for example, an end user who wants to request a catalog item would be ...api_vra_catalog vRealize Automation api_vra_composition POSTMAN CollectionDownload
Updated 1 year
- Submit a catalog item request via vRA API in PowerShellSubmits a catalog item request via the vRA API in PowerShellvRealize Automation PowerShellDownload
Updated 4 months
- vRealize Automation - NSX IntegrationvRealize Automation - NSX Integration NSX integration in vRealize Automation can help creating and configuring existing networks, on-demand NAT networks and on-demand routed networks, creating load ba ...vRealize Automation api_vra_network POSTMAN Collection
- VMware vRealize Automation PluginJenkins vRealize Automation Plugin The vRealize Automation Jenkins plugin enables Jenkins to provision vRealize Automation 7 Blueprints. Requirements Jenkins 1.58+ Java 8 to compile plugin or Java 7 ...vRealize Automation JavaDownload
Updated 2 months
- vRealize Automation - Composition ServicevRealize Automation - Composition Service The composition service allows vRA services to register application components, which the composition service manages so that they can be used in composite bl ...vRealize Automation api_vra_composition POSTMAN Collection
- vRealize Automation - Identity ServicevRealize Automation - Identity Service Identity service manages tenants, business groups (formerly named subtenants), groups (both Single-Sign-On and Custom groups), users and identity stores. It also ...vRealize Automation api_vra_identity POSTMAN Collection
- vRealize Automation - Content Management ServicevRealize Automation - Content Management Service You can use the content management service REST API to import and export content, such as blueprints, software components, and other artifacts, from vR ...vRealize Automation api_vra_content_management api_vra_composition POSTMAN Collection
- vRealize Automation - Component RegistryvRealize Automation - Component Registry Component Registry manages all services (including out-of-the-box services and services from third party solution providers) and serves as the central view for ...api_vra_component_registry vRealize Automation POSTMAN Collection
- vRealize Automation - Event BrokervRealize Automation - Event Broker The event broker provides features for managing subscriptions, event topics, events, and messages. Available Use Case Get event topics Registers or updates an Even ...vRealize Automation api_vra_event_broker POSTMAN Collection
- vRealize Automation - BrandingvRealize Automation - Branding The Branding service enables the user to customize the VRA UI header and footer. The configurable properties include logo image, company name, product name, background c ...api_vra_branding vRealize Automation POSTMAN Collection
- vRealize Automation - Management Service APIvRealize Automation - Management Service API You can use the reclamation service to query the VMs in an installation for non-usage and, if they are not in use, mark them as eligible for reclamation. ...vRealize Automation api_vra_management POSTMAN Collection
- vRealize Automation - Properties ServicevRealize Automation - Properties Service The property service provides APIs to manage property definitions and property groups. Available Use Cases Manage property definitions Manage property groups ...api_vra_properties vRealize Automation POSTMAN Collection
Updated 1 year
- vRA 7 and above prepare_vra_template.ps1Powershell script designed to deploy the needed agents on your windows template. This mimics the prepare_vra_template.sh file for linux and will deploy java, bootstrap and gugent agents from the vRA a ...vRealize Automation PowerShellDownload
Updated 1 year
- chef-client example of a bootstrap install on Ubuntu 16.04A basic example to install the chef-client via the install.sh from Chef Software. This should be noted that this only requires wget and bash, so this can work for CentOS, RHEL, debian, Ubuntu, and the ...vRealize Automation vRA BlueprintDownload
Updated 2 years