Specifications

To create a job with (nested) subfolders, you can use the same mechanisms as described above
for archive hierarchies. See Using hierarchy info on page 91 for more details.
Leaving originals in place
Default mode of operation
In its default mode of operation, Switch moves incoming jobs out of the input folder when
injecting them into a flow. In this mode, Switch needs full access rights to rename, create and
remove files and folders in the input folder.
Read-only mode of operation
Several key flow elements (Folder, Submit hierarchy, FTP receive and Mail receive) also support
a read-only mode of operation. This mode is activated by setting the "Leave originals in place"
property for the flow element to yes.
In read-only mode, Switch leaves all incoming jobs in place rather than removing them from
the original location. Since Switch never writes to the input folder, read-only access rights suffice.
Ignore updates
The "Ignore Updates" option can be used for flow elements in read-only mode, if the "Leave
Originals in Place" option is set to yes.
If "Ignore Updates" is set to yes, Switch processes a job only once, ignoring any changes to the
job’s file size or modification date after it was initially processed. This can be used in workflows
where Switch replaces the input job by a processing result, without triggering an endless loop.
If set to no, Switch will reprocess a job when its file size or modification date changes. This can
be useful when submitting a job with the same name of a previously submitted job. In this case,
Switch will use the list of already processed jobs (see below)
Remembering jobs already processed
For each flow element operating in read-only mode, Switch maintains a list of all files/ folders
in the input folder that were already processed (i.e. actually injected in the flow or skipped due
to filters).
Switch automatically updates the list at regular intervals as follows:
• Items that are updated or replaced in the input folder are reprocessed if "Ignore Updates" is
set to no; changes are detected by looking at the byte count and at the most recent of creation
date and modification date.
• Items that disappear from the input folder are removed from the list (to keep its size down).
Reprocessing originals
The user can manually clear the list of jobs already processed as follows:
• Choose the "Reprocess originals" context menu for the relevant flow element. This causes all
remaining original items to be reprocessed when the flow is next activated.
90
Enfocus Switch 10