2022.2

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805.
Foramulti-page,cross-sectiontableofcontentsyoumustuseaPostPaginationScript;see
"CreatingaTableOfContents"onpage411.
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
3. SectionC(1page)restartPageNumber=false
4. SectionD(1page)restartPageNumber=true
Thecodewouldlooklikethis:
if (merge.context.type == ContextType.PRINT) {
merge.context.sections['Section A'].restartPageNumber = true;
merge.context.sections['Section B'].restartPageNumber = true;
merge.context.sections['Section C'].restartPageNumber = false;
merge.context.sections['Section D'].restartPageNumber = true;
}
Thepagenumberingintheoutputwillbe:
1. SectionApage1
2. SectionBpage1
3. SectionCpage2
4. SectionDpage1
Disabled section
Whenasectionisdisabled,itwillnotbeoutputted,butitsrestartPageNumberflagwillstillbetaken
intoaccountforcomposingthepagenumbersequences.So,iftherestartPageNumberflagsareset
asfollows:
Page 401