2020.2

var foo = merge.context.sections["Section 1"].html();
foo += "<p>hello world</p>";
merge.context.sections["Section 1"].html( foo );
The following script loads a snippet based on the value of a field, and then replaces the content
of a Print section with the snippet using html().
var mySection = merge.context.sections["Section 1"];
var promoTxt = loadhtml('snippets/promo-' + record.fields['City'] +
'.html');
mySection.html(promoTxt);
paginate()
This method of the section object (see "section" on page935) triggers pagination of the current
section. The pagination process re-establishes page boundaries, updates page numbers and
page counts, and reapplies Master Pages.
Depending on whether page numbering restarts in each section this may affect the page
numbers in other sections as well (see "Configuring page numbers" on page149).
When the pagination process has ended, the script resumes.
The 'current section' is always a Print section, since this method can only be used in Post
Pagination Scripts, and Post Pagination Scripts only run on the Print context (see "Post
Pagination Scripts" on page433).
You only need to call merge.section.paginate() in a Post Pagination Script if the script has
added or removed content to such an extent that the page boundaries need to be renewed.
For an example see: "Creating a Table Of Contents" on page435.
template
The template object represents the template with all its contexts and sections. It is used
frequently in Control Scripts (see "Control Scripts" on page417 and "Control Script API" on
page889).
It is retrieved via the merge object: merge.template (see "merge" on page945).
Which contexts are available in the template can be queried using merge.template.contexts.
To get access to a specific context, you have to specify the ContextType (see "ContextType" on
page922).
Page 917