5.5

Workflow Attributes
Workflow elements process data that they receive as input parameters, and set the resulting data as
workflow attributes or output parameters.
Read-only workflow attributes act as global constants for a workflow. Writable attributes act as a
workflow’s global variables.
You can use attributes to transfer data between the elements of a workflow. You can obtain attributes in the
following ways:
n
Define attributes when you create a workflow
n
Set the output parameter of a workflow element as a workflow attribute
n
Inherit attributes from a configuration element
Workflow Schema
A workflow schema is a graphical representation that shows the workflow as a flow diagram of
interconnected workflow elements. The workflow schema is the most important element of a workflow as it
determines its logic.
Workflow Presentation
When users run a workflow, they provide the values for the input parameters of the workflow in the
workflow presentation. When you organize the workflow presentation, consider the type and number of
input parameters of the workflow.
Workflow Tokens
A workflow token represents a workflow that is running or has run.
A workflow is an abstract description of a process that defines a generic sequence of steps and a generic set
of required input parameters. When you run a workflow with a set of real input parameters, you receive an
instance of this abstract workflow that behaves according to the specific input parameters you give it. This
specific instance of a completed or a running workflow is called a workflow token.
Workflow Token Attributes
Workflow token attributes are the specific parameters with which a workflow token runs. The workflow
token attributes are an aggregation of the workflow's global attributes and the specific input and output
parameters with which you run the workflow token.
Workflow Version History
Orchestrator keeps the version history for each workflow, irrespective of whether it is included in the
default workflow library or whether the workflow is newly developed. By keeping the version history in the
database, you can compare different workflow versions and to revert to a previous workflow version.
Orchestrator creates a new version history item for each workflow when you increase and save the
workflow version. Subsequent changes to the workflow do not change the current saved version. The
version history is kept in the database along with the workflow itself.
When you delete a workflow 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
workflows and actions.
Chapter 2 Managing Workflows
VMware, Inc. 15