2020.2

Task See topic Field/function of
section object
Note: When a Control Script changes the
size of a section, it should also change
the size of the linked Media; this is not
done automatically. While the output may
still look good, a size mismatch can
cause an issue if a script or another
component assumes that the media size
matches the section size.
In case of a size mismatch a preflight will
show a warning (see "Doing a Preflight"
on page865).
Control Script: Page numbering
This topic explains how to write a Control Script that changes the page numbering in Print
sections. Note that when you add a Control Script, it already contains a script to make the page
numbering continue over all Print sections.
For information about Control Scripts in general, see "Control Scripts" on page890 and
"Control Script API" on page1379. If you don't know how to write scripts, see "Writing your own
scripts" on page853.
How to change page numbering in a control script
A Control Script can make the page numbering continue over all Print sections or let it restart
on a section. This is done by setting the restartPageNumber field on a section to true or false.
For example: merge.template.contexts.PRINT.sections['Section 2'].restartPageNumber =
true;. (Also see "section" on page1426 and "Control Script API" on page1379.)
Page numbering starts with page 1 for each section. If for a section restartPageNumber is set to
false, that section will start with the page number following the last page of the previous
section.
Note that even if a section is not enabled (so it will not be outputted), its restartPageNumber flag
is still taken into account for composing the page number sequences.
By default, each section has restartPageNumber = false when the first control script runs.
Page 894