Conditions in BPA Server can be chained together, applied to different machines, and apear anywhere in the workflow.

Mutliple Triggers being applied to a task in AutoMate. Any of the triggers added will kick-off the task.

BPA Server Conditions &
AutoMate Triggers

Conditions and triggers add intelligence to workflows by providing awareness of network-wide system events and states.

Conditions are closely correlated with the system, application, and network events that transpire across the automation network. In addition to the events themselves, conditions also encapsulate state changes that events produce. For example, the appearance of a file in a network share is an event, and the existence of that file is a state. Both the event and the state are conditions- the event is "when the file exists" and the state is "if the file exists."

Thus, conditions can be used to initiate workflows (i.e., trigger workflow A when file X appears), wait for certain events to transpire before proceeding in a workflow (i.e., wait for Notepad to appear), or to make a decision and conditional branch within the workflow (i.e., evaluate if Notepad is already open- if yes, execute Task 1; if no, execute Task 2).

AutoMate BPA Server Conditions

• Schedule Watcher Evaluates as true at the date, time or interval specified. It can be used for scheduling tasks to run at night or at the end of every day, week, month or other time frame.
• Folder Watcher Monitors the Windows file system for file additions, modification, or deletions in the folder(s) specified, and evaluates as true when a criterion is met.
• Performance Watcher Evaluates as true when a system or process threshold is met. Parameters include available memory, free disk space, CPU utilization, process count, and more.
• Event Log Watcher Evaluates as true when an event matching specified criteria is added to a Windows Event Log.
• Service Watcher Evaluates as true when the specified service starts, stops, pauses, resumes or stops responding.
• Process Watcher Evaluates as true when the specified process starts, ends or stops responding.
• Startup Watcher Evaluates as true when the AutoMate task service starts or when a user logs onto the system.
• Idle Watcher Evaluates as true when no keyboard or mouse input occurs for a specified period of time.
• Window Watcher Evaluates as true when the specified window opens, closes, is focused or loses focus.
• Key Watcher Evaluates as true when a hotkey is pressed or a word is typed on the keyboard. The event can be configured to occur only when a specific application has focus.
• SNMP Trap Watcher Evaluates as true when an SNMP Trap meeting specified criteria is received.
• WMI Evaluates as true when a WQL query returns true or more than zero rows.