7.0
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- 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
Table 11. XaaS Object Types and Associated Forms
Object Type Default Form Additional Forms
Custom resource Resource details form based on the attributes
of the vRealize Orchestrator plug-in inventory
type (read-only).
n
None
XaaS blueprint Request submission form based on the
presentation of the selected workflow.
n
Catalog item details (read-only)
n
Submitted request details (read-only)
Resource action Action submission form based on the
presentation of the selected workflow.
n
Submitted action details (read-only)
You can modify the default forms and design new forms. You can drag fields to add and reorder them on
the form. You can place constraints on the values of certain fields, specify default values, or provide
instructional text for the end user who is completing the form.
Because of their different 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.
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 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.
Foundations and Concepts
VMware, Inc. 34