2018.1

Table Of Contents
It is possible to enclose the values of the pattern and locale in single or double quotes. This is
required for including whitespace in a pattern, or when the ${expression} would otherwise be
ambiguous.
At run-time, the output engine determines the type of the value yielded by the expression. If this
is a number, a number pattern is expected. For date/time-like types, a date pattern is expected.
When no pattern is specified, some default format is applied. For other types, it is not possible
to specify a pattern or locale.
Generating Email output
The Email context outputs HTML email with embedded formatting to an email client through the
use of an email server. The HTML generated by this context is meant to be compatible with as
many clients and as many devices as possible.
Email is sent in a single batch for the whole record set.
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.
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 dialog.
To learn how to attach other files, see "Email attachments" on page159.
Before generating Email output
l Decide on the use of an Email Service Provider; see "Using an ESP with PrintShop Mail
Connect" on page726.
l Make sure that a data set is loaded, that any necessary files, such as images and
attachments, are in place, and that the correct settings are selected (see below).
l
You may want to rasterize certain elements, such as business graphics. Rasterizing
converts the element to a JPG or PNG image. This is very useful to support as many
clients as possible. For example, some email clients may not support SVG, so converting
a resource to JPG instead would ensure that most email clients would actually see the
Page 724