4.1

Table Of Contents
Table 2-5. Workflow Input Parameter Properties (Continued)
Parameter Property Parameter Type Description
Select as Any parameter type obtained from a
plug-in
Use a list or hierarchical list selector to
select the parameter.
Default value Any Default value for this parameter.
Custom validation OGNL scriptable validation If the OGNL expression returns a string,
the validation shows this string as the
text of the error result.
Auto start Boolean Starts the workflow automatically.
Mandatory input Boolean Makes this parameter mandatory. The
workflow will not run without it.
Data binding Any Binds to a property that you have
already defined in another parameter.
Authorized only Any parameter type obtained from a
plug-in
Only authorized users can access this
parameter.
Multi-lines text input Any Allows users to enter multiple lines of
text in the input parameters dialog box.
Predefined Constant Values for OGNL Expressions
You can use predefined constants when you create OGNL expressions to obtain dynamic parameter property
values.
Orchestrator defines the following constants for use in OGNL expressions.
Table 2-6. Predefined OGNL Constant Values
Constant Value Description
${#__current}
Current value of the custom validation property or matching
expression property
${#__username}
Username of the user who started the workflow
${#__userDisplayName}
Display name of the user who started the workflow
${#__serverUrl}
URL containing the IP address of the server from which the
user starts the workflow
${#__datetime}
Current date and time
${#__date}
Current date, with time set to 00:00:00
${#__timezone}
Current timezone
(Optional) Requesting User Interactions While a Workflow Runs
A workflow can sometimes require additional input parameters from an outside source while it runs. These
input parameters can come from another application or workflow, or the user can provide them directly.
For example, if a certain event occurs while a workflow runs, the workflow can request human interaction to
decide what course of action to take. The workflow waits before continuing, either until the user responds to
the request for information, or until the waiting time exceeds a possible timeout period. If the waiting time
exceeds the timeout period, the workflow returns an exception.
The default attributes for user interactions are security.group and timeout.date. When you set the
security.group attribute to a given LDAP user group, you limit the permission to respond to the user
interaction request to members of that user group.
Chapter 2 Developing Workflows
VMware, Inc. 41