|
|
|
|
|
The action performed by a task and the time it is run are controlled by task elements such as sources, destinations, schedules, processes and next actions. A task's status (enabled or disabled), variable task parameters and other attributes are instead called task information.
All tasks (even sync tasks) are always "scheduled," "unscheduled," "disabled," or "incomplete."
An incomplete task is one that is incapable of being run automatically or manually. In essence, the task cannot do anything, meaning it does not have at least one process, or at least one source and destination. These tasks are marked with red X's.
Unscheduled and disabled tasks have at least one process, or at least one source and destination. These tasks will not be started by the scheduler or file events but can be run manually. Unscheduled tasks have no schedule. Disabled tasks usually do not have a schedule and will be marked with an extra "*** DISABLED ***" tag in their names on the Tasks tab. The primary use of the "disabled" designation is to allow operators to build and save tasks without worrying about the scheduler attempting to run unfinished configurations, and to allow operators to "pull out of production" certain tasks which they would rather not delete.
A scheduled task can be run either manually, or automatically. It has all necessary parts of the task defined: at least one process or at least one source and destination, and at least one schedule.
A scheduled traditional task, featuring 1 source, 2 destinations, 1 next action, and 2 schedules.