OptimizeJDF
For example, the step combines page exceptions for blue media on pages 3-4 and blue media on pages 5-6 into one page exception for blue media on pages 3-6.
Some JDF job tickets have a Sides setting on every page even if only one sheet in the entire job is simplex. When the step processes those JDF files, it makes groups of the series of pages with the same Sides value. Then it counts which Sides setting has the most groups and sets that Sides value at the job level and only inserts page exceptions for the pages that have a different Sides value. JDF job tickets with fewer page exceptions are processed faster by steps in RICOH ProcessDirector.
The JDF job ticket produced by this step is functionally equivalent to the original job ticket. The subsequent steps in the workflow use the JDF file produced by this step.
Job property defaults
- None
Usage Notes
- This step is useful if a JDF job ticket from a source outside RICOH ProcessDirector has not been optimized.
- If the PDF Document Support feature is installed, this step is useful when the BuildPDFFromDocuments step adds page exceptions for media, finishing, and sides options. Run this step after the BuildPDFFromDocuments step.
- When RICOH ProcessDirector sends a job to a Ricoh PDF or Custom PDF printer, the printer object provides the same function as the OptimizeJDF step. However, you cannot use RICOH ProcessDirector to view changes to JDF job tickets made by the printer object.