7.1

Input Tasks
Input tasks are entrances to PlanetPress Suite Workflow Tools. They are used to take data from specific locations and to pass
it on to other tasks included in the same process. Each process must begin with an input tasks, and although a given process
may have multiple input tasks, no task can have more than one initial input task (see "Initial and Secondary Input Tasks"
(page 94)).
When a process is active (see "About Configurations" (page 22)) and on schedule (see "Access Process Properties" (page 41)),
it polls its initial input location at regular intervals. Files sent to a location polled by an initial input task included in a process
that is either inactive or off schedule remain there until the process becomes both active and on schedule (granted that enough
space is available to store all the incoming files).
It is not recommended, in the same configuration, to have two processes that include Folder Capture input tasks that
watch the same folder. In such a case, if the two tasks are looking for the same data and if the two processes have
the same schedule, both tasks will be competing and it will be impossible to predict which task will in fact be the first
to grab the data at any given time.
PlanetPress Suite Workflow Tools input tasks remove the files found at their source location.
Available Input Tasks
l "Create File Input Task Properties" (page 94)
l "Folder Capture Input Task Properties" (page 95)
l "Folder Listing Input Task Properties" (page 96)
l "Concatenate PDF Files Input Task Properties" (page 96)
l "Email Input Task Properties" (page 97)
l "Error Bin Input Task Properties" (page 99)
l "FTP Input Task Properties" (page 99)
l "HTTP Client Input Task Properties" (page 100)
l "WinQueue Input Task Properties" (page 100)
l "HTTP Server Input Task Properties" (page 101)
l "LPD Input Task Properties" (page 102)
l "Serial Input Task Properties" (page 103)
l "PrintShop Web Connect Input Task Properties" (page 103)
l "Telnet Input Task Properties" (page 104)
l "SOAP Input Task Properties" (page 105)
Two input tasks do not follow the convention of pulling in data from outside sources:
l Create File input tasks generate job files regardless of the presence or absence of data files, since they have no input
location. They are therefore performed like clockwork at every polling interval and consistently generate new job files.
l Error Bin input tasks, which are used for error management, are only present at the beginning of error processes. They
pull in jobs that failed to be correctly generated by tasks included in other processes.
Properties common to all input tasks
As with all other tasks, the "On Error"tab is available. See "Task Properties Dialog" (page 51).
The "Other"tab is common to all input tasks and are available in the Properties of all input tasks.
©2010 Objectif Lune Inc - 93 -