2022.1

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499), the Email context folder is created
along with other files that are specific to an Email context; see "Email context" on page556.
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558. 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1560.
Email templates are personalized just like any other template; see "Variable Data" on
page846.
Sending email
When the template is ready, you can change the email settings (see "Email header settings" on
page562) 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557.)
l The output of the Web context, as a self-contained HTML file.
l Other files, an image or a PDF leaflet for example.
Attaching the Print context and/or the Web context is one of the options in the "Send (Test)
Email" on page1080 dialog.
These options are also available in the Create Email Content task in Workflow.
See "Email attachments" on page569 and "Generating Email output" on page1560.
Page 548