Condition Behavior

All available AutoMate Conditions contain Behavior properties that dictate how it should react to a monitored event or condition (as shown below). These properties are important in determining whether the Condition should act as a Trigger, a Wait object or Conditional (or decision making) object. Behavior properties are found in the Behavior tab and are identical in all Conditions.

Behavior Parameters

The Behavior properties are comprised of two primary options that determine the overall behavior of an Automate BPA Condition. These options basically dictate to the  workflow how long it should wait for a particular event/condition to take place:

The default settings in the Behavior properties of a new Condition is to wait indefinitely for the specified event/condition to occur (as shown above). These default options should be selected when the Condition should be set as a trigger object in the beginning of a workflow.

More details about the primary and secondary Behavior options are entered in the table below.

Primary Option


Secondary Option


Wait for condition

Waits for the specified condition according to the parameters set under this option (default).

If this option is selected, other options the following secondary options become available:


If enabled, the system waits indefinitely for the condition to be met. Because the wait is indefinite, this option allows the condition to act as a TRIGGER. (enabled by default).

NOTE: Triggers must be the first object in a workflow.

Timeout After

If enabled, the system waits for the condition to be met within the time range specified. If the condition does not occur within that time period, the workflow times out. This option tells a workflow to pause execution until the specified condition is met, thus allowing the condition to act as a WAIT object.

Trigger on startup if condition is true

If enabled, the system will act upon conditions that already exist upon startup of the current condition. For example, if the Notepad window is already open on the desktop, a newly created Window condition set to monitor for the existence of a Notepad window will trigger the workflow as a result. If disabled, the Condition will ignore the open Notepad window upon startup.

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, if number of times equals 5, in the Notepad example above, the system will wait for the Notepad window to appear five times and then performs the assigned wait instructions upon the 5th Notepad instance (enabled by default).

Don't wait, execute immediately

Does not wait. Instead, evaluates immediately whether the condition has been met. 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 condition to act as a CONDITIONAL object.

For example, if the condition evaluates as TRUE, run TaskA, if FALSE, run TaskB.




See Also

About Events and Conditions

All Available Conditions