Specifications

• input
• hot
• watched
Connections
Submit hierarchy does not allow incoming connections.
Submit hierarchy injects folder filter properties into its outgoing connections so that it is possible
to include/exclude certain subfolders in the hierarchy for particular connections. Also see the
"skip folders" property described below.
Note: The number of eligible jobs for processing is shown in a small rectangle to Submit hierarchy
element.
Properties
DescriptionProperty
The name of the flow element displayed in the canvasName
The path of the submit hierarchy's backing folder on disk, or
"auto-managed"
Path
If set to yes, incoming jobs are left untouched in the hierarchy;
Switch never writes to the hierarchy so read-only access rights
suffice
Leave originals in place
If set to no (the default), incoming jobs are moved out of the
hierarchy; Switch needs full access rights to rename, create and
remove files and folders in the hierarchy
The Ignore Updates option is only available if Leave Originals is
set to yes.
Ignore Updates
If set to yes, a job will only be processed once, regardless of any
changes to the file size or modification date. This can be used
for workflows where the input job is replaced by the processing
result, to avoid triggering endless loops.
If set to no, the job will be reprocessed when its file size or
modification date is different. This allows processing jobs which
have the same file name as previously submitted jobs.
Used to set the minimum file size (in KB) limit before Switch
picks up the files or folders. To set no limits, leave it empty.
Minimum file size (KB)
The frequency with which this submit hierarchy is scanned for
newly arrived jobs; if “Default” or zero the global user preference
is used instead; see Processing on page 187
Scan every (seconds)
If set to yes, the submit hierarchy detects (and moves) newly
arrived jobs only during a certain time of the day (specified in
the subordinate properties)
Time-of-day window
221
Enfocus Switch 10