PDFProduction

Use this workflow for PDF input files as an example of conditional processing. Other supplied workflows provide more sample steps for processing jobs.

This workflow uses conditional processing to process small jobs with fewer than 20 pages differently from large jobs. The workflow sets values for job properties by using values set in each step in the workflow.

The workflow sends a job from the Count pages step to either the AssignJobValues step or the AssignJobValues2 step based on the job’s total pages. The connector from Count pages to AssignJobValues has a rule named < 20pg with one condition: Job.TotalPages < ‘20’. The connector to AssignJobValues2 has a rule named else with no conditions. AssignJobValues sets the Custom 1 job property to Small job. AssignJobValues2 sets the Custom 1 job property to Large job. When using this workflow, adjust the conditional processing rules as needed for your workflow.

On the SetJobPropsFromTextFile and PrintJobs steps, make sure you set the values of the properties that schedule jobs to printers to the values that you want to use. Jobs do not print unless their scheduling properties match the values set on the corresponding properties of the printer. For example:

  • On the SetJobPropsFromTextFile step, change the Customer name property from RicohSample to the value you want to use.
  • On the PrintJobs step, change the Requested printer property to the value that you want to use. If you use connectors with conditional processing rules to set which printer gets a job, set the Requested printer property value in the AssignJobValues and AssignJobValues2 steps. Values in steps based on the AssignJobValues step template override values in the PrintJobs step.
      Note:
    • If you put two PrintJobs steps in the same workflow, all property values that you set in one step are shared by the other step.

When using this workflow with the LPD protocol, remove ${Job.InputFile} from the Job name property in the SetJobPropsFromTextFile step.

The RunExternalProgram step runs a sample external command using a sample external control file template to produce a CSV file with the values of ten job properties. When using this workflow, delete the RunExternalProgram step or modify it to run an external command that you want to use.

Phases and steps

The illustration shows the steps in each phase of the sample workflow.

Parent topic: Supplied workflows