7.1

Workflow Attributes
Workow elements process data that they receive as input parameters, and set the resulting data as
workow aributes or output parameters.
Read-only workow aributes act as global constants for a workow. Writable aributes act as a workow’s
global variables.
You can use aributes to transfer data between the elements of a workow. You can obtain aributes in the
following ways:
n
Dene aributes when you create a workow
n
Set the output parameter of a workow element as a workow aribute
n
Inherit aributes from a conguration element
Workflow Schema
A workow schema is a graphical representation that shows the workow as a ow diagram of
interconnected workow elements. The workow schema is the most important element of a workow as it
determines its logic.
Workflow Presentation
When users run a workow, they provide the values for the input parameters of the workow in the
workow presentation. When you organize the workow presentation, consider the type and number of
input parameters of the workow.
Workflow Tokens
A workow token represents a workow that is running or has run.
A workow is an abstract description of a process that denes a generic sequence of steps and a generic set
of required input parameters. When you run a workow with a set of real input parameters, you receive an
instance of this abstract workow that behaves according to the specic input parameters you give it. This
specic instance of a completed or a running workow is called a workow token.
Workflow Token Attributes
Workow token aributes are the specic parameters with which a workow token runs. The workow
token aributes are an aggregation of the workow's global aributes and the specic input and output
parameters with which you run the workow token.
Workflow Version History
Orchestrator keeps the version history for each workow, irrespective of whether it is included in the
default workow library or whether the workow is newly developed. By keeping the version history in the
database, you can compare dierent workow versions and to revert to a previous workow version.
Orchestrator creates a new version history item for each workow when you increase and save the
workow version. Subsequent changes to the workow do not change the current saved version. The
version history is kept in the database along with the workow itself.
When you delete a workow or an action, Orchestrator marks the element as deleted in the database
without deleting the version history of the element from the database. This way, you can restore deleted
workows and actions.
Chapter 2 Managing Workflows
VMware, Inc. 15