Event Log Condition

Description

Monitors for a specific event to be written to the Windows Event Log and evaluates as TRUE when the condition is met. It can be used in the following manners:

Practical Usage

Used to make AutoMate BPA Server react to system or application generated errors that are sent to the system event log. For example, if the system logs an entry indicating that the DNS server could not be contacted, execute a workflow that alerts the system administrator of the error and performs appropriate steps to remedy the problem.

Related Topics  

Parameters

General

Property

Type

Description

Log

Text

The type of event log to monitor. The default value is Application, however, other log types can be selected by expanding the list box or a user can simply enter the log type manually.

Source

Text

The source of the event in which to monitor. The default value is All Sources, however, expanding the list box will show all available sources on the system to select from or a user can enter the event source manually.

Type

Options

The type of event to monitor. The available options are:

  • Any (default) - Any event type.

  • Information - An event that describes the successful operation of an application, driver, or service. For example, when a network driver loads successfully, it may be appropriate to log an Information event. Note that it is generally inappropriate for a desktop application to log an event each time it starts.

  • Warning - An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event is logged. If an application can recover from an event without loss of functionality or data, it can generally classify the event as a Warning event.

  • Error - An event that indicates a significant problem such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event is logged.

  • Success Audit - An event that records an audited security access attempt that is successful. For example, a user's successful attempt to log on to the system is logged as a Success Audit event.

  • Failure Audit - An event that records an audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt is logged as a Failure Audit event.

Category

Text

The event category to monitor. The only available option is All categories.

Description

Text

Allows a description for the event to optionally be entered. To specify partial matches, use wildcard characters * or ?.

 

Behavior

The Behavior properties dictate how the system should react upon the occurrence of a condition. These properties are significant in determining whether the AutoMate Condition should act as a trigger object (used to fire off workflow execution), wait object (used to suspend workflow execution) or conditional (decision making) object.

More on Condition Behavior

Additional Notes

AMTrigger

When the Event Log condition is used to trigger workflow execution, it automatically creates an AMTrigger dataset which can be used much like the datasets created by the SQL Query and E-Mail actions. The fields that AMTrigger generates can be used to determine properties of the object that caused the workflow to launch, such as the type of trigger, when the trigger was activated and what system event or condition took place to activate the trigger. Along with a collection of global AMTrigger fields that are created and populated by every instance of AMTrigger, a unique set of AMTrigger fields exclusive to each AutoMate trigger are created as well.

To view AMTrigger values exclusive to the Event Log condition, see AMTrigger - Event Log.

AMCondition

When the Event Log condition is used in the middle of a workflow as wait or conditional object, it automatically creates an AMCondition dataset. Similar to AMTrigger, the fields that AMCondition generates can be used to determine properties of the object that caused the condition to activate. Along with a collection of global AMCondition fields that are created and populated by every instance of AMCondition, a unique set of AMCondition fields exclusive to each AutoMate condition are created as well.

To view AMCondition values exclusive to the Event Log condition, see AMCondition - Event Log.

NOTE: A full list of AMTrigger and AMCondition fields exclusive to each trigger/condition can be viewed from Expression Builder by expanding the Objects folder and selecting the desired object from either the Triggers or Conditions folder.