Find out more about our automatic preflight system

BASIC INFORMATION

PM Preflight was designed to make the process of validating files delivered for production and their visualisation in order to gain the clients approval for printing easier. It cooperates closely with a software callas pdfToolbox server. The software serves almost all types of printing production, which includes:

  • flyers, business cards
  • brochures
  • notebooks
  • stitched folders glued brochures calendars
  • large format products
  • various types of print finishes – varnishes, gilding
  • and many ..

Printing validation includes:

The software is available in two versions:

PRINCIPLE OF OPERATION PM Preflight

PmPreflight Application works as so called hot folder service (daemon) “listening” input folder, where user (or application) places JobDefnition files (described hereinafter). Based on data placed in the Job- Definition system creates the following output files:

PmPreflight supports the following formats of an input files: pdf, jpg, png, gif, tiff and bmp.

LOGICAL DESCRIPTION PM Preflight:

  • input folder: the hot folder where the application “listens” for the JSON formatted JobDefinition files, format described hereinafter
  • shared folder: the folder where the application stores generated files, the folder shall be available for all applications using PmPreflight (may be shared on the network)
  • share name: the name under the Shared Foleder is visible on the It is used in the JSON JobResult files to create absolute output file paths.
  • pdfToolbox server binary path (path to the pdfToolbox CLI)
  • error / warning / info translations file path

