2019.2

(see "What Control Scripts are" on page885). For example, the query() function can't be used
in a Control Script because it requires access to the DOM which a Control Script doesn't have.
Object Usage
channel (see
"Channel" on
page1382)
The channel for which output is generated. This is registered in the merge
object: merge.channel.Note that the channel doesn't change when the
output consists of different contexts. When generating email, for example,
the channel is EMAIL, even when merging the Print context to attach it to
the email.
"context" on
page1387
Object that contains one context and its sections. It is accessed through the
template object: merge.template.contexts. To get access to one
context, you have to specify the ContextType (see "ContextType" on
page1383), for example: var printContext =
merge.template.contexts.PRINT;.
Through the merge object you can find out which context is currently being
merged: merge.context.
"masterpage"
on
page1355
The masterpage object is used to set a Master Page's header and footer
or to replace its entire HTML body.
"merge" on
page1405
The merge object gives access to the template with all of its contexts and
sections .
"record" on
page1290
The current record in the main data set. To get the value of a field in the
record, use record.fields['fieldname'] or record.fields.fieldname.
"section" on
page1395
Much of the Control Script magic is performed by setting one of the fields of
the section object. Via the section object you can omit, select and
clone sections; add a background to a Print section; add a header to an
email; etc.
A section can be retrieved via the context that it belongs to, using
merge.template.contexts.ContextType.sections
["section name"]. For example:
merge.template.contexts.PRINT.sections["Section EN"].
Page 1352