Service Condition

Description

Monitors for a service to enter a specific state (i.e. started, stopped, paused, stopped responding) and evaluates as TRUE when the condition is encountered. This condition can be set as one of the following workflow elements:

Parameters

General

Property

Type

Description

Wait for service to

Options

The service state to monitor. The available options are:

  • Stopped responding - The task will run when the specified service stops responding, "hangs" or crashes.

  • Started - The task will run when the specified service is started.

  • Stopped - The task will run when the specified service is stopped.

  • Resumed - The task will run when the specified service is resumed (started again after being paused).

  • Paused - The task will run when the specified service is paused.

  • Installed - The task will run when the specified service is installed.

  • Removed - The task will run when the specified  service is removed.

Service Name

String

Specifies the name of the service to watch. A drop down populated with currently running services is supplied for convenience. The wildcard characters * and ? may be used, for example e*.exe would watch for all processes starting with the letter e.

Include device and file system drivers in list

Yes/No

If enabled, specifies that device and file system drivers are included in the Service Name list.

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 Service 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 Service condition, see AMTrigger - Service.

AMCondition

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

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.