A step that is based on the BuildPDFFromDocuments step template creates a single PDF file for the current job. The step places the documents in the sequence that is specified in the document properties file. After creating the PDF file, the step optimizes the file. The step also creates a JDF job ticket with media and finishing options.
The subsequent steps in the workflow use the PDF and JDF files produced by this step.
This step applies markup if it is defined in one or more RICOH ProcessDirector Plug-in for Adobe Acrobat control files. You specify these control files by name and location in the Build PDF control file properties for this step.
This step combines information from the original RICOH ProcessDirector JDF job ticket with options (simplex or duplex, number of copies, media, and finishing) specified in the Build PDF control files.
Job property defaults
- Duplex: Yes
- Build PDF control file 1: Not set
- Build PDF control file 2: Not set
- Build PDF control file 3: Not set
- Build PDF control file 4: Not set
- Maximum documents in memory: 200
- Page exceptions for sides: Replace with job value
- This step uses the documents and document properties identified in the IdentifyPDFDocuments step to generate the PDF file. If the PDF file changes after IdentifyPDFDocuments runs, the BuildPDFFromDocuments step does not use those changes.
- If the JDF file changes after the IdentifyPDFDocuments step runs, the BuildPDFFromDocuments step does not use those changes, with one exception: media and finishing options for a job. Those changes are not set until BuildPDFFromDocuments runs.
- You can add more than one control file to any Build PDF control file property. If you do, use a semicolon to separate each control file.
- This step discards any page exceptions for media and finishing options specified in the original RICOH ProcessDirector JDF job ticket. If the Page exceptions for sides property is set to Replace with job value, the step also discards sides page exceptions. The step retains media and finishing options for the job. For example, a control file specifies blue paper for page 1 in document 5 of a simplex job. The RICOH ProcessDirector JDF job ticket specifies white paper for the job and green paper for page 7. The BuildPDFFromDocuments step discards the RICOH ProcessDirector page exception for green paper. The JDF job ticket produced by the BuildPDFFromDocuments step specifies blue paper for page 1 of document 5 and white paper for the rest of the job.
- If the PDF job has a JDF job ticket that specifies a combination of simplex and duplex pages, use the Page exceptions for sides property to set how the step combines the Duplex value for the job with the JDF sides settings. If the step creates Sides page exceptions, add an OptimizeJDF step in the workflow after the BuildPDFFromDocuments step to speed processing.
- The value of the Maximum documents in memory property determines the maximum number of documents that are in memory when this step adds documents to the PDF file. If you have memory issues when this step is processing jobs even though other IdentifyPDFDocuments and BuildPDFFromDocuments steps are not running, decrease the value of this property.
- Because the step optimizes the PDF file, you do not need to add the OptimizePDF step after the BuildPDFFromDocuments step.
- If you get unexpected results when you process a PDF 2.0 file with a step based on
the BuildPDFFromDocuments step, do one of these:
- Upgrade the control file to the latest version.
- Place a step based on the OptimizePDF step template in the workflow before the BuildPDFFromDocuments step.
- Use the version of the RICOH ProcessDirector Plug-in for Adobe Acrobat supplied with RICOH ProcessDirector version 3.6 and above to update the control file. Remember to copy the control file to the correct location for RICOH ProcessDirector to use it.