1.8
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Connect 1.8
- 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?
- Known Issues
- Issues with Microsoft Edge browser
- Worklfow - Execute Data Mapping - Issues with mutliple PDFs
- 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
- Server Configuration Settings
- 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
- 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
- Generating output
- Print 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
- 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 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
- Previous Releases
- 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
boundary can be effectively defined. For example, if a string is always found
on the first and on the last page of a document, you could specify a number of
occurrences of 2. This way, there is no need to inspect other items for whether
it is on the first page or the last page. Having found the string two times is
enough to set the boundary.
l
Pages before/after: Defines the boundary a certain number of pages before
or after the current page. This is useful if the text triggering the boundary is not
located on the first page of the record.
l
Operator: Selects the type of comparison (for example, "contains").
l
Word to find: Compares the text value with the value in the data source.
l
Match case: Makes the text comparison case-sensitive.
Text file boundaries
For a text file, Boundaries determine how many 'data pages' are included in each record. These
don't have to be actual pages, as is the case with PDF files. The data page delimiters are set in
the "Text file Input Data settings" on page205.
l
Record limit: Defines how many records are displayed in the Data Viewer. This does not
affect output production; when generating output, this option is ignored. To disable the
limit, use the value 0 (zero).
l
Selection/Text is based on bytes: Select this option for text records with fixed width
fields whose length is based on the number of bytes and not the number of characters.
l
Trigger: Defines the type of rule that controls when a boundary is set, creating a new
record.
l
On delimiter: Defines a boundary on a static number of pages.
l
Occurrences: The number of times that the delimiter is encountered before
fixing the boundary. For example, if you know that your documents always
have four pages delimited by the FF character, you can set the boundaries
after every four delimiters.
l
On text: Defines a boundary on a specific text comparison.
l
Location:
l
Selected area:
l
Select the area button: Uses the value of the current data
selection as the text value. Making a new selection and clicking on
Select the area will redefine the location.
Page 209