2019.2

executed, assuming the script is enabled.
l
The warning icon (!) appears, for example, when a script refers to an unknown field in
the record set, or when ; is missing after a statement.
l
The error icon (x) displays when the script results in an error, for example, when it uses
an undeclared variable.
If an expanded script contains errors or if there are warnings, icons appear in the overview ruler
on the right hand side of the editing area. These icons are shown relative to their position in the
script and do not move as you scroll down. You can click on an icon to quickly jump to the error
or warning. Script errors are highlighted by a red icon, and warnings in yellow. The topmost
icon will display red if any errors exist in the script at all.
Doing a Preflight
In addition to the icons and messages in the Scripts pane, a preflight can show if your scripts
function as expected before generating output:
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877). 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859).
Page 864