2020.2
Table Of Contents
- Table of Contents
- Welcome to PrintShop Mail Connect 2020.2
- 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 ConnectRelease Notes 2020.2.1
- Previous Releases
- OL PrintShop Mail Connect Release Notes 2020.1
- 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
syntax of a fully qualified URL with the "file" protocol is: file://<host>/<path>. If the host is
"localhost", it can be omitted, resulting in file:///<path>, for example:
file:///c:/somefolder/somecontent.html.When using the http/https protocol, remember that
only absolute paths are supported inside remote snippets (see
Skin/Formats/CrossReferencePrintFormat("Remote snippets" on page1)).To quickly get
the location of an HTML snippet in the template resources, right-click the snippet in the
Resources pane and select Copy Resource Location.The path to a remote HTML snippet
can be copied from the snippet's properties: right-click the snippet in the Resources pane
and select Properties.ExamplesThis script loads a local HTML snippet (from the
Resources panel) directly into the matched elementsresults.loadhtml
("snippets/snippet.html");The following script loads a local HTML snippet (Resources
panel) into a variable. The replaceWith() command is used to replace the element(s)
matched by the script's selector with the contents of the snippet.var mysnippet = loadhtml
('snippets/snippet.html'); results.replaceWith(mysnippet);Same result as the previous
script, but a different notation:results.replaceWith(loadhtml('snippets/snippet.html'));The
following script loads a snippet into a variable and finds/replaces text in the variable
before inserting the content into the page. The second find command also adds
formatting to the replacing text.var mysnippet = loadhtml
('file:///C:/Users/PParker/Documents/Example.html'); mysnippet.find('@var1@').text('OL
Connect 1'); mysnippet.find('@var2@').html('<i>OL Connect 2</i>').css('text-
decoration','underline'); results.replaceWith(mysnippet); This last script loads a remote
snippet into a variable and retrieves an element from the snippet using query().var
mysnippet = loadhtml('http://www.somewebsite.com/text-root-wrapped.html'); var subject
= query("#subject", mysnippet).text(); results.append("<p style='font-weight: bold;'>" +
subject + "</p>");loadhtml(location, selector)Retrieves specific content from the specified
HTML file.locationString containing a path that can be absolute or relative to the
section/context. Use snippets/<snippet-name> to retrieve the content from an HTML file
residing in the Snippets folder on the Resources panel. In order to retrieve files from
outside the template the file protocol is supported as well as the http/https protocols. The
complete syntax of a fully qualified URL with the "file" protocol is: file://<host>/<path>. If
the host is "localhost", it can be omitted, resulting in file:///<path>, for example:
file:///c:/somefolder/somecontent.html.When using the http/https protocol, remember that
only absolute paths are supported inside remote snippets (see
Skin/Formats/CrossReferencePrintFormat("Remote snippets" on page1)).To quickly get
the location of an HTML snippet in the template resources, right-click the snippet in the
Resources pane and select Copy Resource Location.The path to a remote HTML snippet
can be copied from the snippet's properties: right-click the snippet in the Resources pane
Page 799










