1.4
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Connect 1.4.2
- Setup And Configuration
- DataMapper Module
- The Designer
- Mark Position Options
- Additional Text Settings
- Additional Image Settings
- Barcode Options
- Codabar Settings
- Code 128 Settings
- Code 39 Settings
- Additional Datamatrix Settings
- Additional EAN 128 Settings
- Additional EAN 13 Settings
- Additional EAN 8 Settings
- Additional Interleave 2 of 5 Settings
- Additional PDF417 Settings
- Additional QR Code Settings
- Additional UPC A Settings
- Additional UPC E Settings
- Additional OMR Mark Settings
- Keystore
- PDF Signature
- Copyright Information
- Legal Notices and Acknowledgements
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.Although the Email
context can contain multiple Email templates, only one of them can be merged with each
record. Which one is used, depends on a setting; see
Skin/Formats/CrossReferencePrintFormat("Email output settings in the Email context and
sections" on page 1).Email Output can be generated in two different ways: from the Designer or
via Workflow. In both cases, 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:The contents of the Print context, in the form of a single PDF
attachment. The output of the Web context, as an integral HTML file.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 dialog; see Skin/Formats/CrossReferencePrintFormat("Generating
Email output" on page 1). To learn how to attach other files, see
Skin/Formats/CrossReferencePrintFormat("Email attachments" on page 1).Web output The
Web context outputs an HTML web page that contains the HTML text and all the resources
necessary to display it.Web output can be generated in two different ways: it can be attached to
an Email template when generating Email output (see above), or it can be generated using
Workflow; see Skin/Formats/CrossReferencePrintFormat("Generating Web output" on page
1).Although the Web context can contain multiple Web pages, only one of them can be merged
with each record. Which one is used, depends on a setting; see
Skin/Formats/CrossReferencePrintFormat("Web output settings in the Web context and
sections" on page 1)." on page 1) to learn how to generate Print documents, Web pages or
Email.
Snippets
A snippet is a small, ready-to-use piece of content in a file. Snippets can be re-used within the
same template, in all contexts and sections. They can contain any contents that a section can
have, such as text, images, variable data, dynamic tables, etc.
When a snippet is added to a section or a master page, a reference to it is placed in the source
code, but the content of the snippet itself is not added to the page. Modifying a snippet in a
section that it has been added to, actually modifies the snippet's source. If a snippet is used in
multiple locations (such as different contexts and sections), modifying one instance will modify
all of them at once.
When a snippet is added to different sections or contexts, it is displayed according to the
section's or context's stylesheet. This means that the same content can appear differently
depending on the styles applied to the section or context, but it still has the exact same
contents.
Page 396