Page tree
Skip to end of metadata
Go to start of metadata

The way that you use the views to create, edit, and preview press runs can be affected by such factors as job types, product requirements and complexity, the number of people who work on the jobs, the feature set supported by your software license, and personal preferences. Here are a few possibilities:

  • You might first use the Pages view to collect the input files or define file placeholders and set up the run list, and then switch to the Press Runs view to build the press-run layouts.
  • For ganged jobs or for basic single-product, single-part jobs, you might work entirely in the Press Runs view to create and interactively edit and preview any number of sheetfed and multiweb press runs to accommodate the job's pages and manage the stock, media, marks, and layout for each sheet or web.
  • For intelligent setup of ganged press runs, you might use the AutoGang feature in the Press Runs view.
  • Jobs for complex publications might be done in stages. For example, a planner, customer service representative, or senior prepress operator might start a job by providing the product intent in the Assembly view. The job can then be completed by a prepress operator who creates the layouts and prints the press runs.
  • In a JDF-based workflow, you use the Assembly view to provide any information that was not received via JDF, and then check the auto-generated press-run layouts in the Press Runs view.


  • No labels