2022.1

For information about Control Scripts in general, see "Control Scripts" on page425 and
"Control Script API" on page917. If you don't know how to write scripts, see "Writing your own
scripts" on page389.
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964 and "Control Script API" on page917.)
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.
Tip
If you are looking to create a short, simple table of contents in one section, you could
add a Standard Script that uses the pageRef() function. For an example, see "pageRef
()" on page905.
For a multi-page, cross-section table of contents you must use a Post Pagination Script;
see "Creating a Table Of Contents" on page443.
Examples
Restarting the page numbers several times
Assume that a template has four sections (of 1 page each) in the Print context and a Control
Script sets the page numbering as follows:
1. Section A (1 page) restartPageNumber = true
2. Section B (1 page) restartPageNumber = true
Page 430