2019.1

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 tasks
Secondary 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
l If your initial Input task does not start, either because there is no data to capture or
because the process is out of its schedule, any secondary Input task will not run either.
l Secondary Input tasks replace both the job file and the job info variables. They do not
change local and global variables.
l If your secondary Input task creates a job file using a different emulation, you will need to
use a "Change Emulation" on page316 task after the secondary Input task to correctly
change to that emulation. (For more information about emulations, see "About data
emulation" on page54.)
Properties common to all input tasks
The Other tab in the Task Properties dialog (see "Task properties" on page235) is common to
all Input tasks.
"Other" Tab
l
Job Information group
l
Information elements: Indicates what Job Info variables are automatically created
by the input task.
l
Add lines before first data page: Using the arrows keys you can add any job
information directly at the beginning of your data file.
Page 240