2019.1

1.
On the menu, select Context > Preflight.
2.
Select All, or enter a selection of records. You can specify individual records separated
by semi-colons (;) or ranges using dashes. For example: 2,4,6-10 would print pages 2, 4,
6, 7, 8, 9 and 10.
3.
Click OK.
Preflight executes the template without actually producing output. When a data mapping
configuration is used, any pre- and postprocessors are run as well.
The Preflight window displays any issues once it’s done. It will tell, for example, which
selectors were not encountered in the template.
Double-click a script warning/error (either in the Preflight Progress dialog or in the Preflight
Result view) to open the script in the script editor. The relevant line will be highlighted.
Tip
Be aware that scripts run in a specific order (see "The script flow: when scripts run" on
page822). When one script unintentionally influences the results of another script,
changing the order of the scripts in the Scripts pane may help (see "Changing the order of
execution" on page804).
Note
An image with an unknown file extension is represented by a red cross in the output, but
no error is logged unless the image refers to a local file that does not exist on disk.
Image file extensions that the software recognizes are: AFP, BMP, EPS, GIF, JPG/JPEG,
PCL, PDF, PNG, PS, SVG, and TIF/TIFF.
Using the Script Debugger
The Designer's Script Debugger allows you to set breakpoints in scripts and step through them.
It simulates an output run with only the current record and shows an overview of the state of all
local and global variables, while the Workspace displays the partially merged document.
There are two ways to start the Script Debugger:
Page 808