|
Input tasksInput tasks are the starting point to any process and determine what file this process will being with. Each process must begin with an Input task, and although a given process may have multiple Input tasks, no task can have more than one initial Input task. Initial Input tasksInitial Input tasks are always at the beginning of a process and are always triggered when the process starts. The process itself may start on a schedule or poll at regular intervals, which means the initial Input task only runs whenever the process is set to run. For more information about what happens outside of the process scheduled times and to learn how to set the schedule, see Process properties. If an error occurs during an initial Input task, the On Error tab is never triggered. See Using the On Error tab. Input tasks may either poll a specific location, or wait for jobs to be sent to a specific PlanetPress Workflow Service. It is not recommended to have two Initial Input tasks capturing the same input location, for the following reasons:
It is important to note that Initial Input tasks process files one at a time, and will return to the Input task once the current file has finished processing. Each time it returns to the Input task, it again only captures one single file. It does this until there are no more files in the folder and will also capture any new file that was added during the time it processed other files. Once no more files are found, it stops processing until it is scheduled to run again. This is an important consideration when scheduling a task, as the Folder Capture task will keep capturing files as long as new files are added, even if it means continuing to capture and process outside its scheduled time. It is also important that while the Folder Capture input task is processing files it keeps a copy of each file in a temporary folder, and will not delete any of these files until it has finished processing all of them. This may cause issues with running out of disk space. Secondary Input tasksSecondary Input tasks are placed in the process like an Action task would and will replace the job file in the process with the file they retrieve. Since they are part of the process, they can use data from previous tasks to pull data from a variable location. Secondary Inputs do not follow a separate schedule from the process - they are automatically run when the process triggers them. Considerations
Properties common to all input tasksThe Other tab in the Task Properties dialog (see Task properties) is common to all Input tasks. "Other" Tab
Available Input tasks |
|