AWE provides an incredibly easy-to-use, intuitive interface for developing automation applications. The basic building blocks are called actions, which are plain-English, drag-and-drop, fill-in-the-blank dialog boxes that you can use to build AWE tasks. Actions enable the development of sophisticated automation processes, and eliminate the need for code. You could think of them as the steps that do the actual work of a task. You can drag and drop actions in the Task Builder to build a series of AWE steps that collectively make up the task. You can view all available actions in the Task Builder's Available Actions pane, categorized into folders. You build a task by dragging actions from the Available Actions pane into the Steps pane of the Task Builder. For more information, see Adding Task Steps.
AWE's pre-built actions include starting applications, sending keystrokes, clicking controls, uploading files, and much more. These actions can be further expanded by the use of variables, constants, and expressions.
AWE Actions are organized in groups (or categories) to facilitate the development process:
|
Action Group |
Description |
|
Allows automation of common Active Directory operations. |
|
|
Allows you to edit the computer registry, event logging, and the addition of VB script to a task. |
|
|
Amazon |
Enables automation of the most common products and services AWS (Amazon Web Service) has to offer, such as EC2, RDS, S3, etc. |
|
These actions allow for control of task execution within the scope of a task. For example, a subtask could be started within the scope of the main task. |
|
|
Clipboard |
These actions enable manipulation of the clipboard, and the population of variables with clipboard content. |
|
Allow for automatic compression/decompression of files using commonly-used formats. |
|
|
Provides encryption automation to secure files before they are transported. |
|
|
Enable the execution of SQL queries and stored procedures on any ODBC database. Microsoft SQL Server, Oracle, mySQL, and more are supported. |
|
|
Dialogs |
These actions allow for user interaction with and input to tasks. |
|
Allow for automation of data input and retrieval from Microsoft Excel spreadsheets and templates. |
|
|
File actions enable automation of file and folder commands such as copy, move, rename, delete, etc. These actions also allow data to be read from and written to files. |
|
|
Flow actions enable complex decision making based on variable data in the context of a task. |
|
|
Interactivity |
Interactivity actions enable automation of the user interface via keystrokes and mouse movements. |
|
Provide the ability to loop through data sets, files, processes, lists, and more for dynamic automation. |
|
|
Multimedia |
Multimedia actions allow for automation of audio and CDs, as well as conversion of text to speech. |
|
Network actions enable drive mapping and the sending of network messages. |
|
|
Security actions allow for user authentication in the context of a task. |
|
|
Session actions enable automatic shutdown, startup, logging off, locking of workstations and servers. |
|
|
Allow for automatic processing of SNMP (simple network messaging protocol) events that occur on the network. |
|
|
System actions enable execution and termination of executables, as well as printer and display control. |
|
|
Enable automation of all terminal emulation and Telnet processes. |
|
|
Text actions enable the manipulation and parsing of textual data. |
|
|
Used to gauge the execution time between selected steps. |
|
|
VMWware |
Provides VM OS and guest OS operations. |
|
Provide the ability to create and perform complex programming elements such as creating and running variables and datasets. |
|
|
Wait actions provide the ability to pause task execution until a specified system event (e.g., the appearance of a file) transpires. |
|
|
Window actions enable interaction with and control of windows. |
|
|
Allows XML parsing and manipulation. |