Service Condition
Description
Monitors for a service to enter a specific state (that is, started, stopped, or paused) and evaluates as TRUE when the condition is encountered. This condition can be set as one of the following workflow elements:
-
Trigger element - When positioned in the beginning of a workflow, triggers its execution when the monitored condition (that is, when the specified service started) evaluates to TRUE.
-
Wait element - Suspends execution of a running workflow until the monitored condition (that is, when the specified service started) valuates to TRUE.
-
Conditional element - Determines the course of a workflow depending on whether or not a specific condition (that is, when the specified service started) evaluates to TRUE.
Parameters
General
| Property | Type | Description |
|---|---|---|
| Wait for service to | Options | The service state to monitor.
The available options are:
|
| 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.
Additional notes
AMTrigger
When the Key event is used to trigger workflow execution, it automatically creates an AMTrigger dataset which can be used much like the datasets created by the Database - SQL query activity and Email action. 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.