1.4

Defining parts is done by setting the part field on a section; also see "Control Script API" on
page 211.
l If a part name is given, then that delimits the start of a new part.
l A part ends at the last enabled section or at the last section before the start of a new part.
If no part name is set on any section, it is assumed that there is only one part, consisting of the
default section (for Web and Email output) or of all sections (for Print output).
Example 1: no parts defined
Assume there are three Print sections: sections A, B and C. When generating Email output with
the Print context as attachment, all three Print sections will be put together in one file and
attached to the email.
Example 2: 2 parts
Assume there are three Print sections: sections A, B and C. In a Control Script a part name is
defined for section C:
var section = merge.template.contexts.PRINT.sections['Section C'];
section.part = 'Part2';
When generating Email output with the Print context as attachment, the email will have two
attachments:
l attachment 1: Section A, Section B
l attachment 2: "part2", which is Section C. The file name of this attachment is the part
name.
Note
For Web sections, a part always consists of only the given section. Web pages cannot be appended
to form a single part. It is however possible to attach multiple Web pages to one email; see "Sample
scripts" on page 216 for an example.
Print section background
In the Print context, a PDF file can be used as a section's background (see "Using a PDF file as
background image" on page 359).
Page 391