AMCondition - Process |
Description
An Automate condition can be used in the middle of a workflow as a means to suspend execution until a specific condition takes place or as a conditional element to determine a workflow's path resulting from the occurrence (or non-occurrence) of a specific condition. When used in this manner, a pre-named (or fixed field) dataset called AMCondition is created and populated with a collection of data related to the observed condition. AMCondition is a standard Automate dataset which can be used during the course of a workflow to examine particular characteristics about the initiated condition, such as the type of condition that occurred, when it occurred and what computer it occurred on.
Parameters
The total number of fields that AMCondition creates during runtime and what they are named depends largely on the Automate condition that was used. Each condition contains its own set of unique AMCondition fields. The table below lists the fields related to the Process Condition. For more details about a specific AMCondition field, click the associated link.
|
Name |
Data Type |
Return Value |
|
String |
Returns the action that took place to cause the condition to activate. |
|
|
String |
Returns the absolute path (full path and file name information) of the process that activated the condition. |
|
|
String |
Returns the file name of the process that activated the condition excluding path information. |
|
|
Number |
Returns the process ID of the process that activated the condition. A process ID is a number automatically assigned to a process by the system. The process ID can be used by other actions in Automate to specify an instance of a process or application. |
|
NOTE: A full list of AMCondition and AMTrigger objects exclusive to each event/condition can be viewed from the Expression Builder by expanding the Objects folder and selecting the desired object from either the Triggers or Conditions sub-folder. |