Page Comparison

...

...

Task Type	Success	Failure	Success/Failure	Step Condition(s)	Variable	Exit Code(s)
Workflow
Linux/Unix
Windows
IBM i
z/OS
Universal Command
PeopleSoft
SAP
File Transfer
Manual
Timer
SQL
Stored Procedure
Email
Web Service
Recurring
Task Monitor
Agent File Monitor
Remote File Monitor
System Monitor
Variable Monitor						Application Control
Email Monitor
Universal Monitor							Email Monitor
z/OS Monitor
Application Control
Universal

...

The status of the tasks in the conditional paths leading to the immediate predecessor tasks do not affect whether or not the successor tasks will run. All tasks leading to an immediate predecessor tasks do not have to have run in order for the successor task to run.

...

Specifying a Condition Expression

...

In the Workflow Editor, you can specify a Condition Expression for the direct predecessor dependencies of a Task vertex.

...

(Task A is Success, Finished or Skipped) and ((Task B is Success, Finished or Skipped) or (Task C is Success, Finished or Skipped))

Condition Expressions

A

...

Condition Expression consists of conditions and/or subexpressions joined by a logical operator.

Valid logical operator values are:

• All Satisfied (And)

• Any Satisfied (Or)

The

...

Condition Expression tree will always have a root node for the top-level expression. The root node cannot be deleted. By default, the root node will have the vertex’s predecessors as children and the logical operator will be set to “All Satisfied”. This represents the default behavior prior to UC 7.7.0.0.

Conditions

You can copy a condition by clicking the Image Modified icon if you need to include it in more than one subexpression.

You can delete a condition by clicking the Image Modified icon. Prohibited if last remaining condition for the predecessor.

You can drag a condition under a new subexpression to make it a child of the subexpression.

You can drag a condition to a change its position.

Subexpressions

You can add a subexpression by clicking the Image Modified icon.

You can delete a subexpression by clicking the Image Modified icon. Prohibited if the subexpression has children.

Clicking the Image Modified icon on a condition will insert the subexpression below the condition.

Clicking the Image Modified icon on a subexpression will add the subexpression to the end of the children list.

You can drag a subexpression under a new subexpression to make it a child of the subexpression.

You can drag a subexpression to a change its position.

Cluster Broadcast

There are 3 scenarios to consider whenusing cluster broadcast.

1. Task with cluster broadcast.

2. Predecessor task with cluster broadcast.

3. Task and predecessor task with cluster broadcast.

Task With Cluster Broadcast

In the following Workflow task, WT1 is the task with cluster broadcast.

Image Added

The Condition Expression for WT1 is shown below.

Image Added

After launching the Workflow task, 2 dynamic vertices will be generated for WT1 as shown below since there are 3 agents in the cluster.

Image Added

When launching the Workflow task, the server will copy the Condition Expression to the dynamic vertices when they are created. All 3 vertices for WT1 should have the following Condition Expression.

Image Added

Predecessor Task With Cluster Broadcast

In the following Workflow task, WT1 is the predecessor task with the cluster broadcast.

Image Added

The Condition Expression for MT1 is shown below.

Image Added

When launching the Workflow task, the server will modify the Condition Expression for MT1 to insert a condition for the dynamic vertices wherever the original vertex is specified. Since dynamic vertices have a negative vertex ID, it is easy to identify them when viewing the Condition Expression.

Image Added

The Condition Expression for MT1 should include original vertex and the dynamic vertices for WT1 under the subexpression.

Image Added

Task and Predecessor Task With Broadcast Cluster

In the following Workflow task, WT2 is the task with the cluster broadcast and WT1 is the predecessor task with cluster broadcast.

Image Added

WT1 has the default Condition Expression shown below.

Image Added

The Condition Expression for WT2 is shown below.

Image Added

Launching the Workflow task, results in the following.

Image Added

All the WT1 vertices should have the default Condition Expression.

Image Added

All the WT2 vertices should have the following Condition Expression. The Condition Expression will be copied from the original WT2 vertex to its dynamic vertices and modified to add the dynamic vertices of WT1.

Image Added

Inheritance

Condition Expressions are defined against direct dependencies. Leave the Condition Expression as All Satisfied (default) to keep the dependency evaluation behavior unchanged.

The predecessor dependencies of a Skipped vertex in a Condition Expression are not applicable if a Condition Expression is specified as anything other than All Satisfied (default), specifically, when a vertex specified in the Condition Expression is Skipped, this is equivalent to the vertex being Success or Finished with respect to Condition Expression evaluation.

An example is provided below.

Image Added

Image Added

Image Added

In the example above, if you need to be able to skip B and still inherit the dependencies of B, you can add a NOOP task (i.e. Timer 0) between B and E, accordingly.

Image Added

Image Added

...

Saving/Updating a Workflow

Click the  icon.

Info

The Controller checks if other users have made changes before updating the workflow. If other modifications were made, a dialog box will appear, giving you options to proceed with the update and overwrite the modifications, cancel the update and return to the workflow editor, or cancel and discard your changes. The Automatically Create Versions system property must be true for the Controller to check for changes made by other users.

Switching Between Workflows

...