8.6

l Split PDFfile based on Metadata group:
l Metadata Level: Determines on which level of the metadata the split occurs. This
can be Group, Document to Data page.
l Sequencing based on:
l The following number of occurrences of the level: Determine a sequence
based on the number of instances found for the metadata level currently
processed. For example, if the Metadata level is set to Group, and this value is
set to 3, each sequence contains 3 groups (except, possibly, the last one,
depending on the number of groups left in the last sequence). The next loop
starts with the next group after this sequence.
l Thefollowing number of sequences in the job:Divides the metadata into a
set number of sequences and equally distributes the number of levels
between the sequences. For example, it the Metadata level is set to
Document, and this value is set to 5, a 100 document job file will be divided
into 5 sequences of 20 documents each.
l Thefollowing rule: Determine if a new sequence starts or if the current one
ends. For each metadata level, the current value of the specified metadata
attribute / field is compared with the one in memory. If they are different, either
a new sequence starts or the current sequence is ended. The next sequence
starts with the next metadata level being processed. For details see the Rule
Interface.
l Optimize resulting PDF: Select to specify whether the resulting PDF should be
optimized. Optimization can lead to a significant reduction in the size of the PDF, but it
may also add a certain amount of time to the process. This option should only be
unchecked if the timing of the process is critical and needs to be done quickly, but keep in
mind that the resulting PDFmay be much larger than it should be and may even be too
large for PlanetPress Workflow to handle.
l Reset Metadata according to new PDF: Metadata will be recreated according to the
new PDFthat was created, including page numbering, etc.
On Error Tab
The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog"
on page723.
By default, any action task, branch, splitter or condition that generates an error will simply be
ignored, and the task just under it (not within a branch)will be given control of the job file
without any modification. Any initial input task that generates an error will stop the process from
Page 368