Condition Behavior


AutoMate BPA Server 9 Conditions are objects that watch for the occurrence of are used to fire off workflow execution or determine a workflow's path resulting from the occurrence (or non-occurrence) of a specific system state or condition. All available AutoMate Conditions (excluding Schedule and Key Events) contain behavioral properties that dictate how it should react when an observed system state or condition is met. These properties are significant in determining whether the Condition should act as a trigger object (used to fire off workflow execution), wait object (used to suspend workflow execution) or conditional (or decision making) object. Behavior parameters are identical in all AutoMate Conditions. They are found in the properties of a given AutoMate Conditions under the Behavior tab (Behavior properties of Idle Condition shown below).


The Behavior properties are comprised of two main options that primarily determine the overall behavior of an Automate Condition. These options generally dictate to the workflow whether or not it should wait for the monitored condition to take place. The available options are:

The behavioral properties of a newly created AutoMate Condition is always set to wait indefinitely for the specified state or condition to occur (as shown above), which means that it will behave as a trigger object and placed in the beginning of a workflow. To modify the behavior, simply make the proper adjustments. For more details, see the table below.

Primary Option


Secondary Option


Wait for condition

Waits for the occurrence of the specified condition according to the parameters set under this option (default). If this option is selected, the following secondary options become available:


If enabled, the system waits indefinitely for the monitored condition to occur and begins workflow execution as a result. Because the wait is indefinite, selecting this option allows the AutoMate Condition to behave as a TRIGGER object. This option is enabled by default.

NOTE: Triggers are used to initiate workflow execution, therefore, they must be the first object in a workflow.

Timeout After

If enabled, the system suspends workflow execution at a specific point until the monitored condition occurs. Because this option requires entry of a time out value, the AutoMate Condition no longer behaves as a trigger object, but rather, as a WAIT object placed in the middle of a workflow.

NOTE: If the condition does not occur within the time out period entered, the workflow times out. In this situation, a Failure (Red) Arrow can be used to run a specific task (for example, one that remedies the problem) in case a time out occurs.

Trigger on startup if condition is true

If enabled, the system will react to conditions that already exist upon startup.

For example, imagine that FileA.txt already exists in C:\Temp. If this parameter is enabled in the properties of a newly created File Condition set to monitor for the existence of C:\Temp\FileA.txt, it will immediately start the workflow as a result. If this parameter is disabled, the Condition will ignore the current  existence of C:\Temp\FileA.txt upon startup. Instead, it will monitor for subsequent occurrences as specified in the Trigger after the condition has been met X times parameter.

NOTE: In reference to "startup", a newly created AutoMate Condition starts up as soon as the developer clicks the Update button to save its properties. Startup of existing Conditions normally commence when the Condition becomes active, such as when the BPA Service starts or the workflow in which it resides is re-enabled.

Trigger after the condition has been met X times

If enabled, the system continues to wait until the monitored condition has been met the specified amount of times.

For example, a Window Condition is set to watch for the existence of an Internet Explorer window. If this parameter is set to trigger after the condition has been met 3 times, the system will ignore the first two times that an Internet Explorer window appears on the desktop. It will perform the assigned wait instructions only after the third instance of an Internet Explorer window appears.

Don't wait, execute immediately

Does not wait. Instead, evaluates immediately whether the specified condition has occurred. This option allows decisions to be made during the course of a workflow. It can determine a workflow's path based on results, thus, allowing the AutoMate Condition to behave as a CONDITIONAL (decision making) object.

For example, using the Window Condition example mentioned above, if this option is enabled, the system does not wait for the existence of an Internet Explorer window. Rather, it will immediately determine if the window already exists on the desktop. If the evaluation results to TRUE, the execution is marked as  success and therefore execution follows the path marked by a Success (Green) Arrow. If the evaluation results to FALSE, the execution is marked as failure and execution follows the path marked by a Failure (Red) Arrow.

NOTE: This option supports ensuing use of Success and Failure Flow Control Arrows only. It does not support the use of Result Arrows.



See Also

Events and Conditions | Setting Conditions | Condition Behavior