2019.1

Tip
It is possible to define a function in a Control Script which calls these functions, as long as that
function is only invoked from a Post Pagination Script.
Object or
function
Usage
merge.context.
"query(selector)"
on page841
Call merge.context.query(selector) to run a query across all
sections in the Print context.
merge.section.
"paginate()" on
page855
A call to merge.section.paginate() triggers pagination of the
current section.
"PaginationInfo"
on page842
This object contains essential information about one element in order
to create a table of contents (see "Creating a Table Of Contents" on
page407).
results."info()" on
page846
A call to results.info() returns pagination information (see
"PaginationInfo" on page842) for the first element in the result set of a
query (see "query(selector)" on page841).
Other objects that are available to Post Pagination Scripts
The list above isn't exhaustive: the objects listed in the Designer API (see "Standard Script
API" on page749) and in the Control Script API (see "Control Script API" on page811) are also
available in Post Pagination Scripts.
contentitem
The contentitem object holds the Print Content Item that will be written to the Connect
database when generating Print output.
Its properties field allows to add custom properties to the Print Content Item, in the form of key-
value pairs (a JSON string).
Page 839