About Events & Conditions

Similar to AutoMate Triggers, BPA Server Events and Conditions provide the ability to automatically "fire off" a workflow. When a specific event or condition occurs, the steps in the associated task (comprised of actions) are automatically executed, thus, initiating the workflow in which the task resides. In BPA Server, 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. They 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.

Click an Event or Condition illustrated below to view more details.

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 one time occurrences. Because of this, it is important to note that an 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 & 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

Available Events & Conditions

Setting Conditions

Setting Condition Behavior