2018.1
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Connect 2018.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
- 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 workstation
- Information about PlanetPress Workflow 8
- Upgrading from PlanetPress Suite 6/7
- What do I gain by upgrading to PlanetPress Connect?
- Preferences
- Server Configuration Settings
- Connect: a peek under the hood
- Known Issues
- Business Graphics: Backward Compatibility Issues
- Minor differences in PCL output introduced in 2018.1
- Windows Server 2016 issue
- No switch for case sensitivity in Dynamic Printer Rules editor
- Limit of 100MB of image files within a single job
- Print Output: Booklet Impositioning changes introduced in 2018.1
- Change in boundaries.find() function
- 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
- Colour Model in Stylesheets
- 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
- The DataMapper Module
- DataMapper basics
- Data mapping configurations
- Data mapping workflow
- The Data Model
- DataMapper User Interface
- Keyboard shortcuts
- Menus
- Panes
- 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
- Designer User Interface
- Codabar Settings
- Code 128 Settings
- Code 39 Settings
- Data Matrix Settings
- EAN-128 Settings
- EAN-13 Settings
- EAN-8 Settings
- Interleaved 2 of 5 Settings
- PDF417 Settings
- QR Code Settings
- UPC-A Settings
- UPC-E Settings
- Designer Script API
- Designer 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
- Designer Script API
- Generating output
- Print output
- Fax output
- Email output
- Web output
- Optimizing a template
- Generating Print output
- Saving Printing options in Print Presets
- Connect Printing options that cannot be changed from within the Printer Wizard
- Generating Print output from Workflow
- 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
- Overview
- 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 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 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 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
- Previous Releases
- 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
- Legal Notices and Acknowledgements
The name attribute of Form elements is sent to the server (together with the input value) after
the form has been submitted. When adding an element to a Form or Fieldset, you cannot
specify a name; the ID will be copied to the element's name attribute. After adding the element to
the Form or Fieldset you can change the name on the Attributes pane.
Adding new HTML5 elements
HTML5 added several new input element types that can't be found in the Designer menu. To
add such an element to a template you can do the following:
1. Add an input element from the menu, for example a Text or Button.
2. Select the element in the template.
3.
On the Attributes pane, select the desired input type from the Type drop-down list.
Changing a form element
Once an element has been added to a Form, it can easily be changed: simply select the
element in the template, go to the the Attributes pane, and edit the element. An input element
can even be changed to another type of input element by selecting the desired input type from
the Type drop-down list.
Specifying a default value
Attribute a default value to a Text, Textarea and other Form elements by dragging a field from
the Data Model pane directly onto the field, once it has been created. This also works when
dragging a field from a detail table in a record set into a Form element that is contained within a
Detail Table.
Note that the default value doesn't disappear when the user clicks the field, as placeholders do.
To insert a placeholder in a field, type a label and choose Use label as placeholder as its style
when adding the element to the form; see "Adding elements to a Form" on page455.
Making elements required
To change the validation of a COTG or Form element, right-click the element and choose
Validation settings. Now you can change the Form's validation method and set the
requirements per field; see "Changing a Form's validation method" on page593.
Page 457