Add a Traditional Task

Configure a Traditional Task

1. On the TASKS tab select New Task from the Add Task drop-down list.
2. Enter the task name in the Friendly Name field.
   Note: If starting a task using the Java or Windows API, ensure that the task name does not exceed 254 characters. If the task name exceeds this limit, the Task ID should be used to start the task.
3. Select the Traditional Task type.
4. To save and open the new task, click Add Task .
5. Click Step to add a Source, Process, or Destination to the task. The minimum requirements to run a task are, the task must have a Source and a Destination, or a Source and a Process.
6. To run the task automatically, click Schedule and select the required options. Tasks with or without schedules can be run manually.
7. Click Next Action to add additional actions, such as send an email or run the task when a specific outcome is achieved.

A task must be correctly configured before it can be processed. For information on minimum configuration requirements, see Minimum Task Configuration Requirements.

Elements in Traditional Tasks

Typically, you define the elements in the order shown.

• Source:

  A source defines a single location from which files are obtained for use in a task. Each source is a reference to a host. A task can have an unlimited number of sources.

• Process:

  In a task, a process runs a single built-in script or custom script. The script must exist before you can add it to a process. For more information, see Scripts.

  In a traditional task, the process can run on each file downloaded source file, or it can be run once after all files are downloaded.
• Destination:

  A destination defines a single location to which files are sent when a task runs. A task can have any number of destinations, or no destinations. If a task has no destinations, it must have at least one process to be eligible to run.

• Schedule:

  A task can have more than one schedule. To run automatically, a task must have a minimum of one schedule. Tasks with or without schedules can be run manually by the operator.

• Next Action - Send Email: Sends an email based on the results of the task.
• Next Action - Run Task: Runs another task based on the results of the task you are configuring.

Examples of What Traditional Tasks Can Do

• Run processes.
• Delete/rename/move files on sources after copying them to destinations.
• Rename downloaded files and folders before writing or creating them on destinations.
• Pull from multiple sources in a single task.
• Push to multiple destinations in a single task.
• Work with AS1, AS2, AS3 and SMTP/POP3 (email) sources and destinations.
• Select source files based on specific date criteria (such as "older than 60 days").
• Handle blind downloads, typically through FTP servers that do not provide directory listings.
• Zip or unzip files.
• Issue per-file FTP commands.