FinalBuilder supports both the DOS 'AT' Scheduler and the Windows Task Scheduler. It is recommended you use the Windows Scheduler actions in most cases.

The Schedule Add Action acts as a front-end to the DOS 'AT' command, and allows you to schedule a program for execution at a later time.

You can schedule an executable command or a FinalBuilder project file to be executed.

Command or FinalBuilder Project

Specify the name of an executable, or a FinalBuilder project, you would like to execute.

Command Line Arguments

Specify the name of any command line arguments to pass to the executable.

Execution Options

Run interactively on logged on user's screen...

If selected, then the program will display on the screen of the logged on user at time of execution. Otherwise, it will execute in the background.

If running a FinalBuilder project file, "Interactive" running means the project will be loaded in FinalBuilder, "non-interactive" means it will be loaded "behind the scenes" with FBCMD.

Log output to file

If checked, the "standard output" of the executable will be sent to a file.

This option is not available when using a FinalBuilder project file in Interactive mode.

Scheduled Date & Time

The execution time can either be scheduled statically, or relative to the time at which the action is executed.

Schedule relative to time of execution...

Specify the duration after which the program will be loaded. In the above example, route.exe will be scheduled to execute one hour after the action is run.

Schedule absolute date / time

Specify a time and (optionally) a date for execution. Execution can be "every" day or only on the "next" day which matches the parameters.

The days specified can be a combination of either the letters M,T,W,Th,F,S,Su (Monday-Friday), or the numbers 1 through 31.

Task ID Number

Store Task ID Number to Variable

If checked, the task ID of the new task will be stored to a variable. It can be used in other actions, for example Deschedule Command.

Remote Computer

The command can be scheduled on a remote computer instead of the local one. The current Windows account must have adequate permissions on the remote machine (a Windows NT Domain may be necessary in order to achieve this.)

Automatically executing FinalBuilder project files on a remote machine will only succeed if the FinalBuilder installation directory path & FinalBuilder project file paths are the same on both computers. If not, you will need to specify the execution path manually and pass in the FinalBuilder project file as a command line argument.
  • No labels