Events & Conditions

Similar to Triggers in AutoMate 9, AutoMate BPA Server 9 Events and Conditions provide the ability to automatically "fire off" a task upon the occurrence of a particular event or condition. When the task is triggered, the steps (comprised of actions or activities) execute, thus, initiating the workflow in which the task resides. In AutoMate BPA Server 9, the term Trigger is replaced with Events and Conditions due to the fact that these objects are capable of doing more than just triggering task/workflow execution. Conditions can also be used at any point of a workflow’s path by causing a workflow to wait until a certain condition occurs or they can determine a workflow’s path depending on whether or not a condition has occurred.

Available Events & Conditions

Below is an alphabetical list of the available conditions AutoMate provides, with links to the topics covering each type.




Event Log Condition

Evaluates to TRUE when the monitored event appears in the Windows Event Log.

File System Condition

Evaluates to TRUE when one or more files are added, modified or deleted in the folder specified. Can also monitor for when the number of files exceeds the amount specified,  when one file size exceeds the amount specified or when the total size of the specified folder exceeds the amount specified.

Idle Condition

Launches a task when no keyboard or mouse input occurs for the specified period of time (i.e. the system is idle).

Key Event

Launches a task when a hot-key combination is pressed or a specific word is typed on the keyboard.

Performance Condition

Launches a task when a system or process threshold (such as CPU utilization and memory usage) is met.

Process Condition

Launches a task when the specified process starts, ends or stops responding.

Schedule Event

Launches a task at the date, time or interval specified. This trigger can be used for scheduling tasks to run at night or at the end of every work-day, week, month or other time frame.  

Service Condition

Launches a task when the specified service starts, stops, pauses, resumes or stops responding.

Schedule Trigger

SNMP Trap Condition

Launches a task when a SNMP (Simple Network Management Protocol) trap is received.

Logon Condition

Launches a task when the AutoMate task service starts or when a user logs onto the system.

Window Trigger

Window Condition

Launches a task when the specified window opens, closes, is focused or loses focus.

WMI Condition

Launches a task when a WQL (WMI Query Language) query executed on the agent machine returns true or more than 0 rows. Queries built using WQL are used to manage and control the WMI Service.   

Difference Between Events and Conditions

An Event is essentially a specific occurrence or incident that takes place which automatically triggers the execution of a workflow. For example, the Key Event can automatically start a workflow when a specified hot-key combination is pressed or a particular word is typed. Events can be something that occurs during a particular time period or interval as well. For example, when the Schedule Event is used, once the specified date/time occurs, the event will trigger the workflow to start. Events are typically defined as one time occurrences. Because of this, it is important to note that an AutoMate Event is used primarily as a "triggering" object, thus, can only exist in the beginning of a workflow.

Conditions are similar to Events in that they can be used as a triggering object to automatically start a workflow. However unlike an event, which is essentially a one time occurrence, a condition can have a duration. Therefore, Conditions influence workflows in a more versatile manner because they can also determine the path of a workflow depending on whether or not the specified condition has been met or used to pause workflow execution until a specific condition is met. For example, when a new file is added to a folder, whether it was copied, moved or created inside that folder, the addition of that file in the folder is considered an event and the existence of that file in the folder is considered a condition. The event is “when” the file exists and the condition is “if” the file exists.

For example, a File Condition can be used in the following scenarios:

Attaching Multiple Conditions

Multiple conditions of the same or differing types may be attached to a single task. For example, if a task should run once daily, add a Schedule event. If it should also run when a certain key combination is pressed, simply add a Key event as well. Attaching multiple conditions acts as an "OR" condition (as opposed to "AND") whereby occurrence of either of the conditions will launch the task.

Additionally, a single Condition object can be attached to multiple tasks in a workflow. In this case, all associated tasks are executed (according to its Priority settings) upon the occurrence of the specified condition.

NOTE: AND conditions can be created by attaching the first requirement as a condition and then adding steps at the beginning of the task that use the IF action to evaluate any extra conditions and stop the task if the conditions are not met.

AMTrigger and AMCondition

When a task is started by an event or condition, it automatically creates a dataset called AMTrigger. This dataset can be used within a task to determine specific elements about the object that initially triggered the task, such as which trigger started the task, when the task was triggered, which agent ran the task, etc. See Using AMTrigger for more information.

When a condition is not used as an object that triggers the start of a workflow, but rather, it is initiated in the middle of a workflow, a similar dataset called AMCondition is created instead. See Using AMCondition for more information.

See Also

Setting Conditions | Condition Behavior | Using AMTrigger | Using AMCondition