2018.2
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Connect 2018.2
- 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
- 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
- Job Creation Presets: External Sorting
- Engine Preferences: Backward Compatibility Issues
- Business Graphics: Backward Compatibility Issues
- 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
- The DataMapper Module
- 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
- 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
- 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
- Designer Script API
- Generating output
- Print output
- Email output
- Web output
- Generating Print output
- Saving Printing options in Print Presets
- Print settings in a template
- Generating Print output from Workflow
- 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
- Overview
- Connect 2018.2 Enhancements
- Connect 2018.2 Designer Updates
- JSON support added to the Data Model Panel
- Minimum Pages option added to Print Sections
- Color Output option added to Print Contexts
- Breadcrumb Improvements
- Send To Workflow Improved
- Paste as Plain Text option added
- Scripting Improvements
- Post Pagination Improvements
- Barcode Improvements
- Business Graphics Improvements
- General Designer Improvements
- Connect 2018.2 DataMapping Updates
- Connect 2018.2 Server Enhancements
- Connect 2018.2 Output updates
- Print Wizard and Preset Wizard Improvements
- Workflow 2018.2 Updates
- Known Issues
- Overview
- Connect 2018.2.1 Enhancements/Fixes
- Connect 2018.2 Enhancements
- Connect 2018.2 Designer Updates
- JSON support added to the Data Model Panel
- Minimum Pages option added to Print Sections
- Color Output option added to Print Contexts
- Breadcrumb Improvements
- Send To Workflow Improved
- Paste as Plain Text option added
- Scripting Improvements
- Post Pagination Improvements
- Barcode Improvements
- Business Graphics Improvements
- General Designer Improvements
- Connect 2018.2 DataMapping Updates
- Connect 2018.2 Server Enhancements
- Connect 2018.2 Output updates
- Print Wizard and Preset Wizard Improvements
- Workflow 2018.2 Updates
- Known Issues
- Previous Releases
- 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
- Legal Notices and Acknowledgements
Extracting dates
To extract data and have that data interpreted as a Date, set the type of the respective field to
Date:
1. Select the field in the data model.
2.
On the Step properties pane, under Field Definition, specify the Type as Date.
3. Make sure that the date in the data source is formatted in a way that matches the
expectations of the DataMapper. If the date doesn't match the format that the DataMapper
expects, it cannot be interpreted as a date. For example, if a date in the data source is
formatted as "yyyy-mm-dd" but the DataMapper expects a time as well, the date cannot be
read and the DataMapper will stop with an error.
The expected date format can be set in three places:
l In the user preferences ("DataMapper preferences" on page892).
l In the data source settings ("Data source settings" on page177).
l
In the field properties: on the Step properties pane, under Data Format, specify the
Date/Time Format.
4. For the letters and patterns that you can use in a date format, see "Defining a date/time
format" below.
Data format settings tell the DataMapper how to read and parse data from the data
source. They don't determine how these data are formatted in the Data Model or in a
template. In the Data Model, data are converted to the native data type. Dates, for
example, are converted to a DateTime object in the Data Model, and will always be
shown as "year-month-day" plus the time stamp, for example: 2012-04-11 12.00 AM..
Defining a date/time format
A date format is a mask representing the order and meaning of each digit in the raw data, as
well as the date/time separators. The mask uses several predefined markers to parse the
contents of the raw data. Here is a list of markers that are available in the DataMapper:
l
yy: Numeric representation of the Year when it is written out with only 2 digits (i.e. 13)
l
yyyy: Numeric representation of the Year when it is written out with 4 digits (i.e. 2013)
l
M: Short version of the month name (i.e. Jan, Aug). These values are based on the
current regional settings.
l
MM: Long version of the month name (i.e. January, August). These values are based on
the current regional settings.
Page 234