A preflight operation is a quality check of your document.
The preflight operation checks if any rules are violated in the PDF file(s). The set of rules is fixed. Some of the rules can be configured. If enabled, the automatic preflight operation is applied when a customer submits an order. The automatic preflight operation allows you to fix the violations according to the configured rules or cancel the operation with that document. A preflight report and an annotated file are generated. The preflight report shows a summary of the problems that have been found. The annotated file shows the complete document with the location of any found problems and fixes. The manual preflight operation automatically fixes the violations according to the configured rules. Some problems are detected by the preflight operation, but cannot be fixed automatically. It is recommended that you fix these problems manually before you print the job.
This topic describes the complete configuration of the preflight workflow.
You have to configure the preflight settings in the [Configuration] workspace:
Enable and configure the preflight rules for the [Order processing] console
Option preflight is now available in the [Order processing] console. The operator can manually preflight the PDF files.
Enable and configure the preflight rules per web shop
Option preflight is now available in the web shop. The operator can manually preflight the PDF files.You can configure the preflight settings for each web shop. These settings will also be used when you create an order for this web shop in the [Order processing].
Configure the number of preflight processes
You can configure the number of preflight processes that can run in parallel.
Email the preflight report to your customer
You can attach the preflight report to emails to your customer.
Optionally, you can customise the preflight settings per user group
You can customise automatic preflight for each user group. The custom settings overrule the web shop settings for the concerning user group. The custom settings are used in all web shops for the concerning user group.
Click [Order processing] - [Preflight].
Enable the rules that you want to use in column [Enabled].
Click on the bar of the rule that you want to configure. If the bar expands, you can configure the rule. If the bar does not expand, you can only enable or disable the rule.
You can configure some rules to detect and fix a violation. Other rules can only be configured to detect a violation. These violations can only be solved in the concerning PDF file by the customer or the operator.
Define the [Severity] of each rule.
[Warning]
A violation of the rule is detected. You can ignore the warning.
[Error]
A violation of the rule is detected. The violation of the rule must be fixed.
You can define a timeout.
When the timeout value is exceeded, the preflight operation is cancelled.
Click [Save].
Click [Web shop] - <web shop> - [Preflight].
Enable the rules that you want to use in column [Enabled].
Click on the bar of the rule that you want to configure. If the bar expands, you can configure the rule. If the bar does not expand, you can only enable or disable the rule.
You can configure some rules to detect and fix a violation. Other rules can only be configured to detect a violation. These violations can only be solved in the concerning PDF file by the customer or the operator.
Define the [Severity] of each rule.
[Warning]
A violation of the rule is detected. You can ignore the warning.
[Error]
A violation of the rule is detected. The violation of the rule must be fixed.
You can define a timeout.
When the timeout value is exceeded, the preflight operation is cancelled.
[Enable automatic preflight]
When you enable this option, the application preflights each PDF file that the customer adds to an order in the web shop. When the customer adds a non-PDF file, then the file must be converted to PDF first before the preflight operation can start.
Click [Save].
Click [System] - [Services settings] - [Automatic process].
Set the number of preflight processes.
It is recommended that you define the same number of preflight processes as you have web shops for which option [Enable automatic preflight] is enabled.
The number of processes can impact the performance of the application.
Click [Save].
Click [Order processing] - [Workflow configuration] - [Email templates].
Select an email template.
Enable option [Attach the preflight report].
Most, but not all, email templates offer option [Attach the preflight report].
Click [User management] - [User groups] - [User group settings].
Click on the bar of the user group that you want to customise. The user group expands.
Scroll to section [Enable automatic preflight].
A customer or operator can be part of a user group. The settings of the user group overwrite the settings for PRISMAdirect.
Web shop
The user group uses the value of setting [Enable automatic preflight] as defined for the web shop.
Custom = Yes
Automatic preflight is enabled for each web shop for the concerning user group. You have to configure the preflight rules, see procedure Enable and configure the preflight rules per web shop.
Custom = No
Automatic preflight is disabled for each web shop for the concerning user group.
Click [Save].