PmPreflight writes two different kind of logs:

  • Error log – internal application errors (file access problems, )
  • Preflight log – CSV file containing statistical information about every job executed (such as execution time, file size, file type, job id, ).
  • bleedBox (float) – bleeds during work in milimetres. The system is checking whether the work has proper bleeds, that is to say, whether the format of the installed work is in netto format + bleed from each side. Default 3
  • cornerRadius (float) – the radius of curvature (default 0 mm) in the corners (used as trimbox visualisation for products with curved corners)
  • foldList (List<List<float>>) – a list of crease lines definition for each page. If there are more pages than foldList objects, the next lines will be used for modulo pages. The positive values indicate the vertical crease lines and the negative values, the horizontal crease The crease lines are placed in relation to a specified work time frame (with inclusion of an eventual trade). E.g. for A4 to DL in Z (format defined as width:297, height:210) we have “foldList”: [[99,198]] because on the first and second page of crease lines you should choose 99mm and 198mm from the left side. In case of A4 to DL in C (format defined as width:297, height:210) we have “foldList”: [[97, 197], [100, 200]], because the crease lines on the first side are a mirror reflection of crease lines on the second side (they are not symmetrical).
  • height (float) – expected net height of a page
  • innerMargin (float) – the size of inner safety margin in mm (Default 3 mm)
  • numberOfPages (int) – number of project pages
  • jobId (int) – unique job number (set by an application which uses PmPreflight, used to identify the job)
  • pathResult (string) – a place where PMPreflight should put the Output file which contains the information about the completed task (in JobResult format). The Output files have a following title: json
  • safeArea (float) – The size of the riser in relation to trimbox (Default 3 mm)
  • token (string) – additional job token – useful if within one job (jobld) there are a few preflight processes being conducted.
  • userFileList (List<string>) – a list of files (full path) which are going to be used for
  • width (float) – expected net width of a page
  • checkBleedbox (bool) – informs whether the program should check if there are bleeds in
    • Default false.
  • applyBleedbox (bool) – informs whether the system should add the bleeds if they are lacking (mirror bleeds). Makes sense only with checkBleedbox = true. Default
  • innerMarginTop (float/null) – allows to overload the inner margin and define a different upper safety margin. Default
  • innerMarginRight, innerMarginBottom, innerMarginLeft (float/null) – as explained above for the right, down and left
  • flipMargin (bool) – information flag, which states whether the margins should rotate if the work is (i.e. the format is 210×297 and the client uploaded 297×210). Default true.
  • mirrorMarginOnEven (bool) – information flag which states if the margin should be reflected on even (i.e. for sewn catalogues). Default false.
  • sizeCheckThreshold (float) – the system informs if the uploaded work isn’t too wide/high. This variable specifies at which point such warning should occur (in mm). default
  • prepareFlyer (bool) –Information flag that asks if the system should prepare files for a 3D pamphlet.
  • creases (SheetCreases) – creasing definition in a 3D Makes sense only if prepareFlyer
    • = true. Null value of this variable will generate a flat leaflet. Default null. SheetCreases structure was described under the list of variables.
  • uvPagesCount (int) – amount of pages with UV varnish .
  • uvFilesList (List<string>) – a list of files (full path) which are going to be used for Preflight UV
  • foldMarksFile (string) – a path to the file with the cutting die which is going to be applied in the preview file as a “diecutter” layer. Pages from foldMarksFile file are applied each in turn in a loop,e. in case of a 10 page work and 4 page foldMarksFile file it will be applied two times in full and additionally the first two pages on pages 9 and 10.
  • foldMarksFileFlipped (string) – a path to a file with a cutting die, which should be used if the client uploads a rotated work. If this parameter will not be provided, system will rotate the foldMarksFile on their
  • flippedClockwise (bool) – defines, if the uploaded file is rotated by 90 degrees in relation to    the given format, should the system assume it was rotated clockwise. Default false – the system assumes that the rotated files where turned anti-clockwise.
  • prepareFlippingBookCover (bool) – Defines if the system should treat the uploaded file as the catalogue cover, meaning, should it cut the pictures in a way which enables to use them in 3D
  • spineWidth (float) – makes sense only if prepareFlippingBookCover = It defines how wide is the spine in the uploaded file (in mm). I.e. the file is an A4 catalogue cover with 5mm spine, so its format is 425mm x 297mm. Providing spineWidth parameter = 5, the system in preview will select a 5mm wide spine, moreover, it will prepare jpg file for 3D preview by cutting off  the spine (from both sides).
  • glueOnShortEdge (bool) – Information flag which states if the product is glued on the short   side (it will add in Proof a mark of the glued place). Default false. It also has an influence on generating pictures for 3D
  • glueOnLongEdge (bool) – Information flag which states if the product is glued on the long side (it causes a mark of the glued spot to be added to “proof”). Default false. It also has an influence on generating pictures for 3D
  • overlapWidth (float/null) – A variable which informs about the length of the riser in relation to expected trim Makes sense only with glueOnShortEdge or glueOnLongEdge. In case of products like glued notebook (i.e. A4) a riser ,with which the notebook is glued, is added to the expected trim size. Part of the riser will belong to the spine and some part will overlap its back. This parametre is needed (along with spineWidth and glueOnshortedge or glueOnLongEdge)  to prepare  for  an appropriate 3D preview of the catalogue. Of course in case of A4 notebook with 30mm riser, glued on the short side, the work should have following measurements:  210mm x 227mm. The system does not add  the riser but cuts it for viewing and draws the spine in the right place. Default null.
  • prepareFlippingBookContent (bool) – informs the system whether it should prepare the jpg pictures for previewing the catalogue (middle pages).
  • z flippingBookMergeOnLongEdge (bool) – Information flag that states if the catalogue pages are glued on the long or a short side. Makes sense only in case of using prepareFlippingBookContent or prepareFlippingBookCover. Default false.
  • fixedAutoPages (FixedAutoPages) – a structure that defines files which should be automaticly upploaded to the work. I.e. if we want  to  automatically  add  some  information/advertisement on the second page of a simplex work, then we can use these parameters. Default null. FixedAutoPages structure was described under the list of
  • kfpxProfile – the path to .kfpx file with pdfToolbox profile definition, which should be applied in
  • kfpxUvProfile – the path to .kfpx file with pdfToolbox profile definition, which should be used for preflight files of a selective varnish.

In the float type variables we use ”.” (dot) as a decimal sign.

SheetCreases strucutre description (boxes):

  • vertical (List<floa>) – the list of vertical creases (in relation to work format) in mm. Positive numbers mean creases ”at the front”, negative numbers mean creases ”at the back”.
  • horizontal (List<floa>) – the list of horizontal Mechanism the same as in the verticalcreases.
  • firstFront (bool) – Information flag which states if the first work page should be at the front. I.e. in case of A4 pamphlet to DL in C, the first work page is the outer part and on a 3D preview should be at the back. Default false.
  • foldingOrder (List<string>) – sequence including words like “left” or “right”, which informs of the order of pamphlet

Example (for A4 to DL in C pamphlet, 297×210 format):

“creases”: { “fistFront”: false,

“foldingOrder”: [“left”,”right”], “horizontal”: [],

“vertical”: [-97,-197]

}

FixedAutoPages structure description (boxes):

  • file (string) – a path to the file which will be added
  • fileFlipped (string) – a path to the file which will be added, if the client uploads a work rotated in relation to the given format
  • insertAfter (int) – on which side should be added the pages from this 0 (zero) means, that the pages should be added at the beginning.
  • numberOfCopies (int) – number of page copies from the file which is supposed to be

In order to connect two existing pictures into one (i.e. for visualising product consisting of two compo- nents) you should send a JSON file to PmPreflight in a following format:

  • jobld (string) – as in jobDefinition
  • token (string) – as in jobDefinition
  • pathImage1 (string) – a path to the first image
  • pathmage2 (string) – a path to the second image
  • pathImage1Uv (string, optional) – a path to the first image with UV varnish
  • pathImage2Uv (string, optional) – a path to the second image with UV varnish
  • image1widthMn (float) – the width of the actual work, which the image represents in mm   image1heighMm (float) – the height of the actual work, which the image represents in mm  image2widthMm (float) – the width of the actual work, which the image represents in mm   image2heighMm (float) – the height of the actual work, which the image represents in mm
  • image1widthPx (int) – the width of the first image (in pixels). If not provided, the system will count the parameter on its own
  • image1heightPx (int) – the height of the first image (in pixels). If not provided, the system will count the parameter on its
  • image2widthPx (int) – the width of the second image (in pixels). If not provided, the system will count the parameter on its own
  • image2heightPx (int) – the height of the second image (in pixels). If not provided, the system will count the parameter on its own
  • wegGIMode (bool) – creates images which are mandatory for 3D preview. Requires a 3D module license.
  • overlapMm – number of mm which the 2 image should overlap the 1 image (in mm).
  • joinOn (string) – it can assume top,left,bottom or right The application will join 2 image to joinOn page of 1 image (default top), with overlapMm bookmark.
  • pathResult (string) – as in jobDefnition
  • imagesWithoutMarkers (string) – a list (full path) of miniatures without markers
  • imagesWithMarkers (string) – a list of miniatures (full path) of miniatures with the
  • pdfWithoutMarkers (string) – a path to thePDF output file (without markers)
  • pdfWithMarkers (string) – a path to the ..file (with the markers)
  • pdfUV (string) – a path to the PDF output file (with UV varnish)
  • jobId (int) – job number given for Preflight input
  • token (string) – token given for Preflight input
  • width (float) – page width with considered eventual work rotation. zheight (float) – page height with considered eventual work rotation  znumberOfPages (int) – number of pages
  • logsList<string> – an information list about errors/warnings/applied fixups
  • sourceFiles (List<string>) – a list of files used for preflight
  • flyer (WebGlFlyer) – 3D leaflet definition, used by jacascript that displays the 3D pamphlet
  • flyerBoced (WebGlFlyer) – 3D leaflet definition, used by jacascript that displays the 3D pamphlet in a version with applied
  • flippingBookPages (List<string>) – a list of jpg files for displaying a catalogue in a 3D preview as a middle
  • flippingBookCover (List<string>) – a list of jpg files for displaying a catalogue in a 3D preview  as a cover
  • flippingBookFlipVertical (bool) – Information about rotating the catalogue preview by 90 degrees (i.e. in case of a vertical catalogue sewn on the short edge).

JobDefiniton and JobResult files use JSON format.

  • mergedImage (string) – a path to the connected file
  • mergedImageUv (string) – a path to the connected UV file
  • jobld (string, string) – copied from jobDefinition
  • widthMm, heightMm (decimal, decimal) – work measurements after connection, turned into mm
  • widthPx, heightPx (int, int) – connected file measurements in pixels
  • webGIWidthPx, webGIHeightPx (int, int) – Texture for webGI measurements
  • succes (bool) – informs, if the connection has succeeded
  • logs (List<string>) – list of eventual errors during the connected image creation

In the Jobresult file in the logs box there is a list of warnings/errors/fixups, which could be divided into two groups:

being a result of using profile .kfpx on file (all information which the Callas pdfToolbox can return are enclosed in the profile definition).

  • detected by and application before or after using preflight:
  • blankPage – informs about blank pages in the project
  • fileFliped – informs that the input project is rotated in relation to given parameters (i.e. 297×210 was uploaded instead of 210×297).
  • pageFlipped – Informs that the project pages are reversed in relation to each
  • fileTooWide – Informs that the input file is too wide, meaning its bigger than net + bleedbox
  • fileTooNarrow – Informs that the input file is too narrow, meaning its smaller than the trim
  • fileTooHight – Informs that the input file is too high, meaning its bigger than net +
  • fileTooLow – informs that the input file is too low, meaning its smaller that trim
  • preflightFailed – Informs that the preflight process
  • mirrorBleedAdded – Informs that the preflight process has added
  • mirrorBleedNeeded – Informs that the preflight process has detected lack of
  • tooFewPages – Informs that the given number of pages is smaller than the mandatory
  • tooManyPages – Informs that there are more pages in the work than
  • tooManyUvPages – Informs that in the UV varnish file there are more pages than
  • multiStripImagesNotSupported – Informs that there was given a tiff file with many pages for the input, which the system does not
  • fileTypeNotSupported– Informs that a file was added for the input in a format which is not supported.
  • fileCorrupted– Informs that a corrupt file was added for the

For each log we can define (in a .cvs file given as an input parameter of the program) following information:

  • Severity – a type of error (i.e. info, warning, error, fatal), which can be later used by software that can speak JobResult. The fact alone of a log appearing in JobResult (i.e. fileTooNarrow) does not mean that preflight failed. Its just an information which can be used by outer software in any manner.
  • Message – Text information about an error – any character string, which can be later used by software that interprets the JobResult files.
  • InfoUrl – URL address leading to www page which contains the information about the warning /error.

All parameters are optional. Not giving the .csv file with information as a parameter for an application will cause the JobResult file to contain only warning / error / fixup codes.

Apart form Jobresult files, the program also returns JobStatus files (into the same catalogue in which Jobresult is finally placed). The files have their name constructed the same as JobResult files, with the exception, that the extension is .status.json and not .json. The JobStatus file includes the following data structures:*

  • statusCode (string) — a code status
  • info (string) — text description of the status
  • progres (int) — percentage progress

2D View

3D View

Are You Ready To Start?

More Courses

You might also be interested in these courses

AutoIMP

jak zautomatyzować proces impozycji bez udziału człowieka

AutoIMP jest systemem, który w oparciu o współdziałanie kilku rozwiązań ma prowadzić do pełnej automatyzacji systemu generacji, analizy i akceptacji arkuszy do druku.

Poznaj bliżej nasz system do automatycznej impozycji

Zobacz więcej

AutoIMP

how to automate the imposition process without human intervention

AutoIMP is a system that, based on the interaction of several solutions, is to lead to full automation of the generation, analysis and approval of sheets for printing.

Find out more about our automatic imposition system

See more

CQC

KONTROLUJ DRUK NA KAŻDYM ETAPIE I ZWIĘKSZ PRODUKTYWNOŚĆ.

Używaj systemu, który obliczenia zrobi za ciebie. Oceń wyniki w sposób rzeczywisty i obiektywny. Cqc – inteligencja w poligrafii. Używaj systemu, który obliczenia zrobi za ciebie. Oceń wyniki w sposób rzeczywisty i obiektywny. Cqc – inteligencja w poligrafii.

Poznaj bliżej nasz system do kontroli druku

Zobacz więcej

CQC ENG

CONTROL YOUR PRINT AT EVERY STAGE AND INCREASE PRODUCTIVITY.

Use a system that does the calculations for you. Evaluate the results realistically and objectively. Cqc - intelligence in printing. Use a system that does the calculations for you.

Find out more about our print control system

See more