The Available Objects pane encompasses the major building blocks used to build a workflow. It also contains the Repository button which allows users a convenient way to access the Repository in order to add pre-existing objects to the current workflow.
Available workflow objects are grouped into 5 separate categories. Below describes each category and provides a link to related topics.
Tasks are the workhorses of workflows and provide the instructions for automated execution on agents. They are built using the Task Builder, which allows you to drag and drop over 230 actions without having to write code. For more details regarding the Task Builder, see Task Builder Quick Tour.
Flow Controls are decision-making tools used to connect tasks, conditions and other objects together to make the workflow a cohesive unit. They can also determine the path the workflow will take. For example, if the result of a task is successful, it will proceed to the object that a Success arrow is pointing to. If the task failed, it will proceed to the object that a Failure arrow is pointing to.
Success/Failure arrows - Stems from tasks and conditions and determines the path the workflow will follow depending on the success or failure of the object. For more details, see Workflow Arrows
Wait object - Provides the ability to wait for multiple items within a workflow to all finish before continuing. For more details, see Wait Workflow Object
Evaluation object - Changes the course of a workflow based on the evaluation's results (used in conjunction with the Result arrow) For more information about adding logic to workflows using the Evaluation object, see Evaluation Object.
Result arrow - Stems from the Evaluation object and determines the path the workflow will follow evaluation's results. For more details in regards to linking objects using the Result arrow, see Workflow Arrows.
A one-time occurrence that can initiate a workflow. For example, in the Schedule event, once a date or time or other interval occurs, the event starts the workflow. For more details, see
Schedule - Specifies that a scheduled event starts the beginning of this workflow. For more details, see Schedule Event.
Key - Specifies that a key sequence starts the beginning of this workflow. For more details, see Key Event.
Similar to events, conditions affect workflows, but also capture state changes that events typically produce and direct the workflow according to the state. Unlike an event, which is a one-time occurrence and then it is over, a state has duration once it has been reached. For example, the appearance of a file in a network share is an event, and the existence of that file is a state. Both the event and the state are conditions – the event is "when the file exists" and the state is "if the file exists." Thus, conditions can be used to initiate workflows (i.e., start workflow A when file X appears), wait for certain events to transpire before an active workflow is permitted to proceed past a certain point (i.e., after workflow A is initiated, wait for the Notepad Window to appear before continuing), or to make a decision and conditional branch within the workflow (i.e., after workflow A is initiated, evaluate whether the Notepad Window is open – if yes, execute Task 1; if no, execute Task 2).
Window - Evaluates as true when the specified window opens, closes, is focused or loses focus. For more details, see Window Condition.
Performance - Evaluates as true when a system or process threshold is met. Parameters include available memory, free disk space, CPU utilization, process count, and more. For more details, see Performance Condition.
Idle - Evaluates as true when no keyboard or mouse input occurs for a specified period of time. For more details, see Idle Condition.
Event Log - Evaluates as true when an event matching criteria is added to a Windows Event Log. For more details, see Event Log Condition.
File System - Monitors the Windows file system for file additions, modification, or deletions in the folder(s) specified, and evaluates as true when a criterion is met. For more details, see File Condition.
Process - Evaluates as true when the specified process starts, ends or stops responding. To indicate partial process names, use wildcard characters * and the question mark (?). For more details, see Process Condition.
Logon - Evaluates as true when the AutoMate BPA Server 7 task service starts or when a user logs onto the system. For more details, see Logon Condition.
SNMP - Evaluates as true when an SNMP Trap meeting specified criteria is received. Specify filters to watch for specific traps. An SNMP trap is a message sent by an agent to a management system indicating that an event has occurred on the host running the agent. For more details, see SNMP Trap Condition.
WMI - Evaluates as true when a WQL query returns true or more than zero rows. For more details, see WMI Condition.
NOTE: Conditions can perform dual tasks depending on the settings of the Behavior tab. See the individual Conditions for more information.
The Miscellaneous section contains the Workflow object and Process object.
Workflow object - Allows the capability to create and execute embedded or sub-workflows within a parent workflow. For more details, see sub-workflows.
Process object - Allows commands to be executed on a Task Agent or Process Agent. For more details, see Process Object.
Once you create a workflow, task, event or condition, the system stores these objects in the Repository for re-use. The Repository button allows you to view and select existing repository objects to add to the current workflow. For more details, see repository.
WFD Ribbons & Toolbar
WFD Main Workspace
WFD Output/Shared Objects Pane