TransformToPDFWithMediaInfo

A step based on this step template calls the Advanced Transform feature to transform AFP or PostScript input into PDF output. The step creates a PDF file for the job and a JDF job ticket with media information, including page exceptions.

Basic job property defaults

  • Duplex: Not set
  • Page range to transform:
  • Path to ICC profile:
  • Path to custom profiles: ${AIWDATA}/cpt/profiles
  • PDF page scaling factor:
  • Transform input stream: Use current
  • Transform page length:
  • Transform page width:
  • Transform resolution (dpi):

Advanced job property defaults

  • External command: perl ${AIWDATA}/bin/callxform.pl -C ${getControlFileName()} -i ${getCurrentFile(${Job.Transform.InputStream})} -o ${getAbsoluteFileName( print, pdf, write)} -msg.remove AFP2014
  • External control file template: /aiw/aiw1/control_files/external_programs/xform.cfg
  • External program code page: Not set
  • External program language: Not set
  • Font fidelity: Strict
  • Generate PDF TOC: Not set
  • Include fonts in the output: Not set
  • Media information command: perl ${AIWDATA}/bin/callxform.pl -C ${getControlFileName()} -i ${getCurrentFile(${Job.Transform.InputStream})} -type xif -loglevel I -logdate -logtime -logdir ${Job.SpoolFileStem}tmp -logfile ${Job.ID}.xif.log -verbose -relaxed -msg.add PSI3002 -remove abcefhilnoprst01234
  • Path to media mapping file:
  • Path to system fonts:
  • Path to TrueType fonts:
  • Render output as: Text
  • Valid return codes: 0

Usage Notes

  • This step requires at least one of the following input transforms for the Advanced Transform feature:
    • InputAFP
    • InputPS
    The step also requires the OutputPDF output transform.
  • If you are retrieving media information from an AFP data stream, you must edit the value of the Media information command property. Add the -enablefdp argument between the input argument, -i, and the type argument, -type. This example shows the edited command:
    perl ${AIWDATA}/bin/callxform.pl -C ${getControlFileName()} -i ${getCurrentFile(${Job.Transform.InputStream})} -enablefdp -type xif -loglevel I -logdate -logtime -logdir ${Job.SpoolFileStem}tmp -logfile ${Job.ID}.xif.log -verbose -relaxed -msg.add PSI3002 -remove abcefhilnoprst01234

    If you are retrieving media information from a PostScript data stream, the command works without any edits.

  • If the input PostScript or AFP job specifies a combination of simple and duplex pages, the JDF job ticket produced by the step includes a Sides page exception for every page in the job. To speed processing, add an OptimizeJDF step in the workflow after the TransformToPDFWithMediaInfo step.
  • The step creates a JDF file in the spool directory named Job.ID.overrides.jdf, for example, 10000001.overrides.jdf.
  • When the step generates the JDF job ticket, it uses the media names in the AFP or PostScript input, for example, TRAY1. The media names in the JDF job ticket must match the names of Ricoh ProcessDirector media objects. You can use any of these methods to make the media names match:
    • You can change the media names in the AFP or PostScript input.
    • You can create Ricoh ProcessDirector media objects with the same names as the media names in the AFP or PostScript input.
    • You can create a media mapping file that maps the media names in the AFP or PostScript input to the names of Ricoh ProcessDirector media objects.
      This example maps four AFP or PostScript media names (A4, Letter, TRAY1, and TRAY2) to four Ricoh ProcessDirector media names:

      # AFPorPSmedia=RPDmedia
      A4=A4 Plain
      Letter=Letter Color
      TRAY1=Letter Preprinted
      TRAY2=A3 Plain

      For information about mapping media names in the AFP or PostScript input to Ricoh ProcessDirector media names, refer to the Information Center.

  • If any media name in the JDF job ticket is not defined as a media object in Ricoh ProcessDirector, the job goes into the error state. The Reason for wait status value is No matching media.
  • After this step runs, you can see the results by displaying the page exceptions for the job.
  • Steps based on the TransformToPDFWithMediaInfo step template have positional properties. You can place a step with positional properties in a workflow multiple times, and the job properties can take different values when each step is used. In the job property notebook in the legacy user interface, Ricoh ProcessDirector supplies the names of the phase and step where the value of each positional job property is used. For example: Transform input stream[Prepare][TransformToPDFWithMediaInfo]. In the job property notebook in the updated user interface, the phase and step names appear as section names with the properties of the step shown inside the section.
 
Copyright © 2017, 2018