4.2
Table Of Contents
- Developing with VMware vCenter Orchestrator
- Contents
- Developing with VMware vCenter Orchestrator
- Updated Information
- Developing Workflows
- Principal Phases in the Workflow Development Process
- Accessing the Orchestrator Client
- Testing Workflows During Development
- Workflow Editor
- Provide General Workflow Information
- Defining Attributes and Parameters
- Workflow Schema
- Obtaining Input Parameters from Users When a Workflow Starts
- Requesting User Interactions While a Workflow Runs
- Add a User Interaction to a Workflow
- Set the User Interaction security.group Attribute
- Set the timeout.date Attribute to an Absolute Date
- Calculate a Relative Timeout for User Interactions
- Set the timeout.date Attribute to a Relative Date
- Define the External Inputs for a User Interaction
- Define User Interaction Exception Behavior
- Create the Input Parameters Dialog Box for the User Interaction
- Respond to a Request for a User Interaction
- Calling Workflows Within Workflows
- Running a Workflow on a Selection of Objects
- Developing Long-Running Workflows
- Configuration Elements
- Workflow User Permissions
- Validating Workflows
- Running Workflows
- Develop a Simple Example Workflow
- Create the Simple Workflow Example
- Define the Simple Workflow Example Parameters
- Create the Simple Workflow Example Schema
- Link the Simple Workflow Example Elements
- Create Workflow Zones
- Define the Simple Workflow Example Decision Bindings
- Bind the Simple Workflow Example Action Elements
- Bind the Simple Workflow Example Scripted Task Elements
- Define the Simple Example Workflow Exception Bindings
- Set the Simple Workflow Example Attribute Read-Write Properties
- Set the Simple Workflow Example Parameter Properties
- Set the Layout of the Simple Workflow Example Input Parameters Dialog Box
- Validate and Run the Simple Workflow Example
- Develop a Complex Workflow
- Create the Complex Workflow
- Define the Complex Workflow Example Input Parameters
- Create a Custom Action For the Complex Workflow Example
- Create the Complex Workflow Example Schema
- Link the Complex Workflow Example Schema Elements
- Create the Complex Workflow Example Zones
- Define the Complex Workflow Example Bindings
- Set the Complex Workflow Example Attribute Properties
- Create the Layout of the Complex Workflow Example Input Parameters
- Validate and Run the Complex Workflow Example
- Scripting
- Orchestrator Elements that Require Scripting
- Limitations of the Mozilla Rhino Implementation in Orchestrator
- Using the Orchestrator API
- Access the Scripting Engine from the Workflow Editor
- Access the Scripting Engine from the Action or Policy Editor
- Access the Orchestrator API Explorer
- Use the Orchestrator API Explorer to Find Objects
- Writing Scripts
- Add Parameters to Scripts
- Accessing the Orchestrator Server File System from JavaScript and Workflows
- Accessing Java Classes from JavaScript
- Accessing Operating System Commands from JavaScript
- Exception Handling Guidelines
- Orchestrator JavaScript Examples
- Developing Actions
- Creating Resource Elements
- Creating Packages
- Index
You created a function that calculates a time and date relative to the current time and date and generates a
Date object. A User Interaction element can receive this Date object as an input parameter to set the timeout
period until which it waits for input from the user. When the workflow arrives at the User Interaction element,
it suspends its run and waits either until the user provides the required information, or for 24 hours before it
times out.
What to do next
You must bind the Date object to the User Interaction element's timeout.date parameter. See “Set the
timeout.date Attribute to a Relative Date,” on page 44.
(Optional) Set the timeout.date Attribute to a Relative Date
You can set the timeout.date attribute of a User Interaction element to a relative time and date by binding it
to a Date object. You define the object in a scripted function.
If you create a relative Date object in a scripted function, you can bind the timeout.date attribute of a user
interaction to this Date object. For example, if you bind the timeout.date attribute to a Date object that adds 24
hours to the current time, the user interaction times out after waiting for 24 hours.
Prerequisites
n
Add a user interaction element to the workflow schema.
n
Set the security.group attribute for the user interaction.
n
Create a scripted function that calculates a relative time and date and encapsulates it in a Date object in
the workflow. See “Calculate a Relative Timeout for User Interactions,” on page 43.
Procedure
1 Click the User Interaction element in the workflow schema.
2 Click the Attributes tab for the user interaction.
3 Click Not set for the timeout.date source parameter to set the timeout parameter value.
4 Select the Date object that encapsulates a relative time and date that you defined in a scripted function and
click Select.
You set the timeout.date attribute to a relative date and time that a scripted function calculates.
What to do next
Define the external input parameters that the user interaction requires from the user. See “Define the External
Inputs for a User Interaction,” on page 44.
(Optional) Define the External Inputs for a User Interaction
You specify the information that users must provide during a workflow run as the input parameters of a user
interaction.
When a workflow reaches a user interaction element, it waits until a user provides the information that the
user interaction requires as its input parameters.
Prerequisites
n
Add a user interaction element to the workflow schema.
n
Set the security.group attribute for the user interaction.
n
Set the timer.date attribute for the user interaction
Developing with VMware vCenter Orchestrator
44 VMware, Inc.