1.6
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Connect 1.6.1
- Setup And Configuration
- System and Hardware Considerations
- Installation and Activation
- Installation Pre-Requisites
- User accounts and security
- The Importance of User Credentials on Installing and Running PlanetPress Connect
- Installing PlanetPress Connect on Machines without Internet Access
- Installation Wizard
- Running Connect Installer in Silent Mode
- Activating a License
- Migrating to a new computer
- Information about PlanetPress Workflow 8
- Upgrading from PlanetPress Suite 7.6
- What do I gain by upgrading to PlanetPress Connect?
- Server Settings
- Uninstalling
- The DataMapper Module
- Basics
- Features
- Data Mapping Configuration
- Data Mapping Workflow
- The Data Model
- Data Source (Settings)
- DataMapper User Interface
- Defining Boolean Values
- Defining String Values
- Building String Values
- Defining Integer Values
- Building Integer Values
- Defining Float Values
- Building Float Values
- Defining Currency Values
- Building Currency Values
- Extracting dates
- Entering a date using JavaScript
- Defining Object Values
- DataMapper Scripts API
- The Designer
- Generating output
- Optimizing a template
- Generating Print output
- Saving Printing options in Printing Presets.
- Connect Printing options that cannot be changed from within the Printer Wizard.
- Print Using Standard Print Output Settings
- Print Using Advanced Printer Wizard
- Adding print output models to the Print Wizard
- Splitting printing into more than one file
- Variables available in the Output
- Generating Fax output
- Generating Tags for Image Output
- Generating Email output
- Generating Web output
- Release Notes
- Copyright Information
- Legal Notices and Acknowledgments
Fortunately, there is a workaround for this; see "Using COTG Elements" on
page375.
The Form's validation should ensure that the data that the user submits is valid (see
"Changing a Form's validation method" on page447 and "How to make COTG
elements required" on page377).
2.
Create a Data Mapping Configuration
Use the resulting XML file to create a Data Mapping Configuration (see "Data Mapping
Configuration" on page63).
1.
Choose File > New > Data mapping Wizards > From XML file.
2.
Select the XML data file as its source and click Next.
3.
Set the XML Elements option to /request/values. This will automatically add an
extraction step for the submitted form fields.
4.
Click Finish. The file is opened in the DataMapper and the form fields are
automatically extracted including the data for the signature and camera object.
5. Save the Data Mapping Configuration.
3.
Create a template
Create a Designer template and personalize it using the Data Mapping Configuration
(see "Personalizing Content" on page499). Strings, base64-encoded strings and SVG
data, stored in data fields using the DataMapper can be added to the template just like
any other variable data; see "Variable Data" on page510. They will show up in the
template as they are.
SVG data will be interpreted and displayed as an image. Strings and base64-encoded
strings show up as strings.
Adding Camera data to the template
The Camera widget submits a base64-encoded string, which can be put in a data field using
the DataMapper. When this data field is dragged into a template, the string will show up in the
content, instead of the image.
To make the image appear in a template, the data has to be used as the URL of an image.
The below procedure describes how to use Camera data as an image inside a <div> container.
The benefit of this approach is that the image automatically scales to the size of the container.
Page 363