2019.1
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Connect 2019.1
- Setup And Configuration
- System and Hardware Considerations
- Installation and Activation
- Where to obtain the installers
- Installation - important information
- Installation - How to guides
- Activation
- Installation Prerequisites
- User accounts and security
- Upgrading from previous Connect Versions
- Installing PlanetPress Connect on Machines without Internet Access
- Installation Wizard
- Running Connect installer in Silent Mode
- Activating a License
- Migrating to a new workstation
- Information about PlanetPress Workflow
- Upgrading from PlanetPress Suite 6/7
- Preferences
- Server Configuration Settings
- Connect: a peek under the hood
- Known Issues
- The OL Connect 2019.1 license update does not cater for existing AFP input li...
- Page break changes in 2019.1
- Progress bar pausing during 2019.1 Content Creation
- Backend database might require periodic maintenance
- Windows 10 Search service impacting Connect
- Job Creation Presets: External Sorting change introduced in 2018.2
- Engine Preferences: Backward Compatibility Issues introduced in 2018.2
- Business Graphics: Backward Compatibility Issues introduced in 2018.1
- Known Font issues
- Minor differences in PCL output introduced in 2018.1
- Windows Server 2016 issue
- Limit of 100MB of image files within a single job
- Print Output: Booklet Impositioning changes introduced in 2018.1
- Issues with Microsoft Edge browser
- Installation Paths with Multi-Byte Characters
- Switching Languages
- GoDaddy Certificates
- MySQL Compatibility
- PostScript print presets
- Available Printer Models
- External Resources in Connect
- Using Capture After Installing Workflow 8
- Capturing Spool Files After Installing Workflow 8
- Color Model in Style Sheets
- Image Preview in Designer
- Merge/Weaver Engines when Printing
- REST Calls for Remote Services
- Print Content and Email Content in PlanetPress Workflow
- Print Limitations when the Output Server is located on a different machine
- VIPP Output
- Uninstalling
- General information
- OL Connect projects
- The DataMapper
- DataMapper basics
- Data mapping configurations
- Data mapping workflow
- The Data Model
- DataMapper User Interface
- Keyboard shortcuts
- Menus
- Panes
- Example
- Example
- Settings for location-based fields in a Text file
- Settings for location-based fields in a PDF File
- Settings for location-based fields in CSV and Database files
- Settings for location-based fields in an XML File
- Text and PDF Files
- CSV and Database Files
- XML File
- Text and PDF Files
- CSV and Database Files
- XML Files
- Left operand, Right operand
- Condition
- Operators
- Text file
- PDF File
- CSV File
- XML File
- JavaScript
- Toolbar
- Welcome Screen
- DataMapper Scripts API
- The Designer
- Designer basics
- Web
- Capture OnTheGo
- COTG Forms
- Creating a COTG Form
- Filling a COTG template
- Testing the template
- Sending the template to the Workflow tool
- Using COTG data in a template
- Designing a COTG Template
- Capture OnTheGo template wizards
- Using Foundation
- COTG Elements
- Using COTG Elements
- Testing a Capture OnTheGo Template
- Using the COTG plugin: cotg-2.0.0.js
- Dynamically adding COTG widgets
- Saving and restoring custom data and widgets
- Capture OnTheGo API
- Content elements
- Snippets
- Styling and formatting
- Personalizing content
- Writing your own scripts
- Translating templates
- Designer User Interface
- Australia Post 4 State Settings
- Codabar Settings
- Code 128 Settings
- Code 39 Settings
- Datamatrix Settings
- EAN-128 Settings
- EAN-13 Settings
- EAN-8 Settings
- Interleaved 2 of 5 Settings
- KIX Code (Dutch Post) Settings
- Japan Post Settings
- PDF417 Settings
- QR Code Settings
- Royal Mail 4 State Settings
- Royal Mail 2D Settings
- UPC-A Settings
- UPC-E Settings
- US Postal Service IMB Settings
- US Postal Service IMPB Settings
- Designer Script API
- Standard Script API
- Examples
- Examples
- Examples
- Examples
- Examples
- Examples
- Examples
- Examples
- Examples
- Examples
- Examples
- Examples
- Examples
- Example
- Example
- Example
- Example
- Example
- Examples
- Creating a table of contents
- Example
- Examples
- Examples
- Examples
- Examples
- Replace elements with a snippet
- Replace elements with a set of snippets
- Example
- Example
- Creating a Date object from a string
- Control Script API
- Examples
- Post Pagination Script API
- Setting the margins of a Print section
- Setting the header and footer of a Master Page
- Designer Script API
- Generating output
- Print output
- Email output
- Web output
- Generating Print output
- Generating Print output from the Designer
- Generating Print output from Workflow
- Print settings in a template
- Aborting content creation
- 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
- Print output variables
- Generating Fax output
- Generating Tags for Image Output
- Generating Email output
- Generating Web output
- Optimizing a template
- License Update Required for Upgrade to Connect 2019.1
- Overview
- OL Connect 2019.1 Enhancements
- Connect 2019.1 Designer Updates
- Connect 2019.1 DataMapping Updates
- Connect 2019.1 Output updates
- Print Wizard and Preset Wizard Improvements
- Workflow 2019.1 Updates
- Known Issues
- Previous Releases
- Overview
- Connect 2018.2.1 Enhancements/Fixes
- Connect 2019.1 Enhancements
- Connect 2019.1 Designer Updates
- Connect 2019.1 DataMapping Updates
- Connect 2019.1 Server Enhancements
- Connect 2019.1 Output updates
- Print Wizard and Preset Wizard Improvements
- Workflow 2019.1 Updates
- Known Issues
- Overview
- Connect 2018.1.6 Enhancements/Fixes
- Connect 2018.1.5 Enhancements/Fixes
- Connect 2018.1.4 Enhancements/Fixes
- Connect 2018.1.3 Enhancements/Fixes
- Connect 2018.1.2 Enhancements/Fixes
- Connect 2018.1.1 Enhancements/Fixes
- Connect 2018.1 General Enhancements
- Connect 2018.1 Designer Enhancements/Fixes
- Connect 2018.1 DataMapping Enhancements/Fixes
- Connect 2018.1 Output Enhancements/Fixes
- Workflow 2018.1 Enhancements/Fixes
- Known Issues
- Overview
- Connect 1.8 General Enhancements and Fixes
- Connect 1.8 Performance Related Enhancements and Fixes
- Connect 1.8 Designer Enhancements and Fixes
- Connect 1.8 DataMapping Enhancements and Fixes
- Connect 1.8 Output Enhancements and Fixes
- Capture OnTheGo (COTG) Enhancements and Fixes
- Workflow 8.8 Enhancements and Fixes
- Known Issues
- Overview
- Connect 1.7.1 General Enhancements and Fixes
- Connect 1.7.1 Designer Enhancements and Fixes
- Connect 1.7.1 DataMapping Enhancements and Fixes
- Connect 1.7.1 Output Enhancements and Fixes
- Workflow 8.7 Enhancements and Fixes
- Known Issues
- Overview
- OL Connect Send
- Connect 1.6.1 General Enhancements and Fixes
- Connect 1.6.1 Designer Enhancements and Fixes
- Connect 1.6.1 DataMapping Enhancements and Fixes
- Connect 1.6.1 Output Enhancements and Fixes
- Connect Workflow 8.6 Enhancements and Fixes
- Known Issues
- Overview
- Connect 1.5 Designer Enhancements and Fixes
- Connect 1.5 DataMapping Enhancements and Fixes
- Connect 1.5 Output Enhancements and Fixes
- Connect 1.5 General Enhancements and Fixes
- Connect 8.5 Workflow Enhancements and Fixes
- Known Issues
- Overview
- Connect 1.4.2 Enhancements and Fixes
- Connect 1.4.1 New Features and Enhancements
- Connect 1.4.1 Designer Enhancements and Fixes
- Connect 1.4.1 DataMapping Enhancements and Fixes
- Connect 1.4.1 Output Enhancements and Fixes
- Connect 8.4.1 Workflow Enhancements and Fixes
- Known Issues
- Knowledge Base
- Legal Notices and Acknowledgements
adds the data to the URL, and the length of a URL is limited to 2048 characters.
Especially forms containing one or more Camera inputs may produce a voluminous data
stream that doesn't fit in the URL. GET also leaves data trails in log files, which raises
privacy concerns. Therefore POST is the preferred method to use.
5.
Using the the Method drop-down, select whether the form should be sent using the GET
or POST method.
6.
Using the next drop-down, select the form's Encryption Type (enctype):
l
application/x-www-form-urlencoded: Default. All characters are encoded before
they are sent. Spaces are converted to "+" symbols, and special characters are
converted to ASCII HEX values.
l
multipart/form-data: No characters are encoded. This value is required when you
are using forms that have a file upload control.
l
text/plain: Spaces are converted to "+" symbols, but no special characters are
encoded.
7.
Select a validation method:
l
The Browser validation method leaves it up to the browser to validate the user
input. When adding fields to the Form (see the next step) you can only make fields
required and set the maximum length as an additional requirement for some fields.
l
Select JQuery Validation to validate using JQuery scripts. This allows you to
specify stricter requirements per field and type a different message for each field to
display to the user if the input is not valid. This method ensures a more consistent
validation as it is browser independent. The necessary JQuery files will be added to
the JavaScript folder on the Resources pane when the form is inserted.
8.
Under Fields, click the Add button and click on the desired field type to add a field of that
type; see "Form Elements" on page694.
Note
A Fieldset is not available in the Form Wizard, because a Fieldset itself can contain
multiple different fields. Add the Fieldset after inserting the Form; see "Adding
elements to a Form" on page539.
9. Double-click each field in the Fields list and change its settings. For an explanation of the
settings, see "Adding elements to a Form" on page539.
Page 535