6.2
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- Advanced Service Designer
- Common Components
- Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
An approval phase is a sequence of approval levels associated with a particular stage in the request. The
approval policy type defines how many phases a policy has and which stage in a request triggers a
particular approval phase. For example, an approval policy can define the following phases:
n
A preprovisioning approval phase must be complete before provisioning a requested item
n
A postprovisioning phase occurs after the item is already provisioned but before it is released to the
owner
An approval policy in the Draft status can be edited but after it is activated, it becomes read-only. A policy
with an Inactive status is also read-only.
Notiļ¬cations
You can send automatic notifications for several types of events, such as the successful completion of a
catalog request or a required approval.
System administrators can configure global email servers that process email notifications. Tenant
administrators can override the system default servers, or add their own servers if no global servers are
specified.
Tenant administrators select which events will cause notifications to be sent to users in their tenants.
Each component, such as the service catalog or IaaS, can define events that can trigger notifications, but
none of them are selected by default.
Each user can choose whether to receive notifications. Users either receive all notifications configured by
the tenant administrator or no notifications, they do not have fine-grained control over which notifications
to receive.
Some emails have links that users can use to respond to the notification. For example, a notification
about a request that requires approval can have one link for approving the request and one for rejecting
it. When a user clicks one of the links, a new email opens with content that is automatically generated.
The user can send the email to complete the approval.
Branding
Each tenant can change the appearance of the vRealize Automation console.
System administrators control the default branding for all tenants. A tenant administrator can change the
branding of the portal including the logo, the background color, and the information in the header and
footer. If the branding for a tenant is changed, a tenant administrator can always revert back to the
system defaults.
Foundations and Concepts
VMware, Inc. 38