Subscribe to Blog Posts by: Scott Robinet via RSS Blog Posts by: Scott Robinet
Altering Workflow Paths Based On User Input
A member on the AutoMate Forums recently asked a question about how to have user input drive the starting of other tasks. After some thought, I realized that the solution to this problem provided an excellent example of how AutoMate BPA Server"s workflow capabilities not only provide an easy way to accomplish such tasks, but separates the logic of such decisions into a clear and easily understandable process.
Executing a command-line application using the Run Action
This month's Task Of The Month compliments our Tech Tech article by providing an example of executing a command-line application using the Run action that directs its output and return code to two different files. These files are then read into AutoMate variables for display and analysis.
Executing Command-line Applications Using The Run Action
The AutoMate Run action is used to run Windows applications by specifying the application name (and the full path to the application if necessary). For example, to run notepad, one would simply place the word "notepad.exe" into the Run parameter and notepad will start. Most applications that are designed to run on the command-line will also execute this way provided the command-line does not contain any symbols that are used primarily in a DOS box. In other words, attempting to use the Run action to execute a command-line where the output is to be written to a file, or piping together multiple commands on the same command-line, require special handling.
What is a Dataset?
Like variables, datasets are used to represent data in a task that may be different each time a task runs. But unlike standard variables, datasets can contain multiple rows and columns. This is useful when retrieving information that describes more than one object or represents a collection of data such as a database or spreadsheet.
Inside Development : AutoMate and Windows Vista Security
Microsoft's latest operating system, Windows Vista, is almost complete and nearing release (as of this writing, Vista is slated to be released to large corporate customers under an OEM license in November and the general public in January 2007). Vista promises to improve the user experience by enhancing the graphic user interface and increasing overall system security.
Percentage signs and their use in AutoMate
This month we will concentrate on clarifying the use of the percentage sign and how they relate to the embedded expression evaluator.
Remote Administration
This month we will explore some of the special capabilities of the AutoMate Task Administrator. The Administrator is the gateway to the AutoMate system, allowing the user to configure the AutoMate Task Service, create and manage tasks, assign triggers, and tailor the way tasks are run.
AutoMate 7 Task Builder in Depth
From what we saw on the AutoMate Forums during the past month it appears we may have whetted some of your appetites with the tiny screenshot of the AutoMate 7 Task Builder. Without further adieu here is the low-down on what that screenshot really means.
AutoMate Attachments
A great feature lies tucked away in the AutoMate Task Builder than can make exporting and sharing tasks a whole lot easier: attachments. Attachments allow a file of any type to be embedded within a task so that third-party elements can be included with a task for greater portability. For example if you have a task that plays a .wav file when a certain event occurs you can guarantee the sound file will always be present on the system by attaching the file to the task.
Debugging Tasks
This month we'll explore some of the techniques you can use to debug tasks in the AutoMate Task Builder. Several features available in AutoMate 6.1 can help make this an easier process.
AutoMate 6.1 Coming Soon
The AutoMate Development Team is happy to report that AutoMate 6.1 will be available at the end of March. The 6.1 release is a comprehensive update that wraps together all the feature additions, enhancements and bug fixes from the initial AutoMate 6.0 release. Some of the major highlights include:
Running A Task In Different Workstation States
By default, an AutoMate Managed Task runs as the user that is currently logged onto the machine at the time the task is triggered, and will not run if the workstation is logged off or locked. But what if the task must run if there is or is not a user logged on? What if the task must run as a specific user, regardless of who is using the workstation when the task begins?