Cisco Cisco Process Orchestrator 3.0 User Guide
1-20
Cisco Process Orchestrator User Guide
OL-30196-01
Chapter 1 Understanding Service-Oriented Orchestration and the Cisco Process Orchestrator
Process Orchestrator System Elements
Related Topics
Activities
Activities are the steps in a process. They are customized to perform integration with some environment.
For example, an SNMP trap send activity would have a very different UI and set of properties from an
SAP ABAP call, and these would have very different runtime characteristics as well.
For example, an SNMP trap send activity would have a very different UI and set of properties from an
SAP ABAP call, and these would have very different runtime characteristics as well.
Related Topics
Conditions
Many workflow logic elements perform tests to control execution. Conditions implement these tests. For
example, a Condition Branch can split execution to take one path if a condition exists, and another if it
does not. A While Block can iterate execution while a condition exists.
example, a Condition Branch can split execution to take one path if a condition exists, and another if it
does not. A While Block can iterate execution while a condition exists.
Conditions can also be placed on a process trigger, allowing control of situations in which the process
can run. For example, a scenario might require the process to run during two different time ranges, which
would require two triggers: one trigger with an 8am-5pm condition and a totally different trigger with a
5pm-8am condition.
can run. For example, a scenario might require the process to run during two different time ranges, which
would require two triggers: one trigger with an 8am-5pm condition and a totally different trigger with a
5pm-8am condition.
There are two basic types of conditions:
•
State conditions
State conditions evaluate some state. The Process Orchestrator provides a number of state conditions
that can be perceived as a part of the base product, but technically are part of the adapter. For
example, it provides a test to see if a variable has some value.
that can be perceived as a part of the base product, but technically are part of the adapter. For
example, it provides a test to see if a variable has some value.
•
Composite conditions
A composite condition builds a compound condition from individual conditions. It allows
combining conditions with AND logic, where all of the conditions must be TRUE for the composite
condition to be TRUE, or OR logic, where any of the conditions can be TRUE for the composite
condition to return TRUE.
combining conditions with AND logic, where all of the conditions must be TRUE for the composite
condition to be TRUE, or OR logic, where any of the conditions can be TRUE for the composite
condition to return TRUE.
Compound conditions can be used in other compound conditions to produce complex logic, such as
((X AND Y) OR (A AND B)).
((X AND Y) OR (A AND B)).
Process Orchestrator supports these types of conditions:
Condition Type
Purpose
Variable Condition
Specifies a variable to be used as the condition under which the
variable should evaluate as true.
variable should evaluate as true.
Time Condition
Specifies conditions that evaluate to true on the days in the specified
calendar and between the specified start and end time.
calendar and between the specified start and end time.