I, RoboTask

Opinion
Jul 26, 20044 mins

In recent columns we covered a few computer automation products, and it is time for another: RoboTask from NeoWise Software.

We like RoboTask for four reasons: It uses very few system resources (it needs only 64M bytes of RAM and about 7M bytes of free disk); it is easy to use but offers rich and complex functionality; it is robust; and finally, it is inexpensive ($99).

RoboTask runs under Windows 98/ME/NT 4.0/2000/XP, and installation is a breeze. It can run as an application or an NT service, and optionally can be loaded when Windows starts. When running, an icon in the system tray provides access to RoboTask if it is minimized.

The user interface consists of a vertical arrangement of panels consisting of a task browser panel divided into a left-hand subpanel list of folders and a list of the tasks in the selected folder in the right-hand subpanel. From this latter panel, you can run, stop, enable or edit tasks, or save a shortcut to the task on your desktop. The bottom panel is the RoboTask log, which displays information, warnings and error messages.

Creating a new task brings up a new dialog box. You give the task a name and create the actions the task carries out; define the events that trigger the task; and set the task’s advanced options, including setting the task’s external name, the logging level and, if required, whether it should be disabled or deleted after running.

The available actions are divided into categories. There are a lot of features here, so we’ll cover just a few to give you an idea of the scope of RoboTask. General actions include running other programs, opening or printing documents, and logging off (which covers a simple user log-off; shutting down all running programs, computer shutdown, shutdown with power off and restart), and dialogs for user interaction.

File and folder operations include a folder-synchronization feature (very useful); Zip actions for packing and unpacking archives; Internet functions to check for and send e-mail, execute HTTP downloads, and ping hosts; extensive FTP support; and dial-up support. Then there are more actions to create, set and remove RoboTask user variables; loops and flows to provide if . . . then . . . else conditionals; and loops that iterate through the contents of text files or data extracted from SQL queries; and . . . well, the list goes on and on.

As you will have noted from the discussion of operations, RoboTask supports user variables, either single values or arrays of values. It also provides a constellation of system variables that provide date and time data, files and folder information, system information, and window information.

The triggering events include scheduled (by specific date and time criteria) and cyclic triggers (every so many seconds); hot keys; changes to files; dial-up connection status changes; and a number of system events, including low battery power, user log-off and system idle.

While you can do very complex things with RoboTask, there are a few free add-ons that extend the system even further. The DVD/CD writer add-on is very powerful, and let you check on the presence of media, capacity remaining, eject and load media, and so on, but it is the add-on BASIC interpreter that really turbo charges RoboTask.

The interpreter is actually the Sax ActiveX Scripting Control from Sax Software. This ActiveX control is almost identical in features and functions to Microsoft’s Visual Basic for Applications.

What is really cool about the Sax Basic system is it comes with a built-in editor that also sports a graphical user dialog editor and a debugger, all of which makes developing scripts very easy.

The Sax control also knows all about the RoboTask application (and for that matter, any other ActiveX controls in the system). It can interact with RoboTask by, for example, creating, reading or deleting RoboTask user variables; enabling, starting and stopping RoboTask tasks; and the like.

So far, we’ve found little about RoboTask that we don’t like. Our only complaints are that we’d like more examples included in the distribution and we’d like to see the documentation expanded (it is a little skimpy in a few places).

In an enterprise environment, the lack of a central console for managing multiple copies of RoboTask could be a problem, but the scope of RoboTask’s programmability – particularly when extended by Sax Basic – should let you create your own centralized control system.

RoboTask is a great tool at a great price, and the potential for creating powerful automation solutions is fantastic.

Your task? Write to gearhead@gibbs.com.