Process Condition

Description

Monitors for a process to enter a specific state (i.e. started, ended, stop responding) and evaluates as TRUE when the condition is encountered. The Process condition can be used as one of the following workflow elements:

Practical Usage

Frequently used to monitor external applications for unexpected crashes. Process condition is also used to start a task when an external application starts.

Related Topics  

Parameters

General

Property

Type

Description

Wait for process to

Options

Specifies the process state to monitor. The available options are:

  • Stop responding - The trigger activates when the specified process stops responding or "hangs".

  • Started - The trigger activates when the specified process starts.

  • Ended - The trigger activates when the specified process ends.

Process name

String

Specifies the process to watch. The provided combination list box accepts manual text entry or the process can be selected from the drop-down list of open processes. In addition, the folder icon can be clicked to open a standard Windows Explorer dialog in order to navigate to the desired application. The filename alone or the full path and filename may be entered. Wildcard characters * and ? can be used to indicate partial process names. For example, entering e*.exe will watch for all processes starting with the letter e.

Behavior

The Behavior tab 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 about Condition Behavior

Additional Notes

AMTrigger

When the Process 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 Process condition, see AMTrigger - Process.

AMCondition

When the Process 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 Process condition, see AMCondition - Process.

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.