Orchestrations are created in
They are containers for design elements such as orchestration workflows.
The primary purpose of an
orchestration workflow is to enable the use of
Web services for coordinating the interaction between an
application workflow and one or more external systems. This
lets the application workflow present data that can be exchanged and modified
in these external systems. Orchestration workflows can also perform
modifications on the data that flows within the application workflow.
Note: Orchestration workflows are used to automate processes, while
application workflows are generally manual processes for users. Typically,
users never see a process controlled by an orchestration workflow, but they
must interact with an application workflow.
An orchestration workflow is an arrangement of control flow structures,
Web services, and data elements.
- Control flow structures enable an orchestration workflow to make
calculations, decide between two possible sets of instructions, handle
exceptions, and so on. In
these structures are known as
steps, and they are listed on the
Step Palette of the orchestration workflow
- Web services can be called by means of the
Service step, which is also listed on the
Step Palette. Web services let orchestration
workflows query and update data in application workflow items and in external
- Data elements include data sent with the
event, data expected by or returned by a Web service, and
working data created for temporary use during the execution of an orchestration
workflow. Data elements are mapped in the step Property Editor.
Copyright © 2007–2016 Serena Software, Inc. All rights reserved.