2020.1
Table Of Contents
- Table of Contents
- Welcome to PrintShop Mail Connect 2020.1
- Setup And Configuration
- System and Hardware Considerations
- Installation and Activation
- Preferences
- Clean-up Service preferences
- Database Connection preferences
- Editing preferences
- Email preferences
- Emmet preferences
- Engines preferences
- Hardware for Digital Signing preferences
- Language preferences
- Logging preferences
- Parallel Processing preferences
- Print preferences
- Project Wizards preferences
- Save preferences
- Scripting preferences
- Engines preferences
- Parallel Processing preferences
- Known Issues
- Uninstalling
- General information
- The Designer
- Designer basics
- Content elements
- Snippets
- Styling and formatting
- Personalizing content
- Preferences
- Clean-up Service preferences
- Database Connection preferences
- Editing preferences
- Email preferences
- Emmet preferences
- Engines preferences
- Hardware for Digital Signing preferences
- Language preferences
- Logging preferences
- Parallel Processing preferences
- Print preferences
- Project Wizards preferences
- Save preferences
- Scripting preferences
- Writing your own scripts
- Script types
- Creating a new Standard Script
- Writing a script
- Setting the scope of a script
- Managing scripts
- Testing scripts
- Optimizing scripts
- The script flow: when scripts run
- Selectors in Connect
- Loading a snippet via a script
- Loading content using a server's API
- Using scripts in Dynamic Tables
- Control Scripts
- Post Pagination Scripts
- Translating templates
- Designer User Interface
- Designer Script API
- Generating output
- Print Manager
- PrintShop Mail Connect Release Notes
- OL PrintShop Mail Connect Release Notes 2020.1
- Previous Releases
- License Update Required for Upgrade to Connect 2019.x
- Backup before Upgrading
- Overview
- OL Connect 2019.2 Enhancements
- Connect 2019.2 Designer Improvements
- Connect 2019.2 Output Improvements
- Print Manager Improvements
- Known Issues
- License Update Required for Upgrade to Connect 2019.1
- Overview
- OL Connect 2019.1 Enhancements
- Connect 2019.1 Designer Updates
- Connect 2019.1 Output updates
- Print Wizard and Preset Wizard Improvements
- Known Issues
- Overview
- Connect 2018.2.1 Enhancements/Fixes
- Connect 2018.2 Enhancements
- Connect 2018.2 Designer Updates
- Connect 2018.2 Output updates
- Print Wizard and Preset Wizard Improvements
- Connect 2018.2 Print Manager 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 Output Enhancements/Fixes
- Connect 2018.1 Print Manager 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 Output Enhancements and Fixes
- Connect 1.8 Print Manager 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 Output Enhancements and Fixes
- Known Issues
- Overview
- Connect 1.6.1 General Enhancements and Fixes
- Connect 1.6.1 Designer Enhancements and Fixes
- Connect 1.6.1 Output Enhancements and Fixes
- Known Issues
- Overview
- Connect 1.5 Designer Enhancements and Fixes
- Connect 1.5 Output Enhancements and Fixes
- Connect 1.5 General 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 Output Enhancements and Fixes
- Known Issues
- Knowledge Base
- Legal Notices and Acknowledgements
the Rule Editor is used. For instance, within Job Creation, there can be data rules that are
based on record data belonging to a content item, but there will also be "location rules" that
deal with the position of a document within the job.
The Rule types are as follows:
l
Data Rule: This rule operates upon Data entries. Select the Data Field, then select the
logical test and the associated test value(s). The options available will depend upon the
Data Field type (they are "type aware"), but all have at least "is equal to" and "is not equal
to" to another entry as an option.
The data type specific options are as follows:
l
Alphanumeric data field specific selections: Whether the alphanumeric string
"contains", "does not contain", "starts with" or "ends with" another string value.
The "is like" and the "is not like" selections allow the use of "*" wildcards.
The comparison string could be a manually entered string, or it could be another
textual data field. The data field could be from the data model, or it could be a
runtime parameter entered as part of Job Creation. Runtime parameters are
expressed as "params.xxxx", where the xxxx is the name of the runtime parameter.
In the Data Filtering Options rules editor the comparisons are always case sensitive.
In other rule editors there is an option to turn of case sensitivity.
l
Date data field specific selections: Whether the date field is "before", "after", "not
before" or "not after" another date entry, or "is between" two other date entries. The
comparison dates can be a manually entered dates, or date data fields (either from
the data model or runtime parameters).
The date value should be in ISO 8601 format. When entering dates manually it is
best to select the date using the date selection option.
l
Boolean data field specific selections. Check whether the selected Boolean data
field "is true" or "is false", or whether it "is equal to", or "is not equal to" a Boolean
runtime parameter.
l
Numeric data field specific selections: Whether the numeric fields is "less than",
"less than or equal to", "greater than" or "greater than or equal to" another number
entry. The comparison number could be a specified number, or it could be another
numeric data field (either from the data model or runtime parameters).
l
Media Rule: This rule operates on either the Media Name or coating (either Front Coating
or Back Coating) .
For the Name value, the choice is a straight binary option based upon the selected Media
Page 658










