Specifications

DescriptionProperty
The number of upper levels for which not to cleanup subfoldersStarting from this level
Archive hierarchy
Archive hierarchy is a consumer that creates a nested hierarchy with one or more levels of
subfolders. It is used to archive jobs into a structured hierarchy at the end of a flow. The resulting
jobs are to be consumed (and removed) by an external process. The backing folder (on disk) for
an archive hierarchy should typically be user-managed.
It is not allowed for an external process or a user to place files into an archive hierarchy.
An archive hierarchy uses the hierarchy location path stored in a job’s internal job ticket to
determine where the job should be stored, up to the nesting level specified for the archive
hierarchy. Any superfluous segments in a location path are ignored. Subfolders are created
automatically.
See Using hierarchy info on page 91 for more details.
Keywords
Keywords can be used with the search function above the Elements pane.
The keywords for the Archive hierarchy element are:
• backing
• folder
• subfolder
• structure
• output
Connections
Archive hierarchy does not allow outgoing connections
Properties
DescriptionProperty
The name of the flow element displayed in the canvasName
The path of the archive hierarchy's backing folder on disk, or
"auto-managed"
Path
The number of nested subfolder levels in the archived structure; see
also the description on subfolders earlier.
Subfolder levels
If set to yes, the unique name prefix added to the filename by Switch
is removed before placing the job in the archive hierarchy; the default
Strip unique name
is to strip the prefixes from jobs deposited in an archive hierarchy -
224
Enfocus Switch 10