2020.2

Table Of Contents
generate output from the Email context, it can merge only one of the templates with each
record; see "Generating Email output" on page973.
Email templates are personalized just like any other template; see "Variable Data" on
page341.
Sending email
When the template is ready, you can change the email settings (see "Email header settings" on
page178) and send the email. 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 page174.)
l Other files, an image or a PDF leaflet for example.
Attaching the Print context is one of the options in the "Send (Test) Email" on page516 dialog.
See "Email attachments" on page185 and "Generating Email output" on page973.
Designing an Email template
With the Designer you can design Email templates. It is strongly recommended to start creating
an Email template with an Email Template Wizard, because it is challenging to design HTML
email that looks good on all email clients, devices and screen sizes that customers use when
they are reading their email.
This topic explains why designing HTML email design is as challenging as it is, which
solutions are used in the Email Template Wizards and it lists good practices, for example
regarding the use of images in HTML email. It will help you to create the best possible Email
templates in the Designer.
HTMLemail challenges
Creating HTMLemail isn't like designing for the Web. That's because email clients aren't like
web browsers. Email clients pass HTML email through a preprocessor to remove anything that
could be dangerous, introduce privacy concerns or cause the email client to behave
unexpectedly. This includes removing javascript, object and embed tags, and unrecognized
Page 165