Specifications

DescriptionProperty
The string is used only for the purpose of determining which jobs
belong together; it has no other meaning
A job (using Custom scheme) is completed if this condition is true,
even if the required number of jobs hasn’t arrived. The condition
Complete condition
is re-evaluated for each newly arrived job in the context of that
job. A value of None means this option is disabled.
If set to no, the metadata for the assembled job is copied from a
single (arbitrary) incoming job, and metadata from all other jobs
Merge metadata
is lost. If set to yes, the metadata for the assembled job is derived
from all incoming jobs:
• All email addresses are used, and email bodies are merged.
• User name and Job state will be arbitrarily selected from all
jobs, or will be empty if this is empty for all jobs
• The highest priority among all incoming jobs will be used.
• Private data and External datasets will all be retained. If
multiple jobs have private data or external datasets with the
same tag, a dataset or value will be arbitrarily chosen.
All other metadata will be arbitrarily selected from one of the
incoming jobs
The filename of the created job folder, or Automatic to construct
a default name depending on the scheme (e.g. the reassemble
scheme uses the job name stored by the ungroup tool)
Job folder name
Question marks in the filename pattern are replaced by a running
count; e.g. Job??? will produce Job001, Job002, ...
Variables ( and script expressions) are executed in the context of
one of the incoming jobs, chosen arbitrarily
The number of nested subfolder levels in the job folder being
assembled
Subfolder levels
The tool uses the hierarchy location path or the ungrouped job
private data to determine where the job should be stored, up to
the specified nesting level (similar to archive hierarchy)
If set to yes, the unique name prefix is removed before placing
the job in the job folder being assembled
Strip unique name
Determines what happens when “strip unique name” is set to
yes and a job arrives with the same name and location as a job
already residing in the job folder being assembled:
Duplicates
• Overwrite: replace the existing job with the new one – this is
the default behavior
• Keep unique name: preserve the new job’s unique name prefix,
leaving the existing job untouched (without unique name
prefix)
232
Enfocus Switch 10