2020.2

The Email context is the folder in the Designer that can contain one or more Email templates,
also called Email sections. The HTML generated by this context is meant to be compatible
with as many clients and as many devices as possible.
Email template
It is strongly recommended to start creating an Email template with a Wizard; see "Creating an
Email template with a Wizard" on page500.
Also see "Designing an Email template" on the next page for guidelines on the design.
Designing HTML email that displays properly on a variety of devices and screen sizes is
challenging. Building an email is not like building for the web. While web browsers comply with
standards (to a significant extent), email clients do not. Different email clients interpret the same
HTML and CSS styles in totally different ways.
When an Email template is created, either with a Wizard or by adding an Email context to an
existing template (see "Adding a context" on page448), the Email context folder is created
along with other files that are specific to an Email context; see "Email context" on page504.
Only one Email section is created at the start, but you can add as many Email sections as you
need; see "Email templates" on page506. However, when the Designer merges a data set to
generate output from the Email context, it can merge only one of the templates with each
record; see "Generating Email output" on page1470.
Email templates are personalized just like any other template; see "Variable Data" on
page785.
Sending email
When the template is ready, you can change the email settings (see "Email header settings" on
page510) and send the emaildirectly from the Designer or via Workflow. To test a template,
you can send a test email first.
Output, generated from an Email template, can have the following attachments:
l The contents of the Print context, in the form of a single PDF attachment. (Compression
options for PDF attachments can be specified in the Email context's properties; see
"Compressing PDF attachments" on page506.)
l The output of the Web context, as a self-contained HTML file.
l Other files, an image or a PDF leaflet for example.
Page 496