7.2
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Updated Information
- Using Scenarios
- Using the Goal Navigator
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- XaaS Blueprints and Resource Actions
- Common Components
- Life Cycle Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Extending vRealize Automation with Event-Based Workflows
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
- Index
Table 11. XaaS Object Types and Associated Forms
Object Type Default Form Additional Forms
Custom resource Resource details form based on the
aributes of the vRealize Orchestrator
plug-in inventory type (read-only).
n
None
XaaS blueprint Request submission form based on the
presentation of the selected workow.
n
Catalog item details (read-only)
n
Submied request details (read-only)
Resource action Action submission form based on the
presentation of the selected workow.
n
Submied action details (read-only)
You can modify the default forms and design new forms. You can drag elds to add and reorder them on
the form. You can place constraints on the values of certain elds, specify default values, or provide
instructional text for the end user who is completing the form.
Because of their dierent purposes, the operations you can perform to design read-only forms are limited
compared to the operations for designing submission forms.
Common Components
vRealize Automation includes several common components in addition to the service catalog and catalog
item sources such as Infrastructure as a Service and XaaS.
Notifications
You can send automatic notications for several types of events, such as the successful completion of a
catalog request or a required approval.
System administrators can congure global email servers that process email notications. Tenant
administrators can override the system default servers, or add their own servers if no global servers are
specied.
Tenant administrators select which events cause notications to be sent to users in their tenants. Each
component, such as the service catalog or IaaS, can dene events that can trigger notications, but none of
them are selected by default.
Each user can choose whether to receive notications. Users either receive all notications congured by the
tenant administrator or no notications, they do not have ne-grained control over which notications to
receive.
Some emails have links that users can use to respond to the notication. For example, a notication 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.
Foundations and Concepts
36 VMware, Inc.