The system options determine how AutoMate behaves on a system level. The default settings are adequate in most cases, but you may want to change these settings to suit your own system's needs.
NOTE: These options can be viewed and modified by an authenticated user through Remote Administration
From the System menu in the Task Administrator window, select Options.
Click the System tab (as shown below)
Enter specific system related properties as follows:
Select from the following to control when the AutoMate icon is visible in the system task tray (located near the system clock):
a task is running
AutoMate uses TCP/IP communication to interact with itself and other AutoMate installations. By default, AutoMate will accept connections from local copies of the Task Administrator and from remote AutoMate installations (if enabled) on port 7477. This port can be changed if it conflicts with other applications on the system. After changing the port, be sure to restart AutoMate: Right-click the AutoMate tray icon and select Exit. Then restart the AutoMate Task Administrator.
NOTE: To use remote administration to connect to a machine using a different server port than 7477, you must include the server port preceded by a colon after the machine name, for example, MachineName:7677.
When a new Managed Task is created, AutoMate generates an associated task file that contains the task's steps. By default, task files are saved to a location accessible by all users on the system, typically Documents and Settings\All Users\Documents\My AutoMate Tasks. To select a different location for your managed tasks, click the Open Folder button and browse to the location.
NOTE: If selecting a network share as the default location, make sure to specify the path in Universal Naming Convention (UNC) format as opposed to a mapped drive. For example: X:\pathname\ should be \\servername\pathname\. This is because mapped drives are connected and created when the user logs on, however, paths specified in UNC format are available whether the user is logged on or not.
Use this to tailor the step-by-step execution speed of a task. The delay is displayed in milliseconds. A delay of this duration will automatically be placed between each task step. This will apply to all steps of all tasks. If you want a delay between specific steps of a particular task, use a Pause Task action or one of the other Wait actions.
When this option is selected, the Windows Foreground Timeout feature is turned off. This is the default option. Windows Foreground Timeout is a feature of Windows operating systems, which, if an application has been accessed within a few seconds, prevents other applications from focusing or changing the order of windows without direct user interaction. Instead of the window being focused and brought to the foreground, Windows will blink the application in the system tray until it is manually clicked. This can prevent AutoMate from properly focusing windows using the Focus Window action. If you want to enable Windows Foreground Timeout, click to clear this selection.
AutoMate tasks can be tailored to execute with varying degrees of isolation allowing for faster startup speeds. Tasks can be set to run under a single pre-loaded process allowing faster startup speeds but eliminating tasks from being isolated from one another or each task can be set to start in their own process isolating them from other running tasks at the cost of a reduction in startup speeds. To modify task isolation, click the Change Task Isolation Level button. A Task Isolation Level dialog will appear (as shown below).
Task Isolation functionality operates only in situations when multiple tasks begin simultaneously (either manually or automatically with the use of a trigger) or when one or more tasks are started while another task is currently in a running state. Keep in mind that certain tasks may need to run independently, such as tasks that contain interactive actions and directly interact with the desktop. Such tasks can be set to run alone within their Priority settings.
The available isolation levels are:
All tasks are set to start in their own process as opposed to starting from a single pre-loaded process. The first task instance and subsequent simultaneous task instances must wait for their corresponding process to start reducing overall startup speed. However, because each task is isolated in their own process, they become independent from all other running tasks. Therefore, failure of a particular task will not effect other running tasks.
The first task instance starts from a pre-loaded process providing faster startup for that task. If other task instances start while the first instance is currently running, each of those tasks will start from their own process which may reduce their startup speed. However, since each subsequent task is isolated in its own process, failure of an individual task will not effect other running tasks.
The first task instance and all other simultaneous instances start from a pre-loaded process allowing for optimum startup speeds. However, since all tasks are run from the same process, failure of a single task will effect all tasks that are running under the same process.
NOTE: When Task Isolation level is set to High, tasks that start in their own process may be delayed by only a few seconds compared to tasks that are started in the same process when isolation is set to Low. Therefore, Task Isolation should be modified only if startup speeds are significantly slow or are imperative to the overall progress or result of a task.