Print job analysis module
In a print workflow, all data contained in the (PJL) header of the print job (e.g. user login name or PC IP address) is always analyzed. The number of pages is also always determined.
If you want the rest of the data stream, i.e. the pages of the print job, to be analyzed as well, use the Print Job Analysis module. Only then are the characteristics available in the workflow (for example, for Accounting or for The Decision Module).
The module also generates the print preview (if the module is missing, no print preview is available on the device).

The module may occur only once in the workflow.

The module should be executed immediately after the start of the workflow so that the data are available in the workflow.

The module can be connected to all modules (this can result in nonsensical workflows).


You can switch the creation of the print preview on or off here, see Print Preview.

Specify how many pages of the print job should be analyzed. The setting 0 (default setting) causes all pages to be analyzed.
If a print job has more pages than were analyzed, the analysis will most likely not be correct. When printing on a device without an Embedded Client, this has an effect on billing, since the analysis result is used for billing.
- All pages that have not been analyzed are defined as color pages (which can mean that a print job that was printed completely in black and white is then a color job).
- The paper size of the last analyzed page is assumed for all following pages.
If the print job is output on a device with Embedded Client, all pages will be billed correctly because the device outputs an event with the actual page properties for each page – these are used by IQ4docs for billing, see also Page Counting.
If the number of pages to be analyzed was set by an entry similar to <add key="MaxPagesForDetailedAnalysis" value="20" /> in the LocalService.config of the PrintService, this value is used and not the value that can be set here.


The print service accepts and analyses print jobs. It also checks the user rights when printing. It also sends the print data to the device. Its log file is Logs\PrintService.log.