Conditions Tab

IF workflows process various tasks depending on the conditions that you have specified. The START node includes the conditions that are defined in its properties. After the START you see two parallel branches in which you can add any executable objects of your choice. These branches are referred to as True and False branches. It depends on the condition(s) that should be fulfilled whether the True or the False branch will be processed. Both branches lead to the END object.

Overview
Defining Conditions
List of Statements to Build Conditions
- CONDITION Statements (IF)
- ACTION Statements (THEN)
- FINALLY Statements (FINALLY)

Overview

The structure is predetermined and cannot be changed. This means that objects can only be added to the True and Else lines and are arranged in series. You cannot create new branches or draw individual lines. For this purpose, and if you need more complex structures, you must embed other workflows.

IF workflows can include any executable object except Schedules. They can also include other IF workflows.

However, you cannot use external dependencies within them.

The tasks of the branch that should run (True or False) will only be activated and processed when the conditions have been evaluated. The tasks of the other branch are not processed. They appear in white and obtain the status UNPROCESSED within the workflow. No activities are created and no RunID is assigned to the tasks that are not processed.

Defining Conditions

To define conditions for an IF Workflow:

Right-click the START node
Select Properties
Open the Conditions tab.

The Condition tab can be used to determine the branch (True or False) that should run plus the time at which it should run. The final action RUN PATH ends the evaluation process and starts the True or False branch depending on what you have specified.

You also define various conditions and actions here. They are processed when the workflow starts before the subordinate tasks are processed.

The Condition tab is similar to the Preconditions and Postconditions tabs of STANDARD Workflows. For a detailed description on how to add conditions and actions and how to work with the conditions editor please see Preconditions, Postconditions, Conditions .

Important Considerations

The workflow aborts if the Condition tab does not include a final action.
You can define actions that are not included in a condition, which means that they will always be processed.
The Workflow activation report contains detailed information on the processes and results of your definitions here.

List of Statements to Build Conditions

There are three sets of predefined statements that you can use to build your conditions:

Condition statements, which are the basis of IF statements in your task preconditions and postconditions.
Action statements, which are the basis of THEN statements.
Finally statements.

Each statement is a sentence with placeholders for parameters. You specify the values for the parameters to describe the conditions or actions that you need.

CONDITION Statements (IF)

Condition	Description	Parameters
CHECK ACTIVITIES	Checks the number of times that an object has run with a particular status.	TASK=Name or alias of the task OPERATOR=Comparison operator (>, <, =, etc.) COUNT=Number of runs STATUS
CHECK CONNECTION	Checks whether there is a connection to a machine or a system.	CONNECTION=Connection object AGENT
CHECK FILE	Checks whether a particular file exists.	FILENAME CONDITION=Exists/Does not exist AGENT The value "*OWN" uses the task's agent(if available). LOGIN=
CHECK HISTORY	Checks whether the last run of a task has ended with a particular status in a particular time span.	DAYS TIME TASK=Object name of the task STATUS
CHECK PROCESS	Checks whether a particular process runs on a machine.	PROCESS AGENT LOGIN=Login object CONDITION
CHECK CURRENT TIME	Checks whether a certain point in time lies before or after the current (physical) point in time. The task time zone is used.	CONDITION=Before/After TIME (HH:MM)
USER DEFINED	Compares two values of your choice.	VALUE 1 OPERATOR=Comparison operator (>, <, =, etc.) VALUE 2

ACTION Statements (THEN)

Action	Description	Parameters
DELETE ENTRY FROM VARIABLE	Removes a key (entry) from a static Variable object.	VARIABLE=Name of the VARA object KEY- Wildcards (* and ?) are allowed.
START OBJECT	Starts any object and does not check its end status. The UC_CAUSE* ReadBuffer Variablesare supplied with values and can be read in this object's script.	OBJECTNAME=Name of the executable object PARAMETERS=Values as defined in the PromptSet assigned to the object. You have to select an object and accept the condition first and then click on PARAMETERS to load the PromtSet values you must populate. If the object has no PromptSets assigned, clicking PARAMETERS opens an empty section. END=Wait/No wait
PUBLISH VALUE	Makes a specific value available for the Workflow as a variable.	VALUE VARIABLE name=Name of the VARA object
SET OBJECT VARIABLE	Creates or changes an object variable. To use this object variable, you must have activated the option Generate at runtime (Post Process is exempted) regardless of the settings that are defined in the parameter scope of the task or the workflow. Otherwise, the system tries to access a non-existing variable or returns the old value (if the variable is already defined in the object).	OBJECT VARIABLE VALUE SCOPE=Task or Workflow
SET VARIABLE	Creates or changes variable value.	VARIABLE NAME=Name o the VARA object KEY COLUMN VALUE

FINALLY Statements (FINALLY)

Action	Description	Parameters
CANCEL WORKFLOW	Cancels the Workflow at the specified levels. Processing stops immediately.	SCOPE=OWN*/Parent/Top SUBORDINATE TASKS=Include/exclude
PROCESS IF BRANCH	Based on the condition results, determines whether processing continues on the TRUE or FALSE branch of the IF-workflow.	TRUE/FALSE return value ALIAS of true or false branch for the action

Action

Description

Parameters

CANCEL WORKFLOW

Cancels the Workflow at the specified levels.

Processing stops immediately.

SCOPE=OWN*/Parent/Top

SUBORDINATE TASKS=Include/exclude

PROCESS IF BRANCH

Based on the condition results, determines whether processing continues on the TRUE or FALSE branch of the IF-workflow.

TRUE/FALSE return value

ALIAS of true or false branch for the action