In this article, you will learn
- which Checks are available in Check-in Preflight and Fixup Templates regarding Quality and Content, and
- which solutions are provided to fix the found issues.
1. Introduction
When print files are uploaded into the Workflow, the documents are checked using Check-in Preflight and Fixup Templates to identify potential errors or warnings at the very beginning of the production process. These errors and warnings can be displayed on the respective page within the Workflow and provided to the customer as a PDF report for further clarification.
The Preflight Check of the print file is performed based on the enabled checks and the severity levels defined for each individual Check – Error, Warning, or Info.
2. Available Checks for Quality and Content
To take full advantage of a Check-in Preflight and Fixup Template, the templates must first be created. A template essentially consists of Checks and Fixups. Currently, more than 58 Checks are available in the Workflow. To maintain clarity, the individual Checks are divided into different categories.
This article provides a detailed description of all checks that fall under the category Quality and Content.
2.1. Bleed is available
Category: Object
Description: This Check verifies whether the expected Bleed is present in the file. Additionally, it checks if the BleedBox is correctly set and whether the entire Bleed is filled with printable content. By specifying the safety zone also, it also ensures that no text elements are positioned within this area.
Solution: Using the Fixups «Create Bleed by Mirroring», «Create Bleed by Upscaling» and «Create Bleed on Irregular Shape», the Bleed for the print file can be generated retroactively for the print file. This helps prevent cutting errors that can cause unwanted white edges («blitzers»).
Figure 1: The activated Check Bleed is available
2.2. Check Barcode content
Category: Object, Page Content
Description: This Check validates the content of a Barcode or QR code against the value entered in the input field «Barcode Content». If no Barcode or QR code is present in the Print Item, the Check is skipped, and no hit is reported.
Solution: If the Barcode or QR code is incorrect or unreadable, the code values must be adjusted afterwards. A dedicated Fixup is not available for this purpose.
Figure 2: The activated Check Check Barcode content
Please note...
Validating Barcode content requires significant resources, as the entire Print Item must be fully rendered in order to identify and analyze the Barcode.
2.3. CMYK Object uses Rich Black
Category: Object, Color, Text
Description: This Check verifies whether CMYK objects of the selected object type – Text, Vector, Text and Vector, Image, or All Objects – are printed using Rich Black. While text and vector objects are checked based on a maximum value for each CMYK channel, images are evaluated according to the maximum total ink coverage (TAC). This check helps identify objects in the print file that uniformly rendered as black or that are printed with an excessively high ink coverage.
Solution: Non-uniform black objects can be adjusted using the Fixup «Redye CMYK Objects». The Fixup «Map CMYK Values from Vector Objects to a Spot Color» can be used to convert the affected objects into a Spot Color.
Figure 3: The activated Check CMYK Object uses Rich Black with predefined values
2.4. Comment inside the print area
Category: Page Content
Description: This Check verifies whether any annotations such as text corrections, notes, text highlights, stamps, etc., are located within the printable area of the print file. Comments are ignored by default during rendering and will not appear in the printed output.
Solution: If text corrections or highlights were added as comments in Acrobat Pro or Adobe Reader and are intended to be printed, the Fixup «Render Comments» can be used.
Figure 4: The activated Check Comment inside the print area
2.5. Compare the content of a user-defined field
Category: Object, Page Content, ERP
Description: This Check compares the content of the selected user-defined field with the value entered in the input field Comparison Value to generate a match. Additionally, it can verify whether a specific Spot Color is present in the print file. A match is triggered, for example, if the value of the user-defined field is «Foil» or «Metallic» and the print file does not contain the Spot Color «White».
Solution: If the content of the user-defined field does not match the comparison value, the cause of the issue must be investigated. In some cases, manual corrections may be possible, and in other cases, it may be advisable to request a corrected print file. Missing Spot Colors such as «White» can be added using the Fixup «Create Spot Color Separation to Printed Objects».
Figure 5: The activated Check Compare the content of a user-defined field
2.6. Document is damaged
Category: Document, PDF/X-1a, PDF/X-3, PDF/X-4, PDF/X-6
Description: This Check determines whether the document is damaged. Although Acrobat attempts to repair the file when opening it a flawless display or error-free output on the printing device cannot be guaranteed. Additionally, damaged documents are not permitted in any PDF/X-based workflows.
Solution: In this case, a new print file should or must be requested from the file creator.
Figure 6: The enabled check Document is damaged
2.7. Document is encrypted
Category: Document, PDF/X-1a, PDF/X-3, PDF/X-4, PDF/X-6
Description: This Check identifies whether the document is encrypted or requires a password to be opened or modified. Encrypted documents cannot be processed within the Workflow and are not permitted in any PDF/X-based workflows.
Solution: Request an unencrypted version of the file from the data provider, or try to decrypt the file using a service such as https://freemypdf.com/.
Figure 7: The activated Check Document is encrypted
2.8. Glyph uses overlapping path objects
Category: Object, Font, Page Content
Description: This Check detects whether individual characters in the layout overlap each other. While such overlaps are often an intentional design element, in some cases they may indicate an incorrect font encoding that causes unintended character misplacement.
Solution: If the overlapping Glyphs are the result of incorrect font encoding, the data provider must supply a corrected print file.
Figure 8: The activated Check Glyph uses overlapping path objects
2.9. Object with white stroke is not set to Knockout
Category: Object
Description: This Check examines the print file for white, overprinting strokes – CMYK=0/0/0/0, RGB=255/255/255, and gray=100. White overprinting strokes are removed during rendering and will not appear as graphic elements in the output.
Solution: White overprinting strokes can be set to Knockout in the Workflow either by applying the Fixup «Set White Objects to Knockout» or by enabling the option Set White Objects To Knockout under Administration > Settings > Preflight / Fixups > General.
Figure 9: The activated Check Object with white stroke is not set to Knockout
2.10. RGB Object uses Rich Black
Category: Object, Color, Image, Text
Description: This Check verifies whether RGB objects of the selected object type – Text, Vector, Text and Vector, Image, or All Objects – are printed as Rich Black. Text and vectors are checked by specifying a minimum value for each RGB Channel, while for images, the maximum total ink coverage (TAC) is used as a benchmark. This Check helps to identify objects in the print file that may not appear as uniformly black in print or that might be printed with excessive ink coverage.
Solution: Rich black RGB objects must first be converted to the CMYK color space using the Fixup «Convert to CMYK». Afterwards, non-uniformly black objects can be adjusted with the Fixup «Redye CMYK Objects» or converted to a Spot Color using the Fixup «Map CMYK Values to a Spot Color».
Figure 10: The enabled check RGB Object uses Rich Black
2.11. White object is not set to Knockout
Category: Object
Description: This Check analyzes the print file for white objects (CMYK=0/0/0/0, RGB=255/255/255, and gray=100) that are overprinting. White overprinting objects will disappear during rendering and will not appear as graphical elements in the final print output.
Solution: White overprinting objects can either be removed in the Workflow using the Fixup «Set White Objects to Knockout» or be set to Knockout by enabling the option «Set White Objects To Knockout» under Administration > Settings > Preflight / Fixups > General.
Figure 11: The activated Check White object is not set to Knockout
«White object is not set to Knockout»
Use this Check only if you want to detect white, overprinting objects. In this case, the other Checks – «White text is not set to Knockout», «White stroked text is not set to Knockout», and «Object with white stroke is not set to Knockout» do not need to be activated. If these Checks are activated in addition, all hits will appear twice!
2.12. White stroked text is not set to Knockout
Category: Text
Description: This Check analyzes the print file for white – CMYK=0/0/0/0, RGB=255/255/255 and gray=100 – overprinting strokes applied to text. White overprinting text strokes will disappear during rendering and will not appear as a graphical element in the printed output.
Solution: White overprinting text strokes can either be removed in the Workflow using the Fixup «Set White Objects to Knockout» or set to Knockout by enabling the option «Set White Objects To Knockout» under Administration > Settings > Preflight / Fixups > General.
Figure 12: The activated check White stroked text is not set to Knockout
2.13. White text is not set to Knockout
Category: Text
Description: This Check analyzes the print file for white (CMYK=0/0/0/0, RGB=255/255/255, and gray=100) overprinting text. White overprinting text will disappear during rendering and will not be visible as a graphic element in the final print output.
Solution: White overprinting text can be removed in the Workflow using the Fixup «Set White Objects to Knockout» or set to Knockout by enabling the option «Set White Objects to Knockout» under Administration > Settings > Preflight / Fixups > General.
Figure 13: The activated Check White Text is not set to Knockout
Article update: Workflow 1.20.1 – 05/2025