2022.1

elements in the results.
l Each matched element: The script runs once for each element that matches the selector.
The current element is accessible via the this object (see "this" on page1425). If the
script targets (something in) a row that is bound to a detail table, the current detail record
is accessible via this.record.
Note
The scope of Control Scripts can't be set, because they don't have a selector.
Managing scripts
Changing the order of execution
When a record set is merged with a template to generate output, all scripts are executed once
for every record in the record set, in the order in which they appear in the Scripts pane at the
bottom left.
The order in which scripts are executed is particularly important when one script produces
content that contains a selector for another script. If the other script has already been executed,
it will not run again automatically. So, scripts that produce content that contains one or more
selectors for other scripts, need to come first.
To change the order in which scripts are executed:
l Click a script or a folder in the Scripts pane at the bottom. Drag it up or down and drop it.
Note
Control scripts are always executed first, regardless of where they are in the Scripts pane.
They can not be excluded from execution for a specific context or section, using the
execution scope of a folder; see "Execution scope" on the facing page. What you can do
is disable the script or the containing folder; see "Enable/disable scripts" on page927.
Script folders
Scripts can be organized in folders. Why would you do that? For three reasons:
Page 925