2020.1

Manuals Brands Objectif Lune Manuals Applications PlanetPress Connect

Table Of Contents

Summary of content (1714 pages)

PAGE 1
PAGE 2
PAGE 3

User Guide Version 2020.1 Last Revision: 2020-11-19 Objectif Lune, Inc. 2030 Pie-IX, Suite 500 Montréal, QC, Canada, H1V 2C8 +1 (514) 875-5863 www.objectiflune.com All trademarks displayed are the property of their respective owners. © Objectif Lune, Inc. 1994-2020. All rights reserved. No part of this documentation may be reproduced, transmitted or distributed outside of Objectif Lune Inc. by any means whatsoever without the express written permission of Objectif Lune Inc. Objectif Lune Inc.
PAGE 4

Table of Contents Table of Contents 4 Welcome to PlanetPress Connect 2020.
PAGE 5

The Connect server The Connect database The File Store The engines The REST API Log files Location Name Format Connect file types OL Connect projects 127 128 128 129 129 130 130 131 131 132 134 Project Wizards Project wizard: Basic Email Project Wizard: COTG Timesheets Project Wizard: Print Promotional Jobs Project Wizard: Print Transactional Jobs Project Wizard: Submitting Data with Web Forms Project Wizard: Serving a Web Page Workflow processes in OL Connect projects About Workflow processes Common OL C
PAGE 6

Using the wizard for XML files Advanced PCL to PDF options Data mapping workflow Creating a data mapping workflow Testing the extraction workflow Data source settings Properties and runtime parameters Extracting data Steps The Data Model About records Creating a Data Model Editing the Data Model Using the Data Model Fields Detail tables Data types Data Model file structure DataMapper User Interface Keyboard shortcuts Menus Panes Toolbar Welcome Screen DataMapper Scripts API Using scripts in the DataMapper S
PAGE 7

Print context Print sections Pages Master Pages Media Email Designing an Email template Creating an Email template with a Wizard Email context Email templates Email header settings Email attachments Web Creating a Web template with a Wizard Web Context Web pages Forms Using Form elements Using JavaScript Capture OnTheGo COTG Forms Creating a COTG Form Filling a COTG template Sending the template to the Workflow tool Using COTG data in a template Designing a COTG Template Capture OnTheGo template wizards Usi
PAGE 8

Element types Editing HTML Attributes Inserting an element Selecting an element Deleting an element Styling and formatting an element Barcode Boxes Business graphics COTG Elements Date Forms Form Elements Hyperlink and mailto link Images Table Text and special characters Snippets Adding a snippet to the Resources Adding a snippet to a section Creating a snippet Editing a snippet Renaming a snippet Translating a snippet Styling and formatting Local formatting versus style sheets Layout properties Styling tem
PAGE 9

Fonts Locale Spacing Personalizing content Variable data Conditional content Dynamic images and Print section backgrounds Dynamic tables Snippets Scripts Loading data Variable Data Formatting variable data Showing content conditionally Conditional Print sections Dynamic images Dynamic Table Dynamic Print section backgrounds Personalized URL Preferences General preferences COTG Servers preferences Clean-up Service preferences DataMapper preferences Database Connection preferences Editing preferences Email pr
PAGE 10

Web 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 Translating a template Tagging elements for translation Pluralization Exporting and importing translation files
PAGE 11

Fax output Email output Web output Generating Print output Generating Print output from the Designer Generating Print output from Workflow Print settings in a template Aborting content creation Print using standard print output settings Print Presets 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 Before generating Email output Te
PAGE 12

Connect 2020.1 Designer Improvements Connect 2020.1 DataMapping Improvements Connect 2020.1 Output Improvements Workflow 2020.1 Improvements OL Connect Send Improvements Known Issues 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 DataMapping Improvements Connect 2019.2 Output Improvements Workflow 2019.
PAGE 13

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.
PAGE 14

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.
PAGE 15

Welcome to PlanetPress Connect 2020.1 Note Since we are always looking for new ways to make your life easier, we welcome your questions and comments about our products and documentation. Use the feedback tool at the bottom of the page or shoot us an email at doc@ca.objectiflune.com. PlanetPress Connect is a series of tools designed to optimize and automate customer communications management. They work together to improve the creation, distribution, interaction and maintenance of your communications.
PAGE 16

Setup And Configuration This chapter describes the PlanetPress Connect installation and the different considerations that are important in regards to the installation and use of PlanetPress Connect. l "System and Hardware Considerations" below l "Installation and Activation" on page 34 l "Known Issues" on page 110 l "Server Configuration Settings" on page 89 l Uninstalling System and Hardware Considerations There are a variety of considerations to be aware of.
PAGE 17

Directories and folders All Connect applications are installed under an arbitrarily selectable main folder. If the default installation folder options were used, this installation folder would be %PROGRAMFILES%\Objectif Lune\OL Connect. The installation folder will hold all the executable files and other files and folders required for the operation of the whole product suite. All these files and folders remain static after installation.
PAGE 18

Working folders Working folders for Connect are created and used on a per-user-basis under the respective user's profile folder, accessible on Windows with the standardized system variable %USERPROFILE% in the subfolder "Connect". Working folders are: l l l l %USERPROFILE%\Connect\filestore: This folder will hold non-intermediate files for the operation of Connect. Files in this folder will be used frequently, but not with a high frequency.
PAGE 19

Database Considerations This page describes the different considerations and pre-requisites for the database back-end used by PlanetPress Connect, whether using the MySQL instance provided by the installer, or pre-existing (external) instance. Using the MySQL Instance from the Installer The MySQL Instance provided in the Installation Wizard is already pre-configured with options to provide the most stable back-end setup. These are the specific options that have been changed in our version of "my.
PAGE 20

Warning If you chose not to install the supplied MySQL database, and instead opt for using a preexisting (External) database then you yourself must ensure that the External database is accessible to Connect. Objectif Lune Inc. will take no responsibility for database connections to any but the supplied MySQL database. Options available within the installer: l l l The Configuration page for the local MySQL is displayed.
PAGE 21

Server is SQL Server 2012. l l l When MS SQL is selected, the default values for root user are sa and 1433 for the port. If database settings from a previous OL Connect installation are found, the pre-exising settings will be displayed for the matching database type. For MS SQL settings, this will only work if they were created with Server Config Tool 1.5.0 or later, or the Installer for OL Connect 1.6.0 or later.
PAGE 22

supplied MySQL service. Note The Microsoft SQL selection capability will be available only with 1.6 version and upwards. To remove this dependency the user needs to do the following 1. Have a foreign Microsoft SQL running, ready for use with Connect Server. 2. Use the Server Configuration Tool "Database Connection preferences" on page 822 to switch the database to Microsoft SQL. 3. Re-start the Connect Server Service, so that the modifications become active. 4.
PAGE 23

l It is not possible to uninstall the supplied MySQL hereafter, when running the Connect 1.5 Installer in Modify mode. Important If a Server Product and a MySQL Product were selected to be installed on Connect 1.5.0, and then the Server Configuration Tool is used to switch the database used by the Server to an external Microsoft SQL, then the Update to 1.6 requires an extra step. The procedure is as follows: 1. Run the Update to Connect 1.6.
PAGE 24

will not be supported by Objectif Lune Inc.. Furthermore, using PlanetPress Connect in a Terminal Service environment is an infringement of our End-User License Agreement. Virtual Machine Support PlanetPress Connect supports the following virtual environments: l l l VMWare Environments. This includes VMWare Player, VMWare Workstation as well as VMWare ESX Server. VMWare VMotion.
PAGE 25

PlanetPress Connect 1.3 and later have been certified under Remote Desktop. 32-bit or 64-bit Operating Systems? PlanetPress Connect is a 64-bit software and can only be installed on 64-bit operating systems. Antivirus Considerations l l Antivirus software may slow down processing or cause issues if they are scanning in temporary folders or those used by PlanetPress Connect. Please see "Antivirus Exclusions" on page 16 for more information.
PAGE 26

entries and command-line switches are accepted, when one of Connect components is started and run. Please be therefore advised, that any non-whitelisted ini entry or command-line switch will be accepted and will - if tried to be used - lead to the respective application’s “sudden death”. If you should encounter such a behaviour then please double-check your Connect log file/s for respective entries.
PAGE 27

l If a local proxy is configured (in the Internet Explorer Options dialog), the option Bypass proxy server for local addresses must be checked, or some features depending on local communication will not work. Firewall/Port considerations The following describes all of the ports that can be used by an OL Connect solution. IT staff may decide the firewall strategy to follow for their internal requirements and needs depending on the statements outlined herein.
PAGE 28

Listens on port Destination # port # plugin Secure Email Output plugin LPR LPD 515 Telnet 9100 FTP Input/Output MySQL 3306 Microsoft 1433 SQL Server HyperSQL 9001 Type 587 TCP 515 TCP TCP TCP 21 TCP Comment TCP+UDP TCP+UDP TCP l Port numbers in bold type are user configurable. l Port numbers in bold underlined type are based on the type of database used. l Some of the ports listed above may also be used by other modules.
PAGE 29

Performance analysis details Connect's output speed is limited to a certain number of output items (web pages, emails, or printed pages) per minute. What the maximum total output speed will be is determined by your licence and any additional Performance Packs you might have (see "Speed quota: Pages Per Minute" on page 93).
PAGE 30

Configuring these engines to match both the hardware configuration and the typical usage situation is probably the most effective way to improve Connect's performance. The number of engines is one of the "Parallel Processing Preferences" that let the Connect Server manage its workload in such a way that the highest possible output speed is achieved. For an explanation and guidelines to these settings, see "Engine configuration" on page 91 and "Parallel Processing preferences" on page 101.
PAGE 31

Connect stores intermediate files. You could exclude the entire C:\Users\\Connect folder. See also: "Antivirus Exclusions" on page 16. l l l l l Use a high-performance, low-latency hard drive. Connect benefits from fast I/O. This is especially true for DataMapper engines (see "DataMapper engine" on page 95). Preferably use a Solid State Drive (SSD) or similar for storage. Use at least 8+ GB High-Quality RAM.
PAGE 32

Note Windows Vista, Windows 8.0, Windows 2003 Server and earlier versions of Windows are not supported by OL Connect products. Virtual Environments l VMWare/VSphere l Hyper-V l Azure l Amazon Web Services (AWS). Note that only EC2 M4 was certified, other instances may not work as expected. Minimum hardware requirements As with any software application, minimum hardware requirements represent the most basic hardware on which the software will run.
PAGE 33

l File system: NTFS (FAT32 is not supported) l CPU: Intel Core i7-4770 Haswell or equivalent l RAM: 16GB l Disk Space: 4GB for the software modules, 20GB for work files* l Storage Type: Solid State Drive (SSD) l Networking: 10Gb Ethernet * This depends on the amount of data you process through OL Connect. For instance, a PostScript file containing several thousands of documents could easily take up several GBs.
PAGE 34

Note As with any JAVA application, the more RAM available, the faster PlanetPress Connect will execute. Installation and Activation This topic provides detailed information about the installation and activation of PlanetPress Connect 2020.1. Note A PDF version of this guide is available for use in offline installations. Click here to download it. PlanetPress Connect 2020.1 is comprised of 2 different installers: one for the PlanetPress Connect software and one for PlanetPress Workflow 2020.1.
PAGE 35

l "Installation prerequisites" below l "User accounts and security" on the facing page l "Migrating to a new workstation" on page 58 l "Upgrading from previous Connect versions" on page 67 Installation - "How to" guides For information on how to conduct the installation itself, choose from the following topics: l "Installation Wizard" on page 38 l "Running Connect installer in Silent Mode" on page 47 l "Installing PlanetPress Connect on Machines without Internet Access" on page 37 Activation F
PAGE 36

.NET 3.5 must also be installed. This will need to be installed manually, as .NET 3.5 is not included in the Workflow setup. User accounts and security Connect requires local Windows Administrator rights when installing the software and activating the software license. This is to allow read/write access to protected Windows folders and registry entries. Once installed Connect requires only standard Windows user credentials to run.
PAGE 37

l In the Connection tab, define the account name and password that the service should use. This can be a local account on the computer or an account on a Windows Domain. The account must have administrative access on the machine. It should also correspond to the user account set up in PlanetPress Worfklow. Installing PlanetPress Connect on Machines without Internet Access Installing PlanetPress Connect2020.1 in offline mode requires some extra steps. These are listed below.
PAGE 38

2. Install the certificates: Right mouse click -> Install Certificate, and follow the steps through the subsequent wizard. 3. Now copy the PlanetPress Connect installer to the offline machine and start the installation as normal Windows certificate validation - Certificate Revocation List retrieval should be switched off For your security Objectif Lune digitally signs all relevant files with our own name and certificate.
PAGE 39

page 67 Starting the PlanetPress Connect installer The PlanetPress Connect installer may be supplied as an ISO image or on a DVD. l If an ISO image, you can choose between the following, depending upon your Operating System and the choices available: 1. Burn the ISO image onto a DVD 2. Un-zip the contents to a folder (keeping the internal folder structure intact) 3.
PAGE 40

l l l PlanetPress Connect Designer: The Designer module (see "The Designer" on page 421) can be installed standalone (with no other installed modules) on as many machines as you like. It does not require a license to run as a standalone designer tool . This allows for any number of people to use the Designer for creating jobs, but without production capabilities such as automation and commingling.
PAGE 41

characters that Windows disallows in filenames (such as '?', ''>' or trailing spaces). If an invalid character is entered, the Installation Path entry box will turn red and a description of the error will be displayed in the information area. The installer can also calculate how much disk space is required for installing the selected components as well as how much space is available: l l l l Disk space required: Displays the amount of space required on the disk by the selected components.
PAGE 42

l a lower case character (a, b, c ... ) l an upper case character (A, B, C ...) l a numeric digit (1, 2, 3 ...) l a punctuation character (@, $, ~ ...) For example: "This1s@K" Note When updating from an earlier Connect version, the appropriate MySQL password must be entered or the update will fail. If the password is subsequently forgotten, then MySQL must be uninstalled and its database deleted from disk before attempting to reinstall.
PAGE 43

machine. It will also be required if the MySQL database is on a separate machine to this PlanetPress Connect installation. Tip This option may represent a security risk if the machine is open to the internet. We heavily recommended that your firewall is set to block access to port 3306 from external requests. Configuring External Database Connection The Database Connection page appears if the supplied MySQL module was not selected for installation.
PAGE 44

created/modified/dropped in the database. If accessing a database on a different machine, the server must also be able to accept non-local TCP connections, and the user account must also be configured to accept remote connection. For example, the "root" MySQL user entered as root@localhost is not allowed to connect from any other machine than the one where MySQL is installed. l l Administrator Password: Enter the password for the above user account.
PAGE 45

PlanetPress Connect Server Configuration The Server Configuration page is where the Connect Server component is configured. Connect Server settings The Connect Server settings are as follows:. l Run Server as: Defines the machine username and password that the Connect Server module's service uses. Note The user account must have access rights to all local and network resources required for production, as well as Windows "Log on as a Service" rights.
PAGE 46

Selection Confirmation This page confirms the installation selections made. Click Next to start the installation itself. This process can take several minutes. Completing the installation This screen describes a summary of the components that have been installed. l l l Configure Update Check checkbox: This option is enabled by default. It causes the Product Update Manager to run after the installation is complete. This allows configuring PlanetPress Connect to regularly check for entitled updates.
PAGE 47

l l Note that the Product Update Manager can also be called from the “Objectif Lune Update Client” option in the Start menu. It can be uninstalled via Control Panel | Programs | Programs and Features. Product Activation After installation, it is necessary to activate the software. See Activating your license for more information. Before activating the software, please wait 5 minutes for the database to initialize.
PAGE 48

l Comment Lines, starting with # (e.g. # The options to configure an external database) l Key = Value pairs (e.g. install.product.0 = Connect Designer) For supported keys, please refer to the next paragraph. Note The install.properties file notation must follow commons configuration rules. Please refer to Properties files for more details. Required and optional properties Required properties depend on the specified product. Only fields related to that specified product must be entered.
PAGE 49

Verbose logging (optional) By default, the Silent Installer will log the same way as the GUI installer. That means logging of error and warnings, and certain information during database configuration. A more verbose logging can be switched on by using logging.verbose = true. Product selection (optional) By default, if nothing is entered for the products to be installed (install.product.
PAGE 50

Database configuration Case 1: MySQL is among the selected Connect products to be installed (new MySQL installation) If MySQL is selected and there is no previous MySQL configuration on the machine, the following properties should be defined: database.password = (required and must meet the rules) database.port = (3306 is the default port value) database.
PAGE 51

Case 2: The Connect Server is selected and MySQL is not selected In this case, an external database must be configured for the Server (and other Connect products included in the Silent installation) to be used. 2a: Configuring an external MySQL database To configure an external MySQL database, the following properties should be defined: database.type = mysql (required) database.host = (default value is localhost, otherwise required) database.
PAGE 52

Repository selection The Connect installation process requires a repository from which the installer copies (locally) or downloads (online installation) all selected Connect products. In Silent Installer mode, the installation process looks for the property product.repository in the install.properties file and then proceeds with the following steps: 1. If the property exists, and its value contains an existing file location with a repository, the installer will attempt to install from that repository. 2.
PAGE 53

l en-US (English, US) l de-DE (German, Germany) l fr-FR (French, France) l ja-JP (Japanese, Japan) l zh-CN (Chinese, China) l zh-HK (Chinese, Hongkong) l zh-MO (Chinese, Macau) l zh-TW (Chinese, Taiwan) l it-IT (Italian, Italy) l pt-BR (Portuguese, Brazil) l es-419 (Spanish, Latin America) Locale selection by defining user.language and user.country If both user.language and user.country are defined in the install.
PAGE 54

1. If the System Locale is in the list of supported Locales, it will be selected. 2. Otherwise, if there is an entry in the list of supported Locales, which matches the System language, it will be selected (e.g. on a fr-CA system, fr-FR is selected). 3. As last resort, the first Locale in the preinstall.ini is selected (usually that should be enUS). Getting the exit code of a silent installation If getting the exit code of a silent installation is desirable, use the following procedure. 1.
PAGE 55

if errorlevel 10 goto err_installer if errorlevel 2 goto err_unknown if errorlevel 1 goto err_preinstall echo Success goto:eof :err_installer echo "Installer error - see OL_Install_.log" goto:eof :err_unknown echo "Unknown preinstall error - see preinstall_err.log" goto:eof :err_preinstall echo "Preinstall error - see preinstall_err.
PAGE 56

l The PlanetPress Connect Software Activation application consists of the following: l License Information subsection: l l l Magic Number: Displays the PlanetPress Connect Magic Number. Copy the magic number to the clipboard: Click to copy the Magic Number to the clipboard. It can then be pasted in the activation request email using the Windows CTRL+V keyboard shortcut. Licensed Products subsection: l Name: Displays the name of the application or module relevant to this activation.
PAGE 57

l l Customers must submit their Magic Number and serial number to Objectif Lune via the Web Activations page: http://www.objectiflune.com/activations. The OL Customer Care team will then send the PlanetPress Connect license file via email. Resellers can create an evaluation license via the Objectif Lune Partner Portal by following the instructions there: http://extranet.objectiflune.com/ Note that if you do not have a serial number, one will be issued to you by the OL Activations team.
PAGE 58

l l l Click the Load License File button, and browse for the .olconnectlicense file you received from Objectif Lune Inc.. Read the EULA and click the I agree option to accept it. Click Install License to activate the license. The license will then be registered on the computer and you will be able to start using the software. Warning After installation message will appear warning that the Server services will need to be restarted. Just click OK to proceed.
PAGE 59

Backing up files from the current workstation The first step in migrating to a new workstation would be to make sure all necessary production files and resources are backed up and copied over to the new system. Note Although it is not necessary to convert all of your documents when upgrading to the latest version, we strongly recommended doing so. It is considered "Best Practice" to convert the documents to the version installedand then re-send them to the Workflow Tools.
PAGE 60

3. Click on the down pointing triangle under the Uncategorized group. 4. Select Import Plug-in and select the .dll file. l l l l l l l Import any external scripts used by the Run Script plugin, making sure they reflect the same paths as on the previous workstation Install any external application, executable and configuration files used by the External Program plugin, making sure they reflect the same paths as on the previous workstation Reconfigure local ODBC connections (i.e.
PAGE 61

l l Reconfigure each of the plugins, where necessary, under Plug-in as previously. Capture OnTheGo users may want to enable the Use PHP Arrays option under Plug-in > HTTP Server Input 1. Send the configuration to the local Workflow service. Backing up Connect Resources The following resources are used by Connect and can be backed up from their respective folders: l l l l l Job Presets (.OL-jobpreset): C:\Users\ [UserName]\Connect\workspace\configurations\JobCreationConfig Output Presets (.
PAGE 62

l l l l OL Connect Designer Templates , DataMapperor Package files, copied from the folder where they reside. All PostScript, TrueType, Open Type and other host based fonts used in templates must be reinstalled on the new workstation. Import all dynamic images and make sure their paths match those in the old server. Make sure the new workstation can also access network or remote images, JavaScript, CSS, JSON, and HTML resources referenced in the Connect templates.
PAGE 63

the PlanetPress Capture options under Behavior >PlanetPress Capture > Use ODBC Database. 6. Start the Messenger 8 service on new server from the Workflow menu bar: Tools > Service Console > Messenger > right-click and select Start. OL Connect Send l l l As of version 8.6 the Connect Send plugins are installed automatically with Workflow. If you are using an older version, run the OL Connect Send Plug-in Installer on the new Workstation to re-install the Connect Send plugins.
PAGE 64

l C:\Program Files\Objectif Lune\OL Connect\Connect Server\Server.ini l C:\Program Files\Objectif Lune\OL Connect\Connect Merge Engine\MergeEngine.ini l C:\Program Files\Objectif Lune\OL Connect\Connect Weaver Engine\WeaverEngine.ini 4. Now start the OLConnect_Server service Configuring the Server Extensions In the case where the OLConnect MySQL is installed on the new Master Server, it is important to reconnect all Server Extension systems to the new Master Server.
PAGE 65

l l If you want to transfer your licenses to the new machine right away, you may ask your local Customer Care department for a 30day Transition activation code for your old machine. Upgrades cannot be activated using the automated Activation Manager. Contact your local Customer Care department. To apply the license file received from the Activation Team: 1. Ensure that all services are stopped on your old machine before activating and starting the services on the new machine.
PAGE 66

Information about PlanetPress Workflow If you wish to use PlanetPress Workflow (automation) in conjunction with PlanetPress Connect, you will need to install PlanetPress Workflow 2020.1 as well. Workflow 2020.1 is provided through a separate installer which is available on CD or for download as follows: l l If you are a Customer, the installer can be downloaded from the Objectif Lune Web Activations page: http://www.objectiflune.
PAGE 67

Upgrading This page provides information about Upgrading to PlanetPress Connect version 2020.1.
PAGE 68

that is required by the installers of those products. If you do not have Update Client version 1.2.40 installed already, then the next time you run your Update Client it will show that there is an update available of itself to Version 1.2.40 (or later). Simply click on the “Install” icon to initiate the upgrade. For further details on how to upgrade the Update Client and update your Connect License see the Update Client 1.2.40 Upgrade Guide.
PAGE 69

Note From PlanetPress Connect Version 1.2 onwards, the new version (1.1.8) of the Update Client is included by default with all setups. Users of Connect 1.0 Users of Connect version 1.0 cannot upgrade directly to Version 2020.1. This is because Connect Version 1.0 is a 32 bit version of Connect. Users must first upgrade to Version 1.1 and from there upgrade to Version 2020.1 If you are updating manually you must first upgrade to Version 1.1 before installing 2020.1.
PAGE 70

current Scheduling settings for reference before proceeding with an upgrade. Backup these folders l C:\ProgramData\Objectif Lune\OL Connect\.settings\ConnectHostScope l C:\Users\[UserName]\Connect\filestore l C:\Users\[UserName]\Connect\workspace\configurations l C:\Users\ [UserName]\Connect\workspace\Designer\.metadata\.plugins\org.ec lipse.core.runtime\.settings l C:\Users\ [UserName]\Connect\workspace\Server\.metadata\.plugins\org.ecli pse.core.runtime\.
PAGE 71

Upgrading from PReS Classic PReS Classic and PlanetPress Connect are very different products. Whilst PlanetPress Connect provides considerably more options for email and web output, one need not abandon existing PReS Classic print jobs. They can still be run through Connect Workflow, via the PReS Print Controls task in the Online Help of Workflow (see http://help.objectiflune.com/en/PlanetPress-workflow-userguide/2020.1/#Workflow/TasksProperties/PReS_Print_Control.html).
PAGE 72

IMPORTANT: If you owned them, you must also upgrade your Imaging modules to use the new version. l l l PlanetPress Capture is still supported in PlanetPress Workflow 2020.1 but only with documents created with the PlanetPress Suite Design 7. PlanetPress Connect Designer. This is a design tool based on completely new technology. It is not backwards compatible and therefore cannot open PlanetPress Suite Design 7 documents.
PAGE 73

computer, you should consider having at least 16GB of RAM available. See "System requirements" on page 31. Distributed installation or not You can decide to install PlanetPress Connect modules all on the same computer or have each module on a different computer. Reasons for this could be: l l There is insufficient memory in the computer currently running PlanetPress Workflow 2020.1 to also run PlanetPress Connect Server.
PAGE 74

Create new documents and integrate them into your workflow at your own pace You can start benefiting from the innovative technology of the new PlanetPress Connect Designer right away by designing new documents, or re-doing existing ones at your own pace. You can also now: l l l Use the new DataMapper to easily map any input data into a clean data model that any designer person can use.
PAGE 75

l Service configuration l Access manager configuration l Custom plug-ins l PlanetPress Fax settings l PlanetPress Image settings l PlanetPress Search profiles l Printer activation codes l PlanetPress Capture database l PlanetPress Capture pen licenses l Custom scripts l Content of your virtual drive l PlanetPress Messenger configuration 5. If you installed PlanetPress Workflow 2020.
PAGE 76

7.
PAGE 77

8. Then select the product from which you wish to upgrade: 9.
PAGE 78

10.
PAGE 79

11. After that you will need to get the activation file for your product. To obtain your activation, download the PlanetPress Connect installer from the Web Activation Manager (http://www.objectiflune.com/webactivationmanager/), follow the instructions for the installation using the serial number provided to you. You can activate your license through the Web Activation Manager. 12.
PAGE 80

PlanetPress Workflow tool to which you want to send the PlanetPress Design document. How to perform a Workflow migration What do you need to consider when upgrading from PlanetPress Suite 7 to PlanetPress Connect Workflow 2020.1 on a new computer? Installing and Activating Workflow 2020.1 on a new computer Points to consider: l l l l Before installing, be sure to read "Installation and Activation" on page 34.
PAGE 81

from the PlanetPress Suite Designer Help > Printer Activation menu option. When the "Activate a printer" dialog is launched, right click within it and select the Export context menu option, then save the file on the new computer. Double clicking on the .pac file will then activate all of your printers on the new computer. l l Login to our Web Activation Manager (www.objectiflune.com/activations) using your customer number and password to get your Printer Activation Codes.
PAGE 82

computer: "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Watch\Documents" 2. Copy all the PlanetPress Suite 7 Documents and Compiled forms (*.ptk and *.ptz) from the Documents folder on the PlanetPress Suite computer and paste them into the equivalent folder on the Connect Workflow Computer. The PlanetPress Suite 7 folder would be "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Watch\Documents". The PlanetPress Connect Workflow 8 folder will be "C:\ProgramData\Objectif Lune\Plan
PAGE 83

Make sure that you copy only the custom plug-ins. Alternatively, you can download custom plug-ins from http://planetpress.objectiflune.com/en/suite/resources/support onto the new computer. Once you've copied your PlanetPress Suite Workflow configurations to Connect Workflow, you can confirm their availability through the Plug-in Bar Uncategorized category. There you will find all the Custom plug-ins that have been installed.
PAGE 84

l l l l l Manually install all external executables that will be referenced by the Connect Workflow processes in the configuration file. If possible, retain the local path structure as used on the older installation. If the Windows "TCP/IP Print Server" service is running on the new computer, it is recommended that you disable the Server so that it does not interfere with the PlanetPress LPD/LPR services. If you are using images from a virtual drive, copy the entire contents of "C:\ProgramData\Objectif
PAGE 85

How to perform a Capture migration This page provides information on how to conduct a proper migration of a Capture solution. For information about Capture see: http://capture.objectiflune.com/en/howitworks. These steps must be executed after a proper Workflow Migration has been completed. Instructions on how to do such can be found here: "How to perform a Workflow migration" on page 80. Failure to do so will result in unexpected problems.
PAGE 86

"C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\capture" and overwrite the existing database. Note Prior to PlanetPress Suite 7.6, all Capture patterns, documents and several other details were contained within the one single database. As of PlanetPress Suite 7.6 a separate database has been used for the patterns alone (PPCaptureDefault.mdb). 5. Copy the contents of this folder: "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Watch\DocumentManager" to this folder: "C:\
PAGE 87

to the old computer will be lost unless the steps to migrate are reproduce again. Once a Pen has been docked and the data transfer done, its memory is wiped, thus rending the parallel mode very hard to produce. It is not impossible, but describing how it can be done is beyond the scope of this migration article. Steps to migrate: 1. Update existing installation to PlanetPress Suite version 7.6 if not already done. 2. Install PlanetPress Connect Workflow 2020.1 on new computer. 3.
PAGE 88

2. Select Messenger in the tree list, right click and select Stop from the context menu. Note These steps must be done for both PlanetPress Suite Workflow 7 and PlanetPress Connect Workflow 8. 5. Copy the file PPCaptureDefault.mdb from this folder on the PlanetPress Suite 7.6 computer: "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Watch\capture" to this folder on the new PlanetPress Connect Workflow 2020.1 computer: "C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\c
PAGE 89

> Service Console). 2. Select Messenger in the tree list, right click and select Start from the context menu options. 9. Contact your local Objectif Lune activation team and transfer any Pen(s) licenses across. Server Configuration Settings This chapter describes configuring the PlanetPress Connect Server. The Connect Server settings are maintained by the Connect Server Configuration utility tool which is installed alongside PlanetPress Connect.
PAGE 90

l Engines preferences l "Automatic Restart Settings" on page 100 l "Hardware for Digital Signing preferences" on page 833 l "Language preferences" on page 101 l "Logging preferences" on page 835 l "Parallel Processing preferences" on page 101 Connection preferences Background The Connection preferences are a way to control precisely how to connect to the PlanetPress Connect Connect Server. This preference page was added in Connect 2018.2 to simplify management of HTTP communication with Connect.
PAGE 91

Note This does not limit the number of requests that can be received, just how many are processed in parallel. Additional requests are buffered and are processed as capabilities allow. The default setting is twice the number of processing cores available to the computer. This can be expanded, if the limitation is deemed a bottleneck. l Dedicated Internal Connection checkbox: Set the internal connection HTTP communication setting values. These settings are purely for Connect inter-engine communication.
PAGE 92

Settings for these engines are made in the Connect Server Configuration tool (see "Server Configuration Settings" on page 89). Connect allows for the parallelization of jobs. This means you can allocate 1 or more engines to process jobs. The number of each type of engine is configurable, as well as the amount of Merge engines than can work together on the same job (determined by job size: small, medium or large) and at what maximum speed.
PAGE 93

l l The processing power of your machine. How many cores it has determines how many engines can be launched (see "Launching multiple engines" on the facing page). The size and number of jobs of one kind that need to be handled, sequentially or simultaneously. In other words, your use case. By allocating processing power to jobs of different sizes you can make the setup match your usage situation (see "Allocating processing power to jobs" on page 96).
PAGE 94

In situations where Print and Email and/or Web output are created at the same time, only the Merge engines that create Email/Web output count towards the maximum number of Licensed tasks for that type of output. Spare speed units are distributed proportionally Since the number of engines is configurable, and jobs may run concurrently, the number of engines in use may not match the exact number of available Licensed tasks.
PAGE 95

1. Open the Connect Server Configuration utility tool (see "Server Configuration Settings" on page 89). 2. Under Parallel Processing, go to the Content Creation tab and set the number of Merge engines for the various tasks. 3. Go to the Output Creation tab and set the Reserved Weaver (Output) engines. See "Deciding how many engines of each type to launch" below. 4. Click Apply or Apply and Close. It is advised that you do not configure more engines than can be backed by actual processing power.
PAGE 96

When the database is installed on a system with a slow hard drive, adding a DataMapper engine may not increase the overall performance. Weaver engine Adding extra Weaver (Output) engine(s) might be useful when large Print jobs are to be run simultaneously with smaller Print jobs. Memory per engine By default, each engine is set to use up to a predetermined amount of RAM. To make optimum use of a machine's capabilities it might be useful to increase the amount of memory that the various engines can use.
PAGE 97

The first step in this process is to define the size of small, medium and large jobs. Job size Connect lets you define job sizes by setting the maximum number of pages a job can have and still be considered a small job, and what the minimum number of pages a job can have in order to be considered large. Jobs that fall between the small and large jobs are medium jobs.
PAGE 98

handled at the same time by that kind of engine, because there are only so many engines (and speed units) available. Note When each individual record in a job is composed of a very large number of pages, the Memory per engine setting and the machine's hard drive speed are probably more important than the number of Merge engines, since one record cannot be split over multiple cores (see "Memory per engine" on page 96).
PAGE 99

may have to wait (or wait longer). However, if the server receives many web requests then having engines reserved for HTML output can help performance. l l By reserving a number of parallel engines for Print jobs of a certain size (see "Number of parallel engines per Print job" on page 97). More parallel engines will make them run faster, but they will have to wait (longer) if the required number of engines isn't available when they come in.
PAGE 100

Batch processing. In a batch processing situation, jobs don't have to be handled simultaneously. All jobs - whether they are big and small - are processed one after another. Every job should be handled as quickly as possible. It is therefor recommended to assign the maximum number of engines and target speeds to all jobs. Do not reserve engines for certain jobs. Web requests. In online communication, response times are critical.
PAGE 101

l l Daily restart period begin: Only available if Daily restart in period selected. Enter the daily start time for the time window in which automatic restarts will be scheduled to occur. Daily restart period end: Only available if Daily restart in period selected. The end of the daily time window in which the automatic restarts are scheduled to occur. Memory limit Enter the memory limit for individual Engines.
PAGE 102

Parallel Processing properties (Designer Preferences) Preset selection (Designer Preferences) Only the Custom setting is applicable to the Designer Preferences, so this option is always selected and the field made read-only. Content Creation Tab (Designer Preferences) A Tab with data that relates solely to Content Creation. The options are: l l Total Merge engines configured read only display: This is a read only entry that shows the total number of Merge engines available.
PAGE 103

l Additional engine every (records) entry: This controls how many Merge engines are used for a Content Creation task. It means that for every additional 'x' records in the task, an additional Merge engine will be used. For example, with the default 100 record threshold, tasks with 1-100 records will be assigned 1 Merge engine, tasks with 101-200 get assigned 2 merge engines, tasks with 201-300 get assigned 3 merge engines, and so on. Note These entries aren't applied instantaneously. There is often a lag.
PAGE 104

l l l l l l l Default - Basic settings that are good for running most things. Single jobs have preference over multi-tasking, however. Batch Print - Best settings for processing jobs, one by one, in a sequential, first in first out (FIFO) order. On demand Print - Best settings for processing many small print jobs simultaneously. On demand - Use when serving web pages, sending emails, and printing many on demand jobs simultaneously. Connect Send - Settings optimized for use with Connect Send.
PAGE 105

l Multi tasking group: When starting a new Content Creation task, the task will immediately commence if there is a Merge engine available. How many Merge engines to use is based on the number of records in the input data. Select from the following options: l Optimize per task: This runs each task with as many Merge engines as needed (until engines are exhausted). Using this option means that Merge engines will not be reassigned when new tasks come in. This option is better suited for batch processing.
PAGE 106

number, not because it has been proven to have any significant value. It means that on an average system (i.e., less than 10 Merge engines) any decently sized task is allowed to use all Merge engines. It also assumes that using more than one Merge engine for less than 100 records will probably not make a big enough difference to throughput speed. Obviously, there are situations where these assumptions will not apply.
PAGE 107

If only the single Weaver Engine is configured in the Engines preferences page, then this whole tab will be disabled. l l Licensed speed limit (pages per minute): This read only entry shows the current license speed limitations, in pages per minute. The speed limitations are determined by your Connect license. This information is to help you choose what settings would make sense when assigning the “Target speed” values later in the Tab.
PAGE 108

Output Creation tasks. This it to prevent large jobs from using all available engines and blocking small or medium jobs from running. Since Weaver engines cannot switch tasks, such behaviour can only be achieved through reserving engines for small and/or medium jobs. Engines may be reserved both for small, and for medium sized jobs. Engine reservations are not required for either though. l l l Small job (engines): Optionally enter the number of Weaver engines you wish to reserve for Small jobs.
PAGE 109

l Small job (PPM): Enter the target speed for Small jobs, in Pages Per Minute (PPM). l Medium job (PPM): Enter the target speed for Medium jobs, in Pages Per Minute (PPM). l Large job (PPM): Enter the target speed for Large jobs, in Pages Per Minute (PPM) The entire licensed speed limit will always be distributed among jobs when running jobs simultaneously. After assigning a target speed, any remaining licensed speed will be distributed throughout any simultaneous jobs by a ration of the target speed.
PAGE 110

Warning It is highly recommended to keep security enabled and change the password on any server that accessible from the web. If these precautions are not taken, data saved in the server may be accessible from the outside! l l l l l Enable server security: Enable to add authentication to the REST server. - When enabled, the same username and password (which cannot be blank) must be entered in any remote Connect Designer that links to this Server.
PAGE 111

Connect Updates failing due to Microsoft Visual C++ 2017 Redistributable product Certain updates to Connect 2019.2 from earlier Connect versions are failing due to an issue with two specific Microsoft Visual C++ Redistributable packages. These two versions of the Visual C++ Redistributables remove a registry entry which the Connect installer uses to determine whether or not it needs to install the Microsoft Visual C++ 2015 Redistributable. These two versions are: l MSVC++ 2017 v14.14.26405.
PAGE 112

To get around the problem, please close and reopen the plugin. The problem only occurs on the initial opening, and should work fine thereafter. The OL Connect 2019.1 license update does not cater for existing AFP input licenses AFP Input is an add on option for OL Connect licenses. Unfortunately, the update to the 2019.1 version of the OL Connect license does not cater for existing AFP input licenses.
PAGE 113

period of prolonged and intensive processing this can result in a degradation in performance, with the whole database slowing down as it struggles to clean itself up. In Connect terms the effect can be felt as the Data Mapper and/or Job Creation progressively slowing down. To cure this issue, it is recommended that you periodically run manual maintenance on the backend database.
PAGE 114

Job Creation Presets: External Sorting change introduced in 2018.2 Versions prior to 2018.2 did not correctly save the line end characters for external sort configurations in Job Creation Presets, which meant the job could not be externally sorted. This issue has been fixed in version 2018.2. However, Job Creation Presets created with an earlier version may still have the wrong line end character for external sorting.
PAGE 115

All charts l l l Legend position: The position of the legend is not converted. It defaults to 'left' in a converted chart. Rows are series/Columns are series: Only one type of data structure for detail tables is supported in the new version: the one that corresponds to the former Columns are series setting (with which charts display one series per record, one bar/point per data field). After conversion to 2018.
PAGE 116

Minor differences in PCL output introduced in 2018.1 The browser component (Mozilla Gecko) used in the WYSIWYG editor of the Designer was updated for Connect 2018.1. This allows use of new CSS properties, such as flexbox. However this update could lead to increased output file sizes for some PCL jobs. This is generally not a cause for concern, however there might be some associated increase in processing times, as well as some minor differences in the output.
PAGE 117

Print Output: Booklet Impositioning changes introduced in 2018.1 When Booklet Impositioning is enabled, all pages within a document need to be changed to duplex prior to Impositioning . The method for duplexing jobs has been changed to now always combine existing pages into the front and backsides of sheets, rather than adding empty backsides to any simplex pages. The result is that now every document in the job becomes a booklet without any empty pages between the first page and the last page.
PAGE 118

1. Go to the .ini files for the Designer and Server Config: l C:\Program Files\Objectif Lune\OL Connect\Connect Designer\Designer.ini l C:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.ini 2. Change the language parameter to the required one under Duser.language=en | es | de | fr | it | ja | ko | pt | tw | zh Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up.
PAGE 119

Available Printer Models Note that only the single Printer Model (Generic PDF) will appear on the Advanced page of the Print Wizard by default. To add additional printer models click on the settings entry box. button next to the Model selection Note that the descriptions of some of the printers were updated in version 1.2 meaning that if you had version 1.n installed, you may find that the same printer style appears twice in the list, but with slightly different descriptions.
PAGE 120

Warning Important Note: The Designer itself and Proof Print do not use processes that run as services and they may find local files with non-UNC paths which can lead to the false impression that the resources are correct. Using Capture after installing Workflow 8 If PlanetPress Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, Capture can no longer be used within Workflow 7. The plugins are now registered uniquely to Workflow 8 and the Messenger for Workflow 7 is taken offline.
PAGE 121

Merge/Weaver engines when printing The print operation in the Designer will automatically detect whether the Merge\Weaver engines are available and display a message for the user to retry or cancel if not. Once the Merge/Weaver engine becomes available and the user presses retry the print operation will proceed as normal. This message can also occur in the following circumstances: l If the server is offline and you are not using Proof Print. l On some occasions before the Print Wizard opens.
PAGE 122

VIPP Output Some templates set up with landscape orientation are being produced as portrait in VIPP. It can also sometimes be the case that text and images can be slightly displaced. These are known issues and will be addressed in a later release of Connect. Magic Number changes when installing Docker Installing Docker on a system where Connect has already been installed may impact Connect's licensing mechanism and require reactivation.
PAGE 123

recommended that any anti-virus application be stopped prior to uninstalling PlanetPress Connect, as otherwise the Connect uninstallation might not work correctly. Impacts upon other applications and services l l The Uninstall will terminate the installed Server / MySQL service(s). The following applications / services should be stopped in a controlled fashion, before running the PlanetPress Connect Uninstall: 1. PlanetPress Connect 2. Connect products on remote systems which refer to this MySQL database.
PAGE 124

Note If an error occurs during uninstallation or after/when re-installing Connect after uninstalling it, please see: Problems during a Connect installation or version upgrade in Connect's Knowledge Base (https://help.objectiflune.com/en/kbconnect/#KB/FAQ/OL%20Connect/KB2002.htm).
PAGE 125

General information Connect consists of visible and invisible parts. The invisible parts process the Connect job to provide the actual output. They are introduced to you in the topic: "Connect: a peek under the hood" below. For information about Connect logging, see "Log files" on page 130. For a list of all file types used in Connect, see: "Connect file types" on page 132.
PAGE 126

The Workflow server The Workflow server (also referred to as the 'Watch service') executes processes independently, after a Workflow configuration has been uploaded and the services have been started. The Workflow server can run only one configuration at a time. There are a number of services related to Workflow.
PAGE 127

tool. The Workflow Service Console lets you start and stop the different services, except the Connect server, and see their log files (see Workflow Service Console). Note that Workflow isn't limited to Connect functionality. It was originally developed as part of the PlanetPress Suite. Many of the plugins in the Workflow configuration tool are older than Connect. They were left in for compatibility reasons, even though they aren't all useful or usable within Connect.
PAGE 128

The Connect Server Configuration tool lets you change the settings for the Connect server, the engines and the service that cleans up the database and the file store. These settings can also be made in the preferences of the Designer. The Connect database The Connect database is the database back-end used by Connect itself when processing jobs. It can be either the MySQL instance provided by the Connect installer, or a pre-existing (external) instance (see "Database Considerations" on page 19).
PAGE 129

The engines DataMapper engine/s. A DataMapper engine extracts data from a data file. The number of DataMapper engines is configurable (Engines preferences). Merge engine/s. A merge engine merges data with a template using the scripts in the template, in order to create (Print,Email or Web) content items. The number of merge engines is configurable (see Engines preferences): it can be increased depending on the capacity of the machine that runs the solution (see "Performance considerations" on page 28).
PAGE 130

Printing and emailing from the Designer To print or send email from within the Designer, the PlanetPress Connect service has to be running. The service is started automatically when the Designer starts, but it may not be running if the Connect Server and the Designer are installed on different computers. The PlanetPress Connect service can be found on the Services tab in the Task Manager. For a proof print the Connect server is not used. Proof printing is always done locally, by the Designer.
PAGE 131

Every time output is generated, the Designer and/or Connect Server and any engines involved in the operation produce their own log files. Each component writes its log files to a dedicated subfolder of the Log folder. Merge engines write to the logs/Mergeengine folder, Weaver engines to the logs/Weaverengine folder, DataMapper engines to the logs/Datamapperengine folder, Server to the logs/Server folder, and so forth. Note that actions of the Cleanup service are only logged in the Server's log file.
PAGE 132

l l The Designer's logging preferences are set via the Designer; see: "Logging preferences" on page 835. The Connect Server's settings are maintained by the Connect Server Configuration utility tool; see "Server Configuration Settings" on page 89. The logging level that is set applies to the Server as well as the engines. The Designer's log messages are also displayed in the Messages pane (see "Preflight Results and Messages" on page 1031).
PAGE 133

l l l l .OL-package: A transfer file used to package one or many of the above files (the data model being part of both the template and the data mapping configuration). Created by using the File > Package dialog. (See "Package dialog" on page 955.) .OL-script: One or more Designer scripts. Scripts personalize the output of a template. They are either added via wizards (see "Personalizing content" on page 762) or selfwritten (see "Writing your own scripts" on page 843).
PAGE 134

OL Connect projects An OL Connect project is an automated process, or combination of processes, in which the Connect Server and Database are used. (For an overview of the architecture of the OL Connect software, see "Connect: a peek under the hood" on page 125). Typically, an OL Connect project aims at automating (part of) a company's communication with its customers, suppliers, or other parties.
PAGE 135

Wizards" on page 968 in the online help or the Project Wizards overview video on the OL Learn website. Typically, in an OL Connect project there is a number of Workflow processes that communicate with the Connect Server, Database and/or File Store through one or more of the specially developed OL Connect tasks. For help on building these Workflow processes see "Workflow processes in OL Connect projects" on page 178 and "OL Connect tasks" on page 179.
PAGE 136

There is an introductory Project Wizards overview video on the OL Learn website. For generic information about Connect solutions and their components, see "OL Connect projects" on page 134. Note The projects require that the Connect Server and Connect Workflow be installed on the local machine. These are the projects that can be installed with a wizard. l l Print promotional jobs.
PAGE 137

and PDF. In order to create the PDF, the data are merged with a Connect template. (See: "Project Wizard: COTG Timesheets" on page 144.) Project wizard: Basic Email The Basic Email project wizard creates an OL Connect project that sends emails with two attachments: a Return and Refund Policy (PDF) which is the same for all emails, and a delivery note (PDF) which is attached to the email dynamically. The email has a mailto link.
PAGE 138

Testing and running the project Once the project wizard has finished the installation, the project is ready to be tested. 1. If the templates and data mapping configurations haven't been sent to Workflow yet, do that first (see "Sending files to Workflow" on page 429). This requires that the Workflow service is running (see Starting the Workflow service in Workflow's Online Help). 2. Locate the Workflow configuration in the project folder and open it in OL Connect Workflow. 3.
PAGE 139

Project details The email template The email's design is in the EM_BASIC Email Message template. It contains one Email section (see "Email templates" on page 499). Styling is done via style sheets (see "Local formatting versus style sheets" on page 718). The style rules are in the context_htmlemails_styles.css file. Note how they use HTML tags, IDs and classes to select elements. (See also: "Selectors in Connect" on page 864.
PAGE 140

"Variable Data" on page 777.) l l The To and Subject scripts apply to email fields. (Click Email Fields at the top of the email to expand all email fields.) For information about this kind of scripts, see: "Email header settings" on page 503. Finally, there are two custom scripts: l The Personalize Support link script adds the order number to the 'support team' link (which is a mailto link). The Year script puts the current year in the footer.
PAGE 141

The data mapping configuration The Workflow process uses a data mapping configuration, made with "The DataMapper" on page 194: EM_BASIC Data. To open the data mapping configuration, open the Designer, select File > Open from the menu and browse to the Configurations\Resources folder. This data mapping configuration will of course only work with the appropriate data files. It was designed for XML files that are structured like this file: Sample Data.xml (in the Configurations\Resources\Data folder).
PAGE 142

To see the script, click on the DeliveryNote field in the Data Model pane at the right; then take a look at the Step Properties pane (in the middle). To see where the property is defined, click the Preprocessor step on the Steps pane (at the left); then look at the Properties section on the Step Properties pane. Customizing the project A project is a great starting point for building an OL Connect solution. This part explains how to make changes to the project.
PAGE 143

Note If the input data is JSON, you don't need a data mapping configuration: JSON data can be used in a template as is. See: "Adding JSON data from a JSON file" on page 775. However, if you want the data to be saved in the OL Connect database, put the XML/JSON Conversion plugin before the Send to Folder task to convert the JSON to XML, and create an XML data mapping configuration to extract the data.
PAGE 144

Workflow configuration The current Workflow configuration is very simple. In reality, a process that generates email output will be part of a larger project, in which, for example, invoices are produced in a separate process, stored in a folder and attached to an email at a later time. For general information about processes in Workflow see About Processes and Subprocesses, in the Online Help of Workflow.
PAGE 145

Finally, you need a valid COTG account, Repository ID and password. You could use dummy data to create the Project Wizard and finish the installation, but you won't be able to test the project. For more information about the options, see: "COTG Timesheets - Project Wizard" on page 970. Tip If you own PlanetPress Connect or PReS Connect, free COTG trial licenses may be available to you; see http://www.captureonthego.com/en/promotion/.
PAGE 146

Note The process is pre-configured to use the sample data file, which comes with the project, when it runs in Debug mode. Alternatively you could copy the sample data file to the In folder. 5. Launch the COTG app and log in using the COTG account that you entered in the Project Wizard. 6. In the app, open the Repository and download one of the forms. 7. From the app's Library, open the form. 8. Enter data and draw a signature. 9. Submit the form.
PAGE 147

Tip Hover over the name of a script in the Scripts pane to highlight parts of the template that are affected by the script. l l l The guid script adds data to the guid field. This is a hidden field. It is only visible in the Source view. The result of the form action script is added to the form's action attribute. To see how that is done, double-click the script; then click Options. The Year script puts the current year in the footer of the page. This is a custom script.
PAGE 148

COTG Timesheet Form The COTG Timesheet Form data mapping configuration is designed to extract data from the sample data file (Sample Data.xml). The configuration also adds two fields to each record, using JavaScript: a unique ID (guid) and a field that contains the action of the Form. Note that the COTG account is the same in all of the records in the sample data. It is inserted into the sample data by the Project Wizard.
PAGE 149

l l l The Create Web Content task merges the record with the COTG Timesheet Form template. The Send to Folder task saves the form to the Forms folder in the project folder, using the value of one variable as the file name. Finally, the Output to Capture OnTheGo task sends information about the form to the COTG Server. Double-click the task to see how variables are used in its settings. The Delete task is an Output task that does nothing, actually; it doesn't even remove anything.
PAGE 150

Customizing the project A project is a great starting point for building an OL Connect solution. This part explains how to make changes to the project. Do you intend to expand the project into a solution where Workflow runs on a different machine that also has a different regional setting? Then indicate the desired encoding in the Designer preferences (see "Project Wizard deployment settings" on page 840) before installing the project.
PAGE 151

The Send to Folder step will now write the input data - the job file - to a file in the Workspace\Debug folder. When you select the file as sample file (on the Debug ribbon), it can be used to debug the process. Tip The saved file can be used to create a data mapping configuration. The report Using different data in the report requires changing the COTG Timesheet Report template (see "Personalizing content" on page 762).
PAGE 152

Workflow configuration To transform the project into a real solution, the Workflow configuration has to be adapted in two important respects. l l The timing and manner of the production of forms will need to change. The Input task of the cotg_ts_deploy_form process must be adapted to the actual input data. You will also need to create an appropriate data mapping configuration for that data, which probably means saving the input as sample data first (see "Saving input as sample data" on page 150).
PAGE 153

Installing the project Select File > New > Project Wizards > Print Promotional Jobs from the menu to start the Print Promotional Jobs Project Wizard. (See also: "Promotional Print Jobs - Project Wizard" on page 972.) Note In order to use the project, OL Connect Server and OL Connect Workflow must be installed on the local machine. The wizard lets you select the folder in which you want the solution to be installed.
PAGE 154

In Debug mode, the first Input task is skipped and the process is executed using a sample data file. This project is pre-configured to use the file: Sample Data.xml. A successful test run results in a subfolder in the Workspace\Out folder, named after the current month and year. The Print output is written to that subfolder. It consists of one file that should have the proper file extension.
PAGE 155

l l l l The Promo script shows or hides a paragraph (with the ID 'promo') depending on whether the customer's address is in Montréal. (See: "Showing content conditionally" on page 787.) The year script changes the year in the conditional paragraph to the current year. This script only has to look for @year@ in an element that has the ID 'promo', instead of in the entire letter, which makes it run faster. The Dynamic Signature script switches the signature, with a file name based on a data field.
PAGE 156

The Project Wizard installs six Output Creation Presets; two for each type of output. Per output type, all settings in the Output Creation Presets are the same, except one: Print Virtual Stationery. The ones that have this option enabled will include the Media - the Virtual Stationery - in the output. The other presets will not print the Media. Only the selected Output Creation Preset is put to use in the Workflow configuration.
PAGE 157

Both the Folder Capture and the Send to Folder task read the project's Workspace path from a global variable. The value of that variable is set by the Project Wizard when it installs the project. Customizing the project A project is a great starting point for building an OL Connect solution. This part explains how to make changes to the project.
PAGE 158

Template There are countless ways to customize the template to meet your exact requirements. You could, for example: l Add text, images and other elements (see "Content elements" on page 604) l Change the layout (see "Styling and formatting" on page 718) l Change the "Media" on page 481 l Change the "Master Pages" on page 478 l Add sections (see "Print context" on page 454) In order to further personalize the letter, you need to open your data mapping configuration.
PAGE 159

1. Select File > Output Creation Presets from the menu 2. Click the Import button and browse to the Configurations\Resources\Output presets folder to select the preset. All of the presets provided by the wizard save the output to one file. You might want to save the output to a number of files, for instance, one per customer. The Transactional Print Jobs project shows you how to do that.
PAGE 160

The selected folder's path is saved to a global variable in the Workflow configuration (see "Workflow configuration" on page 163). That variable is used in the settings of the Capture Folder task. The path is also copied to the Output Creation Presets which are used in the Create Output tasks. Testing and running the project Once the Project Wizard has finished the installation, the project is ready to be tested. 1. Locate the Workflow configuration in the Configurations\Workflow folder and open it in OL Co
PAGE 161

Project details The invoice template The invoice is designed in the PR_TRAN Invoice template. It contains one Print section (see "Print sections" on page 459) and one Master Page (see "Master Pages" on page 478). The Media (virtual stationery) is included in the output - it is printed on the page's background , according to a setting in the Output Creation Presets. Styling is done via style sheets (see "Local formatting versus style sheets" on page 718). The style rules are in the context_print_styles.
PAGE 162

script shows how to add data using the replace() method (see https://www.w3schools.com/jsref/jsref_replace.asp). Note that this is a native JavaScript function. Functions that are only available in Designer scripts are listed in the "Designer Script API" on page 1248. Dynamic Table The table in the invoice is a Dynamic Table. It is filled and expanded dynamically by the scripts in the Products folder. To learn how to insert and edit such a table, see "Dynamic Table" on page 793.
PAGE 163

All other print settings are in the three Output Creation Presets. These are used by the Create Output tasks in the Workflow process. To see the exact settings, open an Output Creation Preset in the Designer: first select File > Output Creation Presets from the menu; then click the Import button and browse to the Configurations\Resources\Output presets folder to select the preset.
PAGE 164

This project's Workflow configuration contains just one process. It is a typical OL Connect Print process (see "Print processes with OL Connect tasks" on page 184), with the difference that it does not have one Create Output task, but three. Each of them uses its own Output Creation Preset (see "Print settings" on page 162).
PAGE 165

Note If the input data is JSON, you don't need a data mapping configuration: JSON data can be used in a template as is. See: "Adding JSON data from a JSON file" on page 775. However, if you want the data to be saved in the Connect database, let the XML/JSON Conversion plugin convert the JSON to XML and create an XML data mapping configuration to extract the data. Template There are countless ways to customize the template to meet your exact requirements.
PAGE 166

Send the Workflow configuration to the server (see Saving and sending a Workflow Configuration in Workflow's Online Help). Print output To save the output to another type of file, or to send it to a printer, you must change the Output Creation Presets. Output Creation Presets are edited in the Designer. 1. Select File > Output Creation Presets from the menu. 2. Click the Import button and browse to the Configurations\Resources\Output presets folder to select the preset. 3.
PAGE 167

Installing the project From the menu, select File > New > Project Wizards > Submitting Data with Web Forms to start the wizard. See also: "Submitting Data with Web Forms - Project Wizard" on page 974.) Note In order to use the project, OL Connect Server and OL Connect Workflow must be installed on the local machine. The wizard lets you select the folder in which you want the solution to be installed. In the selected folder, the Project Wizard will create two subfolders: Configurations and Workspace.
PAGE 168

Saving input as sample data Testing a process in Debug mode is only possible with a sample data file. The process is preconfigured to use the Sample Data.xml file located in the Configurations\Data folder. To create your own sample data file: 1. Locate the Workflow configuration in the Configurations\Workflow folder and open it in Connect Workflow. 2. Select the process. 3. Enable the Send to Folder step (step 2 in the process). 4.
PAGE 169

The scripts in the Thank you folder only affect the thank_you Web page; on the form Web page, nothing matches their selectors. Tip Hover over the name of a script in the Scripts pane to highlight parts of the template that are affected by the script. l l l Most of the scripts in the Thank you folder directly insert data that were submitted via the Web form; see "Inserting variable data directly (drag-and-drop)" on page 778.
PAGE 170

The Delete task is an Output task that does nothing, actually; it doesn't even remove anything. However, this step is useful when running the project step by step in Debug mode. When it is followed by another task, the Create Web Content task returns its output to the Workflow process, where it can be viewed (click View as HTML). The data mapping configuration To extract the submitted data from the job file (the request XML), the process uses the data mapping configuration: WEB_FORM Data.
PAGE 171

3. Upload the Workflow configuration to the server (see Saving and sending a Workflow Configuration in Workflow's Online Help) and let the process save the input data to a file (see "Saving input as sample data" on page 168). 4. Use the saved file to add the new data to the data mapping configuration (see "Opening a data mapping configuration" on page 200). Send the data mapping configuration to Workflow. 5.
PAGE 172

Wizard" on page 515. Workflow configuration Serving the two web pages could also be achieved using separate processes, but in fact it is more efficient to have a single process, as activity needs to be monitored for each process. In real life the submitted data will probably not be stored in the Data Repository, but used differently. This means that the Push to Repository task will need to be replaced by the appropriate tasks, but that won't change the way the submitted data is retrieved.
PAGE 173

installed on the local machine. The wizard lets you select the folder in which you want the solution to be installed. In the selected folder, the Project Wizard will create two subfolders: Configurations and Workspace. The project's resource files are saved to the Configurations folder. The Workspace folder is used for debugging or running the solution. It has an In folder that may be used to monitor incoming data and an Out folder to write output files to.
PAGE 174

1. Locate the Workflow configuration in the Configurations\Workflow folder and open it in Connect Workflow. 2. Select the process. 3. Enable the Send to Folder step (step 2 in the process). 4. Send the Workflow configuration to PlanetPress Workflow service (see Saving and sending a Workflow Configuration) and run it again, with a custom name value. The Send to Folder step will now write the input data - the job file - to a file in the Workspace\Debug folder.
PAGE 175

l l The My name is script looks for an element that has the ID: hero. Inside that element it looks for the text: @name@ and replaces that with either the default name ("John Doe") or the name given in the URL. The Year script puts the current year in the footer. For more information about writing scripts, see: "Writing your own scripts" on page 843. Tip You don't have to write a script yourself if you just want to insert some data directly into the template.
PAGE 176

To create the data mapping configuration, the input data needed to be saved to a file first (see "Saving input as sample data" on page 173). The sample data file is located in the Configurations\Data folder, but you will also see it when you open the data mapping configuration itself: For more information about data mapping configurations see "The DataMapper" on page 194. Customizing the project A project is a great starting point for building an OL Connect solution.
PAGE 177

Web page There are countless ways to modify the template. You could add text, images and other elements (see "Content elements" on page 604) and change the layout (see "Styling and formatting" on page 718). In order to further personalize the web page, open your data mapping configuration (or JSON data, if the input data will be in that format; see "Adding JSON data from a JSON file" on page 775) and use the data fields to personalize the page. (See: "Personalizing content" on page 762.
PAGE 178

For general information about processes in Workflow see About Processes and Subprocesses, in the Online Help of Workflow. Workflow processes in OL Connect projects About Workflow processes A Workflow configuration consists of one or more processes. Each of these processes waits until it is time to run or until it receives the necessary input, and then does its job. A process is made up of tasks (also referred to as plugins). In the Workflow configuration tool they are divided into groups.
PAGE 179

Common OL Connect Workflow processes In an OL Connect project there are typically a number of Workflow processes that communicate with the Connect Server and/or database through one or more of the OL Connect tasks. These are the most common Workflow processes in Connect solutions. l l l l Print process.
PAGE 180

This topic describes the available OL Connect tasks, which are commonly used in Workflow processes in OL Connect projects (see "Workflow processes in OL Connect projects" on page 178). Data extraction The Execute Data Mapping task is likely to appear in a lot of OL Connect Workflow processes. It generates a record set in the OL Connect database by executing a data mapping configuration on a data source. Output creation Merging the records with a template is the job of one of the following tasks.
PAGE 181

The Create Preview PDF task generates a PDF preview for a single record as fast as possible. This preview is typically used for PDF previews embedded in web pages. PlanetPress Suite Documents The Create PDF/VT task creates PDF/VT files from a PlanetPress Suite Document (created with PlanetPress Design). This PDF/VT is compatible with the Create Print Content task directly, without the use of an OL Connect template (PDF/VT mode).
PAGE 182

configuration tool has three tasks to that end: the File Store - Upload File task, File Store Download File task, and File Store - Delete File task. Capture OnTheGo Workflow processes A Capture OnTheGo solution requires no less than three basic processes in a Workflow configuration: l l l One process that generates a document (most often, a form), stores it and notifies the COTG app of the document's existence. Note that this process doesn't send the actual document.
PAGE 183

Tip An easy way to create a Connect email project, including the Workflow configuration and the files that it needs, is to use a Project Wizard. See "Project wizard: Basic Email" on page 137. The structure of an OL Connect email process In an OL Connect Email process only one plugin is essential: the Create Email Content plugin. The Create Email Content task creates a set of emails, using the Email context in a Connect template, and sends them to the email server.
PAGE 184

l l A template with an Email context. (See "Creating a template" on page 423.) If the email should contain variable data, you might need to make a data mapping configuration (see "Creating a new data mapping configuration" on page 196). If the input is going to be JSON data, you could add them to the design using a JSON file (see "Adding JSON data from a JSON file" on page 775).
PAGE 185

l l l l The Execute Data Mapping task, or the Retrieve Items task. The Execute Data Mapping task extracts data from the job data file and puts them in a record set. This task works according to the instructions in a data mapping configuration, made with the DataMapper (see "Data mapping configurations" on page 195). The Retrieve Items task retrieves records from the OL Connect database. The Create Print Content task. This task merges data with a template, resulting in Print Content Items.
PAGE 186

In addition, the process may use: l l l A data mapping configuration, or a data model at the very least, if the documents should contain variable data. (See "Creating a new data mapping configuration" on page 196.) A Job Creation Preset. (See "Job Creation Presets Wizard" on page 1137.) A Job Creation Preset defines where the output goes and makes it possible to filter and sort records, group documents, and add metadata. An Output Creation Preset. (See "Output Creation Presets Wizard" on page 1154.
PAGE 187

If the Input task is a Server Input task, that task will return the output of the process - the web page - to the caller. The HTTP Action of the Server Input task determines how the process is triggered. If, for example, the HTTP Action is /hello, the process will be invoked when the Workflow server receives a request for a resource called hello.
PAGE 188

l l A template with a Web context. (See "Creating a template" on page 423.) If the web page should contain variable data, you might need to make a data mapping configuration (see "Creating a new data mapping configuration" on page 196). If the input is going to be JSON data, you could add them to the design using a JSON file (see "Adding JSON data from a JSON file" on page 775).
PAGE 189

l l Phase 1: Content is created by merging a print template with data. Newly created print content items are always automatically saved in the Connect database1. Information about the set of items (the "content set"), including the Content Set ID, gets stored in the database as well. Phase 2: Print content items are retrieved from the Connect database using the Retrieve Items task. The Create Job and Create Output tasks transform these items or sets into one or more print jobs.
PAGE 190

How to retrieve: selection methods The Retrieve Items task can retrieve items/sets by ID or based upon conditions. Retrieving items/sets by ID New print content items are automatically saved in the Connect database when the Create Content task creates them. The task returns the IDs of those items, as well as the ID of the content set, to the Workflow process via Metadata (see About Metadata).
PAGE 191

property to retrieve the content set in its entirety (i.e. all content items that belong to that content set); it isn't possible to retrieve individual content items using that property. Properties added to a content set are not propagated to the individual items in that content set. To label both a set and the items in it, use the Set Properties task twice. Note Data field values and properties of items in the Connect database are also used when sorting the output.
PAGE 192

as well as the ID of the content set to the process via the Metadata. Using those IDs, the Set Properties task can either set properties on all new Content Items or on the Content Set that was just created. Use two consecutive Set Properties tasks to set properties on both levels. l Through a Post Pagination script in the template. (See "Post Pagination Scripts" on page 894 and "contentitem" on page 1391.
PAGE 193

Batching/Commingling tab of Retrieve Items task The Batching/Commingling tab of the Retrieve Items task allows you to group and sort print content on two levels. You can: l l Bundle content items into "documents" (mail pieces) and sort the items within each document. Put documents in "groups", and define how documents are sorted within a group. Note that this tab is only available when the Retrieve Items task is configured to retrieve content items - not content sets.
PAGE 194

The DataMapper The DataMapper is the tool to create a data mapping configuration. Data mapping configurations are used to extract data and transpose that data into a format that can be shared amongst different layouts and outputs created with the OL Connect Designer and Workflow. The original data, located in a file or database outside of OL Connect, is called a data source.
PAGE 195

3. Build the data mapping workflow. A data mapping workflow always starts with the Preprocessor step and ends with the Postprocessor step. You can add as many steps as you like and edit the Data Model of the extracted data as required. See "Data mapping workflow" on page 217 and "The Data Model" on page 258. What's next? Use the data mapping configuration in the Designer module to create templates for personalized customer communications. To learn more, see "The Designer" on page 421.
PAGE 196

Creating a new data mapping configuration A new data mapping configuration can be made with or without a wizard. When you open a data file with a DataMapper wizard, the wizard automatically detects a number of settings. You can adjust these settings. Next, the wizard automatically extracts as many data fields (or metadata, in case of a PDF/VT or AFP file) as it can, in one extraction step. Without a wizard you have to make the settings yourself, and configure the extraction workflow manually.
PAGE 197

l From the File menu 1. Click the File menu and select New. 2. Click the Data mapping Configuration drop-down and select Files and then the file type: l Comma Separated Values or Excel (CSV/XLSX/XLS), l Microsoft Access l PDF, PS, PCL or AFP l Text l XML. 3. Click Next. 4. Click the Browse button and open the file you want to work with. 5. Click Finish.
PAGE 198

the DataMapper won't either. If the original is a PDF, it is recommended to find an alternative way to get it in the system instead of going through a print operation. l Rotated pages in a PDF are supported (if rotated 0/90/180/270 degrees). The Extract step will be able to extract data from horizontal and vertical lines of text on rotated pages.
PAGE 199

The steps to take with the wizard depend on the file type. See: l "Using the wizard for CSV and Excel files" on page 201 l "Using the wizard for databases" on page 203 l "Using the wizard for PDF/VT or AFP files" on page 206 l "Using the wizard for XML files" on page 208 Generating a counter Instead of creating a data mapping configuration for a certain type of data file, you may create a data mapping configuration that only contains a series of sequential numbers.
PAGE 200

l l l l l l Increment Value: The value by which to increment the counter for each record. For example, an increment value of 3 and starting value of 1 would give the counter values of 1, 4, 7, 10, [...] Number of records: The total number of counter records to generate. This is not the end value but rather the total number of actual records to generate. Padding character: Which character to add if the counter's value is smaller than the width. Width: The number of digits the counter will have.
PAGE 201

Using the wizard for CSV and Excel files The DataMapper wizard for CSV and Excel files helps you create a data mapping configuration for such files. The wizard automatically detects delimiters and extracts all data in one extraction step. The wizard interprets each line in the file as a record. If your data file contains transactional data, you will probably want more lines to go in one record and put the transactional data in detail tables. The wizard cannot create detail tables.
PAGE 202

Note Excel files saved in "Strict Open XML" format are not supported yet. After selecting the file, take a look at the preview to ensure that the file is the right one and the encoding correctly reads the data. Click Next. For an Excel file you can make the following settings: l l l First row contains field names: Uses the first row of the Excel sheet as headers, which automatically names all extracted fields. Sheet: Select the sheet from which the data should be extracted.
PAGE 203

Tip The Sort on option, combined with the Stop data mapping option of the "Action step" on page 255, allows to process only a group of items without having to examine all records. (See also: "Action step properties" on page 340.) Verify that the data are read properly. Finally click Finish. All data fields are automatically extracted in one extraction step. Using the wizard for databases The DataMapper wizard for database files helps you create a data mapping configuration for a database file.
PAGE 204

4. Use the drop-down to select the database type. 5. Click Next. Wizard settings for a database file After opening a database file with a wizard there are a number of settings to make, depending on the database type (see below). On the last page of the dialog, click Finish to close the dialog and open the actual data mapping configuration. Note After creating the initial data mapping configuration you may use a custom SQL query via the Input Data Settings; see "Settings for a database" on page 221.
PAGE 205

l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text. Microsoft Access l l l Password: Enter a password if one is required. Table name: The selected database is a set of related tables composed of rows and columns corresponding respectively to source records and fields. Select a table from which you want to extract data.
PAGE 206

JDBC Note Since JDBC can connect to multiple types of databases, a specific database driver and path to this driver's JAR file must be specified. l l l l l l l l JDBC Driver: Use the drop-down to select which JDBC Driver to use for the database connection. JAR file path: Enter a path to the JAR file that contains the appropriate driver for the database. Server: Enter the server address for the database server.
PAGE 207

Tip To extract information from the metadata in the extraction workflow itself, you have to create a JavaScript extraction (see "Using scripts in the DataMapper" on page 371 and "extractMeta()" on page 393). If the PDF doesn't contain any metadata, each page is a new record - in other words, a boundary is set at the start of a new page -, which is exactly what happens when you open the file without a wizard. You can open a PDF/VT or AFP file with a wizard using the Welcome screen or the File menu.
PAGE 208

Click Finish to close the dialog and open the actual Data Mapping configuration. On the Settings pane, you will see that the boundary trigger is set to On metadata. The selected metadata fields are added to the Data Model. Note Extracting data from a PDF that comes from a Windows printer queue (a PDF converted to PostScript, converted back to PDF by an Input task in Workflow) might not work (see the Connect Knowledge Base.
PAGE 209

3. From the Using a wizard pane, select XML. 4. Click the Browse button and open the XML file you want to work with. Click Next. l From the File menu 1. In the menu, click File > New. 2. Click the Data mapping Wizards drop-down and select From XML File. 3. Click Next. 4. Click the Browse button and open the XML file you want to work with. Click Next. After selecting the file, you have to set the split level and trigger type: l l XML Elements: This is a list of node elements that have children nodes.
PAGE 210

This topic's intention is to provide you with a method to make LincPDF take these advanced settings into account, so the generated PDF can be correctly read in the DataMapper. Note The method described in this topic can only be done using PlanetPress Workflow. Requirements To be able to import PCL input files, you will need the PCL Input license, in addition to PlanetPress Connect. To check if you have a PCL Input license: 1. Open the Connect Software Activation module. 2.
PAGE 211

1. Add a local variable to your process and name it lincPDFOptions. 2. Add another local variable named workingDir and give it a default Windows path (for example: C:\PCL2PDF\). 3. Add a plugin to capture the PCL File. You may use any input plugin that imports the PCL file into the process, such as Folder Capture, LPD Input, etc. 4. Using the Change Emulation plugin, change the Emulation to ASCII.
PAGE 212

(default: 0). PDF Author -dAuthor:$s string PDF document’s author (default: null). PDF Title -dTitle:$s string PDF document’s title (default: filename). 6. Next, use the External Program plugin to convert the PCL to PDF with the above % {lincPDFOptions} options. In the General tab: l l l l l Set the Executable file to: C:\Program Files\Objectif Lune\OL Connect\LPDFConv\Bin\LincPDFC.exe Set the Parameters to: -i"%F" -o"%{workingDir}\Temp\%O.
PAGE 213

the Workflow log. 7. Save the output of LincPDFC using the –o folder specifier in the parameter (% {workingDir}\Temp, in this case.) In another Workflow process, import the created PDF with the Folder Capture input plugin, specifying the output folder of the previous process (%{workingDir}\Temp in the example) as input folder, and %O.pdf as the file mask.
PAGE 214

Once you have the PDF as job file, you may pass it to the Execute Data Mapping plugin for further processing. LincPDFC Options To view the available options that can be set in LincPDF, run the executable (LincPDFC.exe) in a command prompt window. It will display a help message with available options.
PAGE 215

/*Open Windows Command Prompt Change directory cd C:\Program Files\Objectif Lune\OL Connect\LPDFConv\Bin C:\Program Files\Objectif Lune\OL Connect\LPDFConv\Bin\LincPDFC.exe LincPDF for Command-Line, Version 2.6.6.14 Copyright (c) 2001-2007 Lincoln & Co., a division of Biscom, Inc. Usage: LincPDF -iInput.PCL [-oOutput.
PAGE 216

-dTitle:$s : PDF Title -dSubject:$s : PDF Subject -dAuthor:$s : PDF Author -dKeywords:$s : PDF Keywords -dVersion:num : PDF Version (multiply by 10) Page Setup: -pWidth:num : Page Width (required only if Page Type is Custom) -pHeight:num : Page Height (required only if Page Type is Custom) -pXOff:num : Page X Offset (see also Measurement) -pYOff:num : Page Y Offset (see also Measurement) -pMeasure:num : Page Measurement (0-inch, 1-mm, 2-point) -pOrient:num : Page Orientation (0-Portrait, 1-Landscape) -pTyp
PAGE 217

-yCopyContents : Enable Copying Text and Graphics from Document -yUse128Bit : Use 128-bit Encryption -yAssembleDocument : Enable Assemble Document (128-bit encryption only) -yExtractText : Enable Text and Graphics Extraction (128-bit encryption only) -yLowResolutionPrint : Enable Lower-level Resolution Printing (128-bit encryption only) Tips ---------------------------------------------------. using quotation mark for complicated string, for example, -dKeywords:"key1, key2" .
PAGE 218

after the Data Mapping workflow has completed ("Postprocessor step" on page 256). When you create a new data mapping configuration, these steps are added automatically, but they don't actually do anything until you configure them. In between the Preprocessor and Postprocessor step, the workflow can contain as many steps as needed to extract the required data.
PAGE 219

Editing steps The properties of each step in the extraction workflow become visible in the Step properties pane when you select that step in the Steps pane. The name of each step is shown in the Steps pane. You can change it under Description in the Step properties pane. The other properties are different per step type; see "Steps" on page 246. Rearranging steps To rearrange steps, simply drag & drop them somewhere else on the colored line in the Steps pane.
PAGE 220

If any errors are encountered in one or more records, an error message will be displayed. Errors encountered while performing the extraction workflow on the current record will also be visible on the Messages tab. Note How many records are displayed in the Data Viewer (200, by default) is specified in the Record limit on the Settings pane. Data source settings After opening a data file you have to make a number of settings to make sure that the source data is interpreted and grouped the way you want.
PAGE 221

fields, even if the field delimiter is the semicolon. For an explanation of all the options, see: "CSV file Input Data settings" on page 313. Settings for an Excel File For an Excel file you have to specify which sheet to use. You can also set how many lines should be skipped, if the first row contains field names or not, and how the data should be sorted. See: "Excel file Input Data settings" on page 314. Excel has its own way to display dates.
PAGE 222

width if you are still working with old line printer data; etc. It is important that pages be defined properly. This can be done either by using a set number of lines or using a string of text (for example, the character “P”), to detect on the page. Be aware that this is not a Boundary setting; it detects each new page, not each new record. For an explanation of all the options, see: "Text file Input Data settings" on page 316.
PAGE 223

PDF file) or changing (a customer ID, a user name, etc). To define a more complex trigger, you can write a script (see "Setting boundaries using JavaScript" on page 373). A new record cannot start in the middle of a data field, so if the trigger is something in the data, the boundary will be set on the nearest preceding natural delimiter. If for instance in a PDF file the text "Page 1 of" is used as the trigger, the new record starts at the page break before that text.
PAGE 224

template. In the Data Model, data are converted to the native data type. Dates, for example, are converted to a DateTime object. How they are displayed in the Data Model depends on the current operating system's regional settings. Properties and runtime parameters A data mapping configuration's properties hold data that can be used throughout the data mapping workflow to compare against in conditions or to complement the existing data.
PAGE 225

1. Select the Preprocessor step on the Steps pane. 2. On the Step properties pane, under Properties, click the Add button . See "Properties" on page 331 for an explanation of the settings for properties. Accessing properties and runtime parameters There are different ways to access properties and runtime parameters in a data mapping workflow. l l l Property-based fields. A property-based field is filled with the value of a property. See "Property-based field" on page 265. Step settings.
PAGE 226

Before you start Data source settings Data source settings must be made beforehand, not only to make sure that the data is properly read but also to have it organized in a record structure that meets the purpose of the data mapping configuration (see "Data source settings" on page 220). It is important to set the boundaries before starting to extract data, especially transactional data (see "Extracting transactional data" on page 231).
PAGE 227

Tip In a PDF or Text file, use the Drag icon Data Model. to drag selected data into the With this method, a new Extract step will only be added to the extraction workflow if another Extract step is not currently selected. Otherwise, the field is added to the currently selected Extraction step. Dragging data into an existing field in the Data Model will replace the data. The field name stays the same. Drop data on empty fields or on the record itself to add new fields.
PAGE 228

If you tick the Append values to current record option when several steps are extracting the same field, the step will error out. Extracting data into multiple fields When you select multiple fields in a CSV or tabular data file and extract them simultaneously, they are put into different fields in the Data Model automatically. In a PDF or Text file, when multiple lines are extracted at the same time, they are by default joined and put into one field in the Data Model.
PAGE 229

l Set the data type, data format and default value of each field. l Modify the extracted data through a script. l Delete a field. All this can be done via the Step properties pane (see "Extract step properties" on page 333), because the fields in the Data Model are seen as properties of an Extract step. See also: "Fields" on page 263. Testing the extraction workflow The extraction workflow is always performed on the current record in the data source.
PAGE 230

extraction (Condition step). They can also be used to control the workflow through conditions and loops. Right-clicking on a data selection displays a contextual menu with the actions that can be performed with that selection or the steps that can be added with it. That menu also displays the keyboard shortcuts. Text or PDF file To select data in a Text or PDF file, click on a starting point, keep the mouse button down, drag to the end of the data that needs to be selected and release the mouse button.
PAGE 231

XML File XML data is displayed as a tree view inside the Data Viewer. To get a better overview you can also collapse any XML level. In this tree view you can select nodes just like files in the Windows Explorer: keep the Ctrl key pressed down while clicking on nodes to select or deselect them, or keep the Shift key pressed down to select consecutive nodes. You can select multiple fields even if those fields are in different nodes. Note The Goto step is rarely used in XML extraction workflows.
PAGE 232

Detail tables are created when an Extract step is added within a Repeat step. The Repeat step goes through a number of lines or nodes. An Extract step within that loop extracts data from each line or node. How exactly this loop is constructed depends on the type of source data. For more information about detail tables, multiple detail tables and nested detail tables, see "Detail tables" on page 303. From a CSV file or a Database The transactional data (also called line items) appear in multiple rows.
PAGE 233

1. Select a field in the column that contains the first line item information. 2. Right-click this data selection and select Add Repeat. This adds a Repeat step with a GoTo step inside it. The GoTo step moves the cursor down to the next line, until there are no more lines (see "Goto step" on page 250). 3. (Optional.) Add an empty detail table via the Data Model pane: right-click the Data Model and select Add a table. Give the detail table a name. 4. Select the Repeat step on the Steps pane. 5.
PAGE 234

The extraction step is placed inside the Repeat step, just before the GoTo step. From an XML file The transactional data appears in repeated elements.
PAGE 235

1. Right-click one of the repeating elements and select Add Repeat. This adds a Repeat step to the data mapping configuration. By default, the Repeat type of this step is set to For Each, so that each of the repeated elements is iterated over. You can see this on the Step properties pane, as long as the Repeat step is selected on the Steps pane. In the Collection field, you will find the corresponding node path.
PAGE 236

2. (Optional.) Add an empty detail table via the Data Model pane: right-click the Data Model and select Add a table. Give the detail table a name. 3. Select the Repeat step on the Steps pane. 4. Extract the data: inside a repeating element, select the data that you want to extract. Then right-click the selected nodes and select Add Extraction, or drag & drop them in the Data Model. When you drag & drop data on the name of a detail table in the Data Model pane, the data are added to that detail table.
PAGE 237

1. Select an element in the first line item. 2. Right-click on the selection and select Add Goto. The Goto step will move the cursor to the start of the first line item. 2. Add a Repeat step where the loop must stop. 1. In the line under the last line item, look for a text that can be used as a condition to stop the loop, for example "Subtotals", Total" or "Amount". 2. Select that text, right-click on it and select Add Repeat. The Repeat step loops over all lines until the selected text is found. 3.
PAGE 238

1. Select the start of the Repeat step on the Steps pane. 2. Look for something in the data that distinguishes lines with a line item from other lines (or the other way around). Often, a "." or "," appears in prices or totals at the same place in every line item, but not on other lines. 3. Select that data, right-click on it and select Add Conditional. Selecting data - especially something as small as a dot - can be difficult in a PDF file.
PAGE 239

4. (Optional.) Add an empty detail table to the Data Model: right-click the Data Model and select Add a table. Give the detail table a name.
PAGE 240

5. Extract the data (see "Adding an extraction" on page 226). When you drag & drop data on the name of a detail table in the Data Model pane, the data are added to that detail table. Dropping the data somewhere else on the Data Model pane, or using the contextual menu in the Data Viewer, creates a new detail table, with a default name that you can change later on (see "Renaming a detail table" on page 303).
PAGE 241

Note In a PDF or Text file, pieces of data often have a variable size: a product description, for example, may be short and fit on one line, or be long and cover two lines. To learn how to handle this, see "Extracting data of variable length" on the facing page. 6. Extract the sum or totals. If the record contains sums or totals at the end of the line items list, the end of the Repeat step is a good place to add an Extract step for these data.
PAGE 242

Extracting data of variable length In PDF and Text files, transactional data isn't structured uniformly, as in a CSV, database or XML file. Data can be located anywhere on a page. Therefore, data are extracted from a certain region on the page. However, the data can be spread over multiple lines and multiple pages: l l Line items may continue on the next page, separated from the line items on the first page by a page break, a number of empty lines and a letterhead.
PAGE 243

Using a Condition step or Multiple Conditions step Using a Condition step ("Condition step" on page 251) or a Multiple Conditions step ("Multiple Conditions step" on page 254) one could determine how big the region is that contains the data that needs to be extracted. In each of the branches under the Condition or Multiple Conditions step, an Extract step could be added to extract the data from a particular region. The Extract steps could write their data to the same field.
PAGE 244

Page 244
PAGE 245

Using a script A script could also provide a solution when data needs to be extracted from a variable region. This requires using a Javascript-based field. 1. Add a field to an Extract step, preferably by extracting data from one of the possible regions; see "Extracting data" on page 225. To add a field without extracting data, see "JavaScript-based field" on page 264. 2. On the Step properties pane, under Field Definition, select the field and change its Mode to Javascript.
PAGE 246

Note that this script replicates exactly what can be done in a Condition step. In cases like this, it is recommended to use a Condition step. Only use a script when no steps are sufficient to give the expected result, or when the extraction can be better optimized in a script. Steps In the DataMapper, steps are part of an extraction workflow (see "Data mapping workflow" on page 217). They contain a specific instruction for the DataMapper, for example to extract data, create a loop, or apply a condition.
PAGE 247

also lets you define properties and runtime parameters that can be used throughout the data mapping workflow. For a complete overview of the settings for a Preprocessor step, see: "Preprocessor step properties" on page 329. Properties and runtime parameters A data mapping configuration's properties hold data that can be used throughout the data mapping workflow to compare against in conditions or to complement the existing data.
PAGE 248

Extract step The Extract step is essential in each and every data mapping configuration. It extracts data from the data source, based on their location (a row and column in CSV or tabular data, an XPath in XML, or a region of the page in PDF and Text) or on JavaScript code. The data is stored in the record set that is the result of the extraction workflow. Fields always belong to an Extract step, but they don't necessarily all contain extracted data.
PAGE 249

see: "Extracting data" on page 225. l Alternatively, right-click the Steps pane and select Add a Step > Add Extraction. Make the required settings on the Step properties pane. If an Extract step is added within a Repeat step, the extracted data are added to a detail table by default; see "Extracting transactional data" on page 231 and "Detail tables" on page 303.
PAGE 250

1. On the Steps pane, select the step after which to insert the Condition step. 2. Make sure that the cursor is located where the extraction loop must start. By default the cursor is located at the top of the page or record, but previous steps in the extraction workflow may have moved it down. If necessary, add a Goto step (see "Goto step" below). This step can be skipped when the data source is an XML file. 3.
PAGE 251

l l On the Steps pane, select the step after which to insert the Goto step. In the Data Viewer, select some data, right-click that data and choose Add Goto, to add a Goto step that moves the cursor to that data. Alternatively, right-click the Steps pane and select Add a Step > Add Goto. Make the required settings on the Step properties pane. Configuring a Goto step For information about how to configure the Goto step, see "Goto step properties" on page 359.
PAGE 252

Adding a Condition step To add a Condition step: l On the Steps pane, select the step after which to insert the Condition step; then, in the Data Viewer, select some data, right-click that data and choose Add Conditional. In the Step properties pane, you will see that the newly added Condition step checks if the selected position (the left operand) contains the selected value (the right operand). Both operands and the operator can be adjusted.
PAGE 253

(in the Step properties pane).Make a selection in the Data Viewer and click the Use selected text button in the Right Operand section. You will now be able to see whether or not the proper text is extracted by the current selection. Repeat this until you are satisfied that the proper data is being extracted.Click on the Use selection button in the Left Operand section to fill out the coordinates.The point of origin of each character is at the bottom left of each of them and extends up and to the right.
PAGE 254

Rules are by default combined with AND. To change the way rules are combined, right-click "AND" in the Rule Tree, on the Step properties pane, and select OR or XOR instead. (XOR means one or the other, but not both.) Renaming a rule To rename a rule, double-click its name in the Rule Tree and type a new name. Multiple Conditions step The Multiple Conditions step is useful to avoid the use of nested Condition steps: Condition steps inside other Condition steps.
PAGE 255

Adding a Multiple Conditions step To add a Multiple Conditions step, right-click the Steps pane and select Add a Step > Add Multiple Conditions. To add a case, click the Add case button to the right of the Condition field in the Step properties pane. Configuring a Multiple Conditions step For information about how to configure the Multiple Conditions step, see "Multiple Conditions step properties" on page 356.
PAGE 256

l l l l Execute JavaScript code. Set the value for a record property. Record properties are defined in the Preprocessor step; see "Preprocessor step" on page 246. Stop the processing of the current record and move on to the next one. Normally an extraction workflow is automatically executed on all records in the source data. By stopping the processing of the current record, you can filter out some records or skip records partially.
PAGE 257

l Select the Postprocessor step on the Steps pane. l On the Step properties pane, under Postprocessor, click the Add button l . Under Postprocessor definition, add the script. Postprocessor tasks must be written in JavaScript (see "Using scripts in the DataMapper" on page 371 and "DataMapper Scripts API" on page 368). Configuring the Postprocessor step For an explanation of the settings for post-processors, see "Postprocessor step properties" on page 363.
PAGE 258

mapping workflow. In order to test post-processors you must execute them manually by clicking the Apply button in the Post-processor step properties (see "Postprocessor step properties" on page 363). Note that in the DataMapper and Designer, only one data record is active at any given time. Therefore, the changes made by the post-processes are only visible on the current data record (i.e. the one currently displayed).
PAGE 259

About records A record is a block of information that may be merged with a template to generate a single document (invoice, email, web page...) for a single recipient. It is part of the record set that is generated by a data mapping configuration. In each record, data from the data source can be combined with data coming from other sources. Records can be duplicated by setting the number of copies in a script (see "record" on page 399). Duplicates are not shown in the Data Model.
PAGE 260

Note l l Imported Data Model fields always overwrite existing field properties when the field name is the same (although they will still be part of the same Extract step). Nonexistent fields are created automatically with the appropriate field settings. The import is case-insensitive. All imported data model fields are marked as required in the Data Model (indicated with an asterisk (*) next to their names).
PAGE 261

To change the order in which data are extracted, see "Renaming and reordering fields in an extraction step" on page 266. Moving fields To move a field, a group of fields or a detail table, you can simply drag and drop it to some other place in the Data Model. Alternatively, you can right-click the field, group or detail table and select one of the options in the Move menu, to move it up or down within the list or group. Fields cannot be moved into another table.
PAGE 262

In Workflow, when a data mapping configuration is used to extract data from a data source (see "Data mapping configurations" on page 195), the extracted data is stored in a record set in the OL Connect database. Adding fields and data via Workflow The Data Model is not extensible outside of the DataMapper. When it is used in Workflow - as part of a data mapping configuration - the contents of its fields can be updated but not its structure.
PAGE 263

l Select Metadata as the data source in the Create Preview PDF plugin. Note Many of these actions can also be performed using REST calls. Please refer to PlanetPress Connect Workflow documentation for more information about the plugins involved. Fields Extracted data are stored in fields in the Data Model (see "The Data Model" on page 258). Fields can be present on different levels: on the record level or in a detail table (see "Detail tables" on page 303).
PAGE 264

JavaScript-based field JavaScript-based fields are filled by a script: the script provides a value. Note that the last value attribution to a variable is the one used as the result of the expression. There is a number of ways to add a Javascript based field. Via the Steps pane 1. Make sure there is no data selection in the Data Viewer. 2. Right-click on an Extract step on the Steps pane and select Add a Step > Add Extract Field. (To add a new Extract step, select Add a Step > Add Extraction first.) 3.
PAGE 265

Property-based field A property-based field is filled with the value of a property (see "Properties and runtime parameters" on page 224). Custom properties can be added via the Preprocessor step; see "Preprocessor step" on page 246. A property-based field cannot be added directly. To fill a field with the value of a property, you have to change an existing field's Mode to Properties. 1. Select the field in the Data Model. 2. On the Step properties pane, under Field Definition, change its Mode to Properties.
PAGE 266

Renaming and reordering fields in an extraction step The names of fields, as well as the order of fields in an extraction step, can be changed via the properties of the Extract step that they belong to. 1. Select the Extract step that contains the fields that you want to rename. To do this you could click on one of those fields in the Data Model, or on the step in the Steps pane. 2. On the Step properties pane, under Field Definition, click the Order and rename fields button. 3.
PAGE 267

Setting the data type Fields store extracted data as a String by default. The data type of a field can be changed via the properties of the Extract step that the field belongs to. 1. Select the Extract step that contains the field. You can do this by clicking on the field in the Data Model, or on the step in the Steps pane that contains the field. 2. On the Step properties pane, under Field Definition, set the Type to the desired data type. See "Data types" on page 276 for a list of available types.
PAGE 268

Post function On the Step properties pane, under Field Definition, you can enter a script in the Post function field to be run after the extraction. (Click the Use JavaScript Editor button to open the Script Editor dialog if you need more space.) A Post function script operates directly on the extracted data. Its results replace the extracted data. For example, the Post function script replace("-", ""); replaces the first dash character that occurs inside the extracted string.
PAGE 269

2. In the Step properties pane, under Field Definition, click the Remove Extract Field button next to the Field List drop-down. Detail tables A detail table is a field in the Data Model that contains a record set instead of a single value. Detail tables contain transactional data. They are created when an Extract step is added within a Repeat step; see "Extracting transactional data" on page 231. In the most basic of transactional communications, a single detail table is sufficient.
PAGE 270

3. Click somewhere else on the Step Properties pane to update the Data Model. You will see the new name appear. Creating multiple detail tables Multiple detail tables are useful when more than one type of transactional data is present in the source data, for example purchases (items with a set price, quantity, item number) and services (with a price, frequency, contract end date, etc).
PAGE 271

and you will have to rename the detail table created in each Extract step to pull the detail tables apart (see "Renaming a detail table" on page 269).
PAGE 272

Nested detail tables Nested detail tables are used to extract transactional data that are relative to other data. They are created just like multiple detail tables, with two differences: l l For the tables to be actually nested, the Repeat step and its Extract step that extract the nested transactional data must be located within the Repeat step that extracts data to a detail table. In their name, the dot notation (record.services) must contain one extra level (record.services.charges).
PAGE 273

a number of "details" such as movie rentals or long distance calls.
PAGE 274

The services can be extracted to a detail table called record.services. The "charges" and "details" can be extracted to two nested detail tables.
PAGE 275

The nested tables can be called record.services.charges and record.services.details.
PAGE 276

Now one "charges" table and one "details" table are created for each row in the "services" table. Data types By default the data type of extracted data is a String, but each field in the Data Model can be set to contain another data type. To do this: 1. In the Data Model, select a field. 2. On the Step properties pane, under Field Definition choose a data type from the Type drop-down. Changing the type does not only set the data type inside the record.
PAGE 277

l "HTMLString" on page 283 l "Integer" on page 283 l "Float" on page 282 l "Currency" on the facing page l "Date" on page 279 l "Object" on page 284 Note The Object data type is only available in the DataMapper module. It can be used for properties in the Preprocessor step, but not for fields in the Data Model. Boolean Booleans are a simple true/false data type often used in conditions and comparisons.
PAGE 278

Note The value must be all in lowercase: true, false. Any variation in case (True, TRUE) will not work. Boolean expressions Boolean values can be set using an expression of which the result is true or false. This is done using operators and comparisons. Example: record.fields["isCanadian"] = (extract("Country") == "CA"); For more information on JavaScript comparison and logical operators, please see w3schools.com or developer.mozilla.org.
PAGE 279

Note While Currency values can be set to up to 4 significant digits, only 2 are displayed on screen. Building Currency values Currency values can be the result of direct attribution or mathematical operations just like Integer values (see "Integer" on page 283). Date Dates are values that represent a specific point in time, precise up to the second. They can also be referred to as datetime values. While dates are displayed using the system's regional settings, in reality they are stored unformatted.
PAGE 280

l In the user preferences ("DataMapper preferences" on page 821). l In the data source settings ("Data source settings" on page 220). 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.
PAGE 281

l l ap: AM/PM string. In addition, any constant character can be included in the mask, usually to indicate date/time separators (i.e. / - :) . If one of those characters happens to be one of the reserved characters listed above, it must be escaped using the \ symbol. Note The markers that can be used when extracting dates are different from those that are used to display dates in a template (see the Designer's "Date and time patterns" on page 1262).
PAGE 282

l In a Preprocessor property. To do this, go to the Steps pane and select the Preprocessor step. Then, on the Step properties pane, under Properties add a property, specify its Type as Date and put the JavaScript in the Default Value field. The use of the JavaScript Date() object is necessary when creating dates through a JavaScript expression. For more information, see w3schools - JavaScript Dates and w3schools - Date Object.
PAGE 283

Building Float values Float values can be the result of direct attribution or mathematical operations just like Integer values (see "Integer" below). HTMLString HTMLStrings contain textual data that includes HTML markup. They are essentially the same as String values except in cases where the HTML markup can be interpreted. Example: Assume that a field has the value He said WOW!.
PAGE 284

l l Direct attribution: Assign an integer value directly, such as 42, 99593463712 or data.extract("TotalOrdered");. Mathematical operations: Assign the result of any mathematical operation. For example: 22+51, 3*6, 10/5 or sourceRecord.property.SubTotal. For more information on mathematics in JavaScript , see w3Schools - Mathematical Operators. For more advanced mathematical functions, see w3schools - Math Object. Note When adding numbers that are not integers, for instance 4.5 + 1.
PAGE 285

l Extraction: l In the Data Model, select a field. On the Step properties pane, under Field Definition set the Type to String. The field value will be extracted and treated as a string. l l JavaScript Expression: Set the desired value to any string between quotes. Example: record.fields["countryOfOrigin"] = "Canada"; Building String values String values can be made up of more than just a series of characters between quotes.
PAGE 286

xsi:schemaLocation="http://www.objectiflune.com/connectschemas/Data ModelConfig http://www.objectiflune.com/connectschemas/DataModelConfig/1_0_0_ 3.xsd" xmlns:xsi="http://www.w3.
PAGE 287

Example: transactional details, in a simple invoice format PAGE 288
Example: nested tables (one table into another) PAGE 289
Keyboard shortcuts This topic gives an overview of keyboard shortcuts that can be used in the DataMapper. Keyboard shortcuts available in the Designer for menu items, script editors and the data model pane can also be used in the DataMapper; see "Keyboard shortcuts" on page 1005. Although some of the keyboard shortcuts are the same, this isn't a complete list of Windows keyboard shortcuts. Please refer to Windows documentation for a complete list of Windows keyboard shortcuts.
PAGE 290

Key combination Function displays the corresponding menu.) The menu can then be browsed using the Enter key, arrow up and arrow down buttons.
PAGE 291

Key combination Function Ctrl + Shift + S Save all Ctrl + Shift + W or Ctrl + Shift + F4 Close all Ctrl + F5 Revert Ctrl + F7 Next view Ctrl + Shift + F7 Previous view Ctrl + F8 Next perspective Ctrl + Shift + F8 Previous perspective Ctrl + F10 Save as Ctrl + F12 Send to Workflow / Package files F4 Ignore step/Reactivate step F6 Add an Extract step F7 Add a Goto step F8 Add a Condition step F9 Add a Repeat step Page 291
PAGE 292

Key combination Function F10 Add an Extract field F11 Add an Action step F12 Add a Multiple Conditions step Alt + F12 Add a Case step (under a Multiple Conditions step) Home Go to the first step in the workflow End Go to the last step in the workflow Alt + V Validate records Shift + F10 or Ctrl + Shift + F10 Open context menu Viewer pane The following key combinations activate a function in the Viewer.
PAGE 293

Key combination Function Ctrl + + Zoom in Ctrl + Shift + E Switch to Editor Ctrl + F6 Next editor (when there is more than one file open in the Workspace) Ctrl + Shift + F6 Previous editor (when there is more than one file open in the Workspace) Data Model pane Key combination Function PageUp Go to previous record PageDown Go to next record Alt + CR Property page Alt + PageDown Scroll down to the last field Alt + PageUp Scroll up to the first field Steps tab Key combination Function
PAGE 294

Edit Script and Expression windows The following key combinations have a special function in the Expression and in the Edit Script windows (expanded view). Key combination Function Ctrl + space Content assist (auto-complete) Ctrl + A Select all Ctrl + D Duplicate line Ctrl + I Indent (Tab) Ctrl + J Line break Ctrl + L Go to line; a prompt opens to enter a line number.
PAGE 295

File Menu l l l l l l l l l l New...: Opens the dialog to create a new data mapping configuration; see "Creating a new data mapping configuration" on page 196. Open: Opens a standard File Open dialog. This dialog can be used to open Templates and data mapping configurations. Open Recent: List the most recently opened Templates and configurations. Clicking on a template will open it in the Designer module, clicking on a data mapping configuration will open it in the DataMapper module.
PAGE 296

Edit Menu l Undo: Undoes the previous action. l Redo: Redoes the last action that was undone. l l l l Cut Step: Removes the currently selected step and places it in the clipboard. If the step is a Repeat or a Condition, all steps under it are also placed in the clipboard. If there is already a step in the clipboard, it will be overwritten. Copy Step: Places a copy of the currently selected step in the clipboard. The same details as the Cut step applies.
PAGE 297

l l l l l l Add Goto Step: Adds a Goto step that moves the selection pointer to the beginning of the data selection. For instance if an XML node is selected, the pointer moves to where that node is located. Add Condition Step: Adds a condition based on the current data selection. The "True" branch gets run when the text is found on the page. Other conditions are available in the step properties once it has been added.
PAGE 298

l l Reset Perspective: Resets all toolbars and panes to the initial configuration of the module. Preferences: Click to open the Preferences dialog. Help Menu l l l Software Activation: Displays the Software Activation dialog. See Activating your license. Help Topics: Click to open this documentation. Contact Support: Click to open the Objectif Lune Contact Page in the default system Web browser. l About PlanetPress Connect Designer: Displays the software's About dialog.
PAGE 299

Filter To find a certain table, group or field in a large Data Model, start typing characters in the Filter box. This immediately narrows down the list of displayed items to all tables, groups and fields whose name contains the characters that were typed. Note that the filtering is case-insensitive. Data Model toolbar buttons : Import Data Model: Click to browse to a file that contains a Data Model. This may l be: l A Data Model file (*.OL-datamodel). l A JSON file (*.json; see the note below).
PAGE 300

l l l l : Synchronize Fields and Structure: Click to synchronize the Data Model fields and structure in the currently loaded template and data mapping configuration. If you click this button when working on the data mapping configuration, the Data Model gets updated to the one in the template. If you click it when working on the template, the Data Model gets updated to the one in the data mapping configuration. : Show the ExtraData field. Note that this field is not meant to be filled via an extraction.
PAGE 301

Note Rename, Delete and Set Type are only available for Data Model fields or detail tables that are not filled via an extraction. Fields and detail tables that are filled via an Extract step are to be changed (renamed, deleted etc.) via the properties of that Extract step; see: "Editing fields" on page 265 and "Renaming a detail table" on page 303. l l Rename: Click to rename the selected table, field or group. Enter the new name and click OK to rename.
PAGE 302

l l l l l l l l The column on the left displays the name of the field. The column on the right displays the current value of the extracted field based on the record shown in the Data Viewer, if an Extract step has an extraction for this field (see "Extracting data" on page 225). The icon to the left of the name indicates the data type of the field (see "Data types" on page 276). A field name with an asterisk to the right indicates that this field is required.
PAGE 303

l l l l Previous Record: Go to the previous record in the data sample. This button is disabled if the first record is shown. Current Record: Displays the current record or table entry. Type a record number and press the Enter key to display that record. The number has to be within the number of available records in the data sample. Next Record: Go to the next record in the data sample. This button is disabled if the last record is shown. Last Record: Go to the last record in the data sample.
PAGE 304

Note A detail table’s name should always begin with ‘record.’. 3. Click somewhere else on the Step Properties pane to update the Data Model. You will see the new name appear. Creating multiple detail tables Multiple detail tables are useful when more than one type of transactional data is present in the source data, for example purchases (items with a set price, quantity, item number) and services (with a price, frequency, contract end date, etc).
PAGE 305

To create more than one detail table, simply extract transactional data in different Repeat steps (see "Extracting transactional data" on page 231). The best way to do this is to add an empty detail table (right-click the Data Model, select Add a table and give the detail table a name) and drop the data on the name of that detail table.
PAGE 306

Nested detail tables Nested detail tables are used to extract transactional data that are relative to other data. They are created just like multiple detail tables, with two differences: l l For the tables to be actually nested, the Repeat step and its Extract step that extract the nested transactional data must be located within the Repeat step that extracts data to a detail table. In their name, the dot notation (record.services) must contain one extra level (record.services.charges).
PAGE 307

a number of "details" such as movie rentals or long distance calls.
PAGE 308

The services can be extracted to a detail table called record.services. The "charges" and "details" can be extracted to two nested detail tables.
PAGE 309

The nested tables can be called record.services.charges and record.services.details.
PAGE 310

Now one "charges" table and one "details" table are created for each row in the "services" table. The Data Viewer The Data Viewer is located in the middle on the upper half of the DataMapper screen. It displays the data source that is currently loaded in the DataMapper, specifically one record in that data. Where one record ends and the next starts is determined in the Data Source settings (see "Record boundaries" on page 222).
PAGE 311

l l l Hide/Show datamap : Click to show or hide the icons to the left of the Data Viewer which displays how the steps affect the line. Hide/Show extracted data : Click to show or hide the extraction selections indicating that data is extracted. This simplifies making data selections in the same areas and is useful to display the original data. Lock/Unlock extracted data : Click to lock existing extraction selections so they cannot be moved or resized.
PAGE 312

Messages pane The Messages pane is shared between the DataMapper and Designer modules and displays any warnings and errors from the data mapping configuration or template. At the top of the Message pane are control buttons: l Export Log: Click to open a Save As dialog where the log file (.log) can be saved on disk. l Clear Log Viewer: Click to remove all entries in the log viewer. l Filters: Displays the Log filter (see "Log filter" below).
PAGE 313

Settings pane Settings for the data source and a list of Data Samples and JavaScript files used in the current data mapping configuration, can be found on the Settings tab at the left. The available options depend on the type of data sample that is loaded. The Input Data settings (especially Delimiters) and Boundaries are essential to obtain the data and eventually, the output that you need. For more explanation, see "Data source settings" on page 220.
PAGE 314

l l Ignore unparseable lines: Ignores any line that does not correspond to the settings above. Skip empty lines: Ignore any line that has no content. Note that spaces are considered content. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text.
PAGE 315

average character in the font. l l l l Line spacing: Determines the spacing between lines of text. The default value is 1, meaning the space between lines must be equal to at least the average character height. Paragraph spacing: Determines the spacing between paragraphs. The default value is 1.5, meaning the space between paragraphs must be equal to at least 1.5 times the average character height to start a new paragraph. Magic number: Determines the tolerance factor for all of the above values.
PAGE 316

l l l Encoding: Defines what encoding is used to read the Data Source ( US-ASCII, ISO8859-1, UTF-8, UTF-16, UTF-16BE or UTF-16LE ). Sort on: Allows to select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the sorting column has numbers, it will be sorted as a text. With a Custom Query, this option is not available. Skip empty lines: Ignore any row that has no content, e.g. only nulls or empty strings.
PAGE 317

l On text: Triggers a new page in the Data Sample when a specific string is found in a certain location. l Word to find: Compares the text value with the value in the data source. l Match case: Activates a case sensitive text comparison. l l l Location: Choose Selected area or Entire width to use the value of the current data selection as the text value. Left/Right: Use the spin buttons to set the start and stop columns to the current data selection (Selected area) in the record.
PAGE 318

l The XPath must start with = l The entire JavaScript statement must be enclosed in curly brackets: { ... } l Any other curly brackets that are not part of the JavaScript code must be escaped with a backslash. Single line comments (//...) in the code are not supported. Note that since the XPath is a string, the return value of the JavaScript statement will be interpreted as a string.
PAGE 319

Boundaries Boundaries are the division between records: they define where one record ends and the next record begins; for an explanation see "Record boundaries" on page 222. CSV, Excel or Database file boundaries Since database data sources are structured the same way as CSV and Excel files, the options for these file types are identical. l l 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.
PAGE 320

PDF file boundaries For a PDF file, Boundaries determine how many pages are included in each record. You can set this up in one of three ways: by giving a static number of pages; by checking a specific area on each page for text changes, specific text, or the absence of text; or by using an advanced script. l l Record limit: Defines how many records are displayed in the Data Viewer. To disable the limit, use the value 0 (zero).
PAGE 321

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 page 316. l l 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).
PAGE 322

l l Delimiters before/after: Defines the boundary a certain number of data pages before or after the current data page. This is useful if the text triggering the boundary is not located on the first data 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.
PAGE 323

l l Field: Displays the fields and (optionally) attributes in the XML element. The value of the selected field determines the new boundaries. Also extract element attributes: Check this option to include attribute values in the list of content items that can be used to trigger a boundary. Data samples The Data Sample area displays a list of all the imported Data Samples that are available in the current data mapping configuration.
PAGE 324

l l Reload : Reload the currently selected Data Sample and any changes that have been made to it. Set as Active : Activates the selected Data Sample. The active data sample is shown in the Data Viewer after it has gone through the Preprocessor step as well as the Input Data and Boundary settings. Editor Data Format The Editor Data Format setting is only available for Excel files. l Date Display Format: This setting specifies how dates must be displayed in the Data Viewer.
PAGE 325

l Add : Add a new external library. Use the standard Open dialog to browse and open the .js file. l Delete l Replace l Reload to it. : Remove the currently selected library from the data mapping configuration. : Open a library and replace it with the contents of a different js file.
PAGE 326

SQL Query Designer The SQL Query Designer is used to design a custom SQL query to pull information from a database. It can be opened by clicking the Input Data. l l l l Custom SQL button on the Settings pane, under Tables: Lists all tables and stored queries in the database. Custom Query: Displays the query that retrieves information from a database. You may use variables and properties in the query, to make the selection dynamic. See "Using variables and properties in an SQL query" below.
PAGE 327

l Properties that have their scope set to "Automation variable". These are retrieved via automation.variables(see "Objects" on page 378), for example automation.variables.FieldList. Properties that have their scope set to "Each record" and can not be used because the SQL query is executed before any record is created. For the same reason, variables declared in other Steps can not be used. Example = SELECT {automation.variables.FieldList} FROM {automation.jobInfo.
PAGE 328

Viewing step details Hovering over the task shows a tooltip that displays some of the details of that step. To see all details for a step, click on the step and take a look at the Step properties pane ("Step properties pane" on the next page). Clicking on any Extract step in the Steps pane highlights any area in the Data Viewer from which it extracts data. You can also click on the Preprocessor step to select all the steps in the workflow to show a complete map of all the extracted data.
PAGE 329

l Copy/Paste Step: To copy a step, right-click on it and select Copy Step or use the button in the Toolbar. If the step is Repeat or Condition, all steps under it will also be placed in the clipboard. To paste the copied step at its destination, right-click the step in the position before the desired location and select Paste Step, or use the Toolbar. button in the Step properties pane The Step Properties pane is used to adjust the properties of each Step in the process (see "Steps" on page 246).
PAGE 330

Description This subsection is collapsed by default in the interface, to give more screen space to other important parts. Name: The name of the step. This name will be displayed on top of the step's icon in the Steps pane. Comments: The text entered here will be displayed in the tooltip that appears when hovering over the step in the Steps pane. Fixed automation properties The Fixed automation properties subsection lists all the fixed runtime parameters available from PlanetPress Workflow.
PAGE 331

access these property inside of any JavaScript code within the data mapping configuration, use automation.properties.OriginalFilename. l l ProcessName: This property contains the name of the process that is currently executing the data mapping configuration and is equivalent to the %w variable in the process. To access this property inside of any JavaScript code within the data mapping configuration, use automation.properties.ProcessName.
PAGE 332

l l l Entire Data: These properties are statically set at the start of a job, before anything else. They cannot be changed once they have been set, in other words they are global constants. They are mostly useful for static information such as folder locations or server addresses. Each Record: These properties are evaluated and set at the beginning of each source record.
PAGE 333

l l Name: The name to identify the Preprocessor task. Click this field to rename the Preprocessor task. Type: The type of Preprocessor task. Currently there is only one type available: script. The buttons to the right can be used to add, remove and reorder the tasks and to apply them to the current data file. The Export button exports the current data file in its current state. Preprocessing may cost a lot of time when the data file is very large.
PAGE 334

extractions within the same loop. This ensures that, if multiple extracts are present, only one detail table is created. Field Definition The following field definition settings are identical for all fields. l Field List: The Field List displays each of the single fields that belong to the selected step in a drop-down. Fields can be re-ordered and re-named within the Order and rename fields dialog (see "Order and rename fields dialog" on page 339).
PAGE 335

l Use selection: Click to use the value of the current data selection for the extraction. Note If the selection contains multiple lines, only the first line is selected. l Properties: The value of the property selected below will be the value of the selected field. l l l Property: This drop-down lists all the currently defined properties (including system properties). Custom properties can be defined in the Preprocessor step; see "Preprocessor step" on page 246.
PAGE 336

Note If the selection contains multiple lines, only the first line is extracted. l Post Function: Enter a JavaScript expression to be run after the extraction. A Post function script operates directly on the extracted data, and its results replace the extracted data. For example, the Post function script replace("-", ""); would replace the first dash character that occurs inside the extracted string. l Use JavaScript Editor: Click to display the Script Editor dialog.
PAGE 337

l l l l Post Function: Enter a JavaScript expression to be run after the extraction. For example replace("-","") would replace a single dash character inside the extracted string. Trim: Select to trim empty characters at the beginning or the end of the field. Type: The data type of the selected data; see "Data types" on page 276. If the selected data is split (see below), this setting is applied to the first extracted field.
PAGE 338

Settings for location-based fields in an XML File These are the settings for location-based fields in an XML file. l XPath: The path to the XML field that is extracted. l Use selection: Click to use the value of the current data selection for the extraction. Note If the selection contains multiple lines, only the first line is selected. l Post Function: Enter a JavaScript expression to be run after the extraction.
PAGE 339

l Currency Sign : Set the currency sign for a currency value. l Date Format : Set the date format for a date value. l l Date Language : Set the date language for a date value (ex: If English is selected, the term May will be identified as the month of May). Treat empty as 0 : A numerical empty value is treated as a 0 value. Order and rename fields dialog The Order and rename fields dialog displays the extracted fields in the currently selected Extract step.
PAGE 340

l Move Up button l Move Down button : Click to move the selected field up one position. : Click to move the selected field down one position. Note The order of fields in an extraction step isn't necessarily the same as the order of those fields in the Data Model; see "Ordering and grouping fields in the Data Model" on page 260. Action step properties The Action step can run multiple specific actions one after the other in order; see "Action step" on page 255 for more information.
PAGE 341

l l l Run JavaScript : Runs a JavaScript expression, giving much more flexibility over the extraction process. Skip to next record: When this option is selected, the extraction workflow stops processing the current record and moves on to the next one. If fields were already extracted prior to encountering the Action step, then those fields are stored as usual. If no fields were extracted prior to encountering the Action step, then no trace of the record is saved in the database at run time.
PAGE 342

Note If the selection contains multiple lines, only the first line is selected. l l Trim: Select to trim empty characters at the beginning or the end of the field JavaScript : The result of the JavaScript Expression written below the drop-down will be the value of the extracted field. If the expression contains multiple lines, the last value attribution (variable = "value";) will be the value. See "DataMapper Scripts API" on page 368. l l l l Expression: The JavaScript expression to run.
PAGE 343

l l Date Language : Set the date language for a date value (ex: If English is selected, the term May will be identified as the month of May). Treat empty as 0 : A numerical empty value is treated as a 0 value. CSV and Database Files l Property: Displays a list of record properties set in the Preprocessor step (see "Preprocessor step" on page 246). l Type: Displays the type of the property. Read only field. l Based on: Determines the origin of the data.
PAGE 344

l l Use selected text: Inserts the text in the current data selection in the JavaScript Expression. If multiple lines or elements are selected, only the first one is used. Use selection: Click to use the value of the current data selection for the extraction. Note If the selection contains multiple lines, only the first line is selected. l Data Format: Data format settings tell the DataMapper how certain types of data are formatted in the data source.
PAGE 345

l XPath: The path to the XML field that is extracted. l Use selection: Click to use the value of the current data selection for the extraction. Note If the selection contains multiple lines, only the first line is selected. l l Trim: Select to trim empty characters at the beginning or the end of the field JavaScript : The result of the JavaScript Expression written below the drop-down will be the value of the extracted field.
PAGE 346

l Data Format: Data format settings tell the DataMapper how certain types of data are formatted in the data source. Make sure that this format matches the actual format of the data in the data source. l Negative Sign Before : A negative sign will be displayed before any negative value. l Decimal Separator : Set the decimal separator for a numerical value. l Thousand Separator : Set the thousand separator for a numerical value. l Currency Sign : Set the currency sign for a currency value.
PAGE 347

The properties described below become visible in the Step properties pane when the Repeat step is selected in the Steps pane. Description This subsection is collapsed by default in the interface, to give more screen space to other important parts. Name: The name of the step. This name will be displayed on top of the step's icon in the Steps pane. Comments: The text entered here will be displayed in the tooltip that appears when hovering over the step in the Steps pane.
PAGE 348

value returned by the expression must be an integer higher than 0. Note that in the event of an infinite loop, an error will only be raised after the set maximum number of iterations. l l Use JavaScript Editor: Click to display the Edit Script dialog. Collection (only with For Each): The XPath that specifies the level and (optionally) elements to select on that level. To select elements you can either use static values, e.g. ./user[@lastname="Smith"] or JavaScript statements, for example: =.
PAGE 349

Note Both the Left and Right operands have the same properties. Text and PDF Files Note The Repeat Step expects lines of text in a PDF file to be horizontal (regardless of the orientation of the page). Vertical text will cause an error. l Based On: l Position: The data in the specified position for the comparison. l l l l l l l Right: The end position for the data selection. Top offset: The vertical offset from the current pointer location in the Data Sample (Viewer).
PAGE 350

l JavaScript : The result of a JavaScript Expression. l l l l l l l Use JavaScript Editor: Click to display the Edit Script dialog. Use selected text: Inserts the text in the current data selection in the JavaScript Expression. If multiple lines or elements are selected, only the first one is used. Data Property: The value of a data-level property set in the Preprocessor step (see "Preprocessor step" on page 246).
PAGE 351

CSV and Database Files l Based On: l Position: The data in the specified position for the comparison. l l l l l l l l l l Trim: Select to trim empty characters at the beginning or the end of the field. Value: The text value to use in the comparison. Use selected text: Uses the text in the current data selection as the Value. If multiple lines or elements are selected, only the first one is used. Field: The Extracted Record field to use in the comparison.
PAGE 352

l Extractor Property: The value of an internal extractor variable: l l l Counter: The value of the current counter iteration in a Repeat step. Vertical Position: The current vertical position on the page, either in Measure (PDF) or Line (Text and CSV). Operators: l l l l l l is equal to: The two specified value are identical for the condition to be True. contains: The first specified value contains the second one for the condition to be True.
PAGE 353

l JavaScript : The result of a JavaScript Expression. l l l l l l l Use JavaScript Editor: Click to display the Edit Script dialog. Use selected text: Inserts the text in the current data selection in the JavaScript Expression. If multiple lines or elements are selected, only the first one is used. Data Property: The value of a data-level property set in the Preprocessor step.
PAGE 354

Condition step properties A Condition step is used when the data extraction must be based on specific criteria. See "Condition step" on page 251 for more information. The properties of a Conditon step become visible in the Step properties pane when the Condition step is selected on the Steps pane. Description This subsection is collapsed by default in the interface, to give more screen space to other important parts. Name: The name of the step.
PAGE 355

Note Both the Left and Right operands have the same properties. l Based On: l Position: The data in the specified position for the comparison. l l Right (Txt and PDF only): The end position for the data selection. l Height (Txt and PDF only): The height of the selection box. l l l l l l l XPath (XML only): The path to the XML field that is extracted. l Top offset: The vertical offset from the current pointer location in the Data Sample (Viewer).
PAGE 356

JavaScript Expression. If multiple lines or elements are selected, only the first one is used. l l l l Data Property: The value of a data-level property set in the Preprocessor (see "Preprocessor step" on page 246). Record Property: One of the local variables that you can create and that are reset for each document as opposed to data variables that are global because they are initialized only once at the beginning of each job.
PAGE 357

Description This subsection is collapsed by default in the interface, to give more screen space to other important parts. Name: The name of the step. This name will be displayed on top of the step's icon in the Steps pane. Comments: The text entered here will be displayed in the tooltip that appears when hovering over the step in the Steps pane. Condition Left operand, Right operand The Left and right operand can be Based on: l Position: The data in the specified position for the comparison.
PAGE 358

l l JavaScript: The result of a JavaScript Expression. l l l l l l l Field: The Extracted Record field to use in the comparison. Expression: The JavaScript line that is evaluated. Note that the last value attribution to a variable is the one used as a result of the expression. See also: "DataMapper Scripts API" on page 368. Use JavaScript Editor: Click to display the Edit Script dialog (see "Using scripts in the DataMapper" on page 371).
PAGE 359

Operators l Case conditions are made by comparison of the two operands, left and right, using a specific Operator. l l l l l l is equal to: The two specified value are identical for the condition to be True. contains: The first specified value contains the second one for the condition to be True. is less than: The first specified value is smaller, numerically, than the second value for the condition to be True.
PAGE 360

Text file l Target Type: Defines the type of jump. l Line: Jumps a certain number of lines or to a specific line. l l l l Current Position: The Goto begins at the current cursor position. l Top of record: The Goto begins at line 1 of the source record. Move by: Enter the number of lines or pages to jump. Page: Jumps between pages or to a specific page.
PAGE 361

l Left: The starting column, inclusively. l Right: The end column, inclusively. l l l l Use selection: Click while a selection is made in the Data Viewer to automatically set the left and right values to the left and right edges of the selection. Expression: Enter the text or Regex expression to look for on the page. Use selection: Click while a selection is made in the Data Viewer to copy the contents of the first line of the selection into the Expression box.
PAGE 362

l Left: The starting column, inclusively. l Right: The end column, inclusively. l l Use selection: Click while a selection is made in the Data Viewer to automatically set the left and right values to the left and right edges of the selection. Next occurrence of: Jumps to the next occurrence of specific text or a text pattern, either anywhere on the line or in specific columns.
PAGE 363

XML File l Destination (XML files): Defines what type of jump to make: l l l l l Sibling element: Jumps the number of siblings (nodes at the same level) defined in the Move byoption. Sibling element with same name: Jumps the number of same name siblings (nodes at the same level of which the node is the same name) defined in the Move byoption. Element, from top of record: Jumps to the specified node. The XPATH in the Absolute XPATHoption starts from the root node defined by /.
PAGE 364

Postprocessor The Postprocessor subsection defines what postprocessors run on the Data Sample at the end of the data mapping workflow. Each Postprocessor runs in turn, using the result of the previous one as an input. l Name: The name to identify the Postprocessor. l Type: The type of Postprocessor. Currently there is a single type available. l JavaScript: Runs a JavaScript Expression to modify the Data Sample. See "DataMapper Scripts API" on page 368.
PAGE 365

Toolbar In the DataMapper module, the following buttons are available in the top toolbar. File manipulation l New: Displays the New wizard where a new data mapping configuration or a new template can be created. Open: Displays the Open dialog to open an existing data mapping configuration. l l Save: Saves the current data mapping configuration. If the configuration has never been saved, the Save As... dialog is displayed.
PAGE 366

l l l l l l l l Add Extract Field: Adds the data selection to the selected Extract step, if an extract step is currently selected. If multiple lines, nodes or fields are selected, multiple extract fields are added simultaneously. Add Multiple Conditions: Adds a condition that splits into multiple case conditions. Add Action Step: Adds a step to create a custom JavaScript snippet. See "DataMapper Scripts API" on page 368 for more details.
PAGE 367

If you are new to PlanetPress Connect and you don't know where to start, see "Welcome to PlanetPress Connect 2020.1" on page 15. The Welcome Screen can be reopened in two ways: l The Welcome Screen button in the "Toolbars" on page 1048. l From the Menus in Help, Welcome Screen. To go back from the Welcome Screen to the template or data mapping configuration that you were working on: l Close the Welcome Screen by clicking the cross next to the text 'Welcome' at the top.
PAGE 368

l Create/Open: l l l l l Open File: Lets you open an existing template or data mapping configuration. New template: Lets you choose a Context to create a new template without a Wizard. Template Wizards: Displays a list of available Template Wizards, producing premade templates with existing demo content; see "Creating a template" on page 423. Project Wizards: Displays a list of available Project Wizards, producing a complete Connect project; see "Project Wizards" on page 968.
PAGE 369

Name Description Available in scripts of type "db" on page 398 An object that allows to connect to a database. Boundaries, all steps except Goto "logger" on page 399 An object that allows to log error, warning or informational messages. Boundaries, all steps except Goto "record" on page 399 The current record in the main data set. Extract, Condition, Repeat and Multiple Conditions steps "region" on page 400 An object that defines a subsection of the input data.
PAGE 370

Functions These functions are available in Boundaries and Steps scripts. Name Description copyFile() Copies a file to the target file path, replacing it if it already exists. "createGUID()" on page 409 Returns a unique 36-character string consisting of 32 alphanumeric, lower case characters and four hyphens (format: 84-4-4-12). Example: 123e4567-e89b-12d3-a456-426655440000. "createHTTPRequest ()" on page 409 Creates a new HTTP Request Object.
PAGE 371

Name Description openBinaryReader() Opens a file as a binary file for reading purposes. openBinaryWriter() Opens a file as a binary file for writing purposes. openTextReader() Opens a file as a text file for reading purposes. openTextWriter() Opens a file as a text file for writing purposes. Using scripts in the DataMapper In the DataMapper every part of the extraction process can be customized using scripts.
PAGE 372

The script can always be written directly in a small script area or in the Edit script dialog. To invoke this dialog click the Use JavaScript Editor button . Tip In the Edit script dialog, press Ctrl + Space to bring up the list of available JavaScript objects and functions (see Datamapper API). Use the arrow keys to select a function or object and press enter to insert it. Type a dot after the name of the function or object to see which features are subsequently available.
PAGE 373

Take the following JavaScript function, for example: function myAddFunction(p1, p2) { return p1 + p2; }; If this is saved as myFunction.
PAGE 374

Accessing data Data available inside each event Every time a delimiter is encountered, an event is triggered and the script is executed. The event gives the script access to the data between the current location - the start of a row, line or page - and the next delimiter. So at the beginning of the process for a PDF or text file, you have access to the first page only, and for a CSV or for tabular data, that would be the first row or record.
PAGE 375

"Artist","Album","Released" "Beatles","Abbey Road",1969 "Beatles","Yellow Submarine",1969 "Led Zeppelin","Led Zeppelin 1",1969 "Led Zeppelin","Led Zeppelin 2",1969 "Beatles","Let it be",1969 "Rolling Stones","Let it bleed",1969 "Led Zeppelin","Led Zeppelin 3",1970 "Led Zeppelin","Led Zeppelin 4",1971 "Rolling Stones","Sticky Fingers",1971 Note The first line is just the header with the names of the CSV columns. The data is already sorted per year, per artist, and per album.
PAGE 376

!= boundaries.getVariable("lastYear") ) { boundaries.set(); } } boundaries.setVariable("lastBand",zeBand[0]); boundaries.setVariable("lastYear",zeYear[0]); l l l l The script first reads the two values from the input data, using the createRegion() method (see: "createRegion()" on page 401). For a CSV/database data type, the parameter it expects is simply the column name.
PAGE 377

Beatles Led Zeppelin Led Zeppelin Beatles Rolling Stones Led Zeppelin Led Zeppelin Rolling Stones Yellow Submarine Led Zeppelin 1 Led Zeppelin 2 Let it be Let it bleed Led Zeppelin 3 Led Zeppelin 4 Sticky Fingers 1968 1969 1969 1970 1969 1970 1971 1971 The purpose of the script, again, is to set the record boundary when EITHER the year OR the artist changes. The script would look like this: /* Read the values of both columns we want to check */ var zeBand = boundaries.get(region.
PAGE 378

Settings, specify On lines as the Page delimiter type with the number of lines set to 1. When you now set the boundary Trigger to On script, the file will be processed line per line (triggering the event on each line). Paste the above code in the JavaScript expression field and click the Apply button to see the result.
PAGE 379

Properties The following table lists the properties of the automation object. All properties are read-only. Property Description jobInfo Returns a ScriptableAutomation object containing Job Info 1 to 9 values from PlanetPress Workflow (see "Fixed automation properties" on page 330, and Job Info variables in the Workflow Online Help).
PAGE 380

boundaries Returns a boundaries object encapsulating properties and methods allowing to define the boundaries of each document in the job. This object is available when triggering document boundaries On script. Properties The following table lists the properties of the boundaries object. Property Description currentDelim A read-only 1-based index (number) of the current delimiter in the file. In other words, the Beginning Of File (BOF) delimiter equals 1.
PAGE 381

Method Description Script type setVariable () Sets a boundaries variable to the specified value, automatically creating the variable if it doesn't exist yet. Boundaries find() Method of the boundaries object that finds a string in a region of the data source file. The method returns the region in which the string was searched (PDF file) or the exact region in which the string was encountered (Text file). To check if the call to boundaries.
PAGE 382

location where the match was found. This will always be a subset of the in_Region.range property. It can be used to determine the exact location where the match occurred. Use boundaries.get() to retrieve the actual text from the resulting region; see "get()" below. Example This script sets a boundary when the text TOTAL is found on the current page in a PDF file. The number of delimiters is set to 1, so the boundary is set on the next delimiter, which is the start of the next page. if (boundaries.
PAGE 383

Note Boundary variables are carried over from one iteration of the Boundaries script to the next, while native JavaScript variables are not. getVariable(varName) varName String name of the variable from which the value is to be retrieved. If the variable does not exist, the value null is returned. It is considered good practice (almost mandatory, even) to always check whether a variable is defined before attempting to access its value. set() Sets a new DataMapper record boundary.
PAGE 384

start of the next page. if (boundaries.find("TOTAL", region.createRegion (10,10,215,279)).found) { boundaries.set(1); } Assume you want to set record boundaries whenever the text "TOTAL" appears in a specific region of the page of a PDF file, but the PDF file has already been padded with blank pages for duplexing purposes.
PAGE 385

setVariable(varName, varValue) Sets variable varName to value varValue. varName String name of the variable of which the value is to be set. varValue Object; value to which the variable has to be set. Example This script examines a specific region and stores its contents in a variable in the boundaries. var addressRegion = region.createRegion(10, 30, 100, 50); var addressLines = boundaries.get(addressRegion); boundaries.
PAGE 386

Method Description Script type File type "extract()" below Extracts the text value from a rectangular region. Extract, Condition, Repeat, and Action steps All "extractMeta ()" on page 393 Extracts the value of a metadata field. Extract, Condition, Repeat, and Action steps All "fieldExists ()" on page 393 Method that returns true if the specified metadata field, column or node exists.
PAGE 387

Number that represents the distance, measured in characters, from the left edge of the page to the left edge of the rectangular region. The leftmost character is character 1. right Number that represents the distance, measured in characters, from the left edge of the page to the right edge of the rectangular region. verticalOffset Number that represents the current vertical position, measured in lines. regionHeight Number that represents the total height of the region, measured in lines.
PAGE 388

Example 2: The script command data.extract(1,22,9,6,"
"); means that the left position of the extracted information is located at 1, the right position at 22, the offset position is 9 (since the first line number is 10) and the regionHeight is 6 (6 lines are selected). Finally, the "
" string is used for concatenation.
PAGE 389

extract(xPath) Extracts the text value of the specified node in an XML file. xPath String that can be relative to the current location or absolute from the start of the record. Example The script command data.extract('./CUSTOMER/FirstName'); means that the extraction is made on the FirstName node under Customer.
PAGE 390

extract(columnName, rowOffset) Extracts the text value from the specified column and row. columnName String that represents the column name. rowOffset Number that represents the row index (zero-based), relative to the current position. To extract the current row, specify 0 as the rowOffset. Use moveTo() to move the pointer in the source data file (see "moveTo()" on page 405). Example The script command data.extract('ID',0); means that the extraction is made on the ID column in the first row.
PAGE 391

extract(left, right, verticalOffset, lineHeight, separator) Extracts the text value from a rectangular region in a PDF file. All coordinates are expressed in millimeters. left Double that represents the distance from the left edge of the page to the left edge of the rectangular region. right Double that represents the distance from the left edge of the page to the right edge of the rectangular region. verticalOffset Double that represents the distance from the current vertical position.
PAGE 392

lineHeight Double that represents the total height of the region. separator String inserted between all lines returned from the region. If you don't want anything to be inserted between the lines, specify an empty string (""). Tip "
" is a very handy string to use as a separator. When the extracted data is inserted in a Designer template, it will be interpreted as a line break, because
is a line break in HTML and Designer templates are actually HTML files. Example The script command data.
PAGE 393

extractMeta() Method that extracts the value of a metadata field on a certain level in a PDF/VT. This method always return a String. extractMeta(levelName String, propertyName String) levelName String, specifying the PDF/VT's level. Case sensitive. propertyName String, specifying the metadata field. fieldExists() Method of the data object that returns true if a certain metadata field, column or node exists. (See "data" on page 385.
PAGE 394

fieldExists(levelName, propertyName) This method returns true if the given metadata field exists at the given level in a PDF file. levelName String that specifies the metadata field. propertyName String that specifies the level. fieldExists(fieldName) This method returns true if the specified column exists in the current record in a CSV file. fieldName String that represents a field name (column) in a CSV file.
PAGE 395

Partial matches are not allowed. The entire string must be found between the two constraint parameters. The data.find() function only works on the current page. If the record contains several pages, you must create a loop that will perform a jump from one page to another to do a find() on each page. Note Calling this method does not move the current position to the location where the string was found.
PAGE 396

Left=26,76, Top=149.77, Right=40,700001, Bottom=154.840302 These values represent the size of the rectangle that encloses the string in full, in millimeters relative to the upper left corner of the current page. findRegExp() Finds the first occurrence of a string that matches the given regular expression pattern, starting from the current position.
PAGE 397

matching can be enabled by specifying the UNICODE_CASE flag (u) in conjunction with this flag. s: Enables dotall mode. In dotall mode, the expression . matches any character, including a line terminator. By default this expression does not match line terminators. L: Enables literal parsing of the pattern. When this flag is specified, then the input string that specifies the pattern is treated as a sequence of literal characters.
PAGE 398

Examples data.findRegExp(/\d{3}-[A-Z]{3}/,"gi",50,100); or data.findRegExp("\\d{3}-[A-Z]{3}","gi",50,100);}} Both expressions would match the following strings: 001-ABC, 678-xYz. Note how in the second version, where the regular expression is specified as a string, some characters have to be escaped with an additional backslash, which is standard in JavaScript. db Object that allows to connect to a database. Methods The following table describes the methods of the db object.
PAGE 399

user String that represents the user name for authentication. password String that represents the password for authentication. logger Global object that allows logging messages such as error, warning or informational messages. Methods The following table describes the methods of the logger object.
PAGE 400

Property Description index The one-based index of this record, or zero if no data is available. tables The details table that belong to this record. You can access a specific table using a numeric index or the table name. Example See this How-to for an example of how the current record index, and/or the total number of records in the record set, can be displayed in a document: How to get the record index and count. region The region object defines a sub-section of the input data.
PAGE 401

Property/method Description Return Type range Read-only object containing the physical coordinates of the region. Physical location of the region: x1 (left), y1 (top), x2 (right), y2 (bottom), expressed in characters for a text file or in millimeters for a PDF file. For a CSV file, it is the name of the column that defines the region. createRegion() Creates a region by setting the physical coordinates of the region object. A region that has the specified coordinates.
PAGE 402

Example The following script attempts to match ((n,m)) or ((n)) against any of the strings in the specified region and if it does, a document boundary is set. var myRegion = region.createRegion(170,25,210,35); var regionStrings=boundaries.get(myRegion); if (regionStrings) { for (var i=0;i
PAGE 403

l l For a PDF file, the range() method contains the physical coordinates of the region: x1 (left), y1 (top), x2 (right), y2 (bottom), expressed in millimeters. For a CSV file, the range contains the name of the column that defines the region. sourceRecord Returns a sourceRecord object containing custom properties specific to the current source record being processed. These are the custom properties defined in the Preprocessor step that have their Scope set to "Each record".
PAGE 404

Method Description File type millimeters(e.g. PDF data). currentLoopCounter An integer value representing the current iteration of the containing loop. When loops are nested, you have access to the iteration for the current loop but not to any of the parent loops. Note: This variable is a counter so it starts at 1 as opposed to an index which usually starts at 0.
PAGE 405

Example if(steps.currentPage > curPage) { steps.moveTo(0, steps.currentPosition+14); /* Moves the current position to 14 lines below the current position of the pointer in the data */ curPage++; } else if(curLine.startsWith("LOAD FACTOR")) { /* Extracts data to the curLine variable until the string "LOAD FACTOR" is encountered */ break; } else { lineArray.
PAGE 406

Number that may be set to: l 0 or steps.MOVELINES l 1 or steps.MOVEDELIMITERS l 2: next line with content verticalPosition Number. What it represents depends on the value specified for scope. With the scope set to 0 or steps.MOVELINES, verticalPosition represents the index of the line to move to from the top of the record. With the scope set to 1 or steps.
PAGE 407

verticalOffset Double. What it represents depends on the value specified for scope. With the scope set to 0 or steps.MOVEMEASURE, verticalOffset represents the number of millimeters to move the current position, relative to the top of the record (NOT the top of the current page). With the scope set to 1 or steps.MOVEPAGES, verticalOffsetrepresents the index of the target page, relative to the top of the record.
PAGE 408

moveToNext(scope) Moves the current position in a text file or XML file to the next instance of scope. What scope represents depends on the emulation type: text or XML. Text scope Number that may be set to: l l l 0 or steps.MOVELINES: the current position is set to the next line. 1 or steps.MOVEDELIMITERS: the current position is set to the next delimiter (as defined in the Input Data settings). 2 (next line with content): the current position is set to the next line that contains any text.
PAGE 409

Double that represents the right edge (in millimeters) of the text to find. moveToNext() Moves the current position in a CSV file to the next row, relative to the current position. Functions copyFile() Function that copies a file to the target file path, replacing it if it already exists. copyFile(source, target) source String that specifies the source file path and name. target String that specifies the target file path and name. Example This script copies the file test.txt from c:\Content into the c:\out
PAGE 410

instance a process that retrieves certain values from Workflow’s Data Repository. Another possible use is to have a Postprocessor that writes the results of the extraction process to a file and immediately uploads that file to a Workflow process. The returned ScriptableHTTPRequest has a selection of the properties and methods of the standard JavaScript XMLHTTPRequest object (see https://developer.mozilla.org/enUS/docs/Web/API/XMLHttpRequest). Supported properties and methods are listed below.
PAGE 411

password, pass empty strings: request.open ("GET",url,"",""); l send() l send(String requestBody) Sends an HTTP request and returns the HTTP status code. Blocked call. getResponseHeader(String header) Gets the ResponseHeader by name. getResponseHeaders() Returns the full response headers of the last HTTP request. getRequestBody() Gets the HTTP request body (for POST and PUT). setRequestHeader(String requestHeader, String value) Adds an additional HTTP request header.
PAGE 412

getUsername() gets the username for basic HTTP authentication. setUsername(String userName) sets the username for basic HTTP authentication abort() Aborts the request. createTmpFile() Function that creates a file with a unique name in the temporary work folder and returns a file object. This file stores data temporarily in memory or in a buffer. It is used to prevent multiple input/output access to a physical file when writing.
PAGE 413

} } finally{ // Close the reader reader.close(); } deleteFile(data.filename); tmpFile.move(data.filename); deleteFile() Function that is used to delete a file. deleteFile(filename) filename String that specifies the path and file name of the file to be deleted. Examples 1. Deleting a file in a local folder: deleteFile("c:\Content\test.txt"); 2. Deleting the sample data file used in the DataMapper: deleteFile(data.filename); execute() Function that calls an external program and waits for it to end.
PAGE 414

newByteArray(size) Returns a new byte array of of the specified number of elements. size Integer that represents the number of elements in the new array. newCharArray() Function that returns a new Char array. newCharArray(size) Returns a new Char array of the specified number of elements. size Integer that represents the number of elements in the new array. newDoubleArray() Function that returns a new double array. newDoubleArray(size) Returns a new Double array of the specified number of elements.
PAGE 415

newIntArray() Function that returns a new array of Integers. newIntArray(size) Returns a new Integer array of the specified number of elements. size Integer that represents the number of elements in the new array. newLongArray() Function that returns a new long array. newLongArray(size) Returns a new Long array of the specified number of elements. size Integer that represents the number of elements in the new array. newStringArray() Function that returns a new string array.
PAGE 416

openBinaryWriter() Function that opens a file as a binary file for writing purposes. The function returns a DataOutputStream(see DataOutputStream). openBinaryWriter(filename, append) filename String that represents the name of the file to open. append Boolean parameter that specifies whether the file pointer should initially be positioned at the end of the existing file (append mode) or at the beginning of the file (overwrite mode).
PAGE 417

fileIn.close(); fileOut.close(); deleteFile(data.filename); tmp.move(data.filename); tmp.close(); TextReader The TextReader object, returned by the openTextReader() function, allows to open, parse, read and close a text file. (See: "openTextReader()" on the previous page.) Methods The following table describes the methods of the TextReader object. Method Description close() Closes the stream and releases resources. open(inStream, inEncoding) Creates a reader from an input stream.
PAGE 418

Method Description readLine() Reads and returns the next line, or null if the end of the stream has been reached. skip(offset) Skips the specified number of characters. Parameters: l offset: the number of characters to skip openTextWriter() This function opens a file as a text file for writing purposes. The function returns a "TextWriter" on the next page object. This must be closed at the end. openTextWriter(filename, encoding, append) filename String that represents the name of the file to open.
PAGE 419

fileIn.close(); fileOut.close(); deleteFile(data.filename); tmp.move(data.filename); tmp.close(); TextWriter The TextWriter object, returned by the openTextWriter() function, allows to open a text file, write to it and close it. Methods The following table describes the methods of the TextWriter object. Method Description close() Close the stream. newLine() Creates a new line in the file. open(filename) Creates a new writer on a file to write at the beginning of the file.
PAGE 420

Method Description l value: the string value to write Page 420
PAGE 421

The Designer The Designer is a WYSIWYG (what you see is what you get) editor that lets you create templates for various output channels: Print, Email and Web. A template may contain designs for multiple output channels: a letter intended for print and an e-mail variant of the same message, for example. Content, like the body of the message or letter, can be shared across these contexts. Templates are personalized using scripts and variable data extracted via the DataMapper.
PAGE 422

page 423. 2. Fill the template Add text, images and other elements to the template and style them. See "Content elements" on page 604 and "Styling and formatting" on page 718. 3. Personalize the content Personalize the content using variable data. See "Personalizing content" on page 762. 4. Generate output Adjust the settings, test the template and generate output: letters, emails, and/or web pages. See "Generating output" on page 1413.
PAGE 423

l "Print" on page 446. This topic helps you design and fill sections in the Print context. l "Email" on page 488. This topics helps you design an email template. l "Web" on page 514. This topic helps you design a web page. "Sections" on page 442. Sections in one context are designed for the same output channel. "Content elements" on page 604. Elements make up the biggest part of the content of each design. "Snippets" on page 714.
PAGE 424

There are Wizards for the three types of output channels, or contexts as they are called in the Designer: Print, Email and Web. See: l "Creating an Email template with a Wizard" on page 493 l "Creating a Print template with a Wizard" on page 449 l "Creating a Web template with a Wizard" on page 515 Tip The quickest way to create a Print template based on a PDF file is to right-click the PDF file in the Windows Explorer and select Enhance with Connect.
PAGE 425

Warning A template created in an older version of the software can be opened in a newer version. However, opening and saving it in a newer version of the software will convert the template to the newest file format. The converted template can't be opened in older versions of the software. Opening a package file Templates can also be stored in a package file (see "Creating package files" on page 429). To open a package file, switch the file type to Package files (*.OL-package) in the Open File dialog.
PAGE 426

Saving older templates Saving a template in a newer version of the software will convert the template to the newest file format. This makes it unreadable to older versions of the software. The warning message that is displayed in this case can be disabled. To re-enable this message (and all other warning dialogs), go to Window > Preferences > General, and click the Reset All Warning Dialogs button at the bottom.
PAGE 427

Backup files have the same name as the original template with two underscores and a progressive number (without leading zeros) at the end: originalname__1.OL-template, originalname__2.OL-template, etc. Note The Auto Save function does not cause backup files to be created. File properties On the menu, select File > Properties to view and complement the file properties. See "File Properties dialog" on page 931. The file properties can also be used in scripts; see "template" on page 1383.
PAGE 428

To create a package file, select File >Send to Workflowand choose File in the Destination box. For the other options, see "Sending files to Workflow" on the next page. The package file has the extension .OL-package and can be opened in the Designer (see "Opening a package file" on page 425). Exporting a template report A template report can be used for archiving purposes or to provide information about the template to people who do not have access to Connect.
PAGE 429

To test a template first, select Context > Preflight. Preflights execute the template without actually producing output and it displays any issues once it's done (see also: "Testing scripts" on page 853). Sending files to Workflow Workflow can generate output from a template in automated processes. For this, the template has to be sent to Workflow. Alternatively you may create a Package file (see "Creating package files" below) and import that into Workflow.
PAGE 430

Creating a Web template with a Wizard With the Designer you can design Web templates and output them through Workflow or as an attachment to an email when generating Email output. Capture On The Go templates are a special kind of Web templates; see "Capture OnTheGo template wizards" on page 553. A Web Template Wizard helps you create a Web page that looks good on virtually any browser, device and screen size.
PAGE 431

l Jumbotron l Thank You If you don't know what template to choose, see "Web Template Wizards" on page 433 further down in this topic, where the characteristics of each kind of template are described. 3. Click Next and make adjustments to the settings. The wizard remembers the settings that were last used for a Foundation Web template. l Section: l l l Description: Enter the description of the page. This is the contents of a HTML tag.
PAGE 432

l l l l A Web context with one web page template (also called a section) in it. The web page contains a Header, a Section and a Footer element with dummy text, and depending on the type of web page, a navigation bar, button and/or Form elements. Resources related to the Foundation framework (see "Web Template Wizards" on the next page): style sheets and JavaScript files. The style sheets can be found in the Stylesheets folder on the Resources pane.
PAGE 433

Web Template Wizards Foundation With the exception of the most basic one, all Web Template Wizards in the Designer make use of the Zurb Foundation front-end framework. A front-end framework is a collection of HTML, CSS, and JavaScript files to build upon. Foundation is a responsive framework: it uses CSS media queries and a mobile-first approach, so that websites built upon Foundation look good and function well on multiple devices including desktop and laptop computers, tablets, and mobile phones.
PAGE 434

A Capture OnTheGo Form is actually just a Web Form, that you could add without a wizard, but the COTG Template Wizards include the appropriate JavaScript files for the Capture OnTheGo app, and styles to create user-friendly, responsive forms. They are built upon the Foundation framework. Foundation With the exception of the most basic one, all Web Template Wizards in the Designer make use of the Zurb Foundation front-end framework.
PAGE 435

2. Select a template. There are 8 types of Web Template Wizards: l l l l l l l l Blank. The Blank COTG Template has some basic design and the appropriate form, but no actual form or COTG elements. Bill of Lading. The Bill of Lading Template is a transactional template that includes a Dynamic Table with a checkmark on each line, along with Signature and Date COTG elements. Use this wizard as a way to quickly start any new Zurb Foundation based form for Capture OnTheGo. Event Registration.
PAGE 436

Do the same for the background color of the navigation bar at the top and for the buttons on the Form. 4. Click Next to go to the next settings page if there is one. 5. Click Finish to create the template. The Wizard creates: l l l A Web context with one web page template (also called a section) in it. The web page contains an 'off-canvas' Div element, Header, a Section and a Footer element with dummy text, and depending on the type of web page, a navigation bar, button and/or Form elements.
PAGE 437

Filling a COTG template Before inserting elements in a COTG Form, have the design ready; see "Designing a COTG Template" on page 549. In a Capture OnTheGo form, you can use special Capture OnTheGo Form elements, such as a Signature and a Barcode Scanner element. For a description of all COTG elements, see: "COTG Elements" on page 681. To learn how to use them, see "Using COTG Elements" on page 567.
PAGE 438

Tip Click the Edges button on the toolbar t emporarily adds a frame to certain elements on the Design tab. These will not .Print or output. Tip If you have started creating your Capture OnTheGo template using a COTG Template Wizard, you can find ready-made elements in the Snippets folder on the Resources pane. Resources This page clarifies the difference between Internal, External and Web resources that may be used in a template, and explains how to refer to them in HTML and in scripts.
PAGE 439

When refering to them, normally you would simply use the path directly with the file name. The structure within those folders is maintained, so if you create a "signatures" folder within the "Images" folder, you need to use that structure, for example in HTML: . In scripts, you can refer to them in the same way, for example: results.loadhtml("snippets/en/navbar.
PAGE 440

Web resources Web resources are simply accessed using a full URL. This URL needs to be publicly accessible: if you type in that URL in a browser on the server, it needs to be visible. Authentication is possible only through URL Parameters (http://www.example.com/data.json?user=username&password=password) or through HTTP Basic Auth (http://username:password@www.example.com/data.json).
PAGE 441

with an Email Template Wizard; see "Creating an Email template with a Wizard" on page 493. Outputting and combining contexts All contexts can be present in any template and they can all be used to output documents; see "Generating Email output" on page 1443, "Generating Print output" on page 1415 and "Generating Web output" on page 1453. They can even be combined in output. If present in the same template, a Print context and a Web context can be attached to an Email context.
PAGE 442

Warning If you don't have a backup of the template, the only way to recover a deleted section, is to click Undo on the Edit menu, until the deleted section is restored. After closing and reopening the template it is no longer possible to restore the deleted context this way. In the Saving Preferences you can set whether a backup file should be created when you save the template; see "Save preferences" on page 840. Sections Sections are parts of one of the contexts in a template: Print, Emailor Web.
PAGE 443

Editing a section To open a section, expand the Contexts folder on the Resources pane, expand the respective context (Print, Emailor Web) and double-click a section to open it. Each section can contain text, images and many other elements (see "Content elements" on page 604), including variable data and other dynamic elements (see "Personalizing content" on page 762). To preview a section, open the Preview tab in the Workspace (see "Workspace" on page 1045). Copying a section To copy a section: 1.
PAGE 444

Tip The easiest way to copy a section to another template, is to use the Import Resources dialog in the other template. See: "Import Resources dialog" on page 937. Deleting a section To delete a section: l On the Resources pane, expand the Contexts folder, expand the folder of the respective context, right-click the name of the section, and then click Delete. Warning No backup files are maintained in the template.
PAGE 445

Applying a style sheet to a section In order for a style sheet to be applied to a specific section, it needs to be included in that section. There are two ways to do this. Drag & drop a style sheet 1. Click and hold the mouse button on the style sheet on the Resources pane. 2. Move the mouse cursor within the Resources pane to the section to which the style sheet should be applied. 3. Release the mouse button. Using the Includes dialog 1. On the Resources pane, right-click the section, then click Includes.
PAGE 446

Arranging sections Changing the order of the sections in a context can have an effect on how they are outputted; see: "Print sections" on page 459, "Email templates" on page 499 and "Web pages" on page 521. To rearrange sections in a context: l On the Resources pane, expand the Contexts folder, expand the folder of the respective context, and then drag and drop sections to change the order they are in. Alternatively, right-click a section and click Arrange.
PAGE 447

l PCL l PDF l PostScript (including the PPML, VIPP and VPS variants) With the Designer you can create one or more Print templates and merge the template with a data set to generate personal letters, invoices, policies, or any other type of letter you can think of. The Print context is the folder in the Designer that can contain one or more Print sections. Print templates (also called Print sections), are part of the Print context.
PAGE 448

See "Pages" on page 469 for an overview of settings and elements that are specific for pages. Headers, footers, tear-offs and repeated elements (Master page) In Print sections, there are often elements that need to be repeated across pages, like headers, footers and logos. In addition, some elements should appear on each first page, or only on pages in between the first and the last page, or only on the last page.
PAGE 449

Copy Fit Copy Fit is a feature to automatically adjust the font size of text to make it fit the available space. It could be used for the name of a person on a greeting card, for instance, or for the name of a product on a shelf talker. This feature is only available with Box and Div elements in Print sections. For more information about this feature see "Copy Fit" on page 735. Creating a Print template with a Wizard A Print template may consist of various parts, such as a covering letter and a policy.
PAGE 450

Tip Use the Outline pane at the left to see which elements are present in the template and to select an element. Use the Attributes pane at the right to see the current element's ID, class and some other properties. Use the Styles pane next to the Attributes pane to see which styles are applied to the currently selected element. Basic Print template wizards There are two 'basic' Print Template wizards: one for a formal letter, and one for a postcard.
PAGE 451

See "Print context" on page 454 and "Print sections" on page 459 for more information about Print templates. Formal letter The Formal Letter Wizard first lets you select the page settings, see "Page settings: size, margins and bleed" on page 471. These settings are fairly self-explanatory, except perhaps these: l l l l Duplex means double-sided printing. The margins define where your text flow will go. The actual printable space on a page depends on your printer.
PAGE 452

expand the Contexts folder on the Resources pane; expand the Print folder and rightclick "Section 1"; then select Sheet Configuration.) See "Media" on page 481. l Selectors for variable data, for example: @Recipient@. You will want to replace these by the names of fields in your data. See "Variable Data" on page 777. The Wizard opens the Print section. You can add text and other elements; see "Content elements" on page 604. The formal letter template already has an address on it.
PAGE 453

location should be accessible from the machine on which the template's output is produced. External images are updated (retrieved) at the time the output is generated. After clicking Next, you can change the settings for the page. The initial page size and bleed area are taken from the selected PDF. When you click Finish, the Wizard creates: l l l A Print context with one section in it; see "Print context" on the facing page and "Print sections" on page 459.
PAGE 454

l Choose the desired type of business document from the General drop-down. l Select a color for the colored parts of the document; see "Color Picker" on page 926. l Enter your contact details. l l Click the Browse button to select a logo, or select to use a placeholder logo or no logo at all. Select a PDF file with the letterhead stationery. Also see "Media" on page 481. Tip Nice to know: your info and preferences are saved and will be reused the next time you create an ERP template.
PAGE 455

Print templates (also called Print sections), are part of the Print context. They are meant to be printed directly to a printer or a printer stream/spool file, or to a PDF file (see "Generating Print output" on page 1415). The Print context can also be added to Email output as a PDF attachment; see "Generating Email output" on page 1443. When generating output from the Print context, each of the Print sections is added to the output document, one after the other in sequence, for each record.
PAGE 456

In Print sections, there are often elements that need to be repeated across pages, like headers, footers and logos. In addition, some elements should appear on each first page, or only on pages in between the first and the last page, or only on the last page. Examples are a different header on the first page, and a tear-off slip that should show up on the last page. This is what Master Pages are used for. Master Pages can only be used in the Print context. See "Master Pages" on page 478.
PAGE 457

Printing on both sides To print a Print section on both sides of the paper, that Print section needs to have the Duplex printing option to be enabled; see "Enabling double-sided printing (Duplex, Mixplex)" on page 467. This setting can not be changed in a Job Creation Preset or an Output Creation Preset. Note Your printer must support duplex for this option to work.
PAGE 458

Setting the bleed The bleed is the printable space around a page. It can be used on some printers to ensure that no unprinted edges occur in the final trimmed document. The bleed is one of the settings for a section. See "Page settings: size, margins and bleed" on page 471. Overprint and black overprint Normally, when two colors overlap in Print output, the underlying color is not printed.
PAGE 459

1. Right-click the Print context in the Resources pane and select Color Output. 2. Enable the Keep RGB black in output option. In Connect versions prior to 2018.2, RGB black was not automatically converted to CMYK black. Therefore, this option is by default enabled in templates made with an earlier version. In new templates, this option is disabled by default. Print sections Print templates (also called Print sections), are part of the Print context.
PAGE 460

See "Master Pages" on page 478 for an explanation of how to fill them and how to apply them to different pages. Using stationery (Media) When the output of a Print context is meant to be printed on paper that already has graphical and text elements on it (called stationery, or preprinted sheets), you can add a copy of this media, in the form of a PDF file, to the Media folder. Media can be applied to pages in a Print section, to make them appear as a background to those pages.
PAGE 461

to be printed out on paper. When a Print template is created (see "Creating a Print template with a Wizard" on page 449 and "Print context" on page 454), only one Print section is added to it, but you can add as many print sections as you need. To add a section to a context: l On the Resources pane, expand the Contexts folder, right-click the Print context , and then click New section. Note that the new section automatically gets the same properties as the first section.
PAGE 462

Tip If you need a whole Print section to be visible in the output only under certain conditions, consider using the Conditional Print Section script wizard; see "Conditional Print sections" on page 790. You can use the Conditional Content script wizard to hide parts of the content of a section; see "Showing content conditionally" on page 787. Importing a Print section To import a section from another template, click File > Import Resources... in the menu. See: "Import Resources dialog" on page 937.
PAGE 463

output in the order in which they appear on the Resources pane, so changing the order of the sections in the Print context changes the order in which they are outputted to the final document. To rearrange sections in a context: l l On the Resources pane, expand the Print context and drag and drop sections to change the order they are in. Alternatively, on the Resources pane, right-click a section in the Print context and click Arrange.
PAGE 464

gives it less weight. In case of conflicting rules, style sheets read later will override previous ones. Note Style sheets are applied in the order in which they are included in a section. The styles in each following style sheet add up to the styles found in previously read style sheets. When style sheets have a conflicting rule for the same element, class or ID, the last style sheet ‘wins’ and overrides the rule found in the previous style sheet. Note Style sheets that are linked to (i.e.
PAGE 465

this option you don't need to make any other settings; click OK to close the dialog. 3. For a PDF resource, you have to specify the path. Clicking the Select Image button opens the Select Image dialog (see "Select Image dialog" on page 989). 4. l Click Resources, Disk or Url, depending on where the image is located. l l l Resources lists the images that are present in the Images folder on the Resources pane.
PAGE 466

generate output, and that their location should be accessible from the machine on which the template's output is produced. External images are updated (retrieved) at the time the output is generated. 5. Select the PDF's position: l Fit to page stretches the PDF to fit the page size. l Centered centers the PDF on the page, vertically and horizontally. l Absolute places the PDF at a specific location on the page.
PAGE 467

Dynamic backgrounds To make the background change based on the value of a data field, you may use the Dynamic Background Script Wizard; see "Dynamic Print section backgrounds" on page 812. Alternatively you could write your own Control Script to set the background; see "Control Script: Setting a Print section's background" on page 887. The settings in a script take precedence over the settings made in the Print Section Properties dialog.
PAGE 468

Note Your printer must support Duplex for this option to work. To enable Duplex or Mixplex printing: 1. On the Resources pane, expand the Print context, right-click the print section and click Sheet configuration. 2. Check Duplex to enable content to be printed on the back of each sheet. 3. When Duplex printing is enabled, further options become available. l Check Omit empty back side for Last or Single sheet to reset a page to Simplex if it has an empty back side.
PAGE 469

Scripts" on page 879 and "Control Script API" on page 1355). This is especially useful when you need identical sections with different settings. The consequences of empty back sides for printing and page numbering In a Duplex job, the last page of a section may be empty since each new section starts on a new sheet. You may wonder what this means for the number of 'print clicks' and for the page numbering. Note that an empty page is defined as a page that has no content and no Master Page.
PAGE 470

The minimum number of pages can be set via the Print section properties; see "Print section properties" on page 983. Although generally the same content elements can be used in all three contexts (see "Content elements" on page 604), the specific characteristics of pages make it possible to use special elements, such as page numbers; see "Page numbers " on page 472.
PAGE 471

Page settings: size, margins and bleed On paper, whether it is real or virtual, content is naturally limited by the page size and margins. These, as well as the bleed, are set per Print section, as follows: l On the Resources pane, right-click a section in the Print context and click Properties. For the page size, click the drop-down to select a page size from a list of common paper sizes. Changing the width or height automatically sets the page size to Custom. Margins define where your text flow will go.
PAGE 472

2. Insert the promotional image or snippet in the content. Note l l Only a top-level element (for example, a paragraph that is not inside a table or div) can function as a whitespace element. Do not place the promotional image or snippet inside an absolute positioned box. Whitespacing only works for elements that are part of the text flow, not for absolute-positioned boxes. 3.
PAGE 473

in the Sheet Configuration dialog, see "Applying a Master Page to a page in a Print section" on page 480) but no contents, is not included in the Content page count. l l l Content page count: This is the total number of pages in the current document that have contents, supplied by the Print section. A page that has a Master Page but no contents, is not included in the Content page count. Sheet number: The current sheet number in the document.
PAGE 474

Configuring page numbers By default the page numbers are Arabic numerals (1, 2, 3, etc.) without leading zeros nor prefix, and page numbering starts with page 1 for each section. But this can be changed. To do that: 1. On the Resources pane, right-click a section in the Print context and click Numbering. 2. Uncheck Restart Numbering if you want the page numbers to get consecutive page numbers, instead of restarting the page numbering with this section.
PAGE 475

Note Widows and orphans are ignored if the page-break-inside property of the paragraph is set to avoid; see "Preventing a page break" on page 477. In the entire Print context To prevent widows and orphans in the entire Print context: 1. On the menu, select Edit > Stylesheets. 2. Select the Print context. 3. Click New (or, when there are already CSS rules for paragraphs, click the selector p and click Edit). 4. Click Format. 5.
PAGE 476

In tables The CSS properties widows and orphans can be used in tables to prevent a number of rows from being separated from the rest of the table. Dynamic Tables are automatically divided over several pages when needed. A Standard Table doesn't flow over multiple pages by default. Splitting a Standard Table over multiple pages requires setting the Connect-specific data-breakable attribute on all of its rows.
PAGE 477

3. In the Breaks group, set the before or after property. l l Before: Sets whether a page break should occur before the element. This is equivalent to the page-break-before property in CSS; see CSS page-break-before property for an explanation of the available options. After: Sets whether a page break should occur after the element. Equivalent to the page-break-after property in CSS; see CSS page-break-after property for an explanation of the available options.
PAGE 478

Master Pages In Print sections, there are often elements that need to be repeated across pages, like headers, footers and logos. In addition, some elements should appear only on specific pages, such as only the first page, or the last page, or only on pages in-between. Examples are a different header on the first page, and a tear-off slip that shows up on the last page. This is what Master Pages are used for. Master Pages can only be used in the Print context (see "Print context" on page 454).
PAGE 479

applied to different pages; see "Applying a Master Page to a page in a Print section" on the facing page. Importing a Master Page To import one or more Master Pages from another template, click File > Import Resources... in the menu. See: "Import Resources dialog" on page 937. Editing a Master Page Master Pages are edited just like sections, in the workspace. To open a Master Page, expand the Master pages folder on the Resources pane, and double-click the Master Page to open it.
PAGE 480

2. Next, define the margins for the header and footer. The margins for a header and footer are set in the Master Page properties. This does not change the content placement within the Master Page itself; in Master Pages, elements can go everywhere on the page. Instead, the header and footer of the Master Page limit the text flow on pages in the Print sections to which this Master Page is applied.
PAGE 481

consequently, check Omit Master Page Back in case of an empty back page to omit the specified Master Page on the last backside of a section if that page is empty. That page will then also be skipped from the page count unless the page numbers continue on the next section (see "Configuring page numbers" on page 474).
PAGE 482

Per Media, a front and back can be specified and you can specify on what kind of paper the output is meant to be printed on. This includes paper weight, quality, coating and finishing; see "Setting Media properties" below. Adding Media To add a Media, right-click the Media folder on the Resources pane and select New Media. The new Media is of course empty. You can specify two PDF files for the Media: one for the front, and, optionally, another for the back.
PAGE 483

2. Now you can change the name and page size of the Media. Note that it isn't possible to change the page size once the Media is applied to a section. Media can only be applied to sections that have the same size. 3. On the Virtual Stationery tab, you can click the Select Image button to select a PDF image file. Note Encrypted PDF files are not supported in PDF pass-through mode. See "PDF Options" on page 1163. l Click Resources, Disk or Url, depending on where the image is located.
PAGE 484

they are used internally. Therefore, URLs that rely on one of these parameters cannot be used. l With an external image, you can check the option Save with template. If this option is checked, the file will be inserted in the Images folder on the Resources pane at the top left. If it isn't saved with the template, the image remains external.
PAGE 485

1. On the Resources pane, expand the Contexts folder, expand the Media folder, and right-click the Media. Click Characteristics. 2. Specify the paper's characteristics: l l l l l l l Media Type: The type of paper, such as Plain, Continuous, Envelope, Labels, Stationery, etc. Weight: The intended weight of the media in grammage (g/m2). Front Coating: The pre-process coating applied to the front surface of the media, such as Glossy, High Gloss, Matte, Satin, etc.
PAGE 486

1. On the Resources pane, expand the Print context; right-click the Print section, and click Sheet configuration. 2. Optionally, check Duplex to enable content to be printed on the back of each sheet. Your printer must support duplex for this option to work. If Duplex is enabled, you can also check Tumble to duplex pages as in a calendar, and Facing pages to have the margins of the section switch alternately, so that pages are printed as if in a magazine or book. 3.
PAGE 487

2. Decide which pages should have dynamically switching media: every first page in the Print section, every last page, one of the pages in between (a 'middle page'), or a single page. (Uncheck the option Same for all positions, to see all page positions.) 3. In the area for the respective sheet position, click the Edit script button next to Media. The Script Wizard appears with a standard script: results.
PAGE 488

Note l l Any Virtual Stationery settings made for the Media also influence how the Media is displayed in each section (see "Setting Media properties" on page 482). Section backgrounds are rotated separately (see "Using a PDF file or other image as background" on page 464). If in the Media properties, the Virtual Stationery position is set to Absolute, any offset given by the Top and Left values will be applied after rotation.
PAGE 489

HTML email that displays properly on a variety of devices and screen sizes is challenging. Building an email is not like building for the web. While web browsers comply with standards (to a significant extent), email clients do not. Different email clients interpret the same HTML and CSS styles in totally different ways.
PAGE 490

Designing an Email template With the Designer you can design Email templates. It is strongly recommended to start creating an Email template with an Email Template Wizard, because it is challenging to design HTML email that looks good on all email clients, devices and screen sizes that customers use when they are reading their email.
PAGE 491

Email templates: Slate and others The most obvious solution offered in the Designer is to use one of the templates provided with the Designer; see "Creating an Email template with a Wizard" on page 493. The layout of these templates has been tested and proven to look good in any email client, on any device and screen size. The Tables in these templates are nested (put inside another table) and they have no visible borders, so readers won't notice them.
PAGE 492

All standard abbreviations can be found in Emmet's documentation: Abbreviations. To learn more about Emmet, please see their website: Emmet.io and the Emmet.io documentation: http://docs.emmet.io/. Preferences To change the way Emmet works in the Designer, select Window > Preferences, and in the Preferences dialog, select Emmet; see "Emmet preferences" on page 830.
PAGE 493

Do not capture your email in one big image Most e-mail clients do not automatically download images, so do not capture your email in one big image. The recipient initially sees a blank message and probably deletes it right away. Do not resize images in your email Many mail clients do not support image resizing and will show the image in its original dimensions. Resize the images before you link to or embed them.
PAGE 494

1. In the Welcome screen that appears after startup: l l Choose Browse Template Wizards. Scroll down until you see the Email Template Wizards. There are three types of Email Template Wizards: l Basic Email templates l Banded Email templates l Slate: Responsive Email templates by Litmus. Or choose Create a New Template and select the Email template. This starts the Basic Action Email wizard. Alternatively, on the File menu, click New, and: l l Select Email Template.
PAGE 495

called "email-to". After loading dataor a data mapping configuration, you can change the script so that it uses the actual field in your data that holds the customer's email address. See "Email header settings" on page 503 l A style sheet, named context_htmlemail_styles.css, and another style sheet depending on which Template Wizard was used. The style sheets can be found in the Stylesheets folder on the Resources pane.
PAGE 496

Slate: Responsive Email Templates by Litmus Scroll past the Web Template Wizards to see the Slate: Responsive Email templates, created by Litmus (see https://litmus.com/resources/free-responsive-email-templates). More than 50% of emails are opened on mobile. These five responsive HTML email templates are optimized for small screens and they look great in any inbox. They’ve been tested in Litmus and are completely bulletproof.
PAGE 497

l l l The text for the header. The header is the colored part at the top. The text can be edited later. The color of the header and the color of the button. Click the small colored square, right next to the field that holds the default color value, to open the Color dialog and pick a color (see "Color Picker" on page 926). The color can be changed later; see "Colors" on page 752. The web address where the recipient of the email will be taken after clicking the button in the email.
PAGE 498

The Wizard opens the Email section, so that you can fill it with text and other elements; see "Content elements" on page 604 and "Email templates" on the next page. Sending email When the template is ready, you can generate Email output; See "Generating Email output" on page 1443. To test a template, you can send a test email first. This allows you to override the recipient address.
PAGE 499

Compressing PDF attachments For PDF attachments, generated from the Print context, you can set the Print Context Image Compression to determine the quality of the files, and with that, the size of the files. To set the Print Context Image Compression: 1. On the Resources pane, expand the Contexts folder; then right-click the Email context and select PDF Attachments. Alternatively, select Context > PDF Attachments on the main menu. This option is only available when editing an Email section in the Workspace.
PAGE 500

it is advisable to position elements using Tables and to put text in table cells (see "Designing an Email template" on page 490). Email templates are personalized just like any other template; see "Variable Data" on page 777. The subject, recipients (To, CC and BCC), sender and reply-to address are specified with Email Script Wizards; see "Email header settings" on page 503. An Email context can contain multiple templates.
PAGE 501

Importing an Email template To import an Email section from another template, click File > Import Resources... in the menu. See: "Import Resources dialog" on page 937. Remember also to add or import any related source files, such as images. Note that when the imported Email section replaces an Email section in your template, the PDF attachments settings are imported as well. (See: "Compressing PDF attachments" on page 499.
PAGE 502

Tip Before you can style an element, you have to select it. In an Email context it can be difficult to select an element by clicking on it. Use the breadcrumbs at the top and the Outline pane at the left, to select an element. See "Selecting an element" on page 608. In order for a style sheet to be applied to a specific section, it needs to be included in that section. There are two ways to do this. Drag & drop a style sheet 1. Click and hold the mouse button on the style sheet on the Resources pane. 2.
PAGE 503

Note Style sheets that are linked to (i.e. included in) a section show a chain icon in the Resources pane (see "Resources pane" on page 1034). Setting a default Email template for output An Email context can contain multiple templates. When generating output from the Email context, however, only one of the Email templates can be merged with each record.
PAGE 504

Email Fields The subject, the recipients (To, Cc and Bcc), the sender and the Reply to address can be entered in the Email Fields at the top of the workspace. If the fields are not visible, click the words 'Email Fields' (or the small plus before them) to expand the Email Fields area. To use a variable email address in any of the fields, simply drag and drop a data field into the email field. The specified subject and addresses will be visible when viewing the email in the workspace in Preview mode.
PAGE 505

Other header fields At some point you may need to define a header field that isn't available in the Preferences or in the Email Fields. This can be done in a Control Script. For a few examples of such scripts, see "Adding custom ESP handling instructions" on page 1450. To get started with Control Scripts, refer to "Control Scripts" on page 879. Email SMTP settings Simple Mail Transfer Protocol (SMTP) is the standard protocol for sending emails across the Internet.
PAGE 506

be maintained in the new version. In the Send Test Email dialog and Send Email dialog (see "Send (Test) Email" on page 986) you will be able to choose one of the presets and adjust the settings to your needs. Subject To specify a subject for an email template: 1. Open the email section and expand the Email Fields by clicking Email Fields at the top of the section. 2. Type the subject in the Subject field.
PAGE 507

Writing a custom Subject script The default script replaces all @field@ placeholders in the subject line with field values. This script can be modified, for example to create a subject that depends on the value of a data field. Open the Script Wizard (see "The Email Script Wizard" on page 504), click the Expand button and modify the script. If you don't know how to write a script, see "Writing your own scripts" on page 843 first.
PAGE 508

This name and email address will appear as the default in the Send Email and Send Test Email dialogs (see "Send (Test) Email" on page 986). The default can be overwritten by typing an email address directly in the From field (as long as no script is present for this field). Using the Script Wizard you can create a dynamic From address; see "The Email Script Wizard" on page 504. It is also possible to drag and drop one data field into the From field directly.
PAGE 509

Meta information Meta information in an email header is not visible to the receiver, but might have an effect on the representation of the email in the e-mail client. The information may also be used by an Email Service Provider (see "Using an ESP with PlanetPress Connect" on page 1448). To add custom meta information to an email header: 1. Right-click the email section on the Resources pane and select Properties.... 2.
PAGE 510

Password types PDF allows for two types of passwords to be set on a secured PDF file: a user password and owner password. The user password allows a limited access to the file (e.g. printing or copying text from the PDF is not allowed). The owner password allows normal access to the file. The Email PDF password script sets both the user and owner password to the same value, so that when the recipient provides the password, he can manipulate the file without limitations.
PAGE 511

Compression options for PDF attachments can be specified in the Email Context Properties dialog; see "Compressing PDF attachments" on page 499. When adding the Web context to an email, only the default Web section is generated and added to the email as an HTML file that is named after the email subject.
PAGE 512

Dynamic attachments: creating file names based on data fields The new Dynamic Attachment wizard lets you concatenate this value with the base location and/or file extension to construct the path. Dynamic Attachment scripts are created via the New option on the toolbar of the Scripts panel. The Dynamic Attachment Script Wizard lets you add a different attachment for each email recipient. It composes one file name (including the path) based on the value of one or more data fields. 1.
PAGE 513

Note For attachment names, it is recommended to use only US-ASCII characters. Other characters may not be supported by all email servers and clients. Note Certain characters are invalid in a URL (for example, '$', '%', and '&') and must be percent-encoded. The same applies to a file path, since that actually is a URL that starts with the file protocol. Note that even a space character is invalid in a URL.
PAGE 514

Dynamic attachment scripts add a element to the of an Email section. The title attribute of that element specifies the attachment name that will show up in the email. Take a look at the last line of the script: results.append(query("").attr("title", result.split('/').pop()).attr("href", result)); To give the attachment another name, you have to replace the bold part of the code by that new name. For example: results.append(query("").attr("title", "Invoice.
PAGE 515

or COTG Web Template Wizard, the Foundation framework is added to the template, to guarantee just that; see "Creating a Web template with a Wizard" below and "Capture OnTheGo template wizards" on page 553. Tip You can use the Responsive Design View drop-down at the top of the workspace to see how your web page looks and behaves with different screen sizes.
PAGE 516

and function well on multiple devices including desktop and laptop computers, tablets, and mobile phones. Foundation is tested across many browsers and devices, and works back as far as IE9 and Android 2. See http://foundation.zurb.com/learn/about.html. For more information about the use of Foundation in the Designer, see "Using Foundation" on page 557.
PAGE 517

l l l l Set width to Grid: Check this option to limit the width of the top bar contents to the Foundation Grid, instead of using the full width of the page. Stick to the top of the browser window: Check to lock the top menu bar to the top of the page, even if the page has scroll bars. This means the menu bar will always be visible in the browser.
PAGE 518

The Wizard opens the Web section, so that you can fill it with text and other elements; see "Content elements" on page 604, "Web Context" on the next page and "Web pages" on page 521. Web pages can be personalized just like any other type of template; see "Variable Data" on page 777 and "Personalizing content" on page 762. Tip Use the Outline pane at the left to see which elements are present in the template and to select an element.
PAGE 519

important text and its "call to action" button invites a visitor to click on to more information or an order form. Contact Us The Contact Us template is a contact form that can be used on a website to receive user feedback or requests. It's great to use in conjunction with the Thank You template, which can recap the form information and thank the user for feedback. Thank You The Thank You template displays a thank you message with some text and media links.
PAGE 520

l A style sheet, named context_web_styles.css, is added to the template. If a Template Wizard was used to create the template, Foundation style sheets are added as well. Style sheets are located in the folder Stylesheets on the Resources pane. These style sheets are meant to be used for styles that are only applied to elements in the Web context; see "Styling and formatting" on page 718.
PAGE 521

Web pages Web pages (also called Web sections) are part of the Web context (see "Web Context" on page 519) in a template. The Web context outputs one HTML web page. In addition to the HTML text it contains either the resources or references to the resources necessary to display it. JavaScript files are added to the in the generated HTML file. JavaScript toolboxes like jQuery and its plugins, or MooTools, are useful when you want to implement special features in the web page.
PAGE 522

Tip For an example of how to serve different web pages using snippets, see the following how-to: Creating a multi-page Web template. If you would like to start with a template that is identical to the one you already have, consider copying it (see "Copying a section" on page 443). To add a blank section to the Web context: l On the Resources pane, expand the Contexts folder, right-click the Web folder, and then click New Web page.
PAGE 523

Filling a Web page Many of the content elements that are available for all three contexts are particularly suitable for web pages; see "Content elements" on page 604. Do not use Positioned Boxes and Tables to position elements, however; use Inline Boxes instead. Forms and Form elements are only available in a Web context; see "Forms" on page 688 and "Form Elements" on page 694. Using variable data on a Web page Web templates are personalized just like any other template; see "Variable Data" on page 777.
PAGE 524

1. Click and hold the mouse button on the style sheet on the Resources pane. 2. Move the mouse cursor within the Resources pane to the section to which the style sheet should be applied. 3. Release the mouse button. Using the Includes dialog 1. On the Resources pane, right-click the section, then click Includes. 2. From the File types dropdown, select Stylesheets. 3. Choose which CSS files should be applied to this section. The available files are listed at the left.
PAGE 525

Setting a default Web page for output When generating output from the Web context, only one of the Web templates can be merged with each record. To select the Web section that will be output by default: l On the Resources pane, expand the Web context, right-click a section and click Set as Default. Tip Use a Control Script to dynamically select a Web section for output depending on the value of a data field. See "Control Scripts" on page 879.
PAGE 526

1. On the Resources pane, expand the Web context, right-click the section and click Properties. 2. Enter the Page Title. The contents of this field will go in the HTML tag. (Name is the name of the section in the Web context; this has no effect on output.) 3. Add a Shortcut Icon by entering the path to the favicon.ico file, for instance images/favicon.ico. Tip If a valid favicon image is dragged to the Web section, it will automatically be set as a shortcut icon. 4.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-527.html">PAGE 527</a></h6> <p>Example The following script adds a <base> element to the head of a web page. results.append("<base href='https://www.w3schools.com/images/' target='_blank'>"); Forms Web templates can contain Forms. Capture OnTheGo templates always contain a Form. Tip To create a Capture OnTheGo template, preferably use a Template Wizard (see "Capture OnTheGo template wizards" on page 553).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-528.html">PAGE 528</a></h6> <p>Workflow's default port number; 'action' should be replaced by the HTTP action of that particular HTTP Server Input task).The method of a Capture OnTheGo form should be POST to ensure that it doesn't hit a data limit when submitting the form. The GET method adds the data to the URL, and the length of a URL is limited to 2048 characters. Especially forms containing one or more Camera inputs may produce a voluminous data stream that doesn't fit in the URL.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-529.html">PAGE 529</a></h6> <p>multiple different fields. Add the Fieldset after inserting the Form; see "Adding elements to a Form" on page 532. 9. Double-click each field in the Fields list and change its settings. For an explanation of the settings, see "Adding elements to a Form" on page 532. 10. The order of the elements in the list under Fields determines in which order the elements will be added to the Form. Use the Move Up and Move Down buttons to change the order of the elements in the list. 11.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-530.html">PAGE 530</a></h6> <p>page 681). Changing a Form's properties and validation method Once a Form has been added, you can of course edit its HTML code directly in the Source view of the workspace. Apart from that, there are a number of dialogs to change a Form's properties and validation settings. Changing a Form's properties 1. Select the form (see "Selecting an element" on page 608). 2. On the Attributes pane you can change: l l l l The ID and/or class.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-531.html">PAGE 531</a></h6> <p>requirements per field and a different message for each field to display to the user if the input is not valid. This method ensures a more consistent validation, as it is browser independent. The necessary JQuery files will be added to the JavaScript folder on the Resources pane when this option is chosen. To change a Form's validation method: 1. Right-click on the Form element and choose Validation settings. 2. Choose a validation type (see above). 3.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-532.html">PAGE 532</a></h6> <p>the Form's validation method to jQuery Validation, as described above. When you click OK, the new version of the web-form-validation.js file will be added. Submitting a Form When a form is submitted, by clicking or touching the Submit button, the name and value of form elements are sent to the address that is specified in the Form's action (see "Adding a Form" on page 527 or "Changing a Form's properties" on page 530). If the name attribute is omitted, the data of that input field will not be sent at all.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-533.html">PAGE 533</a></h6> <p>ID's and classes are also useful with regard to variable data (see "Personalizing content" on page 762) and styling (see "Styling templates with CSS files" on page 719). 2. Type a label, or choose No label under Style, to omit the label. (For Label elements there are no other options to be set.) 3. If applicable, choose a style for the label (for the label of a Checkbox, for example, you can't set a style). l l l l Wrap input with label places the input element inside the Label element.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-534.html">PAGE 534</a></h6> <p>l For a Button, you can set the button type: l l Submit: The button will validate the form data and if validation is successful, send the data to the provided URL (the action specified for the Form; see "Changing a Form's properties" on page 691). Reset: The button will reset the form to its original configuration, erasing any information entered and options provided. Note: This cannot be undone! 5.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-535.html">PAGE 535</a></h6> <p>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.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-536.html">PAGE 536</a></h6> <p>Between the second pair of square brackets, define the key to which the value belongs. Consider the following HTML form inputs: <input type="hidden" name="user_account" value="pparker@eu.objectiflune.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-537.html">PAGE 537</a></h6> <p><values count="4"> <user_account>pparker@eu.objectiflune.com</user_account> <name>Peter Parker</name> <company>Objectif Lune</company> <pinElm1> <pin _idx=0> <left>122</left> <top>253</top> <type>dent</type> </pin> <pin _idx=1> <left>361</left> <top>341</top> <type>dent</type> </pin> </pinElm1> </values> This option makes it easier to select all elements on the same level in a data mapping configuration, and to convert the XML to a JSON object.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-538.html">PAGE 538</a></h6> <p>Tip The Capture OnTheGo (COTG) plugin automatically adds a hidden field for every unchecked checkbox on a Form when the Form is submitted. It does this for every Form; the template doesn't have to be a COTG template. (See: "Using the COTG plugin: cotg2.0.0.js" on page 579.) Using JavaScript JavaScript files, libraries and frameworks can be added to a template, primarily for use in Web pages and Capture OnTheGo Forms.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-539.html">PAGE 539</a></h6> <p>1. Add the file: l l l Right-click the JavaScript folder on the Resources pane, and click New JavaScript. Double-click it to open and edit it. Alternatively, drag and drop the JavaScript file from the Windows Explorer to the JavaScript folder on the Resources pane. Or import one or more JavaScript files from another template; see "Import Resources dialog" on page 937. 2. Make some settings for the file: right-click the file on the Resources pane and select Properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-540.html">PAGE 540</a></h6> <p>l l These resources are not served by your server, saving on space, bandwidth and processing. Using a popular CDN takes advantage of caching - a client having visited another website using that same CDN will have the file in cache and not re-download it, making for faster load times for the client. To add a remote JavaScript: 1. Right-click the JavaScript folder on the Resources pane, and click New Remote JavaScript. 2. Enter a name for the file as it appears in the JavaScript resources.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-541.html">PAGE 541</a></h6> <p>Tip After adding the remote file, you may right-click it and select Download Resource. This allows you to maintain a central file, from which you can quickly download a copy to your template without having to copy & paste. Note that a local copy of a remote resource is a snapshot; it is not automatically kept in sync with its remote content. You can download the remote resource again to overwrite the local copy with updated content.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-542.html">PAGE 542</a></h6> <p>Using JavaScript in other contexts Email clients do not support JavaScript. Therefore, Email contexts cannot include JavaScript resources. When a JavaScript file is included in a Print section, the Designer itself acts as the browser. When generating Print output, it runs the JavaScript after generating the main page flow contents and the pagination, but before any Master Pages are added.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-543.html">PAGE 543</a></h6> <p>Capture OnTheGo With the Designer you can create Capture OnTheGo templates. COTG templates are used to generate forms for the Capture OnTheGo mobile application. For more information about the application refer to these websites: Capture OnTheGo and Capture OnTheGo in the Resource Center.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-544.html">PAGE 544</a></h6> <p>Before starting to create a COTG Form, take some time to structure the design process and to get familiar with the principles of form design, as explained in the topic "Designing a COTG Template" on page 549. Reusable forms Capture OnTheGo forms can be single-use or reusable. This doesn't depend on the design (although, of course, this should be reflected in the design). What makes a form reusable is a setting in the Output to Capture OnTheGo plugin in Workflow; see Output to CaptureOnTheGo.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-545.html">PAGE 545</a></h6> <p>"COTG Elements" on page 681. To learn how to use them, see "Using COTG Elements" on page 567. Tip If you have started creating your Capture OnTheGo template using a COTG Template Wizard, you can find ready-made elements in the Snippets folder on the Resources pane. Foundation, the framework added by the COTG template wizards, comes with a series of features that can be very useful in COTG forms; see "Using Foundation" on page 557.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-546.html">PAGE 546</a></h6> <p>Using JavaScript COTG plugin Capture OnTheGo widgets do not function without the COTG plugin: cotg-2.0.0.js. This plugin also makes it possible to add COTG Elements dynamically, set defaults for COTG elements, react to events that occur when a user interacts with a COTG element, etc. For more information see: "Using the COTG plugin: cotg-2.0.0.js" on page 579.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-547.html">PAGE 547</a></h6> <p>Next, you can start building a Workflow configuration that receives and handles the submitted data. The configuration should start with a HTTP Server Input task (see Workflow Help: HTTP Server Input) of which the HTTP action is the one specified in the COTG Form's action. Using COTG data in a template When a user submits a COTG Form, a Workflow configuration may store the information in a database and/or push it into other Workflow processes, for example to send a letter or an email receipt.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-548.html">PAGE 548</a></h6> <p>2. Create a data mapping configuration Use the resulting XML file to create a data mapping configuration (see "Data mapping configurations" on page 195). 1. Choose File > New > Data mapping Wizards > From XML file. 2. Select the XML data file as its source and click Next. 3. Set the XML Elements option to /request/values. This will automatically add an extraction step for the submitted form fields. 4. Click Finish.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-549.html">PAGE 549</a></h6> <p>1. Click the Insert Inline Box icon on the toolbar. The Insert Inline Box dialog appears. 2. Enter an ID for the box (anything will do, as long as it helps you identify the box) and click OK. The box is added to the text flow and can be resized if needed. 3. Switch to the Source tab and replace the content of the box: <p> Div content goes here </p> by this text: <img id="camera" src="" width="100%"> 4. Switch back to the Design tab. You will see a small, empty rectangle inside at the top of the inline box.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-550.html">PAGE 550</a></h6> <p>company actually needs will prove to be well worth your time. Creating specifications up front prevents discussions, reduces rework and therefore saves time. 2. Listing the input fields that are needed, their type, and possible input constraints. Think of how the information should be visually grouped.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-551.html">PAGE 551</a></h6> <p>Tip If the COTG Form replaces a paper form, it can be tempting to stick to the original layout for the sake of recognizability. Don't fall into that trap. In the end, the users - customers and employees will be happier with a user-friendly form that adapts to different screen sizes and looks like it was designed for the web. Most design guidelines for web forms apply to COTG forms as well. Two key concepts are responsive design and usability.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-552.html">PAGE 552</a></h6> <p>Usability Usability defines the ease of use of a form. Is the layout intuitive? Are the form elements easy to tap on a mobile device? A visually consistent design allows the user to follow the flow while filling out the form. Below are some key usability aspects to keep in mind when designing forms. Provide clear labels. Many modern web sites show labels inside the actual form inputs while they are empty. This saves space on the form, but once the user has entered data the label is no longer visible.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-553.html">PAGE 553</a></h6> <p>Forms for offline use Capture OnTheGo forms can be used offline. This is the case even when the form relies on remotely stored source files like JavaScript files and style sheets, provided that the option Use cached Capture OnTheGo resource is checked when adding them to the form. Capture OnTheGo template wizards With the Designer you can create Capture OnTheGo (COTG) templates. COTG templates are used to generate forms for the Capture OnTheGo mobile application.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-554.html">PAGE 554</a></h6> <p>user-friendly as possible. See "Designing a COTG Template" on page 549. Creating a COTG template using a wizard To create a COTG template with a template wizard: 1. l l In the Welcome screen that appears after startup and when you click the Home icon at the top right, choose Browse Template Wizards. Scroll down until you see the Capture OnTheGo Starter Template Wizards. Alternatively, on the File menu, click New, expand the Template folder, and then expand the Capture OnTheGo Starter folder. 2.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-555.html">PAGE 555</a></h6> <p>3. Click Next and make adjustments to the settings. The wizard remembers the settings that were last used for a COTG template. l l l l Create Off-Canvas navigation menu: an Off-Canvas menu is a Foundation component that lets you navigate between level 4 headings (<h4>) in the form. Check this option to add the menu automatically. Submit URL: enter the URL where the form data should be sent. The URL should be a server-side script that can accept COTG Form data.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-556.html">PAGE 556</a></h6> <p>The action of a Capture OnTheGo form should specify the Workflow HTTP Server Input task that receives and handles the submitted data. The action will look like this: http://127.0.0.1:8080/action (8080 is Workflow's default port number; 'action' should be replaced by the HTTP action of that particular HTTP Server Input task). The method of a Capture OnTheGo form should be POST to ensure that it doesn't hit a data limit when submitting the form.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-557.html">PAGE 557</a></h6> <p>Tip Use the Outline pane at the left to see which elements are present in the template and to select an element. Use the Attributes pane at the right to see the current element's ID, class and some other properties. Use the Styles pane next to the Attributes pane to see which styles are applied to the currently selected element. Tip Click the Edges button on the toolbar t emporarily adds a frame to certain elements on the Design tab. These will not .Print or output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-558.html">PAGE 558</a></h6> <p>Capture OnTheGo and Jumbotron template wizards automatically add the Foundation files v. 5.5.1 to the resources of the template. In a future version of PlanetPress Connect, Foundation 6 will be included. If you'd rather start using the newest Foundation files right away, you have two options: l l Download the Foundation files (from http://foundation.zurb.com/sites/download.html/) and add them to the template manually. Use remote Foundation files from a CDN, such as https://cdnjs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-559.html">PAGE 559</a></h6> <p>These classes can be combined, so that depending on the screen size, a Div can take more or less space in a row. Separate the class names with a space. Tip Start with the class for small screens. For example: <div class="small-3 large-6" columns>. Larger devices will inherit those styles (thanks to the mobile-first approach of Foundation's style sheet). Customize for larger screens as necessary.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-560.html">PAGE 560</a></h6> <p>To add Grid rows and columns quickly, you could also use the Grid snippets or Row snippets, found in the Snippets folder on the Resources pane after using a wizard to create a Foundation web page or a Capture OnTheGo template. For more information about Snippets, see "Snippets" on page 714. For more information about template wizards, see "Creating a Web template with a Wizard" on page 515 and "Capture OnTheGo template wizards" on page 553.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-561.html">PAGE 561</a></h6> <p>OnTheGo form elements. For more information about the application refer to these websites: Capture OnTheGo and Capture OnTheGo in the Resource Center. Capture OnTheGo (COTG) elements can only be added within a Form element in a Web context; see "COTG Forms" on page 543. For information about how to add and use COTG Elements, see "Using COTG Elements" on page 567.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-562.html">PAGE 562</a></h6> <p>l l l Take now: Opens the device's default Camera application to take a picture using the device's camera. Capture OnTheGo has no impact on the device's applications, so the features available (quality, orientation, filters) are dependent on the device itself. You can, however, set the format, quality and scaling for images that are submitted by the Camera element, as explained below.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-563.html">PAGE 563</a></h6> <p>and edit the Image properties: l Format: The image format can be PNG or JPG. l Quality: Set the compression in a percentage. l Scale Image: Check this option to enable image scaling. Then set the maximum width and height of images before they are sent to the server. Note that only the smallest of these is applied and the size ratio is always maintained. Time stamp A time stamp can be added to each picture taken.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-564.html">PAGE 564</a></h6> <p>Date and Formatted Date The Date element and the Formatted Date element display the current date on the device when the form is first opened. When the element is touched, a date selector appears so the user can modify this date. The Formatted Date element displays dates in a format that depends on the locale of the device on which the user is viewing the form. A Date Element displays dates in the ISO 8601 format: YYYY-MM-DD. When the form is submitted, the date data is sent as plain text.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-565.html">PAGE 565</a></h6> <p>Geolocation The Geolocation Element adds a button to read the device's current GPS coordinates and save them in a form field. When the button is pressed, the GPS coordinates are requested and saved. When the form is submitted, the Geolocation data is sent in plain text. High accuracy By default, devices attempt to retrieve a position using network-based methods.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-566.html">PAGE 566</a></h6> <p>Repository ID The Repository ID element retrieves the repository ID (read only) from the app based on the currently logged on COTG user. You could put the Repository ID in a hidden input, so that when the form is submitted, the Repository ID is submitted as well. This information can be used on the server side to take specific actions, such as sending properly branded emails. Signature The Signature Element adds a signature box to a COTG form.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-567.html">PAGE 567</a></h6> <p>form is available to many different users, to detect who submitted it. If desired the field can be hidden; it will still be submitted. Using COTG Elements Capture OnTheGo (COTG) elements are Web Form elements that are specially designed to be used in a Capture OnTheGo Form (see "Capture OnTheGo" on page 543). This topic explains how to add these elements to a Capture OnTheGo Form or and how to prepare them so that when the Form is submitted, they provide valid data that can be handled easily.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-568.html">PAGE 568</a></h6> <p>l l Use label as placeholder inserts the given label text in the placeholder attribute of the field. No style omits the label altogether. Note The first two label styles ensure that when the user clicks the label, the input element gets the focus. When you add a Capture OnTheGo (COTG) element to a template that you didn't start with a COTG template wizard, the Designer will automatically add the necessary JavaScript files: the jQuery library and the COTG library: cotg-2.0.0.js.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-569.html">PAGE 569</a></h6> <p>All COTG elements have a role attribute. This attribute is not supposed to be edited: without the correct role attribute, the element won't function. As noted, the name attribute is what identifies the element after submitting the form. Tip Use the Outline pane at the left to see which elements are present in the template and to select an element. Use the Attributes pane at the right to see the current element's ID, class and some other properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-570.html">PAGE 570</a></h6> <p>{"timeout":6000}">. Settings in the HTML override the default settings for that element. They are applied to the widget when the Form is created and cannot be changed afterwards. For a complete list of options see the Capture OnTheGo API: "Capture OnTheGo API" on page 592. Settings for a dynamically added element can be made in code; see "Dynamically adding COTG widgets" on page 582.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-571.html">PAGE 571</a></h6> <p><input type="text" name="pinElm1[pin_1][left]" value="361"> <input type="text" name="pinElm1[pin_1][top]" value="341"> <input type="text" name="pinElm1[pin_1][type]" value="dent"> With the Use PHP arrays option enabled in Workflow, the above HTML results in the following XML: <values count="4"> <user_account>pparker@eu.objectiflune.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-572.html">PAGE 572</a></h6> <p><top>341</top> <type>dent</type> </pin> </pinElm1> </values> This option makes it easier to select all elements on the same level in a data mapping configuration, and to convert the XML to a JSON object. You can try out this feature with the COTG Time Sheet template, as explained in this how-to: Using The PHP Array Option. The COTG Fields Table element (see "Fields Table" on page 685) in that template has an Add button to add rows to a table, and groups data following this approach.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-573.html">PAGE 573</a></h6> <p>Previewing the form On a PC A Capture OnTheGo template can be previewed on a PC in two different ways. Note that Capture OnTheGo form elements will not be functional unless they are sent to a device. l l Within PlanetPress Connect Designer. You can open the Preview tab or the Live tab in the Workspace. This displays the output HTML along with any variable data being added.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-574.html">PAGE 574</a></h6> <p>1. Go to the Capture OnTheGo Repository Login: https://config-us.captureonthego.com/. 2. Login with your Repository ID and Password. 3. Go to the Users page. 4. Add a new user. The user name should be in the form of an email address. Next, make sure that the Capture OnTheGo mobile application is installed and that it is logged on as a known user of the Capture OnTheGo Repository. Now, with your Capture OnTheGo template open in the Connect Designer module, click on the Send COTG Test… button in the toolbar.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-575.html">PAGE 575</a></h6> <p>validation method" on page 692 and "How to make COTG elements required" on page 569). Get Job Data File on Submit It is possible to test a COTG Form in the Designer and get access to an XML file that contains the submitted data, without having a Workflow configuration to handle the data. This option requires that: l l Workflow has been installed on the local machine, and the Workflow HTTP/Soap Service has been started.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-576.html">PAGE 576</a></h6> <p>4. Save the XML file to disk. You can view it, create or update a data mapping configuration for it (see "Data mapping configurations" on page 195), and insert the data in a template, using the data mapping configuration (see "Personalizing content" on page 762). Note Checkboxes and Radio buttons that are unchecked will not be submitted to the job data. This is standard behavior in HTML.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-577.html">PAGE 577</a></h6> <p>Capture On The Go input dummy data values Input Dummy Value Signat ure Receives SVG signature data and the onscreen presentation of that data. Camer a A dummy foto is added, and a (SVG) annotation if that option is set for the widget. Note that the script doesn't look at the PNG/JPG or resolution options, the only option it considers is the annotation option.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-578.html">PAGE 578</a></h6> <p>Input Dummy Value widget Locale widget en-US * Note that the formatted date and time can be different from the values that the COTG app provides. In the COTG app the formatted date comes from the COTG API, and the formatted date and time normally depend on the locale/region settings on the mobile device. The ISO date and time should be the same as when using the COTG app.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-579.html">PAGE 579</a></h6> <p>Get submitted data via Workflow Eventually, when a user submits a Capture OnTheGo Form, the data are received by the Workflow HTTP Server Input task (see Workflow Help: HTTP Server Input) that has the same HTTP action as the one specified in the Form's action (see "COTG Forms" on page 543). The Workflow configuration should then handle the submitted data.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-580.html">PAGE 580</a></h6> <p>Form. If you are new to it, spend a few minutes on learning it - it's that easy. For more information, see: https://jquery.com/. and http://learn.jquery.com/. Adding the plugin When you create a template with a COTG Template Wizard (see "Capture OnTheGo template wizards" on page 553), the Designer automatically adds the jQuery library and the COTG library: cotg-2.0.0.js. This also happens when you add a Capture OnTheGo (COTG) element to a template that you didn't start with a COTG template wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-581.html">PAGE 581</a></h6> <p>Example The following code sets the default timeout and accuracy for Geolocation objects. and the default maximum height and width for Camera widgets. $.fn.cotgGeolocation.defaults.timeout = 6000; // 6 secs $.fn.cotgGeolocation.defaults.enableHighAccuracy = true; $.fn.cotgPhotoWidget.defaults.width = 1024; $.fn.cotgPhotoWidget.defaults.height = 768; $.fn.cotgPhotoWidget.defaults.quality = 60; Reacting to, or triggering, widget events The new COTG plugin introduces custom events for COTG controls.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-582.html">PAGE 582</a></h6> <p>$('#date1').trigger("show-date-picker.cotg", new Date("2018 01")); }); }); Dynamically adding COTG widgets Capture OnTheGo (COTG) widgets can be added to a Form dynamically, via jQuery. For example: a new Camera element could be added when the user clicks an Add button. This topic explains how to implement this. It is assumed that you have a basic understanding of HTML forms, CSS, JavaScript, and jQuery.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-583.html">PAGE 583</a></h6> <p>}); }); Creating the widget Now you can start writing the code that constructs, adds and initializes the widget. This code has to be based on jQuery. Constructing the HTML A widget basically is an HTML element with certain attributes and contents. The HTML structure of a widget can be seen on the Source tab after adding the widget to a Form in the Designer. In code, reconstruct the HTML. Make sure to give the new element an ID.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-584.html">PAGE 584</a></h6> <p>Optionally, while initializing an element, you can make settings for this specific element. These settings get prevalence over the options already specified in the HTML and over the default settings specified in the COTG plugin. The code snippet below initializes a new Camera element (with the ID myCamera) with a number of settings: $('#myCamera').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-585.html">PAGE 585</a></h6> <p>addCameraWidget(cameraID); }); }); function getCameraIndex(){ return $("input.camera-dyn").length; } function addCameraWidget(cameraID, value) { if(typeof value == 'undefined') { value = ''; } var html = '<label>Camera' + '<div id="' + cameraID + '" role="cotg.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-586.html">PAGE 586</a></h6> <p>Adding event listeners In the process of closing and opening a Form two important events are triggered by the COTG library: l l olcotgsavestate. This event is meant for custom scripts to save information when the user closes or submits the Form. It occurs after the state of all static input fields has been saved. olcotgrestorestate. This event allows custom scripts to do something when the Form is reopened. It occurs after all static inputs have been restored.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-587.html">PAGE 587</a></h6> <p>Note You should not register for these events after the document has loaded (e.g. on the $(document).ready() event), because these events might get triggered before the document is ready. Place your code in a separate JavaScript file and make sure to include that file in the Web context or in the Web section that contains the COTG Form (see "Including a JavaScript file in a Web context" on page 541). For this file, the order in which JavaScript files are included in the template doesn't matter.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-588.html">PAGE 588</a></h6> <p>Note When you've used jQuery to register for the events - $(window).on() - you must use event.originalEvent in the event handler functions, for example: $(window).on("olcotgsavestate", function(event) { event.originalEvent.detail.state["mywidget"] = "test"; }); Restoring widgets When a COTG Form is reopened, the app restores all input fields and widgets that were already present in the original Form (i.e. the Form deployed via Workflow or sent as test using the Designer).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-589.html">PAGE 589</a></h6> <p>When a user takes or selects a picture with a Camera widget, the COTG app stores the path to the image that was taken or selected in a hidden input. This is the path to the image on the device that runs the COTG app. On submitting the Form the COTG app replaces this value - the path - with the actual image data. In this example the hidden fields of dynamically added Camera elements have got the .cameradyn class.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-590.html">PAGE 590</a></h6> <p>'<div class="panel" role="control-wrapper" style="position:relative;">' + '<img role="photo" src="">' + '<input role="photo-data" class="camera-dyn" name="' + cameraID + '" type="hidden" value="' + value + '">' + '</div>' + '<button class="small" role="take-button" type="button">Take now</button>' + '<button class="small" role="pick-button" type="button">Library</button>' + '<button class="small" role="clear-button" type="button">Clear</button>' + '</div></label>'; $('#cameras').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-591.html">PAGE 591</a></h6> <p>Note When user of the COTG app clicks or touches the Submit button in a Form, the name and value of form elements are submitted. Normally, the name and value of an unchecked Checkbox or Radio Button would not be submitted, but in Connect, they are. Connect uses the workaround described in the following topic: "Getting the status of unchecked checkboxes and radio buttons" on page 572.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-592.html">PAGE 592</a></h6> <p>The below procedure describes how to use Camera data as the source of an image inside a <div> container. The benefit of this approach is that the image automatically scales to the size of the container. 1. Click the Insert Inline Box icon on the toolbar. The Insert Inline Box dialog appears. 2. Enter an ID for the box (anything will do, as long as it helps you identify the box) and click OK. The box is added to the text flow and can be resized if needed. 3.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-593.html">PAGE 593</a></h6> <p>How to use the COTG plugin is explained in the following topic: "Using the COTG plugin: cotg2.0.0.js" on page 579. To learn how to create widgets in code, see "Dynamically adding COTG widgets" on page 582 and "Saving and restoring custom data and widgets" on page 585. For a list of all COTG elements and their intended use, see "COTG Elements" on page 681. Barcode Scanner cotgBarcode() Initializing a Barcode Scanner element prepares it for user interaction. Example: $('myScanner').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-594.html">PAGE 594</a></h6> <p>Initialize the new Camera element with any settings that you want to be different from the defaults. Example: $('#myCamera').cotgPhotoWidget({quality: 50, height: 1024}); How to change the default settings is explained in another topic: "Changing default settings for widgets" on page 580. Option Description Type Default editimage Allows the user to edit the image after taking or selecting it.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-595.html">PAGE 595</a></h6> <p>Option Description Type Default allowdeskew Allows the user to perform a perspective cropping after taking or selecting a picture. Boolean false addtimestamp Adds a time stamp Boolean false stampFormat The date format. For all possible formats see Cordova documentation. 'L' stands for localized date and time.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-596.html">PAGE 596</a></h6> <p>Event Description clear.cotg Fired after the user has clicked the Clear button. set.cotg Fired after the user has taken or selected a picture. Date and Formatted Date cotgDatePicker() Initializing a Date or Formatted Date element prepares it for user interaction. Example: $('myDatePicker').cotgDatePicker(); Note that the difference between a Date and a Formatted Date is laid down in the HTML structure of the element. Events The Date and Formatted Date elements listen for the following custom events.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-597.html">PAGE 597</a></h6> <p>Events The Device Info element listens for the following event. Event Description clear.cotg Removes the Device Info data. The Device Info element broadcasts the following event. Event Description set.cotg This event is fired during initialization of the element, after setting its info to the current device. Document ID cotgDocumentId() Initializing a new Document ID puts the current Document ID in the hidden input of the element. Example: $('#myDocID').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-598.html">PAGE 598</a></h6> <p>Fields Table The Fields Table element itself is just a table, so it doesn't have to be initialized. However, after dynamically adding it to a Form, you still have to add the correct event handlers to the Add and Delete buttons, as follows (replace myTable by the ID of your table): $("#myTable [role=cotg-add-row-button]").on("click", function(){ $(this).closest('table').cotgAddRow(true); }); $("myTable").on("click", "[role=cotg-delete-row-button]", function (){ $(this).closest('tr').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-599.html">PAGE 599</a></h6> <p>Option Description Type Default maximumAge Accept a cached position if it isn't older than the specified time in milliseconds. Number 3000 timeout The maximum length of time (milliseconds) that is allowed to pass before the position is retrieved. Number 2700 Events The Geolocation element listens for the following events. Event Description clear.cotg Removes the Geolocation data. restorestate.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-600.html">PAGE 600</a></h6> <p>Event Description bind-toimage.cotg Bind an annotation to the picture. clear.cotg Removes any annotations. clearnote.cotg Removes any annotations. When using this element with a Camera element, trigger this event to remove annotations without removing the picture. restorestate.cotg Restores the annotations when the form is reopened in the COTG app, after the app has restored previously entered values of static input fields. savestate.cotg Saves the annotations.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-601.html">PAGE 601</a></h6> <p>Event Description set.cotg This event is fired during initialization of the element, after setting its value to the current locale. Repository ID cotgRepositoryId() Initializing a new Repository ID puts the current Repository ID in the hidden input of this element. The Repository ID is based on the currently logged on COTG user. Example: $('#myRepID').cotgRepositoryId(); Events The Repository ID element listens for the following custom events. Event Description clear.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-602.html">PAGE 602</a></h6> <p>Field Description clear.cotg Removes the signature drawing and data. draw.cotg Draws the signature on the form (e.g. after a set.cotg or restore-state.cotg event). restorestate.cotg Called when the form is reopened in the COTG app, after the app has restored previously entered values of static input fields. savestate.cotg Saves the signature data to the local storage of the COTG app. set.cotg Sets the given signature. The signature should be given as an SVG string, for example: $(“#signature”).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-603.html">PAGE 603</a></h6> <p>Note that the difference between a Time and a Formatted Time is laid down in the HTML structure of the element. Events The Time and Formatted Time elements listen for the following custom events. Event Description set.cotg Stores the given time (specified in a Date object). clear.cotg Removes the set time. show-timepicker.cotg Opens the Time Picker. If no time is provided (specified in a Date object), the current time will be shown.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-604.html">PAGE 604</a></h6> <p>Content elements Once you have created a template, it can be filled with all kinds of elements, from text to barcodes and from tables to fields on a web form. All types of elements are listed on this page. There are several ways to insert elements, see "Inserting an element" on page 607. Each element can have an ID and a class, as well as a number of other properties, depending on the element's type.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-605.html">PAGE 605</a></h6> <p>see "Using the Text Script Wizard" on page 780 and "Styling and formatting" on page 718. l "Hyperlink and mailto link" on page 697 l "Barcode" on page 610 l Web "Forms" on page 688 and Web "Form Elements" on page 694 l l l l "Whitespace elements: using optional space at the end of the last page" on page 471 (Print context only) "Page numbers " on page 472 (Print context only) Article, Section, Header, Footer, Nav and Aside are HTML5 semantic elements; see https://www.w3schools.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-606.html">PAGE 606</a></h6> <p>breadcrumbs show the HTML tag of the clicked element, as well as the HTML tags of other elements to which the clicked element belongs. The clicked element is at the end of the line. To edit the HTML text directly: l In the workspace, toggle to the Source tab. On this tab you can view and edit the content of the template in the form of plain text with HTML tags (note the angle brackets: <>). You may add and edit the text and the HTML tags, classes, ID’s and other attributes.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-607.html">PAGE 607</a></h6> <p>For each type of element, a small selection of attributes is visible on the Attributes pane at the top right. In a multilingual template, the proprietary data-translate attribute marks an element for translation. For more information see "Translating templates" on page 901 and "Tagging elements for translation" on page 903. Changing attributes via script Many attributes can be changed via the user interface. Another way to change attributes is by using a script.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-608.html">PAGE 608</a></h6> <p>4. Use the Location drop-down (if available) to select where to insert the element. l l l l l l At cursor position inserts it where the cursor is located in the template. Before element inserts it before the HTML element in which the cursor is currently located. For example if the cursor is within a paragraph, the insertion point will be before the <p> tag.* After start tag inserts it within the current HTML element, at the beginning, just after the start tag.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-609.html">PAGE 609</a></h6> <p>Tip Click the Edges button on the toolbar t emporarily adds a frame to certain elements on the Design tab. These will not .Print or output. There are two more ways to select an element in the content: l Using the Breadcrumbs at the top of the workspace. Breadcrumbs show the HTML tag of the clicked element, as well as the HTML tags of 'parent elements': elements inside of which the clicked element is located. The clicked element is at the end of the line.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-610.html">PAGE 610</a></h6> <p>Styling and formatting an element Format elements directly Images and other graphical elements can be resized by clicking on them and dragging the resize handles. There are toolbar buttons to color, indent or style text. Other toolbar buttons can left-align, right-align, or rotate graphical elements. The toolbar buttons only represent a selection of the formatting options for each element. There are no toolbar buttons to change an element's margins, or to add a border to it, for example.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-611.html">PAGE 611</a></h6> <p>Adding a Barcode Note When generating Print output, you can add extra barcodes and OMR marks. The reason why you would do this, is that at merge time more information is available about the actual output document. The page count, for example, is not available at design time. To add barcodes and OMR marks on the fly when generating Print output, select File > Print and check the option Add additional content (see "Additional Content" on page 1179) in the Print Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-612.html">PAGE 612</a></h6> <p>l l After element inserts it after the element in which the cursor is currently located. For example if the cursor is within a paragraph, the insertion point will be after the end tag of the paragraph (</p>).* Replace inserts it in place of the currently selected element. (This option is not available when inserting content in a Master Page.) * If the current element is located inside another element, use the Elements drop-down to select which element is used for the insertion location.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-613.html">PAGE 613</a></h6> <p>A barcode is always added with the barcode type's default properties and dimensions, but they can easily be changed; see "Barcode type and properties" below. Changing a barcode Barcode script The barcode script determines which value is fed to the barcode generator. Double-click the script on the Scripts pane to change which field or fields are added to the barcode value.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-614.html">PAGE 614</a></h6> <p>l Code 11, see "Code 11, Code 93, Industrial 2 of 5, Interleaved 2 of 5, Matrix 2 of 5" on page 646 l "Code 39" on page 622 l "Code 39 extended" on page 623 l Code 93, see "Code 11, Code 93, Industrial 2 of 5, Interleaved 2 of 5, Matrix 2 of 5" on page 646 l "Code 93 extended" on page 627 l "Code 128" on page 629 l "Data Matrix" on page 631 l EAN-8, EAN-13, see "UPC-A, UPC-E, EAN-8, EAN-13" on page 663 l "GS1 DataMatrix" on page 635 l "GS1-128" on page 637 l l Industrial 2 of 5, see "C</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-615.html">PAGE 615</a></h6> <p>Australia Post, Japan Post, KIX, USPS IMb Australia Post, Japan Post, KIX and USPS IMb are some of the types of barcodes that can be added to a template; see "Barcode" on page 610. In PlanetPress Connect versions prior to 2019.2 the USPS IMb barcode was called "OneCode". The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-616.html">PAGE 616</a></h6> <p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-617.html">PAGE 617</a></h6> <p>Configuration type Use the drop-down to select the format type used when creating the barcode: only full range format, only compact formats, or any format. Preferred configuration Use the drop-down to select the preferred format for the barcode. Note that the barcode generator may choose a different format if the data cannot be represented by the preferred format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-618.html">PAGE 618</a></h6> <p>Tilde processing Check this option to process tilde characters in the data as special characters. (See the Java4less Barcodes Guide to learn what the tilde character can be used for.) Note that with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-619.html">PAGE 619</a></h6> <p>Barcode properties This topic lists the properties of the Codabar barcode. For the properties of other barcode types, see "Barcode type and properties" on page 613. Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Start Char and Stop Char Use the drop-down to select the start and stop character for the barcode, which defines the encoding mode. Available characters are A, B, C.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-620.html">PAGE 620</a></h6> <p>When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-621.html">PAGE 621</a></h6> <p>Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-622.html">PAGE 622</a></h6> <p>l PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. Code 39 Code 39 is one of the barcode types that can be added to a template. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-623.html">PAGE 623</a></h6> <p>Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated. Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size. The font size is given in points (pt).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-624.html">PAGE 624</a></h6> <p>Barcode properties This topic lists the properties of the Code 39 extended barcode type. For the properties of other barcode types, see "Barcode type and properties" on page 613. Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Inter Character Gap Two adjacent characters are separated by an inter-character gap.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-625.html">PAGE 625</a></h6> <p>Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size. The font size is given in points (pt). Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-626.html">PAGE 626</a></h6> <p>Barcode properties This topic lists the properties of the following barcode types : l Code 11 l Code 93 l Industrial 2 of 5 l Interleaved 2 of 5 l Matrix 2 of 5 For the properties of other barcode types, see "Barcode type and properties" on page 613. Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-627.html">PAGE 627</a></h6> <p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-628.html">PAGE 628</a></h6> <p>Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height. Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-629.html">PAGE 629</a></h6> <p>l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. Code 128 Code 128 is one of the types of barcodes that can be added to a template; see "Barcode" on page 610.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-630.html">PAGE 630</a></h6> <p>Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height. Tilde processing Check this option to process tilde characters in the data as special characters. (See the Java4less Barcodes Guide to learn what the tilde character can be used for.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-631.html">PAGE 631</a></h6> <p>Data Matrix Data Matrix is one of the types of barcodes that can be added to a template; see "Barcode" on page 610. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-632.html">PAGE 632</a></h6> <p>Encoding The data represented in the symbol can be compressed using of the following algorithms. l ASCII is used to encode data that mainly contains ascii characters (0-127) l C40 is used to encode data that mainly contains numbers and uppercase characters. l Text is used to encode data that mainly contains numbers and lowercase l Base256 is used to encode 8 bit values l l Auto Detect automatically detects the data content and encodes using the most appropriate method.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-633.html">PAGE 633</a></h6> <p>When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-634.html">PAGE 634</a></h6> <p>Show guardbars Checking this option adds guardbars to the barcode. Guardbars are bars at the start, in the middle and at the end that help the barcode scanner to scan the barcode correctly. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-635.html">PAGE 635</a></h6> <p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-636.html">PAGE 636</a></h6> <p>Barcode properties This topic lists the properties of the barcode type GS1 DataMatrix. For the properties of other barcode types, see "Barcode type and properties" on page 613. Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Preferred format Use the drop-down to select the size of the Data Matrix.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-637.html">PAGE 637</a></h6> <p>l ~1 = FNC1 character (for GS1 DataMatrix barcodes) l ~2 = Structure Append l ~3 = Reader programming l ~5 = Macro5 l ~6 = Macro6 l ~7 = ECI expressions Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size. The font size is given in points (pt).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-638.html">PAGE 638</a></h6> <p>The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu. Barcode properties This topic lists the properties of the barcode type GS1-128.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-639.html">PAGE 639</a></h6> <p>Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size. The font size is given in points (pt). Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-640.html">PAGE 640</a></h6> <p>Barcode properties This topic lists the properties of the following barcode types : l Code 11 l Code 93 l Industrial 2 of 5 l Interleaved 2 of 5 l Matrix 2 of 5 For the properties of other barcode types, see "Barcode type and properties" on page 613. Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-641.html">PAGE 641</a></h6> <p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-642.html">PAGE 642</a></h6> <p>l Industrial 2 of 5 l Interleaved 2 of 5 l Matrix 2 of 5 For the properties of other barcode types, see "Barcode type and properties" on page 613. Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-643.html">PAGE 643</a></h6> <p>Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-644.html">PAGE 644</a></h6> <p>l Bar width: The width of the bars. l Spacing: The distance between the bars. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l l None: The barcode is rendered based on the module width. Proportional: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-645.html">PAGE 645</a></h6> <p>Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu. Note that barcodes of these types don't process tilde characters (~) in the data as special characters. Barcode properties This topic lists the properties of the barcode types Australia Post, Japan Post, KIX and UPS IMb.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-646.html">PAGE 646</a></h6> <p>Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-647.html">PAGE 647</a></h6> <p>Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-648.html">PAGE 648</a></h6> <p>l PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. MaxiCode MaxiCode is one of the barcode types that can be added to a template; see "Barcode" on page 610. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-649.html">PAGE 649</a></h6> <p>w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. MSI MSI is one of the types of barcodes that can be added to a template; see "Barcode" on page 610. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-650.html">PAGE 650</a></h6> <p>Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated. Checksum Type The Checksum type can be MSI10, MSI11, MSI1010 or MSI1110; see https://en.wikipedia.org/wiki/MSI_Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-651.html">PAGE 651</a></h6> <p>The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu. Barcode properties This topic lists the properties of the barcode type PDF417.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-652.html">PAGE 652</a></h6> <p>Compact Check this option to use Compact PDF417 instead of the PDF417 barcode. This shortened form of the PDF417 barcode is useful where the space for the symbol is restricted. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-653.html">PAGE 653</a></h6> <p>POSTNET POSTNET is one of the barcode types that can be added to a template; see "Barcode" on page 610. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode...</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-654.html">PAGE 654</a></h6> <p>Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size. The font size is given in points (pt). Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-655.html">PAGE 655</a></h6> <p>Barcode properties This topic lists the properties of the QR barcode. For the properties of other barcode types, see "Barcode type and properties" on page 613. Module size Enter the size of the square modules in pixels. Auto configure When this option is checked, the barcode generator overwrites the selected Preferred version (see below) and defines the barcode version based on the supplied data. Preferred version There are 40 sizes of QR codes. Select the preferred version for the QR code.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-656.html">PAGE 656</a></h6> <p>FNC Use the drop-down to either disable FNC or select a FNC option: l l First: This mode indicator identifies symbols encoding data formatted according to the UCC/EAN Application Identifiers Second: This mode indicator identifies symbols formatted in accordance with specific industry or application specifications previously agreed with AIM International. You must then set a value for the Application Indicator property.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-657.html">PAGE 657</a></h6> <p>l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. Barcode Data QR Codes can have many different types of data, which determines how the code will be generated.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-658.html">PAGE 658</a></h6> <p>Preferred version Use the drop-down to select the size of the barcode, in a number of modules. The actual size of the barcode can be 12 mm x 12 mm up to 22.4 mm x 22.4 mm, depending on the preferred version and the module width. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l l None: The barcode is rendered based on the module width.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-659.html">PAGE 659</a></h6> <p>Royal Mail 4-State (CBC) Royal Mail 4-State (CBC) is one of the types of barcodes that can be added to a template; see "Barcode" on page 610. In PlanetPress Connect versions prior to 2019.2 this barcode was called "Royal Mail 4 State (RM4SCC)". The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-660.html">PAGE 660</a></h6> <p>Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated. Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size. The font size is given in points (pt).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-661.html">PAGE 661</a></h6> <p>Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu. Barcode properties This topic lists the properties of the barcode types Royal Mail 4-State Mailmark C and Royal Mail 4-State Mailmark L. For the properties of other barcode types, see "Barcode type and properties" on page 613.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-662.html">PAGE 662</a></h6> <p>When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-663.html">PAGE 663</a></h6> <p>Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l l None: The barcode is rendered based on the module width. Proportional: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching. Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-664.html">PAGE 664</a></h6> <p>Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu. Note that these barcode types process tilde characters in the data as special characters. See the Java4less Barcodes Guide to learn what the tilde character can be used for.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-665.html">PAGE 665</a></h6> <p>Note When the chosen supplement type doesn't match the data, the supplement data will be skipped and the additional barcode will not be rendered. l l Height Factor: This is the relative height of the supplement's bars compared to the normal bars. Space Before : Defines the space between the main symbol and the supplement, in cm.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-666.html">PAGE 666</a></h6> <p>In PlanetPress Connect versions prior to 2019.2 the USPS IMb barcode was called "OneCode". The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 611. Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode...</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-667.html">PAGE 667</a></h6> <p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-668.html">PAGE 668</a></h6> <p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-669.html">PAGE 669</a></h6> <p>Positioned Box A Positioned Box is one that can be freely moved around the page and does not depend on the position of other elements. A positioned box is actually a <div> element that has an absolute position; in other words, it has its CSS property position set to absolute (see also: "Using the CSS position property" on page 738). Positioned Boxes are suitable for use in Print templates only. Adding a Positioned Box To insert a Positioned Box, use the icon on the toolbar.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-670.html">PAGE 670</a></h6> <p>Note Do not set the top or left property of a Positioned Box in a style sheet. The position of a Positioned Box in a Print context is handled via its attributes to take the page (or Master Page) and page margins into account. Attributes cannot be overwritten from within a style sheet: style sheets specify style properties, not values of attributes.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-671.html">PAGE 671</a></h6> <p>l l The Float rightbutton aligns the Inline Box to the right, with the text wrapped around it to the left. The No float button positions the Inline Box where it occurs in the text. It is not possible to move an Inline Box using drag and drop. To move the Inline Box to another position in the text, you have to edit the HTML on the Source tab in the Workspace, moving the <div> element using cut and paste. To open the Source tab, click it (at the bottom of the Workspace) or select View > Source View.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-672.html">PAGE 672</a></h6> <p>the Designer; see "Editing HTML" on page 605. In HTML, boxes are <div> elements. Spans are <span> elements. To learn how to change the attributes of elements, see "Attributes" on page 606. Business graphics Business graphics are a great way to visualize data in your documents. Connect Designer lets you create three types of grapics: Bar Charts, Line Charts and Pie Charts. The charts are generated by the integrated amCharts library (https://www.amcharts.com/javascript-charts/).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-673.html">PAGE 673</a></h6> <p>To insert a business graphic in a template: 1. Place the cursor where the graphic should be added. Also make sure that you have loaded data or a data mapping configuration (see "Loading data" on page 765). 2. Click the toolbar button of the type of chart you want to add, or select Insert > Business graphic and choose the chart type. The wizard opens with a page on which you can specify the attributes and insertion point of the graph. 3. An ID is required.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-674.html">PAGE 674</a></h6> <p>5. Click Next and specify the data for the graph. These settings can also be edited when you open the script, after you've inserted the chart. For an explanation of the options in the wizard, see "Selecting data for a Business Graphic" on the next page. 6. For a Bar Chart or Line Chart, you can click Next and set some basic parameters of the chart: l l l Stack Series: Check to stack the values in one bar, instead of having one bar per value. This is only useful with a chart that is based on a data table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-675.html">PAGE 675</a></h6> <p>To rasterize a business graphic, right-click it and select Rasterize Options. For a JPG image you can set the quality of the resulting image in a percentage. Note A business graphic in an Email section is rasterized by default and output as PNG image, because email clients usually don't support SVG images. SVG images in an Email section give an error in the Preflight window (see "Doing a Preflight" on page 855).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-676.html">PAGE 676</a></h6> <p>2. For a Bar or Line Chart based on a detail table, you also have to select a Category: one data field (in the detail table) of which the values will appear under the bars or the line; in other words, on the x axis. 3. Next to Values, select data fields with a numerical value. Tip The Toggle non-numeric fields button filters non-numeric fields from the list. The list will then display only Integer, Float and Currency data fields. 4.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-677.html">PAGE 677</a></h6> <p>Preparing a data table By default, a chart that is based on a detail table shows one series ("category") of bars/points per record. Each of the bars or points in a series has its own color and label, and represents one data field in that record. The following image shows a detail table. Both of the Bar charts below are based on that detail table. The difference between the Bar charts is caused by the number of selected data fields (one, or two).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-678.html">PAGE 678</a></h6> <p>to modify the detail table in the data mapping configuration in order to make it match the default approach. Otherwise this requires changing the Chart script: open the Chart script, click the Expand button, and alter the code that puts data in the dataProvider property. Note How to create a Pie Chart that has one slice per detail record is explained in a How-to: Put one slice per detail record in a Pie Chart. In Connect versions up to 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-679.html">PAGE 679</a></h6> <p>On the Source tab, all settings are given in JSON. For example: { "type": "pie", "legend": { "enabled": false }, "radius": "100", "innerRadius": "30" } (The innerRadius option, found on the Pie tab in the Pie Chart properties, gives this Pie Chart the shape of a donut.) Note that only properties that were modified via one of the tab menus are included in the JSON on the Source tab. To change the chart, you can simply edit the JSON.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-680.html">PAGE 680</a></h6> <p>For inspiration you could use amCharts' online editor: https://live.amcharts.com/new/. Properties can be copied directly from the Code tab in the live editor to the Source tab of the Chart properties dialog in Connect. Note that copying the entire content of the Code tab will also carry over the sample data from the live editor (the dataProvider key). These will be overwritten by the chart script in Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-681.html">PAGE 681</a></h6> <p>C. On the Background tab, set the Color to: l #282828 for the 'dark' theme and the 'chalk' theme l #222222 for the 'black' theme 3. Finally, the 'chalk' theme requires adding a remote stylesheet with this URL: 'https://fonts.googleapis.com/css?family=Covered+By+Your+Grace' to your template. See "Using a remote style sheet" on page 722. COTG Elements With the Designer you can create Capture OnTheGo templates. COTG templates are used to generate forms for the Capture OnTheGo mobile application.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-682.html">PAGE 682</a></h6> <p>When the form is submitted, the image is sent in a base64-encoded string format. To learn how to add Camera data to a template, see "Adding Camera data to the template" on page 548. The Camera element has a number of options, of which most can be set in the Design view. These options are described below. All options, including options that cannot be set via the Design view, can be set via the Source view or in code; see "Changing default settings for widgets" on page 580.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-683.html">PAGE 683</a></h6> <p>Cropping/editing/deskewing To allow the user to crop, edit and deskew the image after taking or selecting it, select Camera properties, and then check Edit Image and/or Allow Deskew. Which editing options the user actually gets and how they are presented to the user depends on the operating system of the device. On an Android device for example, the user may be able only to crop the image, while the user of an iOS device may select part of the image and rotate that selection.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-684.html">PAGE 684</a></h6> <p>1. Load the data mapping configuration (or at least the data model). 2. Insert a dummy image in the template. 3. Right-click the dummy image and select Dynamic Image. The Text Script Wizard appears. 4. Under Field select the field that contains the base64-encoded string. The script puts the given string in the source (src) attribute of the image (<img>). Instead of using the Text Script Wizard, you could also write a script yourself; see "Writing your own scripts" on page 843.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-685.html">PAGE 685</a></h6> <p>Fields Table The Fields Table element adds a table with two rows, a Delete button at the end of the first row and an Add button at the end of the second row. Inside the rows you can put whatever elements you need. The user can click (or rather, touch) the Add button to add a row to the table. The new row will contain the same elements as the first row. The names of all elements in the first row will be extended with __0, while the names of the elements in the second row will be extended with __1, etc.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-686.html">PAGE 686</a></h6> <p>the Image & Annotation element, followed by "-note-data", for example image_annotation1note-data. Locale The Locale Element does not have a UI element in the form. Inserting it adds a hidden input field that will contain the device's set locale when the form is submitted. This data is sent in plain text format and is available when processing the form data. The format is defined by the device.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-687.html">PAGE 687</a></h6> <p>the locale of the device on which the user is viewing the form. A Time Element displays dates in the ISO 8601 format: HH:MM. When the form is submitted, the time data is sent as plain text. A Formatted Time element submits the time in both the ISO format mentioned above and in the format that depends on the device's regional and language settings. A Time element sends the time in the ISO format only.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-688.html">PAGE 688</a></h6> <p>Changing the date Once inserted, a date can be modified directly in the template (if it does not update automatically) or through the date script (if it does update automatically). To modify the date in the script: 1. Double-click the date script in the Scripts pane. 2. Between the round brackets after Date, enter the desired date in the following order: year, month, day, and optionally hours, minutes, seconds, milliseconds (see https://www.w3schools.com/js/js_dates.asp and https://developer.mozilla.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-689.html">PAGE 689</a></h6> <p>Tip To create a Capture OnTheGo template, preferably use a Template Wizard (see "Capture OnTheGo template wizards" on page 553). The Wizard doesn't just add the form, it also adds the necessary Capture OnTheGo form elements (see "COTG Elements" on page 681), style sheets and JavaScript files, and extra pre-made elements. Adding a Form This procedure describes how to add a Form element to an existing Web context. 1. On the Resources pane, expand the Web context and double-click a Web page to open it. 2.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-690.html">PAGE 690</a></h6> <p>l l l application/x-www-form-urlencoded: Default. All characters are encoded before they are sent. Spaces are converted to "+" symbols, and special characters are converted to ASCII HEX values. multipart/form-data: No characters are encoded. This value is required when you are using forms that have a file upload control. text/plain: Spaces are converted to "+" symbols, but no special characters are encoded. 7.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-691.html">PAGE 691</a></h6> <p>l l l l l l At cursor position inserts it where the cursor is located in the template. Before element inserts it before the HTML element in which the cursor is currently located. For example if the cursor is within a paragraph, the insertion point will be before the <p> tag.* After start tag inserts it within the current HTML element, at the beginning, just after the start tag.* Before end tag inserts it within the current HTML element, at the end, just before the end tag.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-692.html">PAGE 692</a></h6> <p>l l l l The ID and/or class. ID's and classes are particularly useful with regard to variable data (see "Personalizing content" on page 762) and styling (see "Styling templates with CSS files" on page 719). An Action: the URL where the form data should be sent. The URL should be a server-side script that can accept form data (a Workflow process that starts with a Server Input task, for example). A Method: this defines whether the form should be sent using the GET or POST method.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-693.html">PAGE 693</a></h6> <p>l l l l Required: Check if the field is required to submit the form. If a field is required but contains no data, a message will be shown to the user. Minimum length: Enter a numerical value for the minimum character length required for this field. Maximum length: Enter a numerical value for the minimum character length accepted for this field. Equal to: Use the drop-down to select another field that is already added to the same Form. The contents of both fields must match for the data to be validated.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-694.html">PAGE 694</a></h6> <p>Form Elements This topic lists the elements that can be added to a form in a Web page or in a Capture OnTheGo template and explains how to add them to a Form, set a default value or change their validation. For more information about Forms and Form elements in the Designer, see "Forms" on page 688 and "Using Form elements" on page 532. For more information about elements in Forms, see https://www.w3schools.com/html/html_ forms.asp. Fieldset A fieldset is a group of related elements in a form.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-695.html">PAGE 695</a></h6> <p>Date The Date element is a text field accepting only dates in a valid format. Text area The Text area element is a text field accepting multiple paragraphs. You can set a number of rows when adding the Text Area to the Form, and change it on the Attributes pane. Hidden field A hidden field can contain specific data used by the server-side script. It is not visible to the user. When adding a Hidden Field you can set the value that will be sent on submit.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-696.html">PAGE 696</a></h6> <p>The option to add a Radio Button Group is only available in the Form Wizard; see "Forms" on page 688. For an explanation of the options in the Radio Button Group dialog, see "Adding elements to a Form" on page 532. You could also create a Radio Button Group by specifying the same submit name for a number of Radio Buttons when adding them to a Form. Radio Button A radio button sends information to the server whether it is selected (true) or not (false).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-697.html">PAGE 697</a></h6> <p>A reset button will reset the form to its original configuration, erasing any information entered and options provided. Note: This cannot be undone! The button's type can also be changed on the Attributes pane. l There may be multiple submit buttons on a Form. If this is the case, specify a different name and/or value for each of the buttons. Note: When adding a Button to a Form, you can specify a value, but no name. The Button's ID will be copied to the element's name attribute.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-698.html">PAGE 698</a></h6> <p>Adding a hyperlink or mailto link 1. Select text or an image. Note Although it is possible, it is not advisable to add a Hyperlink to other elements, such as a Paragraph or Div. HTML 4 specifies that hyperlinks and mailto-links may only contain inline elements. Block elements, such as a Div, may not appear inside a link. HTML 5 states that the link "may be wrapped around entire paragraphs, lists, tables, and so forth, even entire sections, so long as there is no interactive content within (e.g.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-699.html">PAGE 699</a></h6> <p>For a mailto link: l l l Email: enter a valid email address that appears by default in the To: field of the email client. Subject: type a default subject that appears in the Subject: field of the email client. Message: type a message that appears by default in the Message field of the email client. Note that all these can be changed within the email client once the link is clicked. Tip To quickly change the text of a hyperlink, position the cursor on the link and click ~contents in the Breadcrumbs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-700.html">PAGE 700</a></h6> <p>l EPS l GIF l JPG/JPEG l PCL l PDF l PNG l PS l SVG l TIF/TIFF Base64 encoded images are supported; however, they are added differently: set the src attribute of an <img> element to the base64 code (see below, "Images" on the previous page). For Email and Web output, PNG is the preferred image format. EPS, PDF, SVG and TIFF images in an Email or Web section are automatically converted to PNG to ensure that they can be seen in the browser or email client.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-701.html">PAGE 701</a></h6> <p>Background images Several parts of templates, such as sections and media, and elements such as positioned boxes, can have a background image. Right-click the element and click the Background tab to select an image to be used as the element's background image. See "Background color and/or image" on page 748 and "Using a PDF file or other image as background" on page 464.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-702.html">PAGE 702</a></h6> <p>Adding images This section explains the difference between imported and external images and describes a number of ways to add images to a template. Note The Connect image cache size is limited to 100MB. This allows most output jobs to run faster. However, if a job requires more than 100MBs of image files, then the Connect image cache size can be increased to cater for such. Please contact OL Support for instructions on how to modify the image memory cache value, if needed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-703.html">PAGE 703</a></h6> <p>extension, you have to add the filetype parameter to the URL manually. Specify the file extension as its value, for example: ?filetype=pdf, or &filetype=pdf if it isn't the first parameter. Note that the ampersand character needs to be encoded as &. For information about referring to images in HTML or in a script, see "Resources" on page 438. Via drag-and-drop The drag-and-drop method is a quick way to import one or more images into a template. 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-704.html">PAGE 704</a></h6> <p>in file:///<path>, for example: file:///c:/resources/images/image.jpg. l Url lists image files from a specific web address. Select the protocol (http or https), and then enter a web address (for example, http://www.mysite.com/images/image.jpg).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-705.html">PAGE 705</a></h6> <p>Importing images from another template To import images directly from another template, click File > Import Resources... in the menu. See: "Import Resources dialog" on page 937. Using one file that contains a collection of images (a 'sprite') When a template that contains lots of images is merged with a large record set, the many file requests may slow down the process of output generation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-706.html">PAGE 706</a></h6> <p>Images can be styled using the same dialog, or through the CSS files; see "Styling templates with CSS files" on page 719. A number of issues related to image styling are discussed in a separate topic: "Styling an image" on page 745. Just like many other elements, images can be given borders and rounded corners, they can have inner and outer margins and they can be rotated. How to do this is described in general formatting topics, such as "Border" on page 749 and "Spacing" on page 761.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-707.html">PAGE 707</a></h6> <p>Note When CSS repeating gradients are displayed in a PDF reader, artifacts, like very thin lines may occur. When this happens, try setting the gradient's position a little bit different. Table Tables serve two different purposes: they are a way to display data in a tabular format, and they are also a way to position elements on a page. In HTML email, Tables are the most reliable way to position text and images; see "Designing an Email template" on page 490.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-708.html">PAGE 708</a></h6> <p>Inserting a Table 1. On the toolbar, click the Insert Table button, or on the menu select Insert > Table > Standard. 2. Enter the Table's desired attributes: l l ID: a unique identifier for the Table. IDs are used to access the Table from scripts and as CSS selectors for style rules. Class: A class identifier for the Table. Classes can be shared between elements and are used to access the Table from scripts and as CSS selectors for style rules.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-709.html">PAGE 709</a></h6> <p>when you insert a Div into a paragraph, the paragraph gets split in two. This means you end up with two paragraphs with the Div in between. Note l l Tables with an absolute position are only useful in Print sections. Tables on a Master Page have to have an absolute position, unless they are located inside another element with an absolute position. 4. Click Next and select the desired table style. The top left actually applies no styling to the table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-710.html">PAGE 710</a></h6> <p>Rows and columns Adding a row or column To add a row or column to an existing Table, click in a cell. Then click the black triangle next to the Insert Row Above button on the toolbar, and click one of the Insert buttons, or select one of the options in the Insert > Table Elements menu. Alternatively, right-click the Table and on the shortcut menu, select Row > Insert Above or Insert Below, or select Column > Insert Before or Insert After.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-711.html">PAGE 711</a></h6> <p>Resizing and moving a Table Resizing a Table l l l Select the Table (see "Selecting an element" on page 608) and type the desired width and height under Geometry on the Attributes pane. Select the Table and select Format > Table, on the menu. On the Table tab, change the width and height of the Table. Click in the Table and drag the handles to resize it. Press the Shift key while dragging to scale the Table proportionally.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-712.html">PAGE 712</a></h6> <p>Hiding the border When using a Table to position other elements, you will want to hide the borders of the Table. To do this, set the width of the border to 0; see "Border" on page 749. Text and special characters The vast majority of templates for personalized customer communications contain, of course, text. While the most common text element is a <p> or paragraph, other elements such as Headings (<h1> through <h6>) are also considered text elements.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-713.html">PAGE 713</a></h6> <p>This how-to describes another way to maintain extra spaces in the text: Maintain extra spaces in text. Adding special characters To add special characters: 1. Position the cursor where the character should be inserted. 2. On the Insert menu, point to Special Characters click Symbols, Dashes and Spaces, Arrows, or Geometric Shapes, and click one of the available special characters. Adding page numbers Page numbers can only be used in the Print context. See "Page numbers " on page 472.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-714.html">PAGE 714</a></h6> <p>Translating text OL Connect templates can be multilingual. For information about multilingual templates and how to create them, see "Translating templates" on page 901. Snippets A snippet is a small, ready-to-use piece of content in a file. Snippets can be re-used within the same template, in all contexts and sections. They can contain any contents that a section can have, such as text, images, variable data, dynamic tables, etc. Normally, a snippet is an HTML file, but it can also be a JSON file.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-715.html">PAGE 715</a></h6> <p>Adding a snippet to the Resources Before adding a snippet: l l Import the resource files that are related to the snippet, such as image files and CSS files, into the template file. Drag and drop the files to the corresponding folders (Images and Stylesheets, respectively) on the Resources pane. If you want to use external images, see "Images" on page 699.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-716.html">PAGE 716</a></h6> <p>Adding a snippet to a section Drag-and-drop To add the snippet to the content of a section, drag the snippet from the Snippets folder on the Resources pane to the desired location in a section. Check the option Insert as shared content to insert a reference to the original snippet in the template, rather than a copy of the original snippet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-717.html">PAGE 717</a></h6> <p>The option to modify shared content snippets from within a section can be turned off: l l In the menu, select View > Shared Content Editing to enable or disable editing of all shared content. To enable or disable editing on a case by case basis, you can also manually set the contenteditable attribute on the Article element of the shared content to true or false. This overrides the menu setting. Note Remote snippets inserted as shared content cannot be changed from within the Designer.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-718.html">PAGE 718</a></h6> <p>Styling and formatting In the Designer you have everything at hand to make your templates look good: colors, fonts and all the tools to position, align and embellish elements in your designs. This topic informs about the ways to style a template. Local formatting versus style sheets There are in general two ways to style elements: l l Using local formatting. Local formatting means styling an element directly, using a toolbar button or one of the formatting dialogs. Using Cascading Style Sheets (CSS).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-719.html">PAGE 719</a></h6> <p>Text and paragraphs have a number of formatting options that are not available for other elements: font styles and line height, for example. See "Styling text and paragraphs" on page 731. Boxes and a number of other elements can have a background color and/or background image; see "Background color and/or image" on page 748. Several elements, such as boxes, images, paragraphs, and tables, can have a border; see "Border" on page 749.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-720.html">PAGE 720</a></h6> <p>template itself, you can define a layout for all paragraphs, and for all output channels, in a CSS file. The benefit of this is that you can quickly and easily change the look and feel of all contexts in one template, without having to change the contents. In the event that your company chooses to use another font or to adjust its corporate colors, you only have to change the style sheets.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-721.html">PAGE 721</a></h6> <p>l l l One style sheet that applies to all document types: context_all_styles.css. One or more style sheets specific to the context (Print, Email, Web). For example, when you create an action email using the Wizard, the files context_htmlemail_styles.ccs and basic_email_action.css are automatically added to the Stylesheets folder on the Resources pane. A style sheet that defines default styles for tables: default.css.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-722.html">PAGE 722</a></h6> <p>Tip l l To export a CSS file from your template, drag or copy/paste it out of the Stylesheets folder to a folder on the local hard drive. It is possible to open and edit any CSS file in the Designer: select File > Open, select All files (*.*) as the file type and then select a CSS file. Using a remote style sheet A remote style sheet is not located within your template but is located in a network folder or hosted on an external web server (generally called a CDN).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-723.html">PAGE 723</a></h6> <p>Tip After adding the remote file, you may right-click it and select Download Resource. This allows you to maintain a central file, from which you can quickly download a copy to your template without having to copy & paste. Note that a local copy of a remote resource is a snapshot; it is not automatically kept in sync with its remote content. You can download the remote resource again to overwrite the local copy with updated content.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-724.html">PAGE 724</a></h6> <p>Styling your templates with CSS files Note Email clients do not read CSS files and some even remove a <style> tag when it is present in the email's header. Nevertheless, CSS files can be used with the Email context in the Designer. When generating output from the Email context, all CSS rules that apply to the content of the email can be processed and added either to the header of the email or to inline style properties as if local formatting was applied, depending on the Email section properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-725.html">PAGE 725</a></h6> <p>Note Do not give an element the ID 'pages' or the class name 'dynamic'. These are reserved words. Using them as an ID or class name leads to undesirable effects. l l l l An HTML element: p, h1, table, etc. Type the tag name without the angle brackets. A combination of HTML elements, separated by a comma. The CSS rule will apply to all HTML elements that are listed in the selector. For instance, a CSS rule with the selector h1, p applies to first level headings as well as paragraphs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-726.html">PAGE 726</a></h6> <p>Tip Right-click and choose Format, or press Ctrl + Shift + F to "pretty-print" the CSS and make it easier to read and edit. Note Block comments (/* ... */) are allowed in CSS, but single-line comments (// ...) are not standard and might not work as expected in all browsers. In the Designer, syntax highlighting doesn't work on single-line comments in CSS files.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-727.html">PAGE 727</a></h6> <p>Adding a class or ID to an HTML element 1. Select the element (see "Selecting an element" on page 608). 2. On the Attributes pane, type the ID and/or class. Type the ID without the preceding # and class names without a dot. Note Note: Elements can have multiple classes. Separate the class names with a space (eg. “red small”). Alternatively, after selecting an element, you can click the Source tab at the bottom of the workspace. The selected element will be highlighted in the source.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-728.html">PAGE 728</a></h6> <p>gives it less weight. In case of conflicting rules, style sheets read later will override previous ones. Note Style sheets are applied in the order in which they are included in a section. The styles in each following style sheet add up to the styles found in previously read style sheets. When style sheets have a conflicting rule for the same element, class or ID, the last style sheet ‘wins’ and overrides the rule found in the previous style sheet. Note Style sheets that are linked to (i.e.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-729.html">PAGE 729</a></h6> <p>A crossed-out style rule signals that it was overruled by another style rule. This happens when: l l A more specific, and therefore more important rule, is encountered for the same element. See "Using a more specific CSS rule" below to learn more about the specificity of style rules. A rule with the same importance is read after the first rule. Not only is the order of the rules in a CSS file important, but also the order in which the style sheets are read.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-730.html">PAGE 730</a></h6> <p>Rules for HTML elements (p, table, li etc.) are general rules. Rules for classes, pseudo classes, and elements with a certain attribute (.class, :hover, [target]) are more specific. Rules for elements with a certain ID are even more specific. The most specific are inline styles.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-731.html">PAGE 731</a></h6> <p>1. Right-click the Stylesheet folder on the Resources pane, and click New Stylesheet > SCSS file. 2. Enter a name for the file as it appears in the Stylesheet resources. When the name of Sass file begins with an underscore, it is considered a partial .scss file (e.g. _mySass.scss). Partial files are typically imported in a base .scss file. They may include Sass variables or other directives declared in the base file, and they cannot be compiled.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-732.html">PAGE 732</a></h6> <p>This topic explains how to apply local formatting to text. It is recommended though, to format text using style sheets; see "Styling and formatting" on page 718 and "Styling templates with CSS files" on page 719. Tip With the Copy fit feature, text can automatically be scaled to the available space in a Box or Div. See "Copy Fit" on page 735.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-733.html">PAGE 733</a></h6> <p>the Color field directly. It must be a predefined CSS color name (CSS color names), a hexadecimal color code (HTML Hex Color), an RGB color value, for example rgb (216,255,170) or a CMYK color value, for example cmyk(15%, 0%, 33%, 0%). This setting is equivalent to the color property in CSS.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-734.html">PAGE 734</a></h6> <p>Note All settings in the Text Formatting dialog are in fact CSS style rules. When you change one or more settings, the selected text gets wrapped in a Span element that has an inline style tag containing the selected setting(s). Click the Advanced button to add CSS properties and values to the inline style tag of the Span directly. For more information about CSS, see "Styling and formatting" on page 718.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-735.html">PAGE 735</a></h6> <p>Tip When you select an element in the template, the Styles pane will show which styles are applied to that element. The link behind the style will take you to the place (the Source tab, or a CSS file) where that style is defined. Copy Fit Copy Fit is a feature to automatically scale text to the available space: the name of a person on a greeting card for example, or the name of a product on a shelf talker. This feature is only available with Box and Div elements in Print sections.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-736.html">PAGE 736</a></h6> <p>Tip To give an element a class or ID, select it and add the class or ID on the Attributes pane. An ID is meant to be used once in each section, while a class can be shared between several elements. 7. Click Apply or OK. Note that the effect of the Copy Fit feature can only be seen in Preview mode. If it is impossible to make a text fit within the box with the given minimum and maximum font size, this will be reported as an error during a preflight (see "Testing scripts" on page 853).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-737.html">PAGE 737</a></h6> <p>In the Web context, Inline Boxes are the preferred way to position elements; see "Boxes" on page 668. Tables should only be used to display data in a tabular format, not to position text and images. Tables used in web pages to position elements (and often, Positioned Boxes) make those pages less accessible to users with disabilities and to viewers using smaller devices.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-738.html">PAGE 738</a></h6> <p>Guides Guides are horizontal and vertical lines used to help in designing templates, for example when positioning absolute positions boxes over a PDF background. They can only be used in Print sections. l Select View > Guides > Show guides to show or hide the guides and margins. To add a guide, press the Insert Horizontal Guide or Insert Vertical Guide buttons on the Toolbar. To move a guide, click and drag it to a new location.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-739.html">PAGE 739</a></h6> <p>For an explanation of all values that the position property can possibly have, see https://www.w3schools.com/css/css_positioning.asp. Where to use it In Print sections, setting the position property to absolute can be very useful. It takes the element out of the text flow, so that the element stays where it is on the page. On Master Pages (which are only used in Print sections) elements are always positioned absolutely; if not, they must be located inside an element that has an absolute position.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-740.html">PAGE 740</a></h6> <p>Rotating elements In any type of template, boxes, images, tables, text and other elements can be rotated. The toolbar buttons Rotate Clockwise and Rotate Counter Clockwise rotate the element in which the cursor is located 90 degrees at a time. To rotate an element into another angle position, use the 'angle' CSS property of the element. In most cases, this can be done in the element's Formatting dialog. In other cases, such as with text, you have to enter the CSS property and value manually.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-741.html">PAGE 741</a></h6> <p>l l With local formatting. This means styling the table directly, using the Formatting dialog. Via Cascading Style Sheets (CSS). In a style sheet, style rules are declared for elements with different HTML tags, ID's and classes. These two methods are described below. See "Styling and formatting" on page 718 for background information about these two methods. Selecting a table, row or cell There are several ways to select a table or row: l l l Click in the table or row.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-742.html">PAGE 742</a></h6> <p>l Click in a cell and choose Format > Table or Format > Table Cell. l Right-click it and choose Cell... or Table... from the shortcut menu. Note that in this case Table styles the table as a whole. When you choose Table and change the border, for example, the borders of the cells inside it will not be changed. To style all cells in a table or row at the same time via the Formatting dialog, you have to select the table or row first; see "Selecting a table, row or cell" on the previous page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-743.html">PAGE 743</a></h6> <p>rule to be more specific you need to add an ID (for a unique element) or a class (for a set of similar elements) to the table, row or cell, and use that as the style rule's selector. Adding an ID or class to a table, row or cell Before you can add an ID or class to a table, row or cell, you have to select that table, row or cell (see "Selecting a table, row or cell" on page 741). After selecting the cell, row or table, type the ID or class in the respective field on the Attributes pane.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-744.html">PAGE 744</a></h6> <p>Selecting a specific row, odd or even rows, or every nth row The pseudo-class :nth-child() lets you select a specific row, all odd or even rows, or every nth row. Between the round brackets in :nth-child() you can fill in a number, odd or even, or a formula: an+b. In the formula, a represents a cycle size (every...), n is a counter (for the child elements), and b is an offset value ('start at b'). The following examples will make this clear. :nth-child(3) matches just one element: the third child element.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-745.html">PAGE 745</a></h6> <p>Styling an image Just like many other elements, images can be given borders and rounded corners, and they can be rotated. How to do this isn't any different from the way it is done with other elements, so it isn't described in this topic, but in general formatting topics; see "Styling and formatting" on page 718. This topic discusses specific image formatting issues. Note that image characteristics like brightness and contrast can not be changed within the Designer. Local formatting vs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-746.html">PAGE 746</a></h6> <p>Resizing an image There are several ways to resize an image after inserting it in the content of a template. l l l l Click the image and drag the handles to resize it. Press the Shift key while dragging, to scale the image proportionally. Select the image (see "Selecting an element" on page 608) and type the desired width and height in the respective fields on the Attributes pane. Select the image and select Format > Image, on the menu. On the Image tab, change the width and height of the image.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-747.html">PAGE 747</a></h6> <p>To position an image using the menu, select the image and then select one of the options in Format > Float. Alternatively, open the Formatting dialog (see "Applying local formatting to an image" on page 745): select the image; on the menu, select Format > Image and on the Image tab, under Text Wrap, set the Float property. The float property could also be changed via a style sheet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-748.html">PAGE 748</a></h6> <p>element, but generally elements should not be positioned absolutely. Designs for the Web should be flexible so that they display nicely on a variety of devices and screen sizes. Background color and/or image In any type of template, boxes, tables and table cells can have a background color and/or a background image. To select a background image or color: 1. Right-click the box and click Box on the shortcut menu. 2.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-749.html">PAGE 749</a></h6> <p>l l Disk lists image files that reside in a folder on a hard drive that is accessible from your computer. Click the Browse button to select a folder (or an image in a folder). As an alternative it is possible to enter the path manually. The complete syntax is: file://<host>/<path>. Note: if the host is "localhost", it can be omitted, resulting in file:///<path>, for example: file:///c:/resources/images/image.jpg. Url lists image files from a specific web address.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-750.html">PAGE 750</a></h6> <p>Elements have a rectangular shape, so their border has four sides. Each side of the border can have a different layout. Adding a border 1. Right-click the element and click the respective element on the shortcut menu. Alternatively, select the element (see "Selecting an element" on page 608) and on the Format menu click the respective element. 2. Click the Border tab. 3. Uncheck the option Same for all sides to be able to style each side of the border separately. 4. Specify the width of the border (side).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-751.html">PAGE 751</a></h6> <p>1. Select a Box, Image or Table element (see "Selecting an element" on page 608) and on the Format menu click the respective element. Alternatively, right-click the element and click the respective element on the shortcut menu. 2. On the first tab in the Formatting dialog (the Box, Image or Table tab respectively) specify the corner radius in a measure (10mm, 5px, 0.5in) or percentage (0 - 90%). 3. For a Box or Image, click Apply to see the effect without closing the dialog or OK to close the dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-752.html">PAGE 752</a></h6> <p>3. Under Property, type border-radius. 4. Under Value, type the value of the corner radius in a measure (10mm, 5px, 0.5in) or percentage (0 - 90%). 5. Click OK, and click OK again to close the Formatting dialog. Using a CSS file Of course you could also add this rule to a CSS file; see "Styling templates with CSS files" on page 719. The following rule sets the border-radius of the corners of all paragraphs to 5 pixels: p { border-radius: 5px; }.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-753.html">PAGE 753</a></h6> <p>l l Click the New button (the green plus). Select an existing color from the list and copy it using the Duplicate button . (The Filter drop-down limits the list to colors of a certain type.) Select the new color and click the Edit button . 3. In the Edit color dialog, type a name for the color (or let the Designer create a name based on the values that you select). The color’s name can be used in style sheets. It should not contain spaces or special characters.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-754.html">PAGE 754</a></h6> <p>process of printing one color on top of other colors. This is sometimes required, for example to deal with special print applications, such as applying UV ink or varnish to a certain area, or to avoid mis-registration when printing black on top of colored areas. Note Black overprint can be enabled for text smaller than a given size; see "Overprint and black overprint" on page 458. Defining a tint A tint is a transparent color, based on another color in the template. To define a tint: 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-755.html">PAGE 755</a></h6> <p>time and again, when the company's layout preferences change. See "Styling templates with CSS files" on page 719. In style sheets, you can color every type of element that has a CSS color property, such as color, background-color or border-color.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-756.html">PAGE 756</a></h6> <p>1. Select an HTML element (see "Selecting an element" on page 608). 2. On the Format menu, click the element. For a div element, click Box. The Formatting dialog opens up. 3. Click the Border or Background tab. 4. Click the downward pointing arrow next to Color to select a color from the list of predefined colors (see "Defining colors, spot colors and tints" on page 752). Alternatively, click the small rectangle to the right of the color list to open the Color Picker dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-757.html">PAGE 757</a></h6> <p>to importing them into the template) is not recommended. If output is produced on the server whilst running under a different account, that account might not have access to the font. If you do add a font to a server, select the option "Install for all users", and do not forget to restart the machine, as otherwise the font might not be available, due to the way certain Windows versions handle fonts.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-758.html">PAGE 758</a></h6> <p>Note Font software may have specific restrictions for copying and redistribution. Please consult the license agreement for each font vendor before using it in a template. It is your responsibility to comply with the requirements of third-party agreements. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-759.html">PAGE 759</a></h6> <p>slower) and results in bigger files. Finally, because of the plain machine transformation of the font, the result will probably not look as good as when using a carefully designed, properly styled, font. It is much better, if you have separate files for the bold, italic and any other versions of a font, to use those. Font types The Designer currently supports 5 font types: TTF, OTF, WOFF, EOT and SVG.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-760.html">PAGE 760</a></h6> <p>section (see "Applying a style sheet to a section" on page 727) or, when editing a Snippet, in the section that was active when the Snippet was opened. Note Support for remote fonts in email clients cannot be relied upon, and not all remote fonts are supported by all browsers. It is therefore recommended to add fallback fonts to the specific style rules whenever using remote fonts in a Web or Email section (see "Applying a font" on page 757).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-761.html">PAGE 761</a></h6> <p>l l Select Explicit Locale to specify a static locale which will remain static for this template, whichever server the template is used on. Use the Locale drop-down to select a specific locale. The locales comprise a language code followed by a 2letter country code (de-DE, zh-CN, fr-CA, fr-FR, etc), as defined by the international standards ISO-639-1 and ISO 3166. Select Data Field to use a data field from the record. The locale will be recordspecific in this case.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-762.html">PAGE 762</a></h6> <p>2. Click the Spacing tab. Note All settings in the Formatting dialog are in fact CSS style rules. Click the Advanced button to manually add CSS properties (at the left) and values (at the right). For more information about CSS, see "Styling and formatting" on page 718. It is also possible to change an element's formatting via a style sheet; see "Styling templates with CSS files" on page 719. 3. Set the value for the padding in measure or percentage.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-763.html">PAGE 763</a></h6> <p>Variable data Variable data are data from a database or data file that are used to personalize documents. Data fields can be inserted in the text directly. For example, if a person's last name can be found in your data, the field that holds the last name can be used in the text of a web page,letter, invoice or email. Scripts in PlanetPress Connect Designer are the basis of Variable Data Publishing and are used to personalize documents based on your data.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-764.html">PAGE 764</a></h6> <p>To swap a Print section's background dynamically, you can use the Dynamic Background Script Wizard; see "Dynamic Print section backgrounds" on page 812. Dynamic tables A Dynamic Table is a table with a variable number of rows that can overflow on one or more pages. It can also display subtotals on transport lines. In invoices, a Dynamic Table is an essential element. Read "Dynamic Table" on page 793 to learn how to insert a dynamic table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-765.html">PAGE 765</a></h6> <p>Post Pagination Scripts Post Pagination Scripts are run in a Print context after the content has been paginated. Because they can search through the output of all Print sections, and modify Print sections (one at a time), they may be used to create a Table Of Contents (TOC), as explained in the topic: "Creating a Table Of Contents" on page 896. See "Post Pagination Scripts" on page 894.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-766.html">PAGE 766</a></h6> <p>Designing a template without sample data Strictly speaking, you don't need sample data to design a template; the only thing you really need in order to add variable data fields to a template is a Data Model. You can open a Data Model without data by importing a Data Model file, a JSON file or a Connect template file from within the Data Model pane, using the top-right icon: . The file's data model structure will be displayed in the Data Model pane, but the data is not included.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-767.html">PAGE 767</a></h6> <p>Tip If you have no data at hand, download a demo from http://demo.objectiflune.com and open a dummy data file to test with. Loading a data mapping configuration If you already have an open data mapping configuration, its Data Model and sample data will automatically be used when you start creating a template. You might have to click the Synchronize Model button on the Data Model pane, to update the fields. To open a data mapping configuration: 1. Open the Welcome screen: click the Home Welcome on the menu.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-768.html">PAGE 768</a></h6> <p>DataMapper). Adding data from a data file 1. Click File, select Add Data and then click From file data source. Browse to the location of the file and select it. The Designer can open the following types of data files: l Tabular files: CSV files (.csv, .txt) and Excel files (.xls, .xlsx) Note Excel files saved in "Strict Open XML" format are not supported yet. l Microsoft Access Database (.mdb, .accddb) l XML files (.XML) l PDF/VT files 2.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-769.html">PAGE 769</a></h6> <p>l l l l Comment delimiter: If there are comment lines in the file, type the character that starts a comment line. Text Delimiter: Type the character that surrounds text fields in the file. Other delimiters will not be interpreted within these text delimiters. Ignore unparsable lines: When checked, any line that does not correspond to the above settings will be ignored. First row contains field names: Check this option to use the first line of the CSV as headers.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-770.html">PAGE 770</a></h6> <p>PDF/VT file options After selecting a file, use the drop-down to select what level in the PDF/VT file defines a record in your data. The names of the levels are taken from the PDF/VT file itself. (See "About PDF/VT files" below.) All metadata fields that belong to the chosen level and levels higher up in the tree structure will be listed. The lower the chosen level is in the tree structure, the more records you will get and the more metadata fields will appear in the list.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-771.html">PAGE 771</a></h6> <p>Adding data from a database 1. Click File, select Add Data and then click From database data source. Browse to the location of the file and select it. The Designer can open databases from the following types of data sources: l MySQL l Microsoft Access Database (.mdb, .accddb) l SQL Server l ODBC DataSource l JDBC l Oracle. 2. Review the options presented. The options available depend on the type of database data source; see below. MySQL 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-772.html">PAGE 772</a></h6> <p>descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text. 3. Click Finish to open the database. Microsoft Access 1. Enter the appropriate information to connect to the database: l File name: Browse to your Microsoft Access database file (.mdb) l Password: Enter a password if one is required. 2. Click Next and enter the information for the source table. l l l Connection string: Displays the full path to the database.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-773.html">PAGE 773</a></h6> <p>2. Click Next and enter the information for the source table. l l l Connection string: Displays the full path to the database. Table: Use the drop-down to select the appropriate table or stored query to retrieve the appropriate data set. Encoding: Use the drop-down to select the encoding with which to read the data in the table. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-774.html">PAGE 774</a></h6> <p>l Server: Enter the server address for the database server. l Port: Enter the port to communicate with the server. l l l l l Database name: Enter the exact name of the database from where the data should be extracted. User name: Enter a username that has access to the server and specified database. The user only requires Read access to the database. Password: Enter the password that matches the username above.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-775.html">PAGE 775</a></h6> <p>2. Click Next and enter the information for the source table. l l l Connection string: Displays the full path to the database. Table: Use the drop-down to select the appropriate table or stored query to retrieve the appropriate data set. Encoding: Use the drop-down to select the encoding with which to read the data in the table. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-776.html">PAGE 776</a></h6> <p>2. Either browse to the location of the file and select it, or paste or write the JSON directly in the box below the file name. You can add the following types of JSON data: l A JSON object or an array of JSON objects representing records. The data type is derived from the data: l Any value surrounded with quotes is converted to a field of type String. l Any numeric value containing a period is converted to a field of type Float.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-777.html">PAGE 777</a></h6> <p>1. To open the Generate Counter Wizard, select File > Add data > Generate counters. 2. Adjust the settings: l l l l l l l Starting value: The starting number for the counter. Defaults to 1. Increment value: The value by which to increment the counter for each record. For example, an increment value of 3 and starting value of 1 would give the counter values of 1, 4, 7, 10, [...] Number of records: The total number of counter records to generate.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-778.html">PAGE 778</a></h6> <p>After loading - or creating - a Data Model (see "Data Model pane" on page 1027), a data mapping configuration, or data from a data file or database (see "Loading data" on page 765), you can add variable data fields to the contents of your template. You can do this via the dragand-drop method, or using the Text Script Wizard. Use the Text Script Wizard when there are empty fields in the data, and the value of a data field needs to be preceded or followed by a space, line break or text in the template.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-779.html">PAGE 779</a></h6> <p>A text script replaces placeholders in the content with the value of a data field in the current record. Switch to the Preview tab at the bottom of the workspace to see the script in operation. The value of the corresponding data field in the first record appears instead of the placeholder, everywhere where the placeholder is found in the text. This value will be refreshed when you browse through the records in the Data Model pane. When the output (the letter, email, etc.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-780.html">PAGE 780</a></h6> <p>Tip Drag the data field directly to the Scripts pane to create a script without adding a placeholder to the template. Note Looking for text in a text is a less optimized operation and may impact output speeds in longer documents. To speed up the output process, put the placeholder(s) in a Box or Span (see "Boxes" on page 668), give that Box or Span an ID and use that ID as the script's selector. See "Using the Text Script Wizard" below for an explanation about the various types of selectors.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-781.html">PAGE 781</a></h6> <p>3. The selector states the text to be found in the template. The results can be replaced by the script. Tip Hover over the name of a script in the Scripts pane to highlight parts of the template that are affected by the script. l Text, for example: @lastname@, or {sender}. The text doesn't have to have any special characters, but special characters do make it easier to recognize the text for yourself. In the Text Script Wizard, click Text and type the text to find.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-782.html">PAGE 782</a></h6> <p>Note Each ID should be unique. An ID can be used once in each section. n l Etcetera. See https://www.w3schools.com/cssref/css_selectors.asp for more selectors and combinations of selectors. A selector and text. This is text inside an HTML element (or several HTML elements) with a specific HTML tag, class or ID. In the Text Script Wizard, click Selector and text and type the selector and the text in the respective fields. 4. Click the the downward pointing arrow in the first row in the column Field.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-783.html">PAGE 783</a></h6> <p>l As the value of an attribute of an HTML element. The selector of the script should be an HTML element. Which attributes are available depends on the selected HTML element. If the script's selector is an image (<img> element) for example, and the attribute is src, the script will modify the image's source. The script's results should be a valid value for the chosen attribute.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-784.html">PAGE 784</a></h6> <p>Formatting variable data When a Text Script, made with the Text Script Wizard (see "Using the Text Script Wizard" on page 780) adds variable data to a template, it can easily change the way the data are formatted as well. This is done in the Text Script Wizard through a special formatting modifier or a format mask for each field that the script adds to the template. The available formatting functions depend on the data type of the corresponding field in the Data Model.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-785.html">PAGE 785</a></h6> <p>3. Under Format you can choose one of the following options: l Custom Pattern opens a dialog in which you can enter a custom pattern the date (and, optionally, the time). The dialog shows an example of a date formatted according to the given pattern. Do not put the pattern in quotes. For possible patterns see "Date and time patterns" on page 1262.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-786.html">PAGE 786</a></h6> <p>4. Close the Script Wizard. For a new script, don’t forget to add the selector to the template. Font style Text originating from variable data can be displayed in uppercase, lowercase or proper case. 1. Open the Text Script Wizard: double-click to open an existing script in the Scripts pane or create a new Text Script using the Text Script Wizard; see "Using the Text Script Wizard" on page 780. 2.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-787.html">PAGE 787</a></h6> <p>l l l l l l Standard: displays the number with the default pattern and symbols for the current Locale. Grouped displays a number with three decimal places and sets the thousands separator for the value based on the current locale; see "Locale" on page 760. Currency displays a number as an amount of money, with a thousands separator and rounded to two decimal places, based on the current locale; see "Locale" on page 760. Currency no symbol does the same as Currency, but omits the currency symbol.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-788.html">PAGE 788</a></h6> <p>2. Rename the script so that it reflects what the script does. Note Scripts can only have the same name when they are not in the same folder. 3. Type a Selector. The selector selects one or more pieces of text or elements from the template, so that the conditional content script can hide or show those pieces. An ID (for example: #conditional-script) is best if you want to show or hide one element only. Use a class selector (for example: .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-789.html">PAGE 789</a></h6> <p>Note If you need more complex conditions, click Expand and edit the code of the script. See "Writing your own scripts" on page 843. 9. Click Apply or OK. 10. To see the result, toggle to the Preview tab at the bottom of the workspace (or select View > Preview View on the menu). Showing or hiding several elements with one conditional script To apply one conditional content script to several elements, you have to use a CSS class or HTML element as the selector of the script.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-790.html">PAGE 790</a></h6> <p>3. Type an ID and/or a class. An ID is fine if this is the only thing that should be shown or hidden on a given condition. Use a class if there is more that should be shown or hidden on the same condition. 4. Start creating a conditional content script from the Scripts pane. Use the ID or class as the selector of the script. See "Showing or hiding elements using the Conditional Content Script wizard" on page 787.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-791.html">PAGE 791</a></h6> <p>Ontario the section will be printed if the Province field reads Québec OR Ontario. Note More complex conditions can be written in the Script Editor: click Expand and edit the code of the script. See "Control Scripts" on page 879. 8. Click Apply or OK. 9. To see the result, toggle to the Preview tab at the bottom of the workspace (or select View > Preview View on the menu).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-792.html">PAGE 792</a></h6> <p>1. Add one image to the template. See "Adding images" on page 702. 2. Right-click the image and click Dynamic Image. Or select the image and click Source (not the field, but the label before the field) in the Attributes pane. The Dynamic Image Script Wizard opens. The image's ID is used as the script's selector. If the image did not have an ID, it is automatically generated. 3. Select the location of the files: l l l Select Resources if the images reside in the Images folder on the Resources pane.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-793.html">PAGE 793</a></h6> <p>this how-to: Dynamic signatures. How to insert dynamic images if there are no data fields with the actual names of the images is described in another how-to: Dynamic image that doesn't contain the data field value. Note An image with an unknown file extension is represented by a red cross in the output, but no error is logged unless the image refers to a local file that does not exist on disk.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-794.html">PAGE 794</a></h6> <p>Creating a Dynamic Table To create a Dynamic Table: 1. Open the Insert Dynamic Table dialog. There are several ways to do that: l Drag the data field that contains the name of the detail table into the template. l On the menu select Insert > Table > Dynamic. l On the toolbar, click the Insert dynamic table button. 2. Enter the table's desired attributes: l l l ID: A unique identifier for the table. IDs are used to access the table from scripts and as CSS selectors for style rules.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-795.html">PAGE 795</a></h6> <p>every element in the breadcrumbs, from the current selection point down to the root of the body. Note: HTML has some restrictions as to which types of elements are allowed as children of other elements. For example, a paragraph element is not allowed to have children that are block level elements - like a Div or a Table. If inserting content at the selected location would produce invalid HTML the final result may be different than expected.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-796.html">PAGE 796</a></h6> <p>page 718.) l Use CSS utility classes: The cells get a class for which the default style sheet for Dynamic Tables (default_table_styles.css) has a style rule. For more information see "Utility classes for text in a Dynamic Table" on page 805. A row is associated with a (nested) detail table. The row will be repeated in the output (or in Preview mode) as many times as necessary to display all the records in the associated detail table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-797.html">PAGE 797</a></h6> <p>in its sub-table. Tip A text like "continued on next page" or "continued from previous page" can be added after the table has been created. See "Mixing text and data in one cell" on page 802. l Activate the Header Row button to display a row with the names of the current row's data fields before each row in the output. The header row is not visible in the Wizard, but is inserted in the body of the table (the <tbody> element) when the Wizard is closed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-798.html">PAGE 798</a></h6> <p>in any nested detail tables. However, it is also possible to add subtotals after the table has been inserted into the template, even for fields in nested detail tables. See "Adding subtotals" on page 800. l l Show subtotal lines before page break: Check this option to display the subtotal in the footer of the table on each page (including at the end of the table).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-799.html">PAGE 799</a></h6> <p>To personalize the content or style of cells, based on the value of a data field, you'll need a script. See "Using scripts in Dynamic Tables" on page 876. Adding a row to the header or footer of a Dynamic Table A Dynamic Table that is created by the Wizard always has a header (a <thead> element). It will also have a footer (a <tfoot> element) if you chose to add Subtotals.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-800.html">PAGE 800</a></h6> <p>You can fill the new header or footer rows as usual. You could for example drag a root level data field to the row (see "Variable Data" on page 777) or type in the cells. See also: "Mixing text and data in one cell" on page 802. You could also add a subtotal (see below). Adding subtotals When creating a Dynamic Table with the Wizard, you can add subtotals based on one data field to the table's footer and header. It is also possible to add (extra) subtotals to an existing Dynamic Table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-801.html">PAGE 801</a></h6> <p>except the last. l l After page break (header rows only): The row will appear on all pages except the first. At end of table: The row will only appear on the last page. 5. Now, add the subtotal to a cell in that row. This procedure is the same for subtotals in the header and footer. a. Select the cell (see "Selecting an element" on page 608). b. Select the data field: l l On the "Attributes pane" on page 1024, from the Sum drop-down, select the data field on which the subtotal must be based.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-802.html">PAGE 802</a></h6> <p>1. Select the row (see "Selecting an element" on page 608). 2. Change the row's Repeat attribute on the Attribute pane from None to the desired detail table. Usually this will be the detail table that is one level higher than the one that contains the field for which the subtotal must be calculated. 3. Proceed with step 5 in "Adding a row to the header or footer of a Dynamic Table" on page 799.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-803.html">PAGE 803</a></h6> <p>Formatting values in a Dynamic Table Values in Dynamic Table cells can be formatted in different ways. A date value, for example, could be displayed as "Apr 2, 2016" (short date) or "4/2/16 12:00 AM" (medium date/time). Which formats are possible depends on the data type of the field that the cell is associated to (see "Data types" on page 276) For an explanation of the possible formats see "Formatting variable data" on page 784.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-804.html">PAGE 804</a></h6> <p>l l Switch to Source view. Add the data-keep-when-empty attribute to the respective <tr> element(s). For example: <tr data-repeat="Instruments" data-keep-when-empty="">. Tip To locate a row you can select it on the "Outline pane" on page 1033. Styling a Dynamic Table The Insert Dynamic Table wizard lets you select a style for the table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-805.html">PAGE 805</a></h6> <p>l When generating output from a template, a Dynamic Table is created slightly faster when it's styled via Cascading Style Sheets than when it's styled with local formatting. Here are a few tips on how to target rows and cells in a Dynamic Table. l l l There are CSS selectors with which you can target every so-maniest row (see "Styling the first, last and nth rows" on page 743). In the output, Dynamic Table rows are repeated including any classes that are set on the row and on its contents.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-806.html">PAGE 806</a></h6> <p>Resizing a Dynamic Table To change the width of a Dynamic Table or of a column in a Dynamic Table, select it (see "Selecting an element" on page 608) and type the desired width as a percentage in the respective field on the "Attributes pane" on page 1024. It is also possible to resize colums via drag-and-drop (in Design mode only). To allow for this, select the table and check the option Allow Resizing on the Attributes pane.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-807.html">PAGE 807</a></h6> <p>For a list of all data- attributes that can be used in a Dynamic Table, see "A Dynamic Table's data- attributes" below. A Dynamic Table's data- attributes In HTML, a Dynamic Table is a normal <table> element with rows and cells (see "HTML element: table" on page 707). But apart from the native attributes of a table, rows and cells, it has some proprietary data- attributes which make it dynamic.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-808.html">PAGE 808</a></h6> <p>than 2020.1, this attribute's value is the name of a detail table in the data. dataexpander= "2019" <table> Specifies that the table should be expanded using the expander that was introduced in OL Connect version 2020.1. Most of the data- attributes listed here require the Dynamic Table to have the dataexpander="2019" attribute. Tables made with an OL Connect version older than 2020.1 don't have this attribute.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-809.html">PAGE 809</a></h6> <p>Script Wizard. For a detailed description see: "Formatting variable data" on page 784. l Integer, Float, Currency: l grouped l number-ungrouped l currency l currency-nosymbol l l pattern('some pattern') (see "Number patterns" on page 1274) String: l uppercase l lowercase l propercase. Note that it is not possible to set a format on an HTMLString value.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-810.html">PAGE 810</a></h6> <p>page 803. data-keepwhen-empty <tr> (a table row) Hide the row if it is empty. A row is considered empty if all elements with a data-field attribute in that row refer to empty data fields. Note that any additional text is not taken into account. See: "Hiding an empty table row" on page 803. data-repeat= "name of detail table" <tr> (a table row) in the body of the table (<tbody>) A row with this attribute is repeated for each record in the detail table that is specified in the attribute's value.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-811.html">PAGE 811</a></h6> <p>data-show-row <tr> (a table row) When set on a row in the body of the table (<tbody>), this attribute causes a row (a line with data) to appear before and/or after a page break if a sub-table runs over multiple pages. This is particularly useful in tables with several levels and long nested tables. Initially this attribute is omitted. A row without this attribute will be displayed once per record in a detail table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-812.html">PAGE 812</a></h6> <p>required by the pagination routines of Connect to split the table across pages. Differences in Dynamic Tables made with previous Connect versions In Dynamic Tables made with Connect before version 2020.1: l l l l l There is no data-expander attribute on the <table> element. The data-detail attribute on the <table> element specifies the name of the detail table. (In tables made with Connect 2020.1 and up, this attribute has no value.) The data-show-row attribute can only have the value: all.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-813.html">PAGE 813</a></h6> <p>Otherwise, adding a dynamic background requires a self-made script (for help on this, see "Control Script: Setting a Print section's background" on page 887). To use the Dynamic Section Background Script Wizard: 1. Open the Wizard. There are three ways to do that: l l l Right-click the Print section on the Resources pane and click Dynamic Background. On the Scripts pane, click the arrow next to the New button and select Dynamic Background Script. Double-click the script to open it.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-814.html">PAGE 814</a></h6> <p>5. Click Apply or OK. The script assigns the resulting file name, including the path and file extension, to the URL of the section's background. 6. Now click the Preview tab and browse through the records to verify that the script works as expected. Tip If you want to see the underlying script, reopen the script and click the Expand button. For more information on this type of script, see "Control Script: Setting a Print section's background" on page 887).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-815.html">PAGE 815</a></h6> <p>the HTTP Server Input task that starts the process. For example, if its action is MakePDF, you could trigger the process by adding /MakePDF to the address of the Workflow server. The rest of this Workflow process depends on what the pURL is used for. If it should output a personalized landing page, for example, it would be a web process with some OL Connect tasks (see "Web processes with OL Connect tasks" on page 186).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-816.html">PAGE 816</a></h6> <p>4. With the span selected, click on 'ID' on the Attributes pane (click on the field name, not the field itself). This will insert a script that has this ID as selector, and open it in the script editor. Since it's dynamic, inserting a personalized URL always implies writing a script, however small and simple. For a basic explanation of scripts, see "Writing your own scripts" on page 843. 5. Type the code that wraps the span in a <a> element (a hyperlink).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-817.html">PAGE 817</a></h6> <p>configurations. The Preferences dialog is separated into individual tabs, where each tab controls certain aspects of the software. To open the Preferences dialog, select Window > Preferences. General preferences The General Preferences are as follows: l Always run in background: This option correlates with the "Always run in background" option selectable in the "Document Boundaries Refresh" dialog and "Print via Print Server" dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-818.html">PAGE 818</a></h6> <p>l l Restore Defaults. This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences. Apply: This option applies the settings made within the current Preferences page, but does not close the Preferences dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-819.html">PAGE 819</a></h6> <p>scheduling; or when PlanetPress Connect is started (if Run at application start up is selected); or when the Run Now button is pressed. l l l Enable clean-up service: Check to enable the Clean-up services. When checked, either or both of the Database clean-up and File clean-up services can be set individually. If the box is not checked, then no Clean-up will occur. Run at application start up: Click to start the clean-up service when the Designer module is opened, or the Managing Service is started.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-820.html">PAGE 820</a></h6> <p>then reduce the number of threads here. In general, higher end machines (those with multiple cores) will allow a higher numbers of threads, whilst low end machines will perform better with a lower number of threads. l l Number of entities in each deletion batch: The number of entities to be deleted at a time. This is done to break the clean-up into smaller chunks. This improves PlanetPress Connect clean-up responsiveness, whilst the clean-up is occurring.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-821.html">PAGE 821</a></h6> <p>jobs information it contains) is retained within the database before being set for deletion. l l l Minimum time to retain other entities: The minimum time any orphaned data (such as Finishing tables, Media tables, DataModels and Properties tables) are retained within the database before being set for deletion. Database Partition Settings: l Use Database Partitioning: Select to use Database Partitioning.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-822.html">PAGE 822</a></h6> <p>Default Format DataMapper stores user preferences for the Date, Number and Currency formats. By default, the user preferences are set to the system preferences. These user preferences become the default format values for any newly created data mapping configuration. Format settings can also be defined at the data mapping configuration level ("Data mapping configurations" on page 195) and/or per field in the Data Model.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-823.html">PAGE 823</a></h6> <p>When shifting to a different back-end database, the changes won't be applied until PlanetPress Connect is restarted. Including the Connect services. A full machine restart is recommended, as this provides the cleanest restart of all the services. l Basic Connection Settings selections: l Database vendor: Select the database type from the drop down list. Note Moving from one vendor database to another will reset all screen selections to defaults, regardless of what may have been previously selected.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-824.html">PAGE 824</a></h6> <p>l Schema: The individual database schema, within the vendor database. Note If a previously non-existent schema were chosen here, then a new schema of that name will be created within the database when the back-end database swap is applied. The tables within that schema, though, will not be created until Connect is restarted. l Username: Enter the database login username. Tip It is considered best practice for this user to have root privileges.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-825.html">PAGE 825</a></h6> <p>integratedAuthentication=true to the URL. l Property: These are free field text fields. Note These fields and their associated values get appended to the JDBC connection and therefore must follow all rules regarding acceptable URL addresses for such. l l l l Value: The value applied to the associated Property. l Add: Used to add extra Property values to the table. l Delete: Used to remove existing Property values from the table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-826.html">PAGE 826</a></h6> <p>Foundation templates. l l Enable for Print Context: Check to enable <div> resizing in the Print contexts. l Enable for Web Context: Check to enable <div> resizing in the Web contexts. l Enable for Email Context: Check to enable <div> resizing in the Email contexts. Detail tables preview limit l Maximum number of records to show in preview: This setting limits the number of records to show in detail tables in both the Designer (Preview tab) and Datamapper.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-827.html">PAGE 827</a></h6> <p>l l Nested: Each property has its own line, but the indentation isn't constant. Each rule is indented based on how deeply an element is nested in the HTML and CSS structure. Auto compile on saving .scss files: When this option is checked, a .scss file is compiled into a .css file whenever you save it, overwriting any previously compiled version of the .css file. Also, when a partial .scss file is saved all .scss files are recompiled. (A partial .scss file is meant to be imported in another .scss file.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-828.html">PAGE 828</a></h6> <p>l l Margin and guides: These settings only apply to Print sections. l l l l Guides: This is the color for rulers that can help position content correctly; see "Guides" on page 738. Margins: This color delineates the content area on a page; see "Pages" on page 469. Bleed box: This color delineates the printable area on a page; see "Page settings: size, margins and bleed" on page 471. Master pages: These edges are only visible on Master pages; see "Master Pages" on page 478.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-829.html">PAGE 829</a></h6> <p>Email preferences Email (General) preferences l Default From Group: l l l Name: Enter the name that is set by default in the "From name" field in the Send Email and Send Test Email dialogs ("Send (Test) Email" on page 986). Email Address: Enter the email that is set by default in the "From Email" field in the Send Email and Send Test Email dialogs ("Send (Test) Email" on page 986).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-830.html">PAGE 830</a></h6> <p>l l Restore Defaults: There are three default presets, each for working with a different Email Service Provider (ESP): Mandrilapp.com, Sendgrid and Mailgun (see "Using an ESP with PlanetPress Connect" on page 1448). Apply: Apply the new settings without closing the Preferences dialog. The Email preferences also provides you with buttons to : l l Restore Defaults. This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-831.html">PAGE 831</a></h6> <p>Designer. l Extensions Path: Choose a folder where to put json and js files to extend Emmet. This includes custom snippets, preferences and syntax profiles. For more information see http://docs.emmet.io/customization/. Emmet Abbreviation preferences This Preferences tab lets you add and manage custom abbreviations. All standard abbreviations can be found in Emmet's documentation: http://docs.emmet.io/abbreviations/syntax/.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-832.html">PAGE 832</a></h6> <p>Emmet Output preferences The Output Preferences dialog is used to control how the expanded (output) code behaves when expanding abbreviations and snippets. There are 6 different dialogs to control output and, while they all have identical options, they control different output types: CSS, HAML, HTML, XML, XSL and the "Default" one controlling the rest of the types. These options are equivalent to Emmet's syntaxProfiles.json feature (http://docs.emmet.io/customization/syntax-profiles/).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-833.html">PAGE 833</a></h6> <p><!doctype html>\n<html lang="${lang}">...</body>\n</html> In the example above, ${lang} is used to refer lang variable defined in variables below. If your primary language is, for example, Russian, you can simply override lang variable with ru value and keep the original snippets. Also, you can override variable values with inline abbreviation attributes: html:5[lang=ru]. l Name: The name of the variable. This should be a single alphanumeric string with no spaces or special characters.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-834.html">PAGE 834</a></h6> <p>is necessary. 2. The Connect administrator wanting the configuration of DLLs loaded by Connect Server, Designer, and their engines to happen outside of Presets, Templates, or other resources. This so the administrator can control what DLLs are loaded instead of allowing user created configurations triggering third party DLLs at runtime. This preferences page caters for both needs. The PKCS#11 Modules and Tokens table contains a list of Hardware devices that can be used by Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-835.html">PAGE 835</a></h6> <p>Default Locale The Default Locale preferences are only available in the Designer Preferences. This setting determines the locale for new templates. By default this is the system's locale. Select System Locale to use the operating system's locale settings.Select Explicit Locale to choose a specific locale from the drop-down Explicit Locale list.The Locale can be changed on a per template basis. See "Locale" on page 760.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-836.html">PAGE 836</a></h6> <p>Warning Higher logging settings will have an impact upon Connect production speeds, as well as leading to substantially larger log files. We recommended leaving the logging level to Info and only using the higher levels of logging in conjunction with advice from OL support. l Rollover policy selection: Chose whether to retain Connect log files for a certain number of days (Daily logs) or based upon some predetermined hard disk usage limitations (Size-based logs).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-837.html">PAGE 837</a></h6> <p>Warning We recommend leaving the Logging pattern to the default value. If you do need to change the Logging pattern, please see the Pattern Formatting guide (https://logback.qos.ch/manual/layouts.html#conversionWord) for help in doing so. l Log message preview display: This displays a real time example of the format and content of individual log file entries, based upon the Logging pattern setting. Note The language of the log files is determined by the Language preferences.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-838.html">PAGE 838</a></h6> <p>l l Restore Defaults. This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences. Apply: This option applies the settings made within the current Preferences page, but does not close the Preferences dialog. Parallel Processing preferences See "Parallel Processing preferences" on page 101.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-839.html">PAGE 839</a></h6> <p>l l l l l Hostname: Enter the IP, machine name or URL of the Print Server. Default is localhost. Port: Enter the port through which to communicate with the Print Server. Default is 9340. Username: Enter the username to authenticate to the Print Server. Default is ol-admin. This is set on the server's "Security Settings" on page 109. Password: Enter the password to authenticate to the Print Server. Default is secret. Confirm Password: Re-enter the password above.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-840.html">PAGE 840</a></h6> <p>Project Wizards preferences Project Wizard deployment settings l Workflow Configurations l Encoding: By default, "Project Wizards" on page 968 set the encoding of the Workflow configuration that they create to the encoding of the system on which the Designer runs (system default).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-841.html">PAGE 841</a></h6> <p>reached, Auto Backup will overwrite the oldest file. l Destination: Select the directory in which the backups should be stored. l Original: the directory in which the original file is stored. l Other directory: use the Browse button to select another directory. Backup files have the same name as the original file with two underscores and a progressive number (without leading zeros) at the end: originalname__1.OL-template, originalname__ 2.OL-template, etc.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-842.html">PAGE 842</a></h6> <p>l Number of iterations: Enter the number of times to run scripts when running the Profile Scripts dialog. The default is 1000. Accepted values are 1 to 1000000000. Yes, that's 1 billion - which would take a long time to run! The Scripting preferences also provides you with buttons to : l l Restore Defaults. This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-843.html">PAGE 843</a></h6> <p>l l l l After start tag: The element is inserted within the current element, at the beginning, just after the start tag. Before end tag: The element is inserted within the current element, at the end, just before the end tag. After element: The element is inserted after the current element where the cursor is located. For example if the cursor is within a paragraph, insertion occurs after the <p> tag.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-844.html">PAGE 844</a></h6> <p>Paragraphs can be made conditional with a Conditional Script Wizard. For dynamic images, you can use the Dynamic Image Script Wizard. In an Email context, you are provided with a number of Email Script Wizards to set the sender, the recipients and the subject of the email. However, when you want to do something that goes beyond what you can do with a Wizard, like creating a conditional paragraph with a condition that is based on a combination of data fields, you have to write the script yourself.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-845.html">PAGE 845</a></h6> <p>HTML tag for a paragraph, all paragraphs will be collected and passed to the script. Tip Hover over the name of a script in the Scripts pane to highlight parts of the template that are affected by the script. Next, the script can modify the selected pieces of content, using values from the record that is merged to the template at the time the script runs. It can, for example, hide, replace or add text or change the style of those pieces of content. This is how scripts personalize documents.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-846.html">PAGE 846</a></h6> <p>2. Change the name of the script, so that it reflects what the script does. Note Scripts can only have the same name when they are not in the same folder. 3. Choose which kind of selector you want to use. Running a Standard Script starts with searching the template for pieces of content that match the script's selector. The collected pieces of content are passed on to the script (all at the same time, or one by one - see "Setting the scope of a script" on page 849), so that the script can modify them.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-847.html">PAGE 847</a></h6> <p>Tip When output speed matters, choose selector or selector and text. Searching text is a rather lengthy operation, compared to searching for HTML elements and/or CSS selectors. See also: "Testing scripts" on page 853. There is a shorter route to create a script for an element with a specific ID: 1. In the template, click the element for which you want to create a script. 2. On the Attributes pane at the top right, type an ID.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-848.html">PAGE 848</a></h6> <p>https://www.w3schools.com/js/js_syntax.asp and https://www.w3schools.com/js/js_if_else.asp. A few examples can be found in a How-to: Combining record based conditions. Tip In the editor window, press Ctrl + Space to see the available features and their descriptions. Use the arrow keys to select a function or object and press Enter to insert it in the script. Type a dot after the name of the function or object and press Ctrl + space again to see which features are subsequently available.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-849.html">PAGE 849</a></h6> <p>var amount = record.fields.AMOUNT; if (amount >= 0) {results.css('color', 'green');} else if (amount < 0) { results.css('color', 'red'); } When this script executes, it stores the value of the AMOUNT field from the current record in a variable and evaluates it. If the value is zero or higher, the color of text in the results - the table cells in this case - will be set to green; if the value is below zero, the text color will be set to red.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-850.html">PAGE 850</a></h6> <p>l l Result set: The script will run once, regardless of the number of elements that match the selector. It will have access to all elements that match the selector via the results object (see "results" on page 1395). The each() function could be used to iterate over elements in the results. Each matched element: The script runs once for each element that matches the selector. The current element is accessible via the this object (see "this" on page 1317).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-851.html">PAGE 851</a></h6> <p>Script folders Scripts can be organized in folders. Why would you do that? For three reasons: l l l Folders have an execution scope. You can specify for which contexts and sections the scripts in a folder have to run. Folders provide a better overview than a long unorganized list of scripts. Folders make it easier to change the order of execution for a bunch of scripts (see: "Changing the order of execution" on the previous page to learn why the order of execution is important).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-852.html">PAGE 852</a></h6> <p>script in all contexts and sections – unless the script is located in a scripts folder for which the execution scope has been set to the relevant contexts or sections. So, setting the execution scope of a folder saves processing time. To change the execution scope of a script: 1. Put the script in a folder; see "Script folders" on the previous page. 2. Right-click the folder, and then click Properties. 3. Check the contexts and sections for which the scripts in this folder should run.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-853.html">PAGE 853</a></h6> <p>Tip For more ways to optimize scripts, see "Optimizing scripts" on page 858. Import/export scripts The easiest way to import scripts into another template is to open the template and use the Import Resources dialog; see "Import Resources dialog" on page 937. Remember also to import or add any files that a script refers to. Alternatively, scripts can be exported or imported via the Scripts pane. To export a script: 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-854.html">PAGE 854</a></h6> <p>Note Post Pagination Scripts run only when a Print section is previewed or outputted. To verify the results of Post Pagination Scripts on a certain Master Page, preview the Print section to which that Master Page is applied. Testing for errors Information in the Scripts pane One way to see whether a script is functional is to take a look at the Scripts pane. Tip Hover over the name of a script in the Scripts pane to highlight parts of the template that are affected by the script.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-855.html">PAGE 855</a></h6> <p>If an expanded script contains errors or if there are warnings, icons appear in the overview ruler on the right hand side of the editing area. These icons are shown relative to their position in the script and do not move as you scroll down. You can click on an icon to quickly jump to the error or warning. Script errors are highlighted by a red icon, and warnings in yellow. The topmost icon will display red if any errors exist in the script at all.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-856.html">PAGE 856</a></h6> <p>PCL, PDF, PNG, PS, SVG, and TIF/TIFF. Using the Script Debugger The Designer's Script Debugger allows you to set breakpoints in scripts and step through them. It simulates an output run with only the current record and shows an overview of the state of all local and global variables, while the Workspace displays the partially merged document. There are two ways to start the Script Debugger: l l Click the Debug Scripts button in the toolbar of the Scripts pane.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-857.html">PAGE 857</a></h6> <p>l Hover the mouse over a value in the column Count to see the number of times that the script has run, per section. You can also see the breakdown of the execution time across different execution stages: l l Hover the mouse over a value in the column Elapsed to see the time elapsed (in milliseconds) since the start of the session. In the Scripts Profiler, the scripts are by default sorted based on the values in the Elapsed column, from high to low.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-858.html">PAGE 858</a></h6> <p>Script Profiler settings Number of runs By default, the Script Profiler runs on 1000 instances of all the scripts. To test on a higher or lower number of instances: 1. On the menu, select Window > Preferences. 2. Click Scripting. 3. Set a number of iterations (maximum one billion) and click OK. Sorting In the Scripts Profiler, the scripts are by default sorted based on the values in the Elapsed column, from high to low. Click any of the columns to sort the scripts according to the values in that column.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-859.html">PAGE 859</a></h6> <p>This topic presents a number of other ways to speed up script execution by optimizing the scripts. Use an ID as selector Scripts (except Control Scripts) start with a query. The selector in the second column in the Scripts pane is what a script looks for in the template. If you've used the drag-and-drop method (without pressing the Alt or Ctrl key) to insert a data field in a template, the selector is a small text: the name of the data field surrounded by @ signs, @firstname@ for example.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-860.html">PAGE 860</a></h6> <p>Try avoiding DOM modifications, especially within loops. Storing the content in a variable and appending the information after the loop is more efficient: this way, the template will be touched only once. Example The following example loads a snippet into a variable and uses the find() and text() commands of the Designer scripting API. var labelElm = loadhtml('snippets/label.html'); for(var i = 0; i < record.tables.products.length; i++) { var label = labelElm.clone(); label.find('@ProductLabel@').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-861.html">PAGE 861</a></h6> <p>A QueryResult allows you to perform DOM manipulations like adding and removing elements, adding and removing CSS classes etc. When the required manipulations are limited to find/replace actions, you could change the QueryResult into a string. This allows you to replace text using the replace() method. For this, you could use toString(): var labelSnippet = loadhtml('snippets/label.html').toString(); Or you could copy the HTML of the QueryResults to a variable: var block = results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-862.html">PAGE 862</a></h6> <p>In this example, @product@ is a pattern (to be used in a search) and g is a modifier (to find all matches rather than stopping after the first match). For more information about possible regular expressions, see https://www.w3schools.com/js/js_regexp.asp. The script in this how-to: Translate and replace script uses the replace() method with a regular expression.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-863.html">PAGE 863</a></h6> <p>block = block.replace('@customercode@', data.customercode); … results.html(block); The first line retrieves the HTML of the promo block and stores it in a variable called block. To make the code more readible, the fields from the record are stored in a variable named data. After replacing the placeholders by values, the script replaces the HTML of the promoblock with the personalized string. Other resources There are also many resources online to help learn about JavaScript performance and coding mistakes.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-864.html">PAGE 864</a></h6> <p>In a Print context, the Standard scripts in the Scripts pane run once for each section and then for each Master Page (see "Master Pages" on page 478). Next, each processed Master Page is put behind every page to which it should be applied. Scripts are NOT executed again for every page. Finally, Post Pagination Scripts run, in the order in which they appear in the Scripts pane (see "Post Pagination Scripts" on page 894). Post Pagination Scripts are run in a Print context after the content has been paginated.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-865.html">PAGE 865</a></h6> <p>l l An attribute of an HTML element. Type the attribute and, optionally, its value, between square brackets, e.g.: [target], to select HTML elements with a matching attribute. A pseudo-class. For example, tr:nth-child(even) selects all even table rows. These components can be combined in different ways. For example, p div selects all paragraphs inside <div> elements, while p, div selects all paragraphs and all <div> elements.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-866.html">PAGE 866</a></h6> <p>and set the execution scope of the scripts in a folder via the folder properties; see "Execution scope" on page 851. Example The following rule applies formatting to <h1> elements in sections of which the name starts with ‘Letter’: [section^='Letter'] h1 { color: brown; } Note In versions prior to 2019.2 the section selector would work on sections as well as Master Pages. As of version 2019.2 this is no longer the case. The section selector now only selects sections.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-867.html">PAGE 867</a></h6> <p>[masterpage="Master page 1"] body results.html('<div style="background:red;width:1in;height:2in">Hello World</div>'); Sheet position selectors In Print output, pages have a sheet position that depends on the options set in the "Sheet Configuration dialog" on page 990 (e.g. the Duplex and Allow Content On options). Connect gives each page - or rather, the "MediaBox" div element on that page - a class depending on their sheet position: l .frontside l .backside (does not apply to simplex documents) l .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-868.html">PAGE 868</a></h6> <p>.backside.nocontentpage .h1 { display: none; } Print section background selector When you inspect a Print section in a browser, you will see that it has a <div id="pages"> element as the first child of the <body> element. Inside this <div> there are one or more MediaBoxes: elements with the class page_mediabox.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-869.html">PAGE 869</a></h6> <p>Scaling the section background The rule below downscales the section background image and keeps it in the centre of the page: .page_mediabox img.ol_pdf_datamapper_input { transform: translate(-50%, -50%) scale(1.5, 1.5) !important; } View selectors In the Designer, sections can be viewed on different tabs: Source, Design, Preview and - if it is a Web section - Live. In each view mode (except Source) a specific CSS class is added to the <html> element. The view-specific classes are: l .DESIGN l .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-870.html">PAGE 870</a></h6> <p>clearzone. The following style rule assigns a background pattern to elements with that class in the Design view: .DESIGN .clearzone { background:url (data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAQAAAAECAYAAACp8Z5+ AAAAFUlEQVQImWNgQAL/70z7TyqHgYEBANRfDcEzmlBaAAAAAElFTkSuQmCC) repeat; } Note The pattern image was created on www.patternify.com and is added as a data URI (see Data URIs). Showing hidden Foundation elements In Capture OnTheGo templates based on the Foundation framework the .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-871.html">PAGE 871</a></h6> <p>Make sure that the file name is exactly the same as the file in the Snippets folder. If the file name isn’t correct, the snippet will not appear in the template. To load a JSON snippet in script, use: loadjson(‘snippets/nameofthesnippet.json’). Tip To insert the code to load a snippet even quicker, you can: l l Drag a snippet into the script window. The function that loads the script loadhtml() or loadjson(), depending on the file type - will automatically be added, including the file name.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-872.html">PAGE 872</a></h6> <p>Example The following script evaluates if the value of the LANGUAGE field in the record is ‘En’. If so, the snippet is added to the content. if (record.fields.LANGUAGE == ‘En’) { results.loadhtml(‘snippets/nameofthesnippet.html’); } Another example is given in a how-to; see Load a snippet based on a data field value.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-873.html">PAGE 873</a></h6> <p>Load a snippet and insert variable data into it The following script loads part of a snippet based on the value of a field, and then finds/replaces text by the value of a field before inserting the content into the document. var promoTxt = loadhtml('snippets/promo-en.html', '#' + record.fields['YOGA']); promoTxt.find('@first@').text(record.fields['FIRSTNAME']); results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-874.html">PAGE 874</a></h6> <p>Step 2: Preparing the template The next step is to set up a template. If you've got the HTML to embed content in your template you can paste that HTML on the Source tab (and skip Step 3). Otherwise your template has to contain an element that can be replaced or followed by the remote content: an empty paragraph, for example, or a heading. If the element isn't unique in the template, give the element an ID.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-875.html">PAGE 875</a></h6> <p>Tip To load a JavaScript file (.js) or a style sheet (.css) you can use loadtext(). See "loadtext()" on page 1269. Inserting content in the template To insert the content after the selected element, use results.after(). To replace the element with the new content, use results.html() or results.replaceWith(). Example: recent posts The following script loads five posts from Mozilla's blog and inserts their titles as links in a template. Mozilla's blog is a WordPress website.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-876.html">PAGE 876</a></h6> <p>Using scripts in Dynamic Tables In most cases you don't need a script to change the content or style of rows or cells in a "Dynamic Table" on page 793. However, if the contents or style of cells or rows in a Dynamic Table need to be personalized based on the value of a field, you will need a script. This topic gives some information that will help you to write a script for (an element in) a Dynamic Table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-877.html">PAGE 877</a></h6> <p>The scope of the script is set to Each matched element (see "Setting the scope of a script" on page 849). This means that in the code, this refers to the element that matches the selector, and this.record refers to the current (nested) detail record (see "this" on page 1317). Tip To get access to the row in which the cell is located, you can use this.parent().</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-878.html">PAGE 878</a></h6> <p>The selector of a script that targets (something in) a row that is linked to a detail table will probably match multiple elements. By setting the scope of a script you can determine whether you want to run the script once, or once for each element that matches the selector. (See "Setting the scope of a script" on page 849.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-879.html">PAGE 879</a></h6> <p>this.parent().css('color', 'green'); } The following script targets the table, and has its scope set to "Result set". This script loops over the detail table in the record, evaluating the field Shipped. If the value of that field is 1, it looks up the corresponding row in the results (the selected Dynamic Table). Selector: #table_1 tbody Scope: Result set for(var i = 0; i < record.tables.detail.length; i++){ if(record.tables.detail[i].fields['Shipped'] == 1) query("tr:nth-child(" + (i+1) + ")", results).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-880.html">PAGE 880</a></h6> <p>section's background dynamically. (These are only a few examples; for more uses of Control Scripts see "What to use a Control Script for" on the next page.) Control Scripts differ from Standard scripts in two ways: l l Control Scripts run before all other scripts.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-881.html">PAGE 881</a></h6> <p>of a Print context for email and print output, and one to select a Web section. What to use a Control Script for Control Scripts let you change the way a template is merged, by giving access to the template with all its contexts and sections in a script. A Control Script may, for example, omit, group and clone sections; add a background to a Print section; or add a header to an email.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-882.html">PAGE 882</a></h6> <p>Task l See topic Select one Print section as PDF attachment if the output is to be emailed, and another Print section if the output is to be printed. Field/function of section object the examples in the following topic: "section" on page 1400. Add sections dynamically "Dynamically adding sections (cloning)" on page 889. clone() Add a header to an email "section" on page 1400, example: "Adding custom ESP handling instructions" on page 1450.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-883.html">PAGE 883</a></h6> <p>How to change page numbering in a control script A Control Script can make the page numbering continue over all Print sections or let it restart on a section. This is done by setting the restartPageNumber field on a section to true or false. For example: merge.template.contexts.PRINT.sections['Section 2'].restartPageNumber = true;. (Also see "section" on page 1400 and "Control Script API" on page 1355.) Page numbering starts with page 1 for each section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-884.html">PAGE 884</a></h6> <p>merge.context.sections['Section B'].restartPageNumber = true; merge.context.sections['Section C'].restartPageNumber = false; merge.context.sections['Section D'].restartPageNumber = true; } The page numbering in the output will be: 1. Section A page 1 2. Section B page 1 3. Section C page 2 4. Section D page 1 Disabled section When a section is disabled, it will not be outputted, but its restartPageNumber flag will still be taken into account for composing the page number sequences.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-885.html">PAGE 885</a></h6> <p>Parts: splitting and renaming email attachments In a Control Script, parts can be defined to determine which sections should be output to the same file. This way it is possible to split the Print context or the Web context into multiple email attachments. This topic shows how to do that. For information about Control Scripts in general, see "Control Scripts" on page 879 and "Control Script API" on page 1355. If you don't know how to write scripts, see "Writing your own scripts" on page 843.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-886.html">PAGE 886</a></h6> <p>Splitting and renaming a Print attachment Assume there are three Print sections: sections A, B and C. In a Control Script a part name is defined for section C: var section = merge.template.contexts.PRINT.sections['Section C']; section.part = 'Part2'; When generating Email output with the Print context as attachment, the email will have two attachments: l l attachment 1: Section A, Section B attachment 2: "Part2", which is Section C. The file name of this attachment is the part name.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-887.html">PAGE 887</a></h6> <p>} else if (merge.context.type == ContextType.WEB) { merge.context.sections['default Section'].enabled = false; // disable whatever is the default section merge.context.sections['Section A'].enabled = true; merge.context.sections['Section A'].part = "WebPartA"; merge.context.sections['Section B'].enabled = true; merge.context.sections['Section B'].part = "WebPartB"; } } Note For another example, see this how-to: Output sections conditionally.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-888.html">PAGE 888</a></h6> <p>Setting a background in script The Control Script should first enable a background on the section, in case an initial background wasn't set via the user interface. This is done by setting the source type for the background of the section to either DataMapper PDF orResource PDF (see "BackgroundResource" on page 1386). For example: merge.template.contexts.PRINT.sections['Policy'].background.source = BackgroundResource.RESOURCE_PDF; For a DataMapper PDF, nothing else has to be done to set the background.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-889.html">PAGE 889</a></h6> <p>Put the number of the first page in the range in the section's background.start field and the last page in background.end. The following script sets the page range from 2 to 5: merge.template.contexts.PRINT.sections['Policy'].background.start = 2; merge.template.contexts.PRINT.sections['Policy'].background.end = 5; Setting a page range automatically sets background.allPages to false (see "background" on page 1375). On the other hand, when you first define a page range and then set background.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-890.html">PAGE 890</a></h6> <p>useful when the record set defines one or more PDFs (e.g. insurance policies) per recipient. Via a Control Script, for each PDF a section can be cloned and each clone can be given one of the PDFs as background (see "Control Script: Setting a Print section's background" on page 887). For each page in the PDF, a page will be added to the section. For information about Control Scripts in general, see "Control Scripts" on page 879 and "Control Script API" on page 1355.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-891.html">PAGE 891</a></h6> <p>used. This is prevented by giving clones unique names. Unique names also ensure that CSS rules and scripts can target a specific clone. Targeting elements in a cloned section Clones that have a unique name can be further personalized with the use of CSS style sheets (see "Styling and formatting" on page 718) and personalization scripts (see "Variable Data" on page 777 and "Writing your own scripts" on page 843). The selector to use is: [section="name of the clone"].</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-892.html">PAGE 892</a></h6> <p>for( var i = 0; i < numClones; i++){ var clone = printSections["Section 1"].clone(); clone.name = "my_section_clone_" + i; printSections["Section 1"].addAfter(clone); } Cloning a section based on data and assigning a background PDF This script clones a section based on data fields. It disables the source section first and then calls the addPolicy function. addPolicy clones the section, renames it and sets a PDF from the resources as its background.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-893.html">PAGE 893</a></h6> <p>Setting passwords in script To set a password on a Print section in a Control Script, the script should first retrieve the Print section/s using merge.template.contexts.PRINT.sections or merge.context.sections (also see the example below). Next, the script can split the attachments, if needed (see "Parts: splitting and renaming email attachments" on page 885), and it can set a password on each section. For example: l merge.template.contexts.PRINT.sections['Section 2'].password = 'secret'; l merge.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-894.html">PAGE 894</a></h6> <p>Example This scripts splits the Print output into two PDF attachments and sets a password for the second attachment. var printSections; if (channel == Channel.EMAIL) { // only when generating Email output if (merge.context.type == ContextType.PRINT) { printSections = merge.template.contexts.PRINT.sections; printSections['Section 1'].part = 'PDFAttach1'; printSections['Section 2'].part = 'PDFAttach2' printSections['Section 2'].</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-895.html">PAGE 895</a></h6> <p>Pagination Script can change the sheet configuration and re-paginate a section. l Post Pagination Scripts only apply to the Print context. The output of other contexts is not paginated. Just like Standard Scripts, Post Pagination Scripts have a selector (see: "Selectors in Connect" on page 864). A selector selects parts of the content of a section and stores them in the results object, so that they can be modified in the script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-896.html">PAGE 896</a></h6> <p>3. Change the name of the script so that it reflects what the script does. Note Scripts can only have the same name when they are not in the same folder. 4. Write the script. If you are not familiar with scripting, see "Writing your own scripts" on page 843. Note Post Pagination Scripts run only when a Print section is previewed or outputted. To verify the results of Post Pagination Scripts on a certain Master Page, preview the Print section to which that Master Page is applied.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-897.html">PAGE 897</a></h6> <p>Step 2: Creating a placeholder for the TOC Create one extra Print section to put the Table Of Contents in. Inside the extra section, insert an Article element (see "Inserting an element" on page 607). Give the element an ID, for example: toc-content. This element is the placeholder for the TOC. Step 3: Inserting the Post Pagination script Insert a Post Pagination script (see "Adding a Post Pagination Script" on page 895). Double-click on the new script to open it.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-898.html">PAGE 898</a></h6> <p>What the script does First the script creates a variable to hold the table of contents: toc. Then it collects all <h1> and <h2> elements - in other words, level 1 and 2 headings. The merge.context.query(selector) function searches across all Print sections (see "query (selector)" on page 1393). The query returns a result set. Each of the elements in the result set goes through the callback function defined in each() (see "each()" on page 1252).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-899.html">PAGE 899</a></h6> <p>Note Whether page numbering restarts in each section, depends on the settings for page numbering; see "Configuring page numbers" on page 474. By default, page numbering starts with page 1 for each section. If the pagination process has changed the page numbers, the TOC needs to be updated as well. To do that, the script first has to collect the page numbers from the table of contents. This is where the number class comes in handy: var $numbers = query('.number');.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-900.html">PAGE 900</a></h6> <p>1. Add the following variable: var linknumber = 1;. This variable is used to generate unique IDs for elements that don't have an ID. 2. Before the first line that starts with 'toc ', add the following: var anchorId = ''; if (this.attr("id")) { anchorId = this.attr("id"); } else { anchorId = 'generatedID-' + linknumber; linknumber++; this.attr("id", anchorId); } This code takes the element's ID. If an element doesn't have an ID, the script generates a new, unique ID for it. 3.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-901.html">PAGE 901</a></h6> <p>p.toc-entry .dots { flex-shrink: 1; white-space: nowrap; overflow: hidden; text-overflow: clip; } p.toc-entry .dots::after { font-weight: normal; content: ". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . "; } p.toc-entry .number { flex-shrink: 1; text-align: right; font-weight: bold; } These styles make use of the CSS Flexbox Layout Module.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-902.html">PAGE 902</a></h6> <p>The files that hold the actual translations are not made in the Designer. They can be made in any translation tool that accepts a .pot file as input, and outputs .po files. l l The .pot file is exported from the "Translations pane" on page 1044 in the Designer. The file contains a list of texts in the base language. In OL Connect this is the language in which the template was originally written. A .po file holds translated texts for one language. Each .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-903.html">PAGE 903</a></h6> <p>The result is a .po file (one per language). 5. Import the .po file or files. See "Importing translations (.po)" on page 908. 6. Set the template's Locale, or select the field that contains a Locale value, in order to get output in the correct language. See "Changing the locale" on page 760. Translating snippets "Snippets" on page 714 get translated when they are inserted in the output, if the text is tagged for translation (see "Tagging text in snippets" on page 905).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-904.html">PAGE 904</a></h6> <p>3. Click the Tag Element button in the toolbar of the Translations pane. This adds the data-translate attribute to the element. (Attributes are visible on the "Source tab" on page 1047.) If there was no translation entry with the same text already, the text of the tagged element is copied to a new translation entry on the Translations pane. One translation entry works for all HTML elements that are tagged for translation and have exactly the same text.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-905.html">PAGE 905</a></h6> <p>The description is added to the <data-translate> attribute of the HTML element in which the source text is located, as its value, for example: <data-translate="Table">. Note that a translation will only be applied if the value of the <data-translate> attribute of the respective HTML element is exactly the same as the given Context (case-sensitive). Tagging text in snippets If the text that you want to tag for translation is located in a snippet, do not tag it in the section where the snippet is used.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-906.html">PAGE 906</a></h6> <p>To add a comment, simply double-click the entry in the Translations pane and enter your comment in the Comments field. Comments will be added to the POT file and are visible to translators in their translation tools. HTML tags in translation entries A translation entry may contain HTML tags, for example when part of the text is styled or when there is a hyperlink in the text. HTML tags must not be translated or removed. Normally, translators will recognize a simple bold or italic tag (<b>...</b> or <i> ...</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-907.html">PAGE 907</a></h6> <p>Adding plurals Entering plurals, or text with plurals, is a natural part of the translation process of a template. This process starts by creating translation entries as described in the following topic: "Translating templates" on page 901. Note that it isn't required to translate the template effectively. You may also create a translation file for the original language of a template and use it just for pluralization by entering plurals only. To enable pluralization on a translation entry: 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-908.html">PAGE 908</a></h6> <p>Exporting and importing translation files In the process of the translation of a template, two types of translation files are involved: Portable Object (.po) files and a Portable Object Template (.pot) file. These are standardized file types following the gettext format. This topic explains how to export the .pot file and how to import a .po file. Tip Translation tools are capable of combining .pot files. Combining .pot files may also result in .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-909.html">PAGE 909</a></h6> <p>Alternatively, right-click the Translations folder in the Resources pane and select New Translation > PO files... Editing an imported .po file When you double-click a .po file in the Translations folder it will be opened in the text editor of the Designer, where you can read and edit it. If you are working with a translator or translating agency, remember to send them a copy of the modified .po file to keep the .po files in sync. Updating an imported .po file OL Connect Designer monitors the .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-910.html">PAGE 910</a></h6> <p>Designer User Interface The main ingredients in the Designer's user interface are the following: l "Menus" on page 1012 l "Toolbars" on page 1048 l "Resources pane" on page 1034 l "Outline pane" on page 1033 l "Attributes pane" on page 1024 l "Styles pane" on page 1044 l "Translations pane" on page 1044 l "Workspace" on page 1045 (Source, Design and Preview tabs) l "Data Model pane" on page 1027 l "Scripts pane" on page 1041 l "Preflight Results and Messages" on page 1031 Page 910</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-911.html">PAGE 911</a></h6> <p>Dialogs Dialogs can allow you to perform a command or make settings. They can also ask you a question or provide you with information or progress feedback. Here is a list of all dialogs: Attachments dialog The Attachments dialog lets you add and remove static Email attachments. For more information about email attachments, see: "Email attachments" on page 510. l l Add: Click this button to open the Select File dialog (see below). Delete: Deletes the file from the list of attachments.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-912.html">PAGE 912</a></h6> <p>l Attach Print context as PDF: If a Print Context exists in the template, its output will be generated and a PDF version of it will be attached to the outgoing email. This option can be overridden by the setting in the Send Test Email or Send Email dialog. Select File dialog Resources: lists the images that are present in the Images folder on the Resources pane. A preview of the selected image will be shown at the right.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-913.html">PAGE 913</a></h6> <p>Note External files need to be available when the template is merged with a record set to generate output, and their location should be accessible from the machine on which the template's output is produced. External files are updated (retrieved) at the time the output is generated. Bar Chart Properties dialog The Bar Chart dialog appears when a Bar Chart object is right-clicked and the Chart... option is clicked.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-914.html">PAGE 914</a></h6> <p>l l l l Font: Enter the font-face to use to display text. The font must be installed on the system and defaults to Verdana if the font is not found. (Equivalent to the fontFamily property; see: fontFamily.) Size: Enter the size of the font. Defaults to 11. (Equivalent to the fontSize property; see: fontSize.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-915.html">PAGE 915</a></h6> <p>property; see: titleColor.) l l Grid group: l l l Font Size: Enter a font size for the label. (Equivalent to the titleFontSize property; see: titleFontSize.) Color: Select a color for the grid lines that divide the value axis: click the colored square to open the Color Picker dialog ("Color Picker" on page 926), or enter a valid hexademical color (HTML Hex Color) or a predefined CSS color (CSS color names). (Equivalent to the gridColor property; see: gridColor.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-916.html">PAGE 916</a></h6> <p>; see: axisThickness.) l Labels: Check this option to make the labels on the value axis visible. This is often useful in rotated charts. (Equivalent to the labelsEnabled property of the ValueAxis ; see: labelsEnabled.) l Frequency: Defines per how many grid lines a label will be placed. (Equivalent to the labelFrequency property of the ValueAxis ; see: labelFrequency.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-917.html">PAGE 917</a></h6> <p>l l l l Color: Select a color for the grid lines that divide the category axis: click the colored square to open the Color Picker dialog ("Color Picker" on page 926), or enter a valid hexademical color (HTML Hex Color) or a predefined CSS color (CSS color names). (Equivalent to the gridColor property; see: gridColor.) Opacity: Enter the opacity percentage of the grid. Default is 15%. 100 is fully opaque, 0 is transparent. (Equivalent to the gridAlpha property; see: gridAlpha.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-918.html">PAGE 918</a></h6> <p>that frequency, add the following to the categoryAxis section on the Source tab: "labelFrequency": "2" (replace 2 by the desired number of grid lines). l Axis group: l l l l Color: Select a color for the value axis: click the colored square to open the Color Picker dialog ("Color Picker" on page 926), or enter a valid hexademical color (HTML Hex Color) or a predefined CSS color (CSS color names). (Equivalent to the axisColor property; see: axisColor.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-919.html">PAGE 919</a></h6> <p>"left", "inside", "middle". (Equivalent to the labelPosition property; see: labelPosition.) l l l l Rotation: Rotation of the data labels. Supported notations: 0.0 , 0.0° or 0.0 deg . (Equivalent to the labelRotation property; see: labelRotation.) Offset: Vertical offset of the data labels. A positive offset moves the data labels up. A negative value moves them down. (Equivalent to the labelOffset property; see: labelOffset.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-920.html">PAGE 920</a></h6> <p>property; see: enabled.) l Legend Group: Defines how the legends are shown. l l l l l l l Position: Use the drop-down to select where the legend is shown: at the Right, Left, Top or Bottom. (Equivalent to the position property; see: position.) Align: Use the drop-down to select how to align the text in the labels: Left, Middle or Right. (Equivalent to the align property; see: align.) Horizontal Space: Horizontal space between legend items, in pixels.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-921.html">PAGE 921</a></h6> <p>l l l l l l Type: Use the drop-down to select in which shape the Markers are displayed; "none" hides the Markers completely. (Equivalent to the markerType property; see: markerType.) Size: Enter the size (in pixels) for the Markers to be displayed. (Equivalent to the markerSize property; see: markerSize.) Label Gap: Enter the distance (in pixels) between the legend marker and legend text. (Equivalent to the markerLabelGap property; see: markerLabelGap.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-922.html">PAGE 922</a></h6> <p>All settings in this dialog are in fact CSS properties. Cascading Style Sheets (CSS) were originally designed for use with web pages: HTML files. Since Designer templates are HTML files, they are styled with CSS. To learn how to use CSS in the Designer, see "Styling and formatting" on page 718 and "Styling templates with CSS files" on page 719. For information about specific properties and their options, see W3Schools CSS Reference.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-923.html">PAGE 923</a></h6> <p>l l Text wrap group: l l l Overflow: Use the drop-down or type in the value for how to handle overflow (text that does not fit in the current size of the box). Equivalent to the overflow property. Float: Use the drop-down or type in the value for how to float the box, if the box is not in an absolute position (see Position, below). Equivalent to the CSS float property. Clear: Use the drop-down or type in the value for clearing pre-existing alignments. Equivalent to the CSS clear property.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-924.html">PAGE 924</a></h6> <p>l General group: l l Color: Specify the color of the box background: select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 926). Alternatively you could type a name or value in the Color field directly.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-925.html">PAGE 925</a></h6> <p>Border tab For information about borders see "Border" on page 749. l l Same for all sides: Defines the border properties for all sides using the Top properties. Equivalent to the CSS border property. Top, Left, Bottom, Right: Each group defines the following properties: l l l Width: Specify the thickness of the border. Equivalent to the CSS borderwidthproperty. Style: Specify the style of the border such as solid, dashed or dotted. Equivalent to the CSS border-style property.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-926.html">PAGE 926</a></h6> <p>l Child (optional): When specified, the Copy Fit feature will only be applied to the given child element (an element inside the Box or Div). Specify the element by giving its ID, for example: #product, or class, for example: .product - note the dot. Color Picker The Color Picker dialog appears when creating a color in the formatting dialogs of certain elements, for example border colors in boxes and paragraphs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-927.html">PAGE 927</a></h6> <p>Colors Properties The Colors Properties defines and sets named colors used in the template; see "Colors" on page 752. Named colors can be used throughout the templates, in all contexts. They are visible in color selector dialogs and useable with their names in style sheets; see "Styling and formatting" on page 718. l l l l Color Type Selector: Click and use the drop-down to display which color types to show in the list: All, RGB, CMYK or Spot colors.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-928.html">PAGE 928</a></h6> <p>l l l Red/Green/Blue (RGB): Each slider sets the values of 0-255 for the color. Set the value using the sliders or type in the value directly in the input boxes. Color Preview: Box displaying the preview of the color (converted to RGB when relevant). Tint: l l l Source: Select an existing Color in the template. The tint or opacity will be applied to this color. Tint/Opacity: The slider sets the percentage of tint or opacity.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-929.html">PAGE 929</a></h6> <p>l Options Group: l Rendering intent: Use the drop-down to specify how colors are converted that are out of range of a profile. For example, you may use tricks like reducing the saturation of the entire print so that a color that is out of range still appears a bit more vibrant than ones that are in range. Rendering intents use different methods to trick the eye into believing that the print can reproduce irreproducible colors.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-930.html">PAGE 930</a></h6> <p>Includes Tab The Includes tab defines which style sheets and JavaScript files should be included in the Web context when generating output, and in which order; see "Includes dialog" on page 938. For more information about stylesheets, see "Styling templates with CSS files" on page 719. For more information about using JavaScript, see "Using JavaScript" on page 538. Edit Label Properties The Edit Label Properties defines how a Pie Chart Label displays its title and data.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-931.html">PAGE 931</a></h6> <p>standard layout. l Custom: To create a custom PDF report, you need two files: l l Template: A template design with the desired layout and variable data. This .OL-TEMPLATE file has to be made in the Designer. DataMapper: A data mapping configuration that provides the variable data. This .OL-datamapper file has to be made in the DataMapper module, using the standard XML template report as data sample.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-932.html">PAGE 932</a></h6> <p>Custom tab On this tab custom properties can be defined. Click the Add icon and enter a name for the property and a value. Use the arrow icons to reorder the list of custom properties. Custom property lists can be exported to, and imported from, a .CSV file, using the Import and Export buttons. Find/Replace Dialog The Find/Replace dialog can replace text within the current template. The scope of the replacement depends on the currently selected tab in the Workspace.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-933.html">PAGE 933</a></h6> <p>l Options l l l l l Case sensitive: Use a case sensitive search, which differentiates TEXT from text or TexT. Wrap search: Loop back from the end of the template or selection to its beginning, when the Search is at the end of the template or the selection. Whole word: Searches for the source string as a whole word. Incremental: With this option selected, each letter you type in the Find field causes the editor focus to move to the first complete occurrence of the text you are typing.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-934.html">PAGE 934</a></h6> <p>The following buttons appear to the right of the list of fonts: l New: Click to open the Edit Font dialog to add a new font. l Edit: Click to open the Edit Font dialog to edit the currently selected font. l Remove: Click to delete the currently selected font entry. l Duplicate: Click to create a copy of the currently selected font entry. Edit Font The Edit Font dialog appears when clicking New or Edit from the Fonts Dialog. l l l Name: Enter the name that should be used to refer to the font.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-935.html">PAGE 935</a></h6> <p>All settings in this dialog are in fact CSS properties. Cascading Style Sheets (CSS) were originally designed for use with web pages: HTML files. Since Designer templates are HTML files, they are styled with CSS. To learn how to use CSS in the Designer, see "Styling and formatting" on page 718 and "Styling templates with CSS files" on page 719. For information about specific properties and their options, see W3Schools CSS Reference.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-936.html">PAGE 936</a></h6> <p>l l Clear: Use the drop-down or type the value to clear pre-existing alignments. Equivalent to the CSS clear property. Positioning: l l l l l l Position: Use the drop-down or type in the value for the type of positioning for the image. Equivalent to the CSS position property (see "Using the CSS position property" on page 738). Top: Set the vertical offset between this image and its parent's top position. Equivalent to the CSS top property.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-937.html">PAGE 937</a></h6> <p>l Top, Left, Bottom, Right: Each group defines the following properties: l l l Width: Specify the thickness of the border. Equivalent to the CSS border-width property. Style: Specify the style of the border such as solid, dashed or dotted. Equivalent to the CSS border-styleproperty. Color: Specify the color of the border: select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 926).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-938.html">PAGE 938</a></h6> <p>Names that represent files or folders on disk are case-insensitive, while all other names are case-sensitive. l l l Rename: Import the resource, giving its name a suffix to make it unique in the target folder. Note that when a section is renamed, the properties of its context are not copied over, except for Includes (Web contexts only; see "Includes" on page 520). Includes are transferred to the imported section. Overwrite: Replace the existing resource.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-939.html">PAGE 939</a></h6> <p>Email clients do not read CSS files and some even remove a <style> tag when it is present in the email's header. Nevertheless, CSS files can be used with the Email context in the Designer. When generating output from the Email context, all CSS rules that apply to the content of the email can be processed and added either to the header of the email or to inline style properties as if local formatting was applied, depending on the Email section properties. See "Email section properties" on page 982. 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-940.html">PAGE 940</a></h6> <p>l Defer: This option postpones the execution of the script until the page has finished parsing. This is required by APIs like Google Maps. It is recommended to check at least one of the options: async or defer, or both. Page content will become visible more quickly, resulting in a better user experience. If you enable both options, async takes precedence on modern browsers, while older browsers that support defer but not async will fallback to defer.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-941.html">PAGE 941</a></h6> <p>Note The JSON Sample Data is not stored with the template. In order to reuse the data you should create a JSON file on disk and load it via the File option in this dialog. Types of JSON data You can add the following types of JSON data: l A JSON object or an array of JSON objects representing records. The data type is derived from the data: l Any value surrounded with quotes is converted to a field of type String. l Any numeric value containing a period is converted to a field of type Float.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-942.html">PAGE 942</a></h6> <p>A single record with a detail table { "name":"Peter Parker", "email":"parkerp@localhostcom", "detail": [{"id":"inv123","ExtraData":"hello"}, {"id":"456","ExtraData":"world"}] } A JSON Record Data List A JSON Record Data List describes a list of data fields (as name/value pairs), a data table schema and nested data records (if any) for one or more data records. This example holds a single, simple record.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-943.html">PAGE 943</a></h6> <p>General tab Most settings on the General tab correspond to properties of the AmSerialChart class in the amCharts library; see: AmSerialChart. l General Group: l l l l Rotate: Check to rotate the chart 90 degrees so that the bars are horizontal starting from the left. (Equivalent to the rotate property; see: rotate.) Stack Series: Check to stack the values in one bar, instead of having one bar per value. (Equivalent to the stackType property of the ValueAxis ; see: stackType.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-944.html">PAGE 944</a></h6> <p>l Angle: The angle of the 3D part of the plot area. (Equivalent to the angle property; see: angle.) Value Axis tab Settings on the Value Axis tab are equivalent to properties of the ValueAxis class in the amCharts library; see: ValueAxis. l Title group: l l l l l Label: Enter a label for the value axis (the Y axis, or the X axis if the graph is rotated). (Equivalent to the title property; see: title.) Bold: Check this option if the title should be bold.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-945.html">PAGE 945</a></h6> <p>l l Thickness: Enter a thickness for the grid lines. Default is 1. (Equivalent to the gridThickness property; see: gridThickness.) l Tick Length: Length of the tick marks. (Equivalent to the tickLength property; see: tickLength.) Axis group: l l l l Color: Select a color for the value axis: click the colored square to open the Color Picker dialog ("Color Picker" on page 926), or enter a valid hexademical color (HTML Hex Color) or a predefined CSS color (CSS color names).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-946.html">PAGE 946</a></h6> <p>Category Axis tab Settings on the Category Axis tab correspond to properties of the CategoryAxis class in the amCharts library; see: CategoryAxis. l Title group: l l l l l Label: Enter a label for the category axis (the X axis, or the Y axis if the graph is rotated).(Equivalent to the title property; see: title.) Bold: Check if you want the title to be bold. (Equivalent to the titleBold property; see: titleBold.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-947.html">PAGE 947</a></h6> <p>of a cell. (Equivalent to the gridPosition property; see: gridPosition.) Tip The position of the ticks (which is Middle by default) does not move with the grid. To change the tick position, add the following to the categoryAxis section on the Source tab: "tickPosition": "start" . l Tick Length: Length of the tick marks. (Equivalent to the tickLength property; see: tickLength.) Tip By default, one label per grid line will appear on the Category axis.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-948.html">PAGE 948</a></h6> <p>property; see: axisAlpha.) l l Thickness: Enter the thickness of the axis. (Equivalent to the axisThickness property; see: axisThickness.) Auto Wrap: Specifies if axis labels (when horizontal) should be wrapped if they don't fit in the allocated space. (Equivalent to the autoWrap property; see: autoWrap.) Graphs Settings on the Graphs tab correspond to properties of the AmGraph class in the amCharts library; see: AmGraph. l Line: l Thickness: Sets the thickness of the lines in a Line chart.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-949.html">PAGE 949</a></h6> <p>property; see: position.) l l l l l Horizontal Space: Horizontal space between legend items, in pixels. (Equivalent to the spacing property; see: spacing.) Vertical Space: Enter a numerical value (in pixels) to define the vertical space between legend items, and also between the legend border and the first and last legend item. (Equivalent to the verticalGap property; see: verticalGap.) Max Columns: Enter a numerical value to define the maximum number of columns in the legend.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-950.html">PAGE 950</a></h6> <p>property; see: markerLabelGap.) l l l Border Width: Use the drop-down to define the thickness of the border added to the Markers. The default value (0) means the line will be a "hairline" (1 px). In case the Marker type is line, this style will be used for the line thickness. (Equivalent to the markerBorderThickness property; see: markerBorderThickness.) Border Color: Color of the Legend's border.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-951.html">PAGE 951</a></h6> <p>l l l Data Field: Select this to use a data field from the record. The locale will be recordspecific in this case. Locale: Use the drop-down to select a specific locale. Only enabled when Explicit Locale is selected above. Data Field: Use the drop-down to select a field within the current data model that contains the locale. This field must be a string and contain the exact locale to be used, such as "en" or "fr-CA". It cannot be an alias such as "english" or "french".</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-952.html">PAGE 952</a></h6> <p>Properties Tab l l Name: The name of the Media, displayed in all drop-downs where the Media is shown as well as in the Resources Pane. Size: This group is read-only and only used to display the size selected in the linked Print section's properties (see "Print section properties" on page 983). l Page Size: The named page size. l Width: The width of the page. l Height: The height of the page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-953.html">PAGE 953</a></h6> <p>l Media Type: The type of paper, such as Continuous, Envelope, Labels, Stationery, etc. l Weight: The weight of the media in grammage (g/m2). l Front Coating: The pre-process coating applied to the front surface of the media, such as Glossy, High Gloss, Matte, Satin, etc. l Back Coating: The pre-process coating applied to the front surface of the media. l Texture: The texture of the media, such as Antique, Linen, Stipple or Vellum.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-954.html">PAGE 954</a></h6> <p>l l Project wizards: Lists all "Project Wizards" on page 968. A Project Wizard generates a Connect solution consisting of a Workflow configuration as well as any templates, data mapping configurations, and Print Presets that are used in that configuration. Templates: Lists all types of templates that you can create with a wizard. See "Templates" on page 423.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-955.html">PAGE 955</a></h6> <p>Package dialog The Package dialog saves templates, data mapping configurations and Print Presets as a package file. Package files can be sent to other Connect Designer users. l Configurations: Initially this list contains the Connect files that are currently open. l l Browse: This button opens the Select Files dialog that lets you add one or more templates (*.OL-template) data mapping configurations (*.OL-datamapper) and Print Presets (*.OL-jobpreset, *.OL-outputpreset) to the list.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-956.html">PAGE 956</a></h6> <p>The Apply button lets you preview the template with the new settings. For information about text and how to style it see "Text and special characters" on page 712 and "Styling text and paragraphs" on page 731. Formats tab l General group: l l l l l l Line-height: Specify the height of each line in the element's text, in measure or percentage. Note that this is not spacing between lines, but rather the complete height of the line itself including the text.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-957.html">PAGE 957</a></h6> <p>to the widows property. Widows and orphans are ignored if the page-breakinside property is set to avoid. l Orphans: Specifies how to handle orphans within the paragraph (lines appearing alone at the end of a page if the paragraph does not fit on the current one). Equivalent to the orphans property. Note For more information on page breaks, widows and orphans, see the W3 Paged Media reference.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-958.html">PAGE 958</a></h6> <p>l Color: Specify the color of the border. select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 926). Alternatively you could type a name or value in the Color field directly. It must be a predefined CSS color name (CSS color names), a hexadecimal color code (HTML Hex Color), an RGB color value, for example rgb (216,255,170) or a CMYK color value, for example cmyk(15%, 0%, 33%, 0%).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-959.html">PAGE 959</a></h6> <p>l Text Group: Determines how text is displayed in labels and legends. l l l l Font: Type in the font-face to use to display text. The font must be installed on the system and defaults to Verdana if the font is not found. (Equivalent to the fontFamily property; see: fontFamily.) Size: Type in the size of the font. Defaults to 11. (Equivalent to the fontSize property; see: fontSize.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-960.html">PAGE 960</a></h6> <p>l l Color: Enter a color for the outline: a valid HTML hexadecimal color value (HTML Hex Color) or a predefined CSS color (CSS color names), or click the colored square to open the Color Picker dialog ("Color Picker" on page 926). (Equivalent to the outlineColor property; see: outlineColor.) Opacity: Enter the opacity of the outline. 100 is fully opaque, 0 is transparent. (Equivalent to the outlineAlpha property; see: outlineAlpha.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-961.html">PAGE 961</a></h6> <p>line: l [[title]] : Refers to the field label. l [[percents]] : Contains the percentage of the Pie chart the value represents. l [[value]] : Contains the numerical value of the field. Any text: Adding text (such as a dollar sign or column, etc) will make it appear in each label. (Equivalent to the labelText property; see: labelText.) l l l Tick Group: Defines how ticks (line between the Pie chart and its labels) is shown. l l l Radius: The distance between the label and the slice, in pixels.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-962.html">PAGE 962</a></h6> <p>property; see: enabled.) l Legend Group: Defines how the legends are shown. l l l l l l l Position: Use the drop-down to select where the legend is shown: at the Right, Left, Top or Bottom. (Equivalent to the position property; see: position.) Align: Use the drop-down to select how to align the text in the labels: Left, Middle or Right. (Equivalent to the align property; see: align.) Horizontal Space: Horizontal space between legend items, in pixels.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-963.html">PAGE 963</a></h6> <p>l l l l l l Type: Use the drop-down to select in which shape the Markers are displayed; "none" hides the Markers completely. (Equivalent to the markerType property; see: markerType.) Size: Enter the size (in pixels) for the Markers to be displayed. (Equivalent to the markerSize property; see: markerSize.) Label Gap: Enter the distance (in pixels) between the legend marker and legend text. (Equivalent to the markerLabelGap property; see: markerLabelGap.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-964.html">PAGE 964</a></h6> <p>the "Scripts pane" on page 1041 execute. It helps greatly in troubleshooting performance issues caused by scripting (see also: "Testing scripts" on page 853). When the dialog opens, the script profiler runs automatically, on 1000 instances of all the scripts by default (this can be changed through the "Scripting preferences" on page 841). Note The script profiler can take a while, so please be patient.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-965.html">PAGE 965</a></h6> <p>Note Rasterization options are only available for Boxes (<div> elements); see "Boxes" on page 668. Note A business graphic in an Email section is rasterized by default and output as PNG image, because email clients usually don't support SVG images. SVG images in an Email section give an error in the Preflight window (see "Doing a Preflight" on page 855).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-966.html">PAGE 966</a></h6> <p>Scripts and call stack The left side of the window displays all enabled scripts that apply to the current context, with the call stack on top. If the selector of a standard script or post pagination script has no matches in the current resource (Master Page or section) the script will be skipped. If an error is thrown, the rest of the current script is skipped and execution continues with the next script. In the call stack, frames are ordered from new to old, top to bottom.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-967.html">PAGE 967</a></h6> <p>Tip When you click on an identifier (such as a variable name) in a script, the overview ruler at the right highlights all other occurrences of that identifier straightaway. Variables At the bottom right the Script Debugger shows a hierarchical overview of all variables in the scope chain and their state. This information is always relative to the current stack frame, which is the one that's selected on the left.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-968.html">PAGE 968</a></h6> <p>Step-through buttons The buttons at the bottom of the Script Debugger let you step through the code. When you step through the code it always steps relative to the most recent stack frame. l l l l l l Into (F5): Step into the function on the current line, if possible. A common use case for this is to step into a results.each() call. Note that you can only step into functions that are defined in user scripts. For other statements this behaves like (Step) Over. Over (F6): Step over the current line.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-969.html">PAGE 969</a></h6> <p>l l Print promotional jobs. This project generates a batch of basic personalized letters, in the format that was selected in the wizard: PDF, PCL or PostScript Level 3. (See: "Project Wizard: Print Promotional Jobs" on page 152.) The Workflow configuration uses the All In One plugin (see "Print processes with OL Connect tasks" on page 184). Print transactional jobs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-970.html">PAGE 970</a></h6> <p>l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder. The Workspace folder is meant to be used when debugging the solution (see "Basic Email - Project Wizard" on the previous page). Send Templates and resources to Workflow: Check this option to send the necessary resource files to the active Workflow instance on the local machine.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-971.html">PAGE 971</a></h6> <p>menu. For more detailed information about this project, and instructions on how to test and customize it, see "Project Wizard: COTG Timesheets" on page 144. The wizard contains the following options. l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-972.html">PAGE 972</a></h6> <p>the same computer, making it impossible for the COTG app to submit form data to Workflow on the same computer. The COTG user guide explains how to change these restrictions; see COTG user guide. l Send Templates and resources to Workflow: Check this option to send the necessary resource files to the active Workflow instance on the local machine.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-973.html">PAGE 973</a></h6> <p>For more detailed information about this project, and instructions on how to test and customize it, see "Project Wizard: Print Promotional Jobs" on page 152. The wizard contains the following options. l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-974.html">PAGE 974</a></h6> <p>For more detailed information about this solution and instructions on how to test and customize it, see "Project Wizard: Print Transactional Jobs" on page 159. To start the Project Wizard, select File > New > Project Wizards > Print Transactional Jobs from the menu. It contains the following options. l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-975.html">PAGE 975</a></h6> <p>l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder. The Workspace folder is meant to be used when debugging the solution (see "Submitting Data with Web Forms - Project Wizard" on the previous page). Send Templates and resources to Workflow: Check this option to send the necessary resource files to the active Workflow instance on the local machine.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-976.html">PAGE 976</a></h6> <p>Without these files the Workflow configuration can be inspected, but it cannot be tested; in order to test the configuration, you'll have to send the resources manually (see "Sending files to Workflow" on page 429). Note In order for this option to work, Workflow and the Designer must be installed on the same machine. In addition, the PPMessenger service must be running. By default, this service is always started automatically from the moment Workflow has been installed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-977.html">PAGE 977</a></h6> <p>Options For the options in Conditional Script wizards see "Conditional script dialog" on page 980. In other Script wizards, the following options are available. l Name: The name of the script, making it easier to identify it. l Selector/Find text: The Selector or Text to apply the result of the script to. l l l Selector: Uses CSS selectors to find the element to which the script applies Text: Uses text as a trigger for the script. The script applies to all instances of the text found in the template.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-978.html">PAGE 978</a></h6> <p>l [+]: Adds a new line to the Wizard Results. Note that by default there is no line return between fields in the list. Adding <br> in the Suffix or Prefix field can establish a line return. l [-]: Removes the currently selected line in the Wizard Results list. l Arrow Up: Moves the currently selected line up one position. l Arrow Down: Moves the currently selected line down one position. l Refresh Types: Updates field types to match the types in the active data model.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-979.html">PAGE 979</a></h6> <p>Expanded Script window When expanded, the Script window replaces all parts of the wizard below the Selector by a box in which the script can be typed. See "Writing your own scripts" on page 843. For an overview of keyboard shurtcuts that can be used in this script editor, see "Keyboard shortcuts" on page 1005. Chart Script dialog The Chart Script dialog specifies which variable data will be displayed in a chart and shows a preview of both the chart (on the right hand side) and the data (at the bottom).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-980.html">PAGE 980</a></h6> <p>l Values: Select data fields with a numerical value. l l l Column: Removing the topmost check deselects all data fields. Labels: Click the label to enter a new label for a field. It depends on the Input Type where the labels appear: with Data Fields, the labels appear under the x-axis of the chart; with a Data Table, labels appear in the Legend. Color: Click on the color to open the Color Picker dialog ("Color Picker" on page 926) and select a different color.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-981.html">PAGE 981</a></h6> <p>Conditional. If the current element has neither an ID nor a class, an ID will be automatically generated. See "Showing content conditionally" on page 787. The options in the Conditional Script wizard are: l Name: The name of the script, making it easier to identify it. l Selector: The Selector or Text to apply the result of the script to. l l l Selector: Uses CSS selectors to find the element to which the script applies. Text: Uses text as a trigger for the script.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-982.html">PAGE 982</a></h6> <p>Email section properties For information about Email sections, see: "Email templates" on page 499. Properties tab The properties for an Email section are minimal and contain the following options: l l Name: Enter the name of the Section in the Email Context. This has no effect on output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-983.html">PAGE 983</a></h6> <p>Includes tab This tab lists the style sheets that can be applied to the email section when producing the output. Style sheets are loaded in the order shown, and styles in later style sheets overwrite earlier ones when the same selector is used. (See "Includes dialog" on page 938 and "Styling templates with CSS files" on page 719.) Attachments tab The Attachments tab lets you select files and delete attachments. For more information, see: "Email attachments" on page 510.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-984.html">PAGE 984</a></h6> <p>Finishing tab This tab defines finishing options for this section when it is printed. For an explanation of all Binding and Hole making options, see "Finishing options" on page 1144. Sheet Configuration tab The Sheet Configuration tab defines how different Print context sections output on different Media (see "Media" on page 481) and using different Master Pages (see "Master Pages" on page 478). For an explanation of all settings on this tab, see "Sheet Configuration dialog" on page 990.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-985.html">PAGE 985</a></h6> <p>Arrange Sections The Arrange dialog is used to change the order of sections within a context. This can have an effect on how they are outputted; see: "Print sections" on page 459, "Email templates" on page 499and "Web pages" on page 521. To access the Arrange dialog, on the Resources pane, right-click on any section or the context containing them, and click Arrange. l Name: Displays the name of each section within the context. l Move Up: Click to move the currently selected section up one position.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-986.html">PAGE 986</a></h6> <p>l General group: l l l l l l l Server: Select the Capture OnTheGo server. COTG servers can be added via the preferences; see "COTG Servers preferences" on page 817. Repository ID: The Nu-Book Repository ID. If you don't have one, you can get a trial account for this purpose; please see this page for more details: http://www.captureonthego.com/en/promotion/. Password: The password to the above Nu-Book Store. Recipient(s): The user name(s) that should receive the document.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-987.html">PAGE 987</a></h6> <p>l From group: l l l l Use Litmus: Check to also send the emails to the Litmus test email set in the Email Preferences (to go to the Email Preferences, select Window > Preferences, click the arrow next to Email, and then click General). Disabled if no Litmus email is set. Also see this how-to: Test your emails with Litmus. Select All, or click Selection and enter the range of records that should be sent. Removing the range disables the selection and sends emails to all records in the record set.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-988.html">PAGE 988</a></h6> <p>See "Using an ESP with PlanetPress Connect" on page 1448. l l l Host: The SMTP server through which the emails are to be sent. Can be a host (mail.domain.com) or an IP address. You can specify a port number as part of the host name, for example: smtp.mandrillapp.com:465. Use authentication: Check if a username and password are needed to send emails through the host. Start TLS: Enabled if authentication is checked.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-989.html">PAGE 989</a></h6> <p>There are two ways to make it easier to find the file that you need: l The Show drop-down list lets you select the type of preset that you want to open. In the Filter field, you can enter (part of) a preset name to filter the list for matching presets. Select one or more Print Presets to add them to the list of configurations in the Send to Workflow dialog. l l l Delete: Deletes the selected file from the list of files to send. Workflow Server: Use the drop-down to select where to send the files.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-990.html">PAGE 990</a></h6> <p>host is "localhost", it can be omitted, resulting in file:///<path>, for example: file:///c:/resources/images/image.jpg. l Url lists image files from a specific web address. Select the protocol (http or https), and then enter a web address (for example, http://www.mysite.com/images/image.jpg).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-991.html">PAGE 991</a></h6> <p>General options The first option defines Duplex printing, which also enables or disables the settings for the Back side of each sheet. If Duplex is enabled, you can also: l l l Check Omit empty back side for Last or Single sheet to reset a page to Simplex if it has an empty back side (no content and no Master Page). Thus changing a Duplex job into a Mixplex job may reduce volume printing costs as omitted back sides aren't included in the number of printed pages.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-992.html">PAGE 992</a></h6> <p>l l Master Page Front: Defines the Master Page used for the front of the selected sheet's position. (Disabled if Back only is selected under Allow content on). Master Page Back: Defines the Master Page used for the back of the selected sheet's position. (Disabled if Front only is selected under Allow content on, or if Duplex is unchecked.) Omit Master Page Back in case of an empty back page omits the specified Master Page on the last backside of a section if that page is empty.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-993.html">PAGE 993</a></h6> <p>l l l Duplicate: Click to create a duplicate of the currently selected rule in the Rule List using the Edit Rule dialog. The default name for the new rule is the name of the current one plus "-duplicated". See "New/Edit Rule dialog" below. Move Up: Move the currently selected rule in the Rule List up one position in the list. Move Down: Move the currently selected rule in the Rule List down one position in the list. l Save: Click to save all changes to the style sheet and close the dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-994.html">PAGE 994</a></h6> <p>colored square to create a new color or to manually enter a color value (a valid HTML color name or hexadecimal color code). This is equivalent to the CSS background-color property. l Spacing group: l l l l Letter Spacing: Set the space between characters in a text in measure or percentage. This is equivalent to the CSS letter-spacing property. Word Spacing: Set the space between each word in a text in measure or percentage. This is equivalent to the CSS word-spacing property.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-995.html">PAGE 995</a></h6> <p>l l Display: Select how to display the element. This can also be used to hide an element completely using the none option. See CSS Display. Equivalent to the display property. Breaks group: l l l l l Before: Specifies whether a page break should occur before the element. Equivalent to the page-break-before property. Inside: Specifies whether to accept page breaks within the element. Equivalent to the page-break-inside property. After: Specifies whether a page break should occur after the element.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-996.html">PAGE 996</a></h6> <p>l l Same for all sides: Defines the border properties for all sides using the Top properties. Equivalent to theborderproperty. Top, Left, Bottom, Right: Each group defines the following properties: l l l Width: Specify the thickness of the border. Equivalent to the border-width property. Style: Specify the style of the border such as solid, dashed or dotted. Equivalent to the border-style property. Color: Specify the color of the border.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-997.html">PAGE 997</a></h6> <p>For more information about template translation, see "Translating templates" on page 901. l l New Strings: Lists the texts, found in elements that are tagged for translation, for which there is no matching translation entry. Orphaned Strings: Lists the translation entries that seem to be unused: currently there is no matching element in the content of the template for them.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-998.html">PAGE 998</a></h6> <p>All settings in this dialog are in fact CSS properties. Cascading Style Sheets (CSS) were originally designed for use with web pages: HTML files. Since Designer templates are HTML files, they are styled with CSS. To learn how to use CSS in the Designer, see "Styling and formatting" on page 718 and "Styling templates with CSS files" on page 719. For information about specific properties and their options, see W3Schools CSS Reference.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-999.html">PAGE 999</a></h6> <p>l Positioning: l l l l l l l Position: Use the drop-down or type in the value for the type of positioning for the table. Equivalent to the CSS position property. Top: Set the vertical offset between this table and its parent's top position. Equivalent to the CSS top property. Left: Set the horizontal offset between this table and its parent's left position. Equivalent to the CSS left property. Bottom: Set the vertical offset between this table and its parent's bottom position.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1000.html">PAGE 1000</a></h6> <p>l l l All sides: Check to set all padding to use the Top value. Equivalent to the CSS padding property. Top, Left, Bottom, Right: Set padding for each side. Equivalent to the CSS padding-left, padding-top, padding-right and padding-bottom properties. Margin group: Defines margins (spacing outside the element) in measure or percentage: l l All sides: Check to set all margins to use the Top value. Equivalent to the CSS margin property. Top, Left, Bottom, Right: Set the margin for each side.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1001.html">PAGE 1001</a></h6> <p>l General group: l l Color: Specify the color of the table background:select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 926). Alternatively you could type a name or value in the Color field directly.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1002.html">PAGE 1002</a></h6> <p>Cell Tab l l l Width: Set the width of the table in measure or percentage. Equivalent to the CSS width property. Height: Set the height of the table in measure or percentage. Equivalent to the CSS height property. Vertical Align: Specify how text is vertically aligned in the cell: top, middle, bottom or baseline. With the baseline value all the table data share the same baseline. Often this has the same effect as the bottom value. However, if the fonts are in different sizes, baseline looks better.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1003.html">PAGE 1003</a></h6> <p>l Underline: Sets the text-decoration to underline. l Strikethrough: Sets the text-decoration to line-through. l Subscript: Sets the vertical-align to super. l Superscript: Sets the vertical-align to sub. l Capitalize: Sets the text-transform to capitalize. l Uppercase: Sets the text-transform to uppercase. l Lowercase: Sets the text-transform to lowercase. l Small-caps: Sets the font-variant to small-caps. Spacing Tab For information about spacing see "Spacing" on page 761.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1004.html">PAGE 1004</a></h6> <p>a hexadecimal color code (HTML Hex Color), an RGB color value, for example rgb (216,255,170) or a CMYK color value, for example cmyk(15%, 0%, 33%, 0%). Equivalent to the CSS border-color property. Background Tab For information about backgrounds see "Background color and/or image" on page 748.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1005.html">PAGE 1005</a></h6> <p>l String: l l l Source: This is the text that will be presented to the translator, and that will be replaced with a translation when OL Connect generates output from the template. It is case-sensitive. When a new translation entry is created by tagging an HTML element for translation (see "Tagging elements for translation" on page 903), the text of that element gets copied to this field.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1006.html">PAGE 1006</a></h6> <p>Although some of the keyboard shortcuts are the same, this isn't a complete list of Windows keyboard shortcuts. To find that, refer to the documentation of the Windows version that you are using. Menu items The following key combinations activate a function in the menu. Key combination Function Alt Put the focus on the menu. (Alt + the underlined letter in a menu name displays the corresponding menu.) The menu can then be browsed using the Enter key, arrow up and arrow down buttons.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1007.html">PAGE 1007</a></h6> <p>Key combination Function Ctrl + O Open file Ctrl + P Print Ctrl + R Show/hide rulers Ctrl + S Save file Ctrl + V or: Shift + Insert Paste Ctrl + X or: Shift + Delete Cut Ctrl + W Close file Ctrl + Y or: Ctrl + Shift + Z Redo Ctrl + Z Undo Ctrl + Alt + ; Lock guides Ctrl + Shif + R Clear preview cache Ctrl + Shift + S Save all Ctrl + Shift + W Close all Ctrl + Shift + ; Snap to guides Ctrl + ; Show guides Ctrl + ' Show/hide virtual stationery Page 1007</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1008.html">PAGE 1008</a></h6> <p>Key combination Function Ctrl + \ Highlight Master Page items Ctrl + F5 Revert Ctrl + F10 Save as Ctrl + F11 "Send COTG Test" on page 985 Ctrl + F12 "Send to Workflow dialog" on page 988 Ctrl + Shift + F12 Package Workspace The following key combinations activate a function in the Workspace.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1009.html">PAGE 1009</a></h6> <p>Key combination Function Workspace) Ctrl + Shift + F6 Previous editor (when there is more than one file open in the Workspace) Shift + F10 or: Ctrl + Shift + F10 Open context menu Design and Preview tab In addition to the keyboard shortcuts for menu items and the Workspace, the following key combinations have a special function in the Design tab and Preview tab of the Workspace.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1010.html">PAGE 1010</a></h6> <p>Key combination Function Tip You can also use the mouse's scroll wheel in combination with the Ctrl button to gradually zoom in or out.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1011.html">PAGE 1011</a></h6> <p>Key combination Function Ctrl + I Indent (Tab) Ctrl + J l l Script Editor: Add a line break. Other editors: Incremental find; start typing a search string directly after pressing this key combination. Ctrl + K Find next Ctrl + L Go to line; a prompt opens to enter a line number.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1012.html">PAGE 1012</a></h6> <p>Data Model pane You can use the following keys to browse records in the Data Model pane: l Page Up: next record l Page Down: previous record l Home: first record l End: last record. Menus The following menu items are shown in the Designer menu. For a list of keyboard shortcuts, see "Keyboard shortcuts" on page 1005. File Menu l l l l l l New...</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1013.html">PAGE 1013</a></h6> <p>l l l l l l Save: Saves the current data mapping configuration or template to its current location on disk. If the file has never been saved, the Save As dialog appears instead. Save All: Saves the open files. If a file has never been saved, the Save As dialog opens for it. Save As...: Saves the current file to a new location on disk. Save a Copy: Save a copy of the current template in the selected Connect version's format. See "Saving a copy / down-saving a template" on page 427.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1014.html">PAGE 1014</a></h6> <p>l l l l l l l Job Creation Presets: Opens the"Job Creation Presets Wizard" on page 1137 dialog. Output Creation Presets: Opens the "Output Creation Presets Wizard" on page 1154 dialog. Proof Print: Opens the "Print options" on page 1158 dialog as a Proof Print dialog which limits the number of records output. The options themselves are identical to the regular Print Output dialog. Send Email: Opens the Send Email dialog; see "Send (Test) Email" on page 986 and "Generating Email output" on page 1443.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1015.html">PAGE 1015</a></h6> <p>l Locale...: Opens the Locale Settings dialog. See "Locale" on page 760. l Color Settings...: Opens the Color Settings dialog. See "Colors" on page 752. Insert Menu l l Image: Inserts an image using a resource that is local to the template, a resource on disk or a URL. See "Images" on page 699. Text: l l Wrap in span: Wraps selected text in a <span> element. The ID or class of the span can be used as a selector for scripts and styles.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1016.html">PAGE 1016</a></h6> <p>l l l l Dashes and Spaces: Use the list to insert special dashes, such as an em-dash, and spaces, such as non-breaking spaces or an en-space. (The HTML code inserted for the dash or space is visible on the Source tab of the workspace.) Arrows: Use the list to insert directional arrows (in one of four directions). Geometric Shapes: Use the list to insert a special geometric shape, such as circles, triangles and squares.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1017.html">PAGE 1017</a></h6> <p>l l Address...: Opens a dialog to add an <address> element. l Preformatted...: Opens a dialog to add a <pre> element. Structural Elements: l Div...: Opens a dialog to add a <div> element; see "Boxes" on page 668 l Span...: Opens a dialog to add a <span> element; see "Boxes" on page 668 l Article...: Opens a dialog to add an <article> element l Section...: Opens a dialog to add a <section> element (the HTML element, not a section in a context). l Header...</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1018.html">PAGE 1018</a></h6> <p>l l l l l l l Number Field...: Opens a dialog to add a Number Field; see "Number" on page 694. Hidden Field...: Opens a dialog to add a Hidden Field; see "Hidden field" on page 695. Label...: Opens a dialog to add a Label; see "Label" on page 695. Checkbox Field...: Opens a dialog to add a Checkbox; see "Checkbox" on page 695. Radio Button...: Opens a dialog to add a Radio Button; see "Radio Button" on page 696. Select Field...: Opens a dialog to add a Select (drop-down); see "Select" on page 696.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1019.html">PAGE 1019</a></h6> <p>l l l l l l l l l l Barcode Scanner...: Opens a dialog to add a Barcode Scanner element, see "Barcode Scanner" on page 681. User Account...: Opens a dialog to add a User Account element, see "User Account" on page 687. Device Info...: Opens a dialog to add a Device Info element, see "Device Info" on page 684. Repository ID: Opens a dialog to add a Repository ID element, see "Repository ID" on page 686. Document ID: Opens a dialog to add a Document ID element, see "Document ID" on page 684.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1020.html">PAGE 1020</a></h6> <p>dialog (Format > Text) and checking the appropriate style. See "Styling text and paragraphs" on page 731. l l l l l l Color: When text is selected, sets the text color by applying the color attribute to the text. The color submenu lists all the colors in the Colors Editor. Text...: Opens the Text Formatting dialog to modify the current text selection. See "Styling text and paragraphs" on page 731. Align: When an element is selected, determines how its contents is aligned inside the element.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1021.html">PAGE 1021</a></h6> <p>l l l l l Box...: Opens the "Box Formatting dialog" on page 921 to modify the box where the cursor is located. Image...: Opens the "Image Formatting dialog" on page 934 to modify the image that is currently selected. Table...: Opens the "Table Formatting dialog" on page 997 to modify the table in which the cursor is located. If the cursor is within a table embedded within another, the innermost table's formatting is the one modified. Table Cell...</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1022.html">PAGE 1022</a></h6> <p>l l l l Includes: Opens the Includes dialog; see "Includes dialog" on page 938. This option is only available when editing a Web section in the Workspace. Preview HTML: Opens the currently selected section in the default system browser to preview it. This feature works in all contexts. Profile Scripts: Opens the "Profile Scripts dialog" on page 963 to test script performance (see "Testing scripts" on page 853). Preflight: Opens the Preflight dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1023.html">PAGE 1023</a></h6> <p>l l l l l Preview View: Shows the template as it will output with the current record, with the personalized content (see "Personalizing content" on page 762). Refresh: Reloads the view, including static external images and remote stylesheets, and re-runs the scripts (the latter in Preview Mode only). Show Edges: Shows or hides a colored border around elements on the page. Rulers: Shows or hides the rulers in the Workspace. Rulers only appear for Print contexts.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1024.html">PAGE 1024</a></h6> <p>l l l l Preflight Results: Shows the results of a Preflight; see "Doing a Preflight" on page 855. l Attributes: Shows the "Attributes pane" below. l Styles: Shows the "Styles pane" on page 1044. l Translations: Shows the "Translations pane" on page 1044. l Data Model: Shows the "Data Model pane" on page 1027. Reset Perspective: Resets all toolbars and panes to the initial configuration of the module.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1025.html">PAGE 1025</a></h6> <p>General These attributes are common to all elements in the template and will always appear. l l ID: A unique identifier for the selected element. Used for CSS selections (see "Styling templates with CSS files" on page 719) as well as scripts (see "Writing your own scripts" on page 843) affecting single elements. Class: One or more classes that can be common to more than one elements. Used for CSS selections and scripts that can affect multiple elements.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1026.html">PAGE 1026</a></h6> <p>For a detailed description of the options see: "Formatting variable data" on page 784. This setting corresponds to the data-format attribute (see "A Dynamic Table's dataattributes" on page 807). l l l Hide when empty: By default, a Dynamic Table gets hidden if it contains no data. Uncheck this option to keep the empty table in the output. This setting corresponds to the data-hide-when-empty attribute (see "A Dynamic Table's data- attributes" on page 807).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1027.html">PAGE 1027</a></h6> <p>l Whitespace element: Check to make the element a whitespace element, meaning it will only appear on the page if there is enough space for it. This is useful for templates with variable height elements or conditional elements, to fill empty spaces with transpromotional material. Note that only top-level elements (i.e. not inside another element such as a table or div) will function as whitespace elements.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1028.html">PAGE 1028</a></h6> <p>Data is displayed as a tree view, with the root level being the record table, levels below it being detail tables, and any level below being called "nested tables". Filter To find a certain table, group or field in a large Data Model, start typing characters in the Filter box. This immediately narrows down the list of displayed items to all tables, groups and fields whose name contains the characters that were typed. Note that the filtering is case-insensitive.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1029.html">PAGE 1029</a></h6> <p>Note When a Data Model is exported to a JSON file or typed JSON file, detail tables are exported, but groups are not. l l l l : Synchronize Fields and Structure: Click to synchronize the Data Model fields and structure in the currently loaded template and data mapping configuration. If you click this button when working on the data mapping configuration, the Data Model gets updated to the one in the template.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1030.html">PAGE 1030</a></h6> <p>The record, detail tables and groups can also be expanded and collapsed using the arrow icon next to them. Changing the Data Model By adding fields to a Data Model, setting their type and entering a (default) value, you may construct or modify a Data Model without having to create or open a data mapping configuration. This is especially useful when a solution does not require a data mapping configuration.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1031.html">PAGE 1031</a></h6> <p>l Move: Click to move the selected field within the current level (record or group) in the Data Model. (See: "Ordering and grouping fields in the Data Model" on page 260.) l Top: Move the field to the first place. l Up: Move the field one step up. l Down: Move the field one step down. l Bottom: Move the field to the last place.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1032.html">PAGE 1032</a></h6> <p>Preflight Results pane The Preflight Results pane displays any notifications or errors related to the template, its scripts, its code or output generation. Double-click a script warning/error to open the script in the script editor. The relevant line will be highlighted. See also: "Testing scripts" on page 853. Log Filter The log filter determines what kind of events are shown in the Messages Pane. l l Event Types group: l OK: Uncheck to hide OK-level entries.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1033.html">PAGE 1033</a></h6> <p>l When the grey outline displays the location where the panel should be, release the mouse button. To minimize a panel: l Click the Minimize panel button at the top-right corner of the panel. A minimized panel displays only as its icon wherever it was docked, generally on the left or right side, or the bottom. To restore a minimized or maximized panel: l Click the Restore button next to the panel's display icon. The restored panel will return to its original docked location.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1034.html">PAGE 1034</a></h6> <p>l l l l Under the Page node, all top-level page elements are displayed. Each element under them is accessible by expanding (with the [+]) elements with children. Clicking on any element will select it in the Workspace, whether it displays the Source, Design or Preview tab. Dragging an element inside the Outline pane re-orders it in the actual HTML. Elements are executed top-to-bottom with lower elements appearing on top of previous elements (unless a CSS Z-Index is used).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1035.html">PAGE 1035</a></h6> <p>l Copy: Click to copy the selected Media to the clipboard. l Paste: Paste the copy into the Media folder. Master Pages Master Pages are layers of content that can be used by multiple Print Contexts to provide a reusable static background of content. Only one Master Page can be selected for each page position in the context. See "Master Pages" on page 478 for more information. Contextual menu l l l l New Master Page: Click to create a new Master Page and open its properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1036.html">PAGE 1036</a></h6> <p>Sections Sections hold part of the contents within a specific context. See "Sections" on page 442 for more information. Contextual menu l l l l l l l l Set as Default (Email and Web contexts only): Click to set the default section that is output if none is selected in the output generation. New Section: Click to add a new section within the context. Rename: Click to open the resource's Rename. This is the same as pressing the F2 key while the resource is selected.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1037.html">PAGE 1037</a></h6> <p>l l l Delete: Click to delete the resource. This is the same as pressing the Delete key while the resource is selected. Copy: Click to copy the selected file. Copy Resource Location: Click to copy the relative path of the resource to the clipboard. It may then be pasted into a script. Fonts Font Resources included in a template are transported with it, so they can be accessed even if the template is moved to a different computer.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1038.html">PAGE 1038</a></h6> <p>file will from then on use the downloaded file (see "Including a JavaScript file in a Web context" on page 541). l Delete: Click to delete the resource. This is the same as pressing the Delete key while the resource is selected. Stylesheets Style sheets control how contents appears on the page. They define spacing, color, size and other properties of elements on the page. See "Styling templates with CSS files" on page 719 for more information.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1039.html">PAGE 1039</a></h6> <p>l Compile (.scss files only): Select to compile the Sass (.scss) file into a Stylesheet which can then be applied to a section. The compiled style sheet will have the same name as the Sass file, but with the extension .css. Compiled CSS files can be recognized by their first line: /* Compiled by https://sasslang.com/libsass */. Compiler options can be set in the Preferences; see "Editing preferences" on page 825. Note Re-compiling a .scss file overwrites any manual changes made to the .css file.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1040.html">PAGE 1040</a></h6> <p>Contextual menu l New HTML Snippet: Click to create a new HTML Snippet resource. l New JSON Snippet: Click to create a new JSON Snippet resource. l New Folder: Click to create a new folder to organize resources more easily. l l l l Rename: Click to open the resource's Rename. This is the same as pressing the F2 key while the resource is selected. Delete: Click to delete the resource. This is the same as pressing the Delete key while the resource is selected. Copy: Click to copy the selected file.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1041.html">PAGE 1041</a></h6> <p>file will from then on use the downloaded file (see "Including a JavaScript file in a Web context" on page 541). l Delete: Click to delete the resource. This is the same as pressing the Delete key while the resource is selected. Scripts pane The Scripts pane contains all of the scripts that are used to replace data in a template, or to modify its look; see "Personalizing content" on page 762.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1042.html">PAGE 1042</a></h6> <p>Buttons l l l Import...: Click to open a standard Open dialog to import a script. The script must have the .OL-script extension. Export...: Click to open a standard Save As dialog to save the currently selected scripts to disk. These scripts can be re-used in other templates. If more than one script is selected, they are all saved to a single file. If some scripts are inside folders, this folder structure is kept and will be restored when the scripts are imported.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1043.html">PAGE 1043</a></h6> <p>l l l l Email scripts (Email sections only): Email scripts define the sender, recipients, subject, dynamic attachments etc. of the email that is sent, and the PDF password. See "Email header settings" on page 503. Conditional Content Script: This script can conditionally show or hide any element in the template. See "Showing content conditionally" on page 787 and "Conditional script dialog" on page 980.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1044.html">PAGE 1044</a></h6> <p>l Enable/Disable: Click to trigger the script to be enabled or disabled. Disabled scripts are greyed out and italic and will not be executed. See "Enable/disable scripts" on page 852 l Import: load a script from a Scripts file (*.OL-script). l Export: save the script to a Scripts file (*.OL-script). l Properties (Script folders only): edit the name and execution scope of the folder. See "Execution scope" on page 851.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1045.html">PAGE 1045</a></h6> <p>Buttons l l l l l Tag Element...: Tag the currently selected element in the template for translation (see "Tagging elements for translation" on page 903). If no translation entry with the same text already exists, the text of the tagged element is copied to a new translation entry. Add Empty String: Adds a new, empty translation entry to the list and opens the "Translation String Options dialog" on page 1004.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1046.html">PAGE 1046</a></h6> <p>The Workspace contains three or, when a Web section is open,four tabs. To switch between the tabs, click on the tab at the bottom, or select View > Design View, Preview View or Source View on the menu. For an overview of keyboard shortcuts, see "Keyboard shortcuts" on page 1005. Design tab The Design tab shows the template including all styles, text and images as well as the placeholders used for variable data. In this tab, the template's scripts are not executed and only placeholders are shown.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1047.html">PAGE 1047</a></h6> <p>l l l Fit Width: Adjusts zoom to fit the exact width of the template to the available workspace. Refresh: Reloads the view, including static external images and remote stylesheets, and re-runs the scripts (the latter in Preview Mode only). Responsive Design View: Use the drop-down to select a specific screen width, to test the design for different devices. Not available in Print contexts. Tip You can also use the mouse's scroll wheel in combination with the Ctrl button to gradually zoom in or out.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1048.html">PAGE 1048</a></h6> <p>Pretty print options In the Source view the HTML source of the template is "pretty printed" (that is: formatted, adding new lines and indentation) to make it more readable. When this is undesirable, the Source view formatting can be turned off for (parts of) a section by adding  in Source view, at the beginning of the text or in between two HTML elements. From that point on, pretty printing will be disabled for that section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1049.html">PAGE 1049</a></h6> <p>File manipulation l New: Displays the New Wizard where a new data mapping configuration or a new template can be created. Open: Displays the Open dialog to open an existing template. l l Save: Saves the current template. If the template has never been saved, the Save As... dialog is displayed. Print: Opens the Print Output dialog. l l Proof Print: Opens the "Print options" on page 1158 dialog as a "Proof Print" which limits the number of records output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1050.html">PAGE 1050</a></h6> <p>l Insert Text Field: Inserts a <input type="text" /> element. A drop-down is available to insert other fields, such as a URL, Password etc. l Insert Text Area Field: Inserts a <textarea> element. l Insert Label: Inserts a <label> element. l Insert Checkbox: Inserts a <input type="checkbox"> element. l Insert Radio Button: Inserts a <input type="radio"> element. l Insert Select Field: Inserts a <select> element and add multiple possible options to it.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1051.html">PAGE 1051</a></h6> <p>l l Insert Dynamic Table...: Inserts a Dynamic Table where the number of rows is determined by a detail table in the data, through the "Dynamic Table" on page 793 Wizard. Select l l l Select Table: Selects the table where the cursor is located. If the cursor is within a table embedded within another, the innermost table is the one selected. l Select Row: Selects the innermost row where the cursor is located. l Select Cell: Selects the innermost cell where the cursor is located.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1052.html">PAGE 1052</a></h6> <p>l l l Insert Pie Chart: Click to insert a new Pie Chart object and open the Chart Script wizard. Insert Bar Chart: Click to insert a new Bar Chart object and open the Chart Script wizard. Insert Line Chart: Click to insert a new Line Chart object and open the Chart Script wizard. Hyperlinks l l Insert Hyperlink...: Creates a Hyperlink or mailto link on the currently selected text or element and opens its properties. See "Hyperlink and mailto link" on page 697.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1053.html">PAGE 1053</a></h6> <p>l l l l l Middle: Aligns the middle of the selected objects with the middle of the last selected object. Objects may move up or down. Bottom: Aligns the bottom side of the selected objects with the bottom edge of the last selected object. Left: Aligns the left side of the selected objects with the left edge of the last selected object. Center: Aligns the center of the selected objects with the vertical center of the last selected object. Objects may move to the left or to the right.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1054.html">PAGE 1054</a></h6> <p>Text editing l Bold: Makes the currently selected text bold. l Italic: Makes the currently selected text italic. l Underline: Makes the currently selected text underline. l Strikethrough: Makes the currently selected text strikethrough. l l l l Create Numbered List: Makes the selected text element a numbered list (<ol>). If multiple paragraphs are selected, each becomes a list item (<li class="Bullet">). Create Bulleted List: Makes the selected text element a bullet list (<ul>).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1055.html">PAGE 1055</a></h6> <p>Welcome Screen The Welcome Screen appears when first starting up PlanetPress Connect. It offers some useful shortcuts to resources and to recent documents and data mapping configurations. If you are new to PlanetPress Connect and you don't know where to start, see "Welcome to PlanetPress Connect 2020.1" on page 15. The Welcome Screen can be reopened in two ways: l The Welcome Screen button in the "Toolbars" on page 1048. l From the Menus in Help, Welcome Screen.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1056.html">PAGE 1056</a></h6> <p>Inserters. The Inserter options in the print settings are dependent upon the HCF model selected; see "Inserter options" on page 1231. l Take A Tour: Click to open the YouTube Playlist giving you a tour of the software. l Create/Open: l l l l l Open File: Lets you open an existing template or data mapping configuration. New template: Lets you choose a Context to create a new template without a Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1057.html">PAGE 1057</a></h6> <p>industry standard print output types. These include PCL, PDF and PostScript (including the optimized PPML, VIPP and VPS variants, if licensed under PlanetPress Connect), with a range of quality settings available for each. The bundled print output Models do not cater for all types of printers, however. There are simply too many different printers with their own individual (often quirky) settings and capabilities to cater for all of them with just a few standardized print Models.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1058.html">PAGE 1058</a></h6> <p>Output options l l Output Local: Select to have the output created using the local Print Server, instead of the Connect Server (see "The Connect server" on page 127 for an explanation). Output Type choices: l l Prompt for file name: Select to output to a local file on the hard drive. When this option is selected, no other configuration is necessary. A Save As dialog will appear to allow selection of the folder and file name. Directory: Select to output to a local folder on the machine.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1059.html">PAGE 1059</a></h6> <p>l Windows Printer: Select to send the Print Job to a printer queue (note that this is an actual printer queue, not a Workflow Printer Queue). For non-PDF output, the job will be first rendered as a PDF before being printed through the Windows driver. For PDF output the Adobe Library is used. l l l l Windows Printer: Use the drop-down to select the Windows printer queue where the job will be sent. Job Owner Name: Optional entry for adding the name of the job owner. Job Name: The name of the output file.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1060.html">PAGE 1060</a></h6> <p>l l l l l l l Runtime Parameters: select "Runtime Parameter Options" on page 1139 to store information which can be used at runtime for comparisons against conditions within Job Creation, or for use with external sorting programs. Override Finishing options (not available in Output Creation Preset Wizard): Check to configure custom "Finishing options" on page 1144, such as binding. Print virtual stationery: Check to enable virtual stationery in the output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1061.html">PAGE 1061</a></h6> <p>Pure Color Thresholds This section is valid for PCL only. It applies to elements within the record that are shades of grey, rather than black or white. l l Black Threshold Percentage: The percentage of shading at which the element will appear as full black, rather than dark grey. White Threshold Percentage: The percentage at which the element will appear as full white, rather than light grey.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1062.html">PAGE 1062</a></h6> <p>made. This page includes a handy illustration that displays how the final binding would look, based upon the current selections. Options: l Configuration: Use the drop-down to select the type of binding to use: l l l l Saddle Binding: This binding places all the pages in a stack, binds the middle and folds the stack as one. Perfect Binding: This binding type is often used for books. Pages are folded in the middle and then set side by side. The pages are then bound along the folded "spine".</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1063.html">PAGE 1063</a></h6> <p>Advanced Print Wizard and Output Creation Preset Wizard navigation options l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1064.html">PAGE 1064</a></h6> <p>below the Job Segment level is lost. If Booklet Binding were selected, some of the imposition settings will be determined by the options made within the "Booklet Options" on page 1221 Page and those imposition settings will thus be disabled on this page. Note During Impositioning, all hyperlinks - both external and internal - are removed from the document (see "Hyperlink and mailto link" on page 697).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1065.html">PAGE 1065</a></h6> <p>l l Imposition Sheet group: Use to select the physical media size that the logical pages will be printed upon. This appears as the white background in the output preview (and validation) diagram. l l l l The Width and Height values are real-only and appear for display and design purposes only. Size: Use the drop-down to select the size of the physical media the output is to be printed upon. Orientation: Select orientation (aspect ratio) of physical media sheet (Landscape or Portrait).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1066.html">PAGE 1066</a></h6> <p>In this example the error is that the logical pages are too large to fit upon the Imposition Sheet that has been selected. l Position group: These settings apply to the positioning of the logical page(s) within the Imposition Sheet. l Method selection: Set the position of the logical page(s) upon the Imposition Sheet. The choices are as follows: l l l l l l Center: Have the logical page(s) centered within the Imposition Sheet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1067.html">PAGE 1067</a></h6> <p>Note If the logic page was set to Rotate in the Position selections, then the Horizontal selection might appear as vertical, and the Vertical selection might appear as horizontal, on the real time output diagram. l l l l Vertical selection: Set how many logical pages are to be placed on one vertical line within the Imposition Sheet. Horizontal Gap selection: Set the amount of blank space to add between each logical page on this axis.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1068.html">PAGE 1068</a></h6> <p>Each set of 5 Imposition Sheets is a discrete drill sorted nUp block that can be guillotined and stacked. The first 5 sheets encompass records 1-50, whilst the next 5 sheets encompass records 51-100.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1069.html">PAGE 1069</a></h6> <p>The following example is the same job but with a Horizontal repetition setting of 6: As you can see, the outputs are very different.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1070.html">PAGE 1070</a></h6> <p>Note If the Stack Depth is greater than the number of sheets in the entire job then you will get a single drill sorted block that can be guillotined and stacked to give the complete job in record order. l l Sides selection: Select how many sides of the Imposition Sheet are to be printed upon. Choice is between Simplex or Duplex. Method selection: In 2018.2 we introduced a new imposition page order for cut & stack impositioning that works with continuous feed devices: Stack by Column.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1071.html">PAGE 1071</a></h6> <p>l l l l Off. Output is not reversed. Stack upside down: Essentially turns the stack upside down by reversing the output imposition page sides. The last sheet becomes the first, and in the case of duplex imposition, the back sides become the front sides. For presets created in a version prior to Connect 2018.2, a "Reverse Pages" selection will apply this Stack upside down setting. Inverse page order: This impositions the output in the exact opposite order from what has been selected.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1072.html">PAGE 1072</a></h6> <p>l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1158 page have been completed or not. Cancel button: Cancels the Print Wizard, without creating any printout.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1073.html">PAGE 1073</a></h6> <p>l l l l Collation level: Select whether the markings will be made at Document level, or Document Set level. Print marks on back: Check to place the Inserter Marks on the rear of the page. Selective Inserts: If selective inserts are supported by the chosen Mark Configuration you can select what markings to include and whether those markings are to included based upon some conditional setting.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1074.html">PAGE 1074</a></h6> <p>through the wizard to return to the main selection page (the "Print options" on page 1158 page) and add or remove printing options from the print run. l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1158 page have been completed or not.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1075.html">PAGE 1075</a></h6> <p>l Show Page: Use the up and down arrows or type a page number to display a specific page within the document. Zoom in/out: Click to zoom in or out by 25% l l Zoom Level: Use the drop-down to select a predefined level or enter a zooming percentage. Selective Insert Dialog The Selective Insert Dialog provides control over individual inserts. In this dialog the selected can be set to be either selected ("Yes") or not ("No"), or selected based upon some conditional criteria ("Conditional").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1076.html">PAGE 1076</a></h6> <p>l l l l l Every: Enter the number of Sheets, Documents, Document Sets or Job Segments at which the output is to be split. This option is only available if the Split entry has been set to "At Exactly". Use the drop-down box to chose what the separation option is to be. The selection is either Sheets, Documents, Document Sets or Job Segments. The default separation option is Sheets, which was the only option available for splitting prior to Connect 2019.1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1077.html">PAGE 1077</a></h6> <p>chosen selections. l l l Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard. Up until the Print button is pressed, one can reverse all the way through the wizard to return to the main selection page (the "Print options" on page 1158 page) and add or remove printing options from the print run.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1078.html">PAGE 1078</a></h6> <p>l l l l l "Additional Image Settings" on page 1182 entry. l "Additional OMR Mark Settings" on page 1216 entry. Edit: Click to edit the currently selected entry. This will launch the appropriate edit box, for the selected entry type. Double clicking on an entry in the table has the same effect as this button. Delete: Click to delete the currently selected entry or entries. Duplicate: Click to create a duplicated copy of the entry. This creates a new entry that is exactly the same as the original.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1079.html">PAGE 1079</a></h6> <p>Advanced Print Wizard and Output Creation Preset Wizard navigation options l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1080.html">PAGE 1080</a></h6> <p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Text, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Text, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1081.html">PAGE 1081</a></h6> <p>Use the Add button for selection options. For details on how to create a conditional, see the "How to Set Conditionals" on page 1220 page. Additional Image Settings The Additional Image dialog displays the properties of the image added in the "Additional Content" on page 1179 page. l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1082.html">PAGE 1082</a></h6> <p>metric (cm/mm), inch (in), pixel (px) or point (pt) values. l l Bottom: Enter the distance between the bottom margin of the page and the image, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Filename: Use the browse button to launch a Browse box to select an image file. This is a mandatory field. Note Transparent images are not supported. l l Preview group: This displays a preview of the selected Image.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1083.html">PAGE 1083</a></h6> <p>l "Australia Post Settings" below l "Codabar Settings" on page 1185 l "Code 128 Settings" on page 1188 l "Code 128 Settings" on page 1188 l "Data Matrix settings" on page 1193 l "EAN-13 Settings" on page 1198 l "EAN-13 Settings" on page 1198 l "GS1-128 Settings" on page 1195 l "Interleaved 2 of 5 Settings" on page 1203 l "Japan Post Settings" on page 1105 l "Japan Post Settings" on page 1105 l "PDF417 Settings" on page 1205 l "QR Code Settings" on page 1207 l "Royal Mail 4 State (</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1084.html">PAGE 1084</a></h6> <p>This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1085.html">PAGE 1085</a></h6> <p>l l Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1086.html">PAGE 1086</a></h6> <p>included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1087.html">PAGE 1087</a></h6> <p>l l Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l l l Font size: Enter a font size for the human readable text. Display start/stop symbols checkbox: Adds the stop/start symbols to the Barcode text.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1088.html">PAGE 1088</a></h6> <p>start/stop asterisk (*) character. If the Extended character set is chosen, then lower-case letters (a-z) and other special ASCII characters can also be included. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1089.html">PAGE 1089</a></h6> <p>l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Code 39 Properties group: l l l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Use extended character set: Check to use the Code 39 Extended character set.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1090.html">PAGE 1090</a></h6> <p>Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l Font size: Enter a font size for the human readable text. Process Tilde: Check this option to process tilde characters in the data as special characters. Note: with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~. l Text: Enter the text used to generate the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1091.html">PAGE 1091</a></h6> <p>the print run and the barcode. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries. This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1092.html">PAGE 1092</a></h6> <p>l Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1093.html">PAGE 1093</a></h6> <p>Data Matrix settings A Data Matrix barcode is a high-density, two-dimensional (2D) matrix barcode which supports encoded text, numbers, files and digital data. Note In order to create a GS1 compliant Data Matrix barcode, the barcode data must meet the following requirements: l l l The barcode data must start with a leading FNC1 character. Either ~1 or ~d232. The GS1 Application Identifiers (AI) must be used for all data.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1094.html">PAGE 1094</a></h6> <p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1095.html">PAGE 1095</a></h6> <p>Note The following tilde codes are supported in GS1 DataMatrix barcodes: l l ~1 = FNC1 character (for GS1 DataMatrix barcodes) l ~2 = Structure Append l ~3 = Reader programming l ~5 = Macro5 l ~6 = Macro6 l ~7 = ECI expressions Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1096.html">PAGE 1096</a></h6> <p>libraries from which you can pick and choose what entries you wish to have included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1097.html">PAGE 1097</a></h6> <p>l l l l Add: Calculate and add a checksum character to Barcode, regardless of current value. Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1098.html">PAGE 1098</a></h6> <p>Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1099.html">PAGE 1099</a></h6> <p>l EAN 13 Properties group: l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. The EAN-13 barcode employs a module width between 0.27mm and 0.66mm. l l l l l l l l Checksum: Use the drop-down to select how to deal with the Barcode checksum: Ignore: Ignore checksum calculations.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1100.html">PAGE 1100</a></h6> <p>l Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields. l Condition: Enter the condition which determines whether or not the Barcode will be added to the document at print time.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1101.html">PAGE 1101</a></h6> <p>l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1102.html">PAGE 1102</a></h6> <p>Elements can be combined using the '+' symbol. l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1103.html">PAGE 1103</a></h6> <p>Interleaved 2 of 5 Settings Interleaved 2 of 5 barcodes are also known as "ITF" and "2/5 Interleaved". It is a numeric only barcode whose data must contain an even number of digits, as the barcode uses sequences of two digits interleaved with each other to create a single symbol. If the numeric data contains an odd number of digits, then a leading zero must be added to the beginning of the data.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1104.html">PAGE 1104</a></h6> <p>l Interleaved 2 of 5 Properties group: l l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. Bar width ratio: Set the Barcode bar width. l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1105.html">PAGE 1105</a></h6> <p>Japan Post Settings Japan Post 4 State Barcodes (also known as Kasutama barcodes, or Japanese Postal Barcode) are used by Japan Post for automated mail sorting. These barcodes contain the address of the receiver encoded as a seven-digit postal code plus optional address data of up to 13 alphanumeric characters. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1106.html">PAGE 1106</a></h6> <p>these options won't apply to the Additional Content added to the physical NUp sheet. l l l l l l l Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Japan Post Properties group: l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Track height: The height of the small vertical centre bars, in metric (mm/cm).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1107.html">PAGE 1107</a></h6> <p>KIX Code (Dutch Post) Settings KIX code barcodes (also known as Klantenindex, or Dutch KIX 4-State), are used by Royal Dutch TPG Post (Netherlands) for Postal code and automatic mail sorting. They contain the address of the receiver, encoded in alphanumeric format (0-9, A-Z). Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1108.html">PAGE 1108</a></h6> <p>Up sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. KIX Code Properties group: l l Track height: The height of the small vertical centre bars, in metric (mm/cm). Value must be between 1 mm and 1.6 mm.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1109.html">PAGE 1109</a></h6> <p>PDF417 Settings PDF417 is a two-dimensional, multi-row Barcode. It is used for encoding large amounts of data, with hundreds or even thousands of characters. It encodes alphabetic text, numbers, binary files and actual data bytes. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1110.html">PAGE 1110</a></h6> <p>Up sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. PDF417 Properties group: l l Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1111.html">PAGE 1111</a></h6> <p>Note that with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~. l Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1112.html">PAGE 1112</a></h6> <p>l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1113.html">PAGE 1113</a></h6> <p>l l Numeric: 7089 numerical characters. l Alphanumeric: 4296 alphanumerical characters. l Byte: 2953 characters. l Kanji: 1817 Japanese/Chinese characters. Version: Select the preferred QR code version (which sets the data length field) from the 40 available. Note The Encoding and Version fields work together to determine how many characters are encoded within a length field. The following table shows the number of bits in a length field, based upon the selections made: Encoding l l l Ver.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1114.html">PAGE 1114</a></h6> <p>Note The Structured Append symbols Part number can never exceed the sum total of Structured Append symbols available (the "of" value). Thus selecting a Part number beyond the existing sum total will increase the sum total to the same value. l Use FNC1: Check to enable Application Identifiers. These are often used to encode links to websites, or to encode production/batch details.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1115.html">PAGE 1115</a></h6> <p>Royal Mail 2D Mailmark Settings Royal Mail 2D Mailmark Barcodes are a variant of 2 dimensional Datamatrix barcodes. They are used by the British Royal Mail postal service. They contain the address of the receiver, encoded in alpha-numeric format (0-9, A-Z). Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1116.html">PAGE 1116</a></h6> <p>Up sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Royal Mail 2D Properties group: l l Module Width: The size of each column and row within the barcode. Value must be between 0.5 mm and 0.7 mm.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1117.html">PAGE 1117</a></h6> <p>l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition. Royal Mail 4 State (CBC) Settings Royal Mail 4-State Customer Bar Code (CBC) is also known as the Royal Mail 4-State Customer Code (RM4SCC or RoyalMail4SCC). It is used by the British Royal Mail postal service. The barcode contains an address, encoded in alpha-numeric format (0-9, A-Z).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1118.html">PAGE 1118</a></h6> <p>l l Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Royal Mail Properties group: l l Track height: The height of the small vertical centre bars, in metric (mm/cm). Value must be between1.02 mm and 1.52 mm. Full bar height: Height of the tallest vertical bars, in metric (mm/cm). Value must be between4.22 mm and 5.84 mm.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1119.html">PAGE 1119</a></h6> <p>The content (or message) of the barcode consists of the following 6 parts (or fields), which are detailed here: Field Length Allowed Characters Format 1 [01234] Version ID 1 [1234] Class 1 [0123456789ABCDE] Supply Chain ID 2 [0123456789] Item ID 8 [0123456789] [ Destination Post Code 9 plus DPS 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ] The value "XY11 " is used for this field to specify an International Designation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1120.html">PAGE 1120</a></h6> <p>l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page. Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1121.html">PAGE 1121</a></h6> <p>This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields. l Condition: Enter the condition which determines whether or not the Barcode will be added to the document at print time. For details on how to create a conditional, see "How to Set Conditionals" on page 1220.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1122.html">PAGE 1122</a></h6> <p>Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries. This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1123.html">PAGE 1123</a></h6> <p>the Full and Track bar heights. l l l l Module width: Thickness of each bar in the Barcode, in metric (mm/cm). Value must be between0.38 mm and 0.63 mm. Module spacing: The spacing between each bar, in metric (mm/cm). Value must be between0.3 mm and 0.7 mm. Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1124.html">PAGE 1124</a></h6> <p>l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries. This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. Description edit box: An edit box for adding an optional Description to the Additional Content entry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1125.html">PAGE 1125</a></h6> <p>l l l l l l l Ignore: Ignore checksum calculations. Auto: Add a checksum character to the Barcode if the initial value does not validate. This is the default value. Check: Verify the Barcode has a valid checksum. Add: Calculate and add a checksum character to Barcode, regardless of current value. Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1126.html">PAGE 1126</a></h6> <p>UPC-E Settings The Universal Product Code (UPC-E) Barcode is widely used for tracking trade items in stores and at the point-of-sale. It consists of 6 numerical digits which are uniquely assigned to each trade item. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1127.html">PAGE 1127</a></h6> <p>Up sheet. l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. UPC A Properties group: l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Module Width: Specifies the width of the narrow bars.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1128.html">PAGE 1128</a></h6> <p>l l Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1129.html">PAGE 1129</a></h6> <p>l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1130.html">PAGE 1130</a></h6> <p>l l Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l l Font size: Enter a font size for the human readable text. Process Tilde: This selection is not applicable to this barcode type.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1131.html">PAGE 1131</a></h6> <p>Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1132.html">PAGE 1132</a></h6> <p>l USPS IMPB Properties group: l l l l l l l l Barcode height: The height of the bars in the barcode, in inches (in). Value must be between 0.075 and 1.0 inches. Module width: The thickness of thin bars in the barcode, in inches (in). Thicker bars are a multiple of this value. Value must be between 0.013 and 0.021 inches. Text to barcode clearance: The space between the barcode bars and the top and bottom text, in inches (in). Value must be between 0.125 and 0.25 inches.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1133.html">PAGE 1133</a></h6> <p>marks are completely independent and customizable. These custom OMR marks can be used to cater for inserter machines not currently supported by a HCF, or they can be used for any non-inserter related post-processing driven by OMR marks. l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1134.html">PAGE 1134</a></h6> <p>l Collation Level: Choices are: l l l l Document: Treats each document as a group and the group and match marks will be set based upon the start and end of a document. Document Set: Treats each document set as a group and the group and match marks will be set based upon the start and end of a document set. Draw Hot Spots: This adds a red rectangle around the location of each individual mark in the output, allowing easier checking of the OMR mark logic.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1135.html">PAGE 1135</a></h6> <p>l l Start: The starting point for the range l Stop: The end point of the range l Start number: The number to start from (from within the selected range). Match Number Range group: Allows selection of Start and Stop points for the wrapping match number for a group. For example, a range of 1-6, with a Start number of 2 would cause the matched numbers to be as follows: 2, 3, 4, 5, 6, 2, 3, 4, 5, 6, 2, ...</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1136.html">PAGE 1136</a></h6> <p>Note In a single page group both Group Start and End marks will print if defined since the page is both the start and end of the group. l l Sequence: This represents a mark that is printed when the specified bit is set in the sequence number of the page. For example, if the bit for the mark is set to 2 and the sequence number for the page is 5 then it will not print since the value 5 consists of the bits 1 and 4. Use the drop down box to select the entry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1137.html">PAGE 1137</a></h6> <p>l Move up: Move a entry up the table l Move down: Move a entry down the table l Edit: Edit a Conditional entry within the table. Tip You can also double click a Conditional entry within the table to edit it. How to Set Conditionals l Condition: Enter the condition which determines whether or not this element will be added to the document at print time. Use JavaScript conditional expressions to construct your conditional.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1138.html">PAGE 1138</a></h6> <p>[UserName]\Connect\workspace\configurations\JobCreationConfig Where [username] is replaced by the appropriate Windows user name. Actually, the path may not begin with 'C:\Users', as this is language-dependent. On a French system, for example, it would be 'C:\Utilisateurs'. Type %userprofile% in a Windows File Explorer and press Enter to open the actual current user's home directory. Once saved, Job Presets can be loaded in the Print Wizard, to have the Print Wizard use the selected Job values.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1139.html">PAGE 1139</a></h6> <p>l l l l l l l l l l l Has Grouping: Becomes Yes if grouping options are set in the "Grouping options" on page 1150. Page Count Splitting: Becomes Yes if page count splitting is used in the "Grouping options" on page 1150. Slip Sheets: Becomes Yes if a slip sheet is set in the "Grouping options" on page 1150. Options: These options are checked, or not, depending on the selected preset chosen in the Configuration name. l l Has Sorting: Becomes Yes if any "Sorting options" on page 1147 are set.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1140.html">PAGE 1140</a></h6> <p>These runtime parameters could be used in a number of ways. Such as in the following scenarios: Filtering rules scenarios A filter condition could be used to compare a date from the record against a date passed in as a runtime parameter. For instance, the record could have a due date, with only documents due in two weeks time to be selected.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1141.html">PAGE 1141</a></h6> <p>Metadata properties The value for a metadata property could be supplied through a runtime parameter. These could be, for example, the production date, or the name of the current operator. Page breakdown Runtime Parameters can be added, edited, removed, duplicated or moved within the Runtime Parameter table via the buttons to the right of the table. The Runtime Parameter options are: l l l l l Add: Click to open a new Runtime Parameter. This launches the Add/Edit Runtime Parameter dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1142.html">PAGE 1142</a></h6> <p>l l l Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard. Up until the Print button is pressed, one can reverse all the way through the wizard to return to the main selection page (the "Print options" on page 1158 page) and add or remove printing options from the print run.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1143.html">PAGE 1143</a></h6> <p>l Not any of the following. This equates to the logical operator (NOT (... OR ...)) If none of the associated criteria are met, then this group resolves to TRUE. The top level is always a group. A group can contain one or more Rules and/or Groups. Rule A Rule is a logic expression using a single operator or function, and their associated operand (s). The number and type of operands is dependent upon the operator or function chosen. Rules can also have different types.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1144.html">PAGE 1144</a></h6> <p>l l l l l l 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. 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.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1145.html">PAGE 1145</a></h6> <p>than using any finishing options that might have been set in the template's Print Context and Print Section options. These settings are only applied when producing print output. They do not modify the original finishing options in either the Section or the Template. Finishing settings can be set on various levels of Job Creation, such as Document Sets and Job Segments. This allows you, for example, to staple Document Sets whilst punching holes in Job Segments.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1146.html">PAGE 1146</a></h6> <p>l l l Location: Sets where the binding is to occur, if applicable. The selections available here will be dependent upon the selection made in the Binding Style. Only Stapled and Stitched bindings have a Location option available to them. Angle: Set Stapling or Stitching binding either horizontally, vertically, or at an angle (as supported by printer). Item count: Select the amount of Staples or Stitches to use.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1147.html">PAGE 1147</a></h6> <p>Sorting options This page appears as part of the Advanced Print Wizard and the "Job Creation Presets Wizard" on page 1137. The Sorting Options page is used to sort the records in the output. Sorting is done from the top to the bottom, one after the other. Sorting Settings l Use standard sort: Sort using the fields below: l Field Name: Use the drop-down to select which field to sort on. l Order: Use the drop-down to choose Ascending or Descending.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1148.html">PAGE 1148</a></h6> <p>selected. l Command: Enter either the full path of the executable file that will sort the CSV file, or a valid Windows command line instruction to sort the records. Placeholders can be used within this command, and are available via the Insert input/output file placeholder options (expressed as either ${input} or ${output}) or via Job Creation runtime Parameters (expressed as ${params.xxxx}, where the xxxx is the name of the runtime parameter).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1149.html">PAGE 1149</a></h6> <p>l Exported sort data group: l l First row of sort data has field names checkbox: select to have field names placed on the first line of the exported CSV file. Fields to export: Lists the fields to export in the CSV file. The buttons to the right of the table provide the following functionality: l Click to select from available datatfields. The Field Selection dialog will appear, which allows selection of one or several fields from those available. Click to remove a field from the list.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1150.html">PAGE 1150</a></h6> <p>l Sorting by selection box: Select whether the sorting will be by the returned sort order or whether it is to be sorted on a selected datafield. l Sequence Field selection box: Select the datafield to be sorted on, if such was chosen in the Sorting by entry. Grouping options This page appears as part of the Advanced Print Wizard and the "Job Creation Presets Wizard" on page 1137.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1151.html">PAGE 1151</a></h6> <p>l Size Grouping section: Check the checkbox to enable size grouping, which separates Documents into different groups, based upon their relative sizes. For example, selecting Document Set Grouping for the Grouping Level, Documents for the Item to group, Group by Page Count and then creating a page range from 1-5 and another page range 6 to Largest, will create two Document Set groups. The first will contain all Documents of 1 to 5 pages in length, and the second will contain any document of 6 or more pages.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1152.html">PAGE 1152</a></h6> <p>l l Meta data property edit box: Select a name for the meta data field that is created. This meta data field can then be used in other Print Wizard/Preset pages, such as in the Job Output Mask Dialog. Size Ranges: Add (or remove ) entries to this list to create new groups based upon the number of pages in the level selected above. All groups must be contiguous from 1-to-Largest and they must not contain any gaps. l l l Range Name: Enter a name identifying the range.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1153.html">PAGE 1153</a></h6> <p>Note Meta data properties have a length limitation of 255 characters. The meta data entries can be added to any of these levels, as indicated by the tabs on top: Job, Job Segment, Document, Document Set, and Page Tags. Note It is important to note that if Impositioning is used then the only meta data that will be available to the job thereafter will be the meta data at Job Segment level.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1154.html">PAGE 1154</a></h6> <p>Once loaded in the table, the meta data fields Tag Names can be modified as desired. As can the source they point to, in the case of runtime parameters and data fields. l l Delete: Click to delete the currently selected meta data entry. / Move Up / Move Down: Click to move the currently selected tag(s) one position up or down. Output Creation Presets Wizard The File > Print Presets > Output Creation Settings... dialog displays a list of available presets and a summary of their settings.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1155.html">PAGE 1155</a></h6> <p>l Properties: Displays a summary of the settings for this Output Creation Preset. l l l l l l Output Type: Displays the print technology used, as defined in the "Print options" on page 1158. Inserter: Indicates whether Inserter Marks have been added in the "Inserter options" on page 1231 dialog. Expand to see which High Capacity Feeder (HCF) model is loaded. Imposition: Indicates if Imposition has been set in the "Imposition options" on page 1222 dialog. Expand to see the specific imposition settings.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1156.html">PAGE 1156</a></h6> <p>Definition supports the extra information will have the Position, Weight, Type or Color options available. l l Map media by options: Select from following choices: This entry will only be available for those printers that support the extra information. l Media Attribute displays all Media details, except the Tray selection. l Tray displays just the Media name and Tray selections. l Both displays all Media details. Media/Tray Table columns: l Media: Lists the Media name, as defined in the template.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1157.html">PAGE 1157</a></h6> <p>l Output Destination group: These settings allow for the selection of output bins. It is available for PCL printers whose Printer Definition caters for multiple output bins. If the selected Printer Definition does not support bins, this group will not be visible on the page. The table has the following choices: l l l Trigger: Select what the trigger will be for changing bins. The options are >Page, >Sheet, >Document, >Document Set or >Job Segment.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1158.html">PAGE 1158</a></h6> <p>This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" below page have been completed or not. l Cancel button: Cancels the Print Wizard, without creating any printout. Print options The Print Options page is the first page of the Advanced Print Wizard (used for both Production and Proof printing in the Designer) and the second page of the "Output Creation Presets Wizard" on page 1154.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1159.html">PAGE 1159</a></h6> <p>with your specific printer. By default, Connect initially displays just a single generic PDF output option, to keep the interface clean. But other print output types can be added to the Printer Model drop-down list at any time via the Import Definitions button The Import Definitions options are: l l l Import Definition: Used to add any customized or tailored Printer Definition that Objectif Lune Inc. has prepared for you, specific to your printer.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1160.html">PAGE 1160</a></h6> <p>Output Mask Dialog. The Job Output Mask may contain (dynamic) folder names, for example: ${document.metadata['Country']}\${template}. The evaluated value of the Job Output Mask is taken as a path relative to the folder specified by the Job Output Folder (the next option in this dialog). The Job Output Folder must exist, but folders specified in the Job Output Mask will get created if they don't exist. l l LPR Queue: Select to send the print job to an LPR queue.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1161.html">PAGE 1161</a></h6> <p>l l Choose paper source by page size: Check to use the PDF page size to determine the output tray rather than the page setup option. This option is useful for printing PDFs that contain multiple page sizes on printers that have different-sized output trays. Scale: Chose from one of the following scaling options: l l l None: Select to not scale any page, whether it fits or not. Expand to printable area: Select to expand any page to fit the page area. Pages larger than the paper size are not re-sized.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1162.html">PAGE 1162</a></h6> <p>l Add additional content: Check to activate the "Additional Content" on page 1179 page of the wizard. Records (Not available in Output Creation Preset Wizard.) l l Record Range: Allows selection of a range of records or a custom selection. You can specify individual records separated by semi-colons (;) or ranges using dashes. For example: 2;4;6-10 would print pages 2, 4, 6, 7, 8, 9 and 10.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1163.html">PAGE 1163</a></h6> <p>This will change the Advanced Print Options to match the entries contained within the Preset. l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1164.html">PAGE 1164</a></h6> <p>l l E-invoice format PDF (PDF/A-3b) l Graphics format PDF (PDF/X-4 ) l Variable data printing format PDF (PDF/VT). Font Creation selection: The choices are: l Simple fonts when possible (smallest size). This is the default option. This option uses Simple fonts in cases where the fonts do not use too many characters. It automatically switches to using composite fonts when the number of characters becomes too large to fit a Simple font.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1165.html">PAGE 1165</a></h6> <p>Note Any pre Connect 2018.2 Output Presets will use the Simple Fonts default, unless updated in Connect 2018.2. l Embed standard fonts: Click to embed the 14 standard system fonts within the PDF output. This increases the output filesize but makes the PDF output truly portable. Such PDFs print as displayed on screen, regardless of whether the 14 standard fonts are present on the target printing system or not.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1166.html">PAGE 1166</a></h6> <p>l Meta data Group: Add optional Metadata to the PDF output. The fields that can be configured are the Title, Author, Description and Keywords. These metadata entries are those that are displayed in the Adobe Reader Document Properties dialog. The values for all the fields can be either static or dynamic (such as values obtained from datamapping) or a combination of both. l l l l l Title: Add the document name(s). This defaults to the existing document name. Author: Add the document author, if desired.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1167.html">PAGE 1167</a></h6> <p>be available. l l l l Add Signature button only becomes active once a Keystore has been added. Selecting this option opens the PDF Signature dialog for adding a new PDF signature to the Keystore. Edit: Click to edit the currently selected item. Either the Keystore or PDF Signature. Delete: Click to delete the currently selected item. Deleting the Keystore will also delete the associated Signature.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1168.html">PAGE 1168</a></h6> <p>l User Interface Options: Select which application interface options to hide, if any, from the following: l Hide menu bar l Hide tool bars l Hide windows controls Advanced Print Wizard and Output Creation Preset Wizard navigation options l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1169.html">PAGE 1169</a></h6> <p>Note JKS and JCEKS represent file based keystores in a Java proprietary format. The Java keytool command line application can be used to create and manage keystores in this format. Type PKCS#12 also represents a file based keystore, but in the PKCS#12 format. Type PKCS#11 represents a keystore on a hardware device. These hardware devices must first be setup in the "Hardware for Digital Signing preferences" on page 833 Preferences page, before they become available as an option in this dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1170.html">PAGE 1170</a></h6> <p>l Slot list index: Select which hardware slot to use. Note Slots are logical partitions in the hardware device. In case of Hardware Security Modules, there could be hundreds or more slots are available while in the case of smart cards, there would likely only be one slot available. Specifying both a Slot list index and a Slot ID is not allowed. Enter one or the other, or neither. l Slot ID: Select which hardware Slot ID to use. Note Slots are logical partitions in the hardware device.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1171.html">PAGE 1171</a></h6> <p>Note PlanetPress Connect currently supports only a single Digital Signature per PDF output file. l l l Name: Enter a name that describes the signature entry. Keystore name: Use the drop-down to select which keystore the signature is pulled from. These keystores are set in the "Keystore" on page 1168 dialog, called from the "PDF Options" on page 1163 page. Signature Properties group: These are optional Metadata fields associated with the signature, which can be omitted.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1172.html">PAGE 1172</a></h6> <p>l l Password: Password specific to the TSA server chosen. l Repeat Password: Repeat of password. Visible Signature: Check to add a visible signature to the PDF file. The signature is added to the specified page of each output file. The signature will be created using Arial 10pt black font. If this font does not exist on the production machine, a substitute font will be used. If the digital signature contents exceed the dimensions of the configured box, the text will be scaled down.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1173.html">PAGE 1173</a></h6> <p>Advanced Print Wizard navigation options l l l l Preview button: Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1174.html">PAGE 1174</a></h6> <p>l l None: No Tray Options specified. This is the default selection. SetPageDevice: This provides a table where one can allocate job Media to different types of print paper stock and assign them to the output via the SetPageDevice entry. The choices are a selection of common print stock Types and Colors. l l l Media column: The available job Media . These will initially be populated with the Job Media entries, but new Media can also be added via the Add button.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1175.html">PAGE 1175</a></h6> <p>information regarding it, and the following new dialog options become available: l Media: This box will initially be populated with any existing Media found in the current Template. You can add or remove Media, as you wish. The options available to the Media table are: l l l l Add: Add new Media entries. This launches the Dynamic Tray Mapping Editor Dialog to allow you to set the Media properties. Delete: Delete the selected Media from the table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1176.html">PAGE 1176</a></h6> <p>l Order column: This column displays any Dependency Order criteria that applies to the selected Printer Option. The choices available to the Printer Options are as follows: l l l l l Add: This launches the Add Printer Options Dialog which allows you to add one or more Printer Options. Edit: This allows you to edit an existing Rule Printer Option. It launches the Add Printer Options Dialog. / Move Up / Down: Move the selected Printer Option(s) up or down within the table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1177.html">PAGE 1177</a></h6> <p>To sort them into the correct dependance order, use the Sort by Order dependency button. This will sort them into the proper dependency sequence. As seen below, where the lower dependency now appears first. Warning Nothing prevents the selection of conflicting and contradictory Print Options.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1178.html">PAGE 1178</a></h6> <p>The breadth and diversity of PPD files as well as individual printer capabilities mean that the Print Wizard cannot meaningfully validate the selections made, and thus does not attempt to. So you must be careful when making selections. We recommend that you always test each individual selection made, to confirm that they are valid and that they do what you expected of them. This could entail considerable trial and error, but should lead to less anguish in the long run.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1179.html">PAGE 1179</a></h6> <p>Additional Content This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. The Additional Content page allows you to add content at the time of printing. There are four different types of Additional Content that can be added at print time: Text; Images; Barcodes and OMR Marks. They can be used to add either static content or variable content.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1180.html">PAGE 1180</a></h6> <p>l Include in Output: Indicates whether the entry is to be included in the output or not. The settings made in the Additional Content dialog box can be over-ridden here. This allows you to create a virtual "library" of Additional Content options in an Output Preset, from which you can then pick and choose from at time of printing. l Type: Displays an icon showing what type the Additional Content entry is. l Description: Displays the Description" that was entered in the Additional Content dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1181.html">PAGE 1181</a></h6> <p>This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1158 page have been completed or not. l Cancel button: Cancels the Print Wizard, without creating any printout. Additional Text Settings The Additional Text Settings dialog displays the property of Text added in the "Additional Content" on page 1179 page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1182.html">PAGE 1182</a></h6> <p>l Font group: l Font Name: Use the drop-down to select which font type to apply to the Text. The drop-down displays all the fonts installed on the system. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l Style: Choose between "Regular", "Italic", "Bold" or "Bold Italic". l Font Size: Enter the font size in points (pt). l Color: Select what color the Text will be.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1183.html">PAGE 1183</a></h6> <p>l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries. This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. Description edit box: An edit box for adding an optional Description to the Additional Content entry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1184.html">PAGE 1184</a></h6> <p>Note Transparent images are not supported. l l Preview group: This displays a preview of the selected Image. Scaling group: Scaling the image expands the image but keeps the aspect ratio. The amount of scale and specific limitations can be applied used a combination of the following options: l l l l Max Width: Enter the absolute maximum width the image can be scaled to, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1185.html">PAGE 1185</a></h6> <p>l "Data Matrix settings" on page 1193 l "EAN-13 Settings" on page 1198 l "EAN-13 Settings" on page 1198 l "GS1-128 Settings" on page 1195 l "Interleaved 2 of 5 Settings" on page 1203 l "Japan Post Settings" on page 1105 l "Japan Post Settings" on page 1105 l "PDF417 Settings" on page 1205 l "QR Code Settings" on page 1207 l "Royal Mail 4 State (CBC) Settings" on page 1117 l "Royal Mail 4 State (CBC) Settings" on page 1117 l "Royal Mail 4 State Mailmark C Settings" on page 1118 l "Ro</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1186.html">PAGE 1186</a></h6> <p>l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries. This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. Description edit box: An edit box for adding an optional Description to the Additional Content entry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1187.html">PAGE 1187</a></h6> <p>l l Default start symbol: Use the drop-down to select the optional Barcode start character, which defines the encoding mode. Default stop symbol: Use the drop-down to select the Barcode stop character, which defines the encoding mode. l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1188.html">PAGE 1188</a></h6> <p>Code 128 Settings Code 128 is a high-density barcode, used for alphanumeric or numeric-only barcodes. It supports all 128 ASCII characters. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1189.html">PAGE 1189</a></h6> <p>l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. l Code 128 Properties group: l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. l Module Width: Specifies the width of the narrow bars.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1190.html">PAGE 1190</a></h6> <p>added to the document at print time. For details on how to create a conditional, see "How to Set Conditionals" on page 1220. l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition. Code 39 Settings Code 39 is a discrete, self-checking barcode that is also known as "Alpha39", "Code 3 of 9" (often abbreviated to "3 of 9"), "Code 3/9", "Type 39", "USS Code 39" and "USD-3".</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1191.html">PAGE 1191</a></h6> <p>l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page. Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1192.html">PAGE 1192</a></h6> <p>l l l l l Check: Verify the Barcode has a valid checksum. Add: Calculate and add a checksum character to Barcode, regardless of current value. Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1193.html">PAGE 1193</a></h6> <p>Data Matrix settings A Data Matrix barcode is a high-density, two-dimensional (2D) matrix barcode which supports encoded text, numbers, files and digital data. Note In order to create a GS1 compliant Data Matrix barcode, the barcode data must meet the following requirements: l l l The barcode data must start with a leading FNC1 character. Either ~1 or ~d232. The GS1 Application Identifiers (AI) must be used for all data.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1194.html">PAGE 1194</a></h6> <p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1195.html">PAGE 1195</a></h6> <p>Note The following tilde codes are supported in GS1 DataMatrix barcodes: l l ~1 = FNC1 character (for GS1 DataMatrix barcodes) l ~2 = Structure Append l ~3 = Reader programming l ~5 = Macro5 l ~6 = Macro6 l ~7 = ECI expressions Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1196.html">PAGE 1196</a></h6> <p>options" on page 1152). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1197.html">PAGE 1197</a></h6> <p>l GS1-128 Properties group: l l l l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. Check Digit marker: This character is used as a placeholder for the check digit, which we be calculated at runtime. The character must be expressed in Hex. Group separator: This character is used to define group separation points.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1198.html">PAGE 1198</a></h6> <p>Note: with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~. l Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1199.html">PAGE 1199</a></h6> <p>l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1200.html">PAGE 1200</a></h6> <p>l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l l Font size: Enter a font size for the human readable text.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1201.html">PAGE 1201</a></h6> <p>l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries. This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. Description edit box: An edit box for adding an optional Description to the Additional Content entry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1202.html">PAGE 1202</a></h6> <p>checksum: l l l l l l l Ignore: Ignore checksum calculations. Auto: Add a checksum character to the Barcode if the initial value does not validate. This is the default value. Check: Verify the Barcode has a valid checksum. Add: Calculate and add a checksum character to Barcode, regardless of current value. Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1203.html">PAGE 1203</a></h6> <p>l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition. Interleaved 2 of 5 Settings Interleaved 2 of 5 barcodes are also known as "ITF" and "2/5 Interleaved". It is a numeric only barcode whose data must contain an even number of digits, as the barcode uses sequences of two digits interleaved with each other to create a single symbol.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1204.html">PAGE 1204</a></h6> <p>l l Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Interleaved 2 of 5 Properties group: l l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. Bar width ratio: Set the Barcode bar width.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1205.html">PAGE 1205</a></h6> <p>l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition. PDF417 Settings PDF417 is a two-dimensional, multi-row Barcode. It is used for encoding large amounts of data, with hundreds or even thousands of characters. It encodes alphabetic text, numbers, binary files and actual data bytes. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1206.html">PAGE 1206</a></h6> <p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1207.html">PAGE 1207</a></h6> <p>l Tilde processing Check this option to process tilde characters in the data as special characters. (See the Java4less Barcodes Guide to learn what the tilde character can be used for.) Note that with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~. l Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1208.html">PAGE 1208</a></h6> <p>libraries from which you can pick and choose what entries you wish to have included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1209.html">PAGE 1209</a></h6> <p>l l Auto: Automatically detect the data content and encodes using the most appropriate method. This is the default option. l Numeric: 7089 numerical characters. l Alphanumeric: 4296 alphanumerical characters. l Byte: 2953 characters. l Kanji: 1817 Japanese/Chinese characters. Version: Select the preferred QR code version (which sets the data length field) from the 40 available. Note The Encoding and Version fields work together to determine how many characters are encoded within a length field.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1210.html">PAGE 1210</a></h6> <p>l l Part: indicates the position of the QR Code symbol within the group of Structured Append symbols. of: indicates how many Structured Append symbols exist. Note The Structured Append symbols Part number can never exceed the sum total of Structured Append symbols available (the "of" value). Thus selecting a Part number beyond the existing sum total will increase the sum total to the same value. l Use FNC1: Check to enable Application Identifiers.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1211.html">PAGE 1211</a></h6> <p>to Set Conditionals" on page 1220. l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition. UPC-A Settings The Universal Product Code (UPC-A) Barcode is widely used for tracking trade items in stores and at the point-of-sale. It consists of 12 numerical digits which are uniquely assigned to each trade item. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1152).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1212.html">PAGE 1212</a></h6> <p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1213.html">PAGE 1213</a></h6> <p>character) are not supported in Connect. l l l Font size: Enter a font size for the human readable text. Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1214.html">PAGE 1214</a></h6> <p>l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries. This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. Description edit box: An edit box for adding an optional Description to the Additional Content entry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1215.html">PAGE 1215</a></h6> <p>l l l l l l l Ignore: Ignore checksum calculations. Auto: Add a checksum character to the Barcode if the initial value does not validate. This is the default value. Check: Verify the Barcode has a valid checksum. Add: Calculate and add a checksum character to Barcode, regardless of current value. Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1216.html">PAGE 1216</a></h6> <p>Additional OMR Mark Settings The Add OMR dialog displays the properties of an OMR Mark that was added in the "Additional Content" on page 1179 page. These OMR marks differ from High Capacity Feeder (HCF) generated inserter marks. Those marks are specific to the inserter machine they were created for, whereas these additional OMR marks are completely independent and customizable.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1217.html">PAGE 1217</a></h6> <p>l l Bottom: Enter the distance between the bottom margin of the page and the OMR Mark, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Options Tab: l Collation Level: Choices are: l l l l Document: Treats each document as a group and the group and match marks will be set based upon the start and end of a document. Document Set: Treats each document set as a group and the group and match marks will be set based upon the start and end of a document set.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1218.html">PAGE 1218</a></h6> <p>Note The Sequence Number iterates per page within a group and is used to identify missing pages in a group. l l Start: The starting point for the range l Stop: The end point of the range l Start number: The number to start from (from within the selected range). Match Number Range group: Allows selection of Start and Stop points for the wrapping match number for a group.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1219.html">PAGE 1219</a></h6> <p>l l l l On: This represents a mark that is always printed. Off: This represents a mark that is never printed; i.e. it pads the marks out with an empty position. Group Start: This represents a mark that is printed on the first page of a group. Group End: This represents a mark that is printed on the last page of a group. Note In a single page group both Group Start and End marks will print if defined since the page is both the start and end of the group.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1220.html">PAGE 1220</a></h6> <p>total number of other printed marks on the page is even in order to keep the overall count odd. Use the drop down box to select the entry. l Conditional: Enter the condition which determines whether or not this OMR Mark will be added to the document at print time.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1221.html">PAGE 1221</a></h6> <p>Booklet Options This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. The Booklet Options page defines how to generate booklets in the output. It is used in conjunction with Imposition settings, which will appear after the Booklet entries have been made. This page includes a handy illustration that displays how the final binding would look, based upon the current selections.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1222.html">PAGE 1222</a></h6> <p>l Back Cover selections: l l Blank: Select to add no data to the back cover. Last two pages on inside and outside: Select to use the final 2 pages as the inside and outside of the back cover. Advanced Print Wizard and Output Creation Preset Wizard navigation options l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1223.html">PAGE 1223</a></h6> <p>You can even select how many pages are to be represented, whilst page numbers appear on the pages in the diagram and change dynamically, like everything else. It is important to note that if Impositioning is used then the only meta data that will be available to the job thereafter will be the meta data at Job Segment level. When using Impositioning everything within the Segment is Impositioned, so all meta data below the Job Segment level is lost.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1224.html">PAGE 1224</a></h6> <p>If no template is loaded or if the template does not have a Print section, then the Sample Page defaults to A4 portrait. l l l l Orientation: Select orientation (aspect ratio) of the logical template page (Landscape or Portrait). The Width and Height values are real-only and appear for display and design purposes only. Imposition Sheet group: Use to select the physical media size that the logical pages will be printed upon.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1225.html">PAGE 1225</a></h6> <p>diagram: In this example the error is that the logical pages are too large to fit upon the Imposition Sheet that has been selected. l Position group: These settings apply to the positioning of the logical page(s) within the Imposition Sheet. l Method selection: Set the position of the logical page(s) upon the Imposition Sheet. The choices are as follows: l l l l l l Center: Have the logical page(s) centered within the Imposition Sheet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1226.html">PAGE 1226</a></h6> <p>Note If the logic page was set to Rotate in the Position selections, then the Horizontal selection might appear as vertical, and the Vertical selection might appear as horizontal, on the real time output diagram. l l l l Vertical selection: Set how many logical pages are to be placed on one vertical line within the Imposition Sheet. Horizontal Gap selection: Set the amount of blank space to add between each logical page on this axis.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1227.html">PAGE 1227</a></h6> <p>Each set of 5 Imposition Sheets is a discrete drill sorted nUp block that can be guillotined and stacked. The first 5 sheets encompass records 1-50, whilst the next 5 sheets encompass records 51-100.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1228.html">PAGE 1228</a></h6> <p>The following example is the same job but with a Horizontal repetition setting of 6: As you can see, the outputs are very different.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1229.html">PAGE 1229</a></h6> <p>Note If the Stack Depth is greater than the number of sheets in the entire job then you will get a single drill sorted block that can be guillotined and stacked to give the complete job in record order. l l Sides selection: Select how many sides of the Imposition Sheet are to be printed upon. Choice is between Simplex or Duplex. Method selection: In 2018.2 we introduced a new imposition page order for cut & stack impositioning that works with continuous feed devices: Stack by Column.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1230.html">PAGE 1230</a></h6> <p>l l l l Off. Output is not reversed. Stack upside down: Essentially turns the stack upside down by reversing the output imposition page sides. The last sheet becomes the first, and in the case of duplex imposition, the back sides become the front sides. For presets created in a version prior to Connect 2018.2, a "Reverse Pages" selection will apply this Stack upside down setting. Inverse page order: This impositions the output in the exact opposite order from what has been selected.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1231.html">PAGE 1231</a></h6> <p>l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1158 page have been completed or not. Cancel button: Cancels the Print Wizard, without creating any printout.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1232.html">PAGE 1232</a></h6> <p>l l l l Collation level: Select whether the markings will be made at Document level, or Document Set level. Print marks on back: Check to place the Inserter Marks on the rear of the page. Selective Inserts: If selective inserts are supported by the chosen Mark Configuration you can select what markings to include and whether those markings are to included based upon some conditional setting.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1233.html">PAGE 1233</a></h6> <p>through the wizard to return to the main selection page (the "Print options" on page 1158 page) and add or remove printing options from the print run. l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1158 page have been completed or not.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1234.html">PAGE 1234</a></h6> <p>l Show Page: Use the up and down arrows or type a page number to display a specific page within the document. Zoom in/out: Click to zoom in or out by 25% l l Zoom Level: Use the drop-down to select a predefined level or enter a zooming percentage. Selective Insert Dialog The Selective Insert Dialog provides control over individual inserts. In this dialog the selected can be set to be either selected ("Yes") or not ("No"), or selected based upon some conditional criteria ("Conditional").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1235.html">PAGE 1235</a></h6> <p>l l Media Attribute displays all Media details, except the Tray selection. l Tray displays just the Media name and Tray selections. l Both displays all Media details. Media/Tray Table columns: l Media: Lists the Media name, as defined in the template. l Tray: Use the drop-down to select in which Tray to send any page using the media. l l l l l Position: Enter a MediaPosition option on the printer to define the media to use.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1236.html">PAGE 1236</a></h6> <p>l l l Trigger: Select what the trigger will be for changing bins. The options are >Page, >Sheet, >Document, >Document Set or >Job Segment. Destination: Select which bin should be used when this trigger is met. The options will be the bins available to the selected Printer Definition. Rules: Defaults to true, but can be altered at will. Double clicking in the field brings up the Rule Editor, which can be used to construct the rule(s) that determines whether this bin is to be used or not.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1237.html">PAGE 1237</a></h6> <p>Dynamic PPD Options This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. The Dynamic PPD mode options page allows you to add PostScript printer capabilities to Connect, through the printer's associated PostScript Printer Definition (PPD) file, and to assign rules to them to trigger those capabilities in conjunction with Connect Templates.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1238.html">PAGE 1238</a></h6> <p>This is not considered good practice, however. It would be better to return to the Printer Model selection dialog and chose the correct Printer Model and PPD combination there. PostScript Options PostScript specific options that are not catered for by the PPD. l Rotate landscape pages checkbox: For certain printers, printing in landscape orientation requires rotating the page content. Typically this cannot be derived from the PPD, nor does the PPD contain instructions for carrying out this rotation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1239.html">PAGE 1239</a></h6> <p>If a Media/Trays Rule has an associated Printer Option that matches a Media entry in the Template or Presets, then it is highlighted in light green. It is possible to create a set of Rules in which none of the Rules ever evaluate to true, and thus no Rule will be applied. This could be done on purpose, to allow the printer's default settings to apply. The types of Rules are as follows: l JCL (Job Control Language) Rules: This option only appears if the PPD contains a "*JCL keywords" section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1240.html">PAGE 1240</a></h6> <p>Once the Media/Trays are entered you will need to assign specific Printer Options (from those contained in the PPD) to the individual Media/Tray types. l Finishing Rules: This allows you to set Finishing options. These settings will be pre-populated from settings contained within the current Connect Template, if such exist. They can also be added from Job Creation Presets and other Templates, selected using the Import button. You can import settings from as many Templates as you like.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1241.html">PAGE 1241</a></h6> <p>settings from, whilst Finishing settings can also be imported from Job Creation Presets. The settings will be added to those already in the Rules table. l Add: This allows you to Add various options, dynamically. What options are available is dependant upon what rule is currently selected. For example, the Plex group does not have an option to Add Rules available to it. 1. Add Rule: This will add a Rule that is specific to the type of option was selected when the Add Rule was pressed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1242.html">PAGE 1242</a></h6> <p>You should add Printer Options for each of the Rules added.See the "Printer Options" on the next page section for how to do this. 2. Add Custom Group: This launches the Custom Group Editor Dialog which adds a new Custom Group entry, and associated Trigger. 3. Add Media/Trays Group: This adds a new blank Media/Trays entry. To add the actual Rule details you must select the new Media/Tray entry and then select the Add Rule option. 4. Add Finishing Group: This adds a new blank Finishing entry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1243.html">PAGE 1243</a></h6> <p>For Media/Trays, Finishing and Plex selections only the Properties are displayed. For Custom selections, the Condition can also be displayed. The tabs can be broken down as follows: l Properties Tab: displaying all the relevant Rule Details. These are: l l Property: The list of properties available to this Rule. What properties are displayed is dependent upon the type of Rule selected. Value: The property's associated value, if set. If not set, the Value will remain blank.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1244.html">PAGE 1244</a></h6> <p>Add custom PostScript: This launches the Add Custom Printer Option dialog which l allows you to add customized PostScript instructions. Note that this option requires an in depth understanding of both the PostScript language and the specific printer itself. l l l l Edit: This allows you to edit an existing Rule Printer Option. It launches the Add Printer Options Dialog. / Move Up / Down: Move the selected Printer Option(s) up or down within the table.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1245.html">PAGE 1245</a></h6> <p>To sort them into the correct dependance order, use the Sort by Order dependency button. This will sort them into the proper dependency sequence. As seen below, where the lower dependency now appears first. Warning Nothing prevents the selection of conflicting and contradictory Print Options.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1246.html">PAGE 1246</a></h6> <p>the Print Wizard cannot meaningfully validate the selections made, and thus does not attempt to. So you must be careful when making selections. We recommend that you always test each individual selection made, to confirm that they are valid and that they do what you expected of them. This could entail considerable trial and error, but should lead to less anguish in the long run.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1247.html">PAGE 1247</a></h6> <p>Documents, Document Sets or Job Segments. l Split: Use the drop-down to select whether or not to split the job based on number of Sheets, Documents, Document Sets or Job Segments. l l l l l Every: Enter the number of Sheets, Documents, Document Sets or Job Segments at which the output is to be split. This option is only available if the Split entry has been set to "At Exactly". Use the drop-down box to chose what the separation option is to be.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1248.html">PAGE 1248</a></h6> <p>Advanced Print Wizard and Output Creation Preset Wizard navigation options l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1249.html">PAGE 1249</a></h6> <p>features are subsequently available. For more keyboard shortcuts, see "Keyboard shortcuts" on page 1005. Designer API The "Standard Script API" on the facing page describes the objects and functions that are available in template scripts, created inside the Scripts pane. Template scripts change the contents of sections in a template. Note In a Print context, the scripts in the Scripts pane run once for each section and once for each Master Page (see "Master Pages" on page 478).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1250.html">PAGE 1250</a></h6> <p>Standard Script API This page lists the global objects and functions that are available in Standard Scripts, created inside the Scripts pane. Click through to an object or function to get a description and examples. Most of these objects and functions are also available in Control Scripts ("Control Scripts" on page 879) and Post Pagination Scripts ("Post Pagination Scripts" on page 894).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1251.html">PAGE 1251</a></h6> <p>Object Description locale Defines which locale to use. (See "Locale" on page 760.) Note that the value is read-only. "formatter" on page 1257 Global object that allows you to format values (such as a date or number). "automation" on page 1357 This object encapsulates the properties of the Workflow process that triggered the current operation. Not available in PrintShopMail Connect. "merge" on page 1410 The merge object is mainly used in Control Scripts.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1252.html">PAGE 1252</a></h6> <p>Function Description "loadjson()" on page 1268 Loads JSON data from a URL. This is a simple way to retrieve content from external systems. "query()" on page 1275 Performs a query in the template's contents and creates a new result set containing the HTML elements that match the given CSS selector. "resource()" on page 1365 This function returns information about an image resource. It can also be used to check if a file exists.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1253.html">PAGE 1253</a></h6> <p>each(callback) Iterates over the elements in a set, such as the enumerable properties of an object, in arbitrary order. For each distinct property, statements can be executed. callback A function. The callback function is passed the iteration index and the current element. In the scope of the callback function, this refers to the current element. Examples The following scripts demonstrate a simple iteration over the elements in the results (the set of HTML elements that match the selector of the script).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1254.html">PAGE 1254</a></h6> <p>Selector Matched element Matched element after script execution p <p></p> <p></p> <p></p> <p>0</p> <p>1</p> <p>2</p> Using each() in a translation script The following script first loads a snippet containing translation strings, depending on the value of a field. Then it inserts translations by iterating over elements in the results (the set of HTML elements that match the selector of the script) and setting the HTML of each element with a value from the array of translation strings.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1255.html">PAGE 1255</a></h6> <p>When a script calls this function in Preview mode, the script that triggers it is marked with an error icon in the Scripts pane, and the given message is displayed in a hint. When generating output from the Designer, the Designer will log the error and display an error dialog with the given message. Content creation is aborted. When generating output from Workflow, the job fails.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1256.html">PAGE 1256</a></h6> <p>Selector Matched element Matched element after script execution <p>last</p> <p>email</p> This script iterates over fields in the current record, retrieving their values. Then it adds the values to a paragraph. for(var i in record.fields){ results.after("<p>" + record.fields[i] + "</p>"); } Selector Matched element Matched element after script execution #test <h1 id="test">Fields</h1> <h1 id="test">Fields</h1> <p>Peter</p> <p>Parker</p> <p>pparker@localhost.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1257.html">PAGE 1257</a></h6> <p>results.append("<option value='" + str + "'>" + str + "</option>"); } formatter The formatter is a global object that allows you to format values in a script. The Text Script Wizard also allows you to format variable data; see "Using the Text Script Wizard" on page 780 and "Formatting variable data" on page 784. Note The TextFormatter object is now deprecated and will eventually be removed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1258.html">PAGE 1258</a></h6> <p>Function l dateTimeMedium() l dateTimeShort() l timeLong() l timeMedium() l timeShort() l lowerCase() l upperCase() l properCase() Description The text formatting functions are used on Strings. lowerCase() transform all characters to lowercase, upperCase() transforms all characters to uppercase and properCase() transforms the first character of each word to uppercase and all other characters to lowercase.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1259.html">PAGE 1259</a></h6> <p>Tip To format a date from a date field in the record set, you can enter a custom pattern via the Text Script Wizard; see "Using the Text Script Wizard" on page 780, "Formatting variable data" on page 784 and "Date and time patterns" on page 1262). date(value, pattern) Formats a date object using a custom pattern. value A Date object. A Date can contain a date and time. pattern String.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1260.html">PAGE 1260</a></h6> <p>dateTime(value, pattern) Formats a date and time object using a custom pattern. value A Date object. A Date can contain a date and time. pattern String. The custom pattern may consist of pattern letters, separating symbols and quoted text, for example: "yyyy.MM.dd G 'at' HH:mm:ss z"; see "Date and time patterns" on page 1262. Note that the repetition of pattern letters determines the exact presentation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1261.html">PAGE 1261</a></h6> <p>pattern String. The custom pattern may consist of pattern letters, separating symbols and quoted text, for example: "'at' HH:mm:ss z"; see "Date and time patterns" on the facing page. Note that the repetition of pattern letters determines the exact presentation. timeLong(value) Formats a time as long string representation, for example 12:00:00 EDT AM. value A Date object. A Date can contain a date and time. timeMedium(value) Formats a time as medium string representation, for example 12:00:00 AM.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1262.html">PAGE 1262</a></h6> <p>Creating a Date object from a string In a data mapping configuration you can set the type of a field to Date, but when you open a data file or database in the Designer without a data mapping configuration, all fields are text fields (fields of the type string). The formatter cannot be used to format a string with a particular date format. The solution is to store the string in a variable as a Date object, and use the formatter with that variable. The following sample script demonstrates this solution.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1263.html">PAGE 1263</a></h6> <p>Text Script Wizard" on page 780 and "Formatting variable data" on page 784. In the Script Editor, the pattern can be passed to a date, dateTime or Time function of the formatter; see "formatter" on page 1257. The custom pattern may consist of pattern letters (see below), for example: "MM/dd/yyyy". The components can be separated with a space or a symbol, e.g. ., /, -. Text must be put in quotes. The repetition of pattern letters determines the exact presentation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1264.html">PAGE 1264</a></h6> <p>k Hour in day (1-24) Number 24 K Hour in am/pm (0-11) Number 0 h Hour in am/pm (1-12) Number 12 m Minute in hour Number 30 s Second in minute Number 55 S Millisecond Number 978 z Time zone General time zone Pacific Standard Time; PST; GMT-08:00 Z Time zone RFC 822 time -0800 zone X Time zone ISO 8601 time -08; -0800; -08:00 zone Note These date and time pattern letters and patterns conform to standard Java notation. For more information, see http://docs.oracle.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1265.html">PAGE 1265</a></h6> <p>Tip To load a JavaScript file (.js) or a style sheet (.css) you can use loadtext(). See "loadtext()" on page 1269. Tip External content is not loaded while editing a script. To test a script that loads external content, you can do a preflight; see "Doing a Preflight" on page 855. loadhtml(location) Loads all HTML from the specified HTML file. location String containing a path that can be absolute or relative to the section/context.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1266.html">PAGE 1266</a></h6> <p>Examples This script loads a local HTML snippet (from the Resources panel) directly into the matched elements results.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.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1267.html">PAGE 1267</a></h6> <p>String 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>.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1268.html">PAGE 1268</a></h6> <p>The next script loads a remote snippet (see "Remote snippets" on page 715), looks for an H1 heading and uses that text. var post = loadhtml('snippets/post.rhtml'); var h1 = query('h1', post).text(); results.text(h1); Another example is given in the following how-to: Using a selector to load part of a snippet. loadjson() Creates a JSON object based on the text retrieved from the supplied location. The function lets you retrieve content from a JSON enabled server using a standard HTTP request.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1269.html">PAGE 1269</a></h6> <p>Examples This sample script retrieves JSON data from a snippet. var localJSON = loadjson('snippets/jsonsnippet.json'); if(localJSON.post){ results.html("<h3>" + localJSON.post.title + "</h3><p>" + localJSON.post.modified + "</p>"); } This script retrieves a post from a WordPress site. var wpPost = loadjson('http://192.168.101.58/2013/06/leave-thethird-dimension-behind-and-focus-on-real-printinginnovation/?json=1'); if(wpPost.post){ results.html("<h1>" + wpPost.post.title + "</h1>" + wpPost.post.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1270.html">PAGE 1270</a></h6> <p>Skin/Formats/CrossReferencePrintFormat("loadhtml()Loads HTML content from the specified HTML file. The file may be located inside the template (see Skin/Formats/CrossReferencePrintFormat("Snippets" on page 1)) or hosted on a Content Management System or on another location outside the template.An optional selector allows you to retrieve only the content of matching elements.The specified HTML file is expected to be UTF-8 encoded.Loadhtml() is cached per batch run (based on the URL) in print/email.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1271.html">PAGE 1271</a></h6> <p>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 page 1)).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1272.html">PAGE 1272</a></h6> <p>the host is "localhost", it can be omitted, resulting in file:///<path>, for example: file:///c:/somefolder/somecontent.js. Examples This script loads a JavaScript file (from the Resources pane) directly into a <script> element. var js = loadtext("js/my-script.js"); results.append(query("<script>").text(js)); The following script loads a style sheet (from the Resources pane) into the <style> element. var css = loadtext("css/my-styles.css"); results.append(query("<style type='text/css'>").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1273.html">PAGE 1273</a></h6> <p>Tip For fields that contain a number, you can also enter a formatting pattern via the Text Script Wizard; see "Using the Text Script Wizard" on page 780, "Formatting variable data" on page 784 and "Number patterns" on the facing page). currency(value) Formats a number as an amount of money. Which currency symbol and which thousands separator are used depends on the Locale; see "Locale" on page 760. value A number.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1274.html">PAGE 1274</a></h6> <p>grouped(value) Formats a number using a thousands separator. Which separator is used depends on the Locale, see "Locale" on page 760. value A number. This can be a value from a field that contains a SmallInteger, BigInteger, Float, SmallCurrency or LargeCurrency. Number patterns Numbers, used in a template and originating from a field in a record set, can be displayed using a custom pattern.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1275.html">PAGE 1275</a></h6> <p>E Number Number Separates mantissa and exponent in scientific notation. Need not be quoted in prefix or suffix. ; Subpattern boundary Number Separates positive and negative subpatterns % Prefix or suffix Number Multiply by 100 and show as percentage \u2030 Prefix or suffix Number Multiply by 1000 and show as per mille value ¤ (\u00A4) Prefix or suffix Number Currency sign, replaced by currency symbol. If doubled, replaced by international currency symbol.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1276.html">PAGE 1276</a></h6> <p>Note The query() function can't be used in a Control Script, since Control Scripts don't have access to the DOM. query(selector) Creates a new result set containing the HTML elements in the current section that match the supplied CSS selector. selector A String containing a CSS selector. See https://www.w3schools.com/cssref/css_selectors.asp for CSS selectors and combinations of CSS selectors. Examples Look for an element with a certain ID This scripts applies a style rule to the queried elements.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1277.html">PAGE 1277</a></h6> <p>selector A String containing a CSS selector. See https://www.w3schools.com/cssref/css_selectors.asp for CSS selectors and combinations of CSS selectors. context A result set (the result of another query) or an HTML string. If the passed context is not a result set or HTML string it will be coerced to a String and interpreted as HTML. Examples This script performs a query in the results of another query.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1278.html">PAGE 1278</a></h6> <p>Tip The Dynamic Attachment script uses this function to add an attachment to an Email section; see "Email attachments" on page 510. record The record object gives access to the record that is currently being merged with the template. Properties Field Type Description fields Array The field values that belong to this record. You can access a specific field value using either a numeric index or the field name: record.fields['fieldname'] or record.fields.fieldname. id Number The id of this record.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1279.html">PAGE 1279</a></h6> <p>} else { results.hide(); } In a Control Script, an entire section could be enabled or disabled based on the same condition: if (record.fields["Country"] == "CANADA") { merge.template.contexts.PRINT.sections["Section 1"].enabled = true; } else { merge.template.contexts.PRINT.sections["Section 1"].enabled = false; } (For more information about Control Scripts, see "Control Scripts" on page 879.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1280.html">PAGE 1280</a></h6> <p>} else { results.hide(); } Note This object can't be used in Control Scripts, because they don't have a selector. Tip The easiest way to access the elements in a result set one by one, is by setting the scope of the script to "Each matched element" and using the this object (see "this" on page 1317). Property Field Type Description length Number Number of elements in this result set. Equivalent to calling size().</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1281.html">PAGE 1281</a></h6> <p>Function Description "append()" on page 1326 Inserts content at the end of each element in a set of HTML elements. "attr()" on page 1329 Change the given attribute of the element or set of HTML elements with the given value. "before()" on page 1330 Inserts content before an element or before each element in a set of HTML elements. "children()" on page 1332 Returns the immediate children of an HTML element.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1282.html">PAGE 1282</a></h6> <p>Function Description "hasClass()" on page 1339 Returns true if the first element in this result set has the specified class. "height()" on page 1340 Gets or sets the outer height of an element, including padding and borders. "hide()" on page 1341 Hides the HTML element or set of HTML elements. "html()" on page 1341 Replaces the inner HTML of the element or of each element in a set of HTML elements with the supplied value, or returns the HTML of the first element if no value is supplied.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1283.html">PAGE 1283</a></h6> <p>Function Description "removeAttr()" on page 1350 Removes the specified attribute from each element in this result set. "removeClass ()" on page 1350 Removes the specified class from an element or from each element in a set of HTML elements. Has no effect if the class is not present. "replaceWith ()" on page 1351 Replaces an HTML element or a set of HTML elements (with a snippet, for example). Returns the result set. "show()" on page 1351 Shows the HTML element or a set of HTML elements.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1284.html">PAGE 1284</a></h6> <p>(see "this" on page 1317 and "Setting the scope of a script" on page 849). l The elements returned by a query in the template (see "query()" on page 1275). add(content) The add() function adds HTML content to one or more HTML elements and returns the union of this result or result set and other content. content A query result. This can be an HTML string or a result set. Examples Add one result set to another This script adds one query result to another and sets the background color to yellow.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1285.html">PAGE 1285</a></h6> <p>Selector Matched element Matched element after script execution <p>Lorem ipsum...</p> <h1>Chapter 2</h1> <p>Lorem ipsum...</p> <h1>Chapter 3</h1> <p>Lorem ipsum...</p> <h1>Chapter 4</h1> <p>Lorem ipsum...</p> addClass() Adds the specified class(es) to one ore more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1286.html">PAGE 1286</a></h6> <p>The following script adds two class names to a paragraph. results.addClass("foo bar"); Selector Matched element Matched element after script execution p <p>Hello world</p> <p class="foo bar">Hello world</p> after() Inserts content after one or more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1287.html">PAGE 1287</a></h6> <p>This script looks up an element with the ID #salesrep, sets its text color to red and inserts a paragraph after it. query("#salesrep").after("<p>Lorem ipsum</p>").css("color","red"); Matched element Matched element after script execution <p id="salesrep">Peter Parker</p> <p id="salesrep" style="color: red;">Peter Parker</p> <p>Lorem ipsum</p> Note: the way the functions after() and css() are used in this script is called 'chaining'.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1288.html">PAGE 1288</a></h6> <p>This script looks up an element with the ID #salesrep and inserts a string after it. The string is automatically enclosed in a span. query("#salesrep").after("Lorem Ipsum"); Matched element Matched element after script execution <p id="salesrep">Peter Parker</p> <p id="salesrep">Peter Parker</p> <span>Lorem Ipsum</span> append() Insert content at the end of one or more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1289.html">PAGE 1289</a></h6> <p>Selector Matched element Matched element after script execution #box <div id="box"> <h1>Personal information</h1> </div> <div id="box"> <h1>Personal information</h1> <p>Peter Parker</p> </div> This script appends a string to the results (the HTML elements that match the selector of the script). The string is added to the end of the matched element(s) and wrapped in a Span element. results.append("Peter Parker"); Selector Matched element Matched element after script execution .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1290.html">PAGE 1290</a></h6> <p>The following script appends a snippet to a Div element with the ID box. var a = loadhtml('snippets/snippet_name.html'); results.append(a); Selector Matched element Matched element after script execution #box <div id="box"> <h1>Personal information</h1> </div> <div id="box"> <h1>Personal information</h1> <p>Peter Parker</p> </div> This script looks for an element with the ID box and appends a paragraph to it. query("#box").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1291.html">PAGE 1291</a></h6> <p>var box = query("#box"); box.append("<p>Peter Parker</p>"); box.css("color","red"); attr() attr(attributeName) : String Returns the value of the specified attribute of an HTML element which can be: l l l The first element in a set of elements that match the selector of a script (see "results" on page 1395). One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1292.html">PAGE 1292</a></h6> <p>Examples This script looks up an image in an element with the ID #calloutbox and sets its alternative text to a value from a data field. var altText = record.fields.FavHobby; query("#callout img").attr('alt', altText); The following script sets the background color of a specific table cell in an email to red if the value of the field TOTAL has a negative value in the current record. if(record.fields.TOTAL<0) { query("#total").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1293.html">PAGE 1293</a></h6> <p>results.before("<p>Lorem Ipsum</p>"); Selector Matched element Matched element after script execution #salesrep <p id="salesrep">Peter Parker</p> <p>Lorem ipsum</p> <p id="salesrep">Peter Parker</p> This script does the same, but it uses the query() function to look up the element. query("#salesrep").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1294.html">PAGE 1294</a></h6> <p>Matched element Matched element after script execution <p>ipsum dolor sit amet, consectetur adipiscing elit.</p> <p><span>Lorem </span>ipsum dolor sit amet, consectetur adipiscing elit.</p> The following script looks for an element with the ID salesrep and inserts the text "Lorem Ipsum" before that element. "Lorem Ipsum" is automatically wrapped in a Span element. query("#salesrep").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1295.html">PAGE 1295</a></h6> <p>clone() This function returns a copy of one HTML element or of a set of HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395). One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849). The elements returned by a query in the template (see "query()" on page 1275). See also: "Dynamically adding sections (cloning)" on page 889.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1296.html">PAGE 1296</a></h6> <p>["ItemTotal"]); this.find('@ItemDesc@').text( record.tables['detail'][i].fields ["ItemDesc"]); this.find('@nr@').text(i); }); The following script clones and populates a boilerplate row. Once completed you will need to hide the boilerplate row. for(var i = 0; i < record.tables['detail'].length; i++) { var row = results.clone(); //Clone our boilerplate row row.find('@ItemNumber@').text( record.tables['detail'][i].fields ["ItemNumber"]); row.find('@ItemOrdered@').text( record.tables['detail'][i].</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1297.html">PAGE 1297</a></h6> <p>To get a child element or all child elements, use children() (see "children()" on page 1332). The closest() command is based on the closest() command found in the jQuery library: https://api.jquery.com/closest/. closest(selector) For one HTML element or for each element in a set, this function gets the first element that matches the selector by testing the element itself and traversing up through its ancestors in the DOM tree. selector A String containing an HTML tag (without the angle brackets, <>).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1298.html">PAGE 1298</a></h6> <p>l l One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849). The first element in a set of elements returned by a query in the template (see "query()" on page 1275). propertyName String; the name of the CSS property. Examples This script stores the text color of the results (the HTML elements that match the selector of the script) in a variable. var textcolor = results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1299.html">PAGE 1299</a></h6> <p>if(record.fields.accounttype == "PRO") { query("#callout p").css("color","red"); } This script sets the text color of the results to a hexadecimal color code. results.css('color' , '#669900'); This script loads a snippet into a variable. Then it finds/replaces text in the snippet and applies a css property to the replacing text. ar mysnippet = loadhtml('snippets/snippet vars.html'); v mysnippet.find('@var@').text('OL Connect').css('textdecoration','underline'); results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1300.html">PAGE 1300</a></h6> <p>l l l The elements that match the selector of a script (see "results" on page 1395). One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849). The elements returned by a query in the template (see "query()" on page 1275). Use "remove()" on page 1348 to remove the elements themselves. Example This script empties all Span elements found in the template. results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1301.html">PAGE 1301</a></h6> <p>Example The selector of the following script is li (list item), so the results object contains all list items in the template. The scripts filters the third and sixth line items from the results, taking advantage of the index that is passed to the filter function, and colors them red. It uses the modulus operator (%) to select every item with an index value that, when divided by 3, has a remainder of 2. (The index starts counting at zero.) results.filter(function(index) { return index % 3 === 2; }).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1302.html">PAGE 1302</a></h6> <p>Example The following piece of code loads a snippet, then looks for placeholders using find(), and replaces them with a text. var mysnippet = loadhtml('snippets/snippet.html'); mysnippet.find('@var1@').text('OL Connect 1'); mysnippet.find('@var2@').html('<i>OL Connect 2</i>').css('textdecoration','underline'); results.replaceWith(mysnippet); get(index) Returns the element found at the supplied index in a set of HTML elements. index Place of the element in the result set. The index starts counting at zero.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1303.html">PAGE 1303</a></h6> <p>Example This script checks if the first of the results (the set of elements matching the selector of the script) has the class 'green'. If so, it colors the text of all the elements in the results green. if (results.hasClass('green')) { results.css('color', 'green'); } height() Gets or sets the outer height, including padding and borders, of an HTML element, or of the first element in a result set (see "results" on page 1395), i.e.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1304.html">PAGE 1304</a></h6> <p>The following script does the same, but in this case, margins are included. ar h = results.height(true); v var w = results.width(true); h = h + 20; w = w + 20; results.height( h, true); results.width( w, true); hide() Hides one or more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1305.html">PAGE 1305</a></h6> <p>l l l The first element in a set of elements that match the selector of a script (see "results" on page 1395). One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849). The first element in a set of elements returned by a query in the template (see "query()" on page 1275). html(value) Replaces the inner HTML of an HTML element or of each element in a result set with the supplied value.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1306.html">PAGE 1306</a></h6> <p>This function can only be used in a Post Pagination Script ; see "Post Pagination Script API" on page 1389. For an example see: "Creating a Table Of Contents" on page 896. overflows() The overflows() method returns a boolean value indicating whether an HTML element overflows its box boundaries. This function could for instance be used in a design where content needs to flow separately from the main text flow, or where a new, full-page, multi-column box should be inserted when the current one overflows.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1307.html">PAGE 1307</a></h6> <p>The following script selects three boxes that all have the class box (selector: .box). It loops over them, inserting as many products from an array as possible into the box. In fact, it inserts one too many and removes the last one before moving on to the next box. var products = ["Appetizer","Beans","Beef","Lettuce","Sprouts","Coconut","Juice"," Soup","Coriander","Cheese","Pasta","Sugar","Vinegar","Bread"]; var i = 0; results.each( function() { // Add elements to the box until it overflows. while ( ! this.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1308.html">PAGE 1308</a></h6> <p>The first line creates a variable for the table of contents, which will be a list (a <ul> element with the ID toc). The start tag of the list is added to the variable. The next line does a query for all level 1 headings (<h1> elements) with the class title in the current section. With each() the script loops through them. For each of the headings it adds a line item to the list, with the text (this.text()) and the page reference of the respective heading.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1309.html">PAGE 1309</a></h6> <p>Example Assume that there are three paragraphs in a Box and that one of those paragraphs matches the selector of this script. The paragraph is stored in the results object (see "results" on page 1395). The following script retrieves the Box (which is the parent of the paragraph) using results.parent(), and then changes its background color to red. results.parent().</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1310.html">PAGE 1310</a></h6> <p>Selector Matched element Matched element after script execution #box <div id="box"> <p>Peter Parker</p> </div> <div id="box"> <h1>Personal information</h1> <p>Peter Parker</p> </div> This script inserts a heading as the first element in an element that has the class name. results.prepend("<b>Name: </b>"); Selector Matched element Matched element after script execution .</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1311.html">PAGE 1311</a></h6> <p>Selector Matched element Matched element after script execution div <div id="box"> <p>Peter Parker</p> </div> <div id="box"> <h1>Personal information</h1> <p>Peter Parker</p> </div> This script uses the function query() to find a box. Then it inserts a heading as the first element in that box. query("#box").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1312.html">PAGE 1312</a></h6> <p>var box = query("#box"); box.prepend("<p>Peter Parker</p>"); box.css("color","red"); remove() Removes the current element or each element in a set from the DOM. This function returns a new result set containing each removed element. These can be changed and inserted in the document. This could be beneficial in terms of performance, as manipulating elements inside the DOM is relatively time consuming. Examples This script removes all Span elements found in the template. results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1313.html">PAGE 1313</a></h6> <p>var cells = row.children(); cells[0].html("some text").css("background-color", "yellow"); cells[1].html("some text").css("font-weight", "bold"); cells[2].html("some text"); // Create a number of copies var rows = row.clone(); for (var i = 0; i < 30; i++) { rows = rows.add(row.clone()); } // Attach all copies to the DOM as children of tbody results.append(rows); removeAttr() Removes the specified HTML attribute from an element or from each element in a set of elements.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1314.html">PAGE 1314</a></h6> <p>Examples This script removes the class name "foo" from all elements in the results that have this class. results.removeClass("foo"); Selector Matched element Matched element after script execution p <p class="foo">Hello world</p> <p>Hello world</p> replaceWith() Replaces one HTML element or each element in a set of HTML elements. replaceWith(content) Replaces one HTML element or each element in a set of HTML elements. Returns the result set. content A query result.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1315.html">PAGE 1315</a></h6> <p>} results.replaceWith(chapters); show() Shows one or more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395). One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849). The elements returned by a query in the template (see "query()" on page 1275). To hide elements (again), use the function "hide()" on page 1341.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1316.html">PAGE 1316</a></h6> <p>This code is used in a script that inserts a table of contents. For the full script and explanation see "Creating a Table Of Contents" on page 896. text() text() : String Returns the text content of an HTML element or of the first element in a result set (see "results" on page 1395). Example This script loads a snippet into a variable and retrieves an element from the snippet using query () and text(). var mysnippet = loadhtml('snippets/text-root-wrapped.html'); var subject = query("#subject", mysnippet).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1317.html">PAGE 1317</a></h6> <p>width(): Number Returns the outer width of this element, including padding and borders, excluding margins. To include margins, call width(true). The returned value is the width in pixels, without measurement unit (e.g. 400). width(value): void Sets the outer width of this element, including padding and borders, excluding margins. To include margins, call width(value, true). value Number. Give the width in pixels, but without the measurement unit (e.g. 400, not 400px).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1318.html">PAGE 1318</a></h6> <p>match the selector of the script - the results (see "results" on page 1395). In such a script, this is an object of the type QueryResult. It represents the current element in the loop. Note The scope of Control Scripts can't be set, because they don't have a selector. Example If the selector of a script is p.onlyCanada, and its scope is set to "Each matched element", the script will be repeated for all paragraphs that have the onlyCanada class; it can access only one paragraph at a time.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1319.html">PAGE 1319</a></h6> <p>Field Type Description element of a row in a Dynamic Table. (See "Dynamic Table" on page 793.) If this (the current QueryResult instance) cannot be matched to a detail record, this.record is null. runningTotal Number Can be used to update a running total. It is initialized to zero when a loop over results starts. Functions The functions below can be called by the results object and by any other result set that is returned by a query, see "query()" on page 1275.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1320.html">PAGE 1320</a></h6> <p>Function Description "clone()" on page 1381 Returns a copy of the current HTML element. "closest()" on page 1335 This function gets the first parent element that matches a selector, by testing the element itself and traversing up through its ancestors in the DOM tree. "css()" on page 1336 Gets the value of a style property for the HTML element or sets one or more CSS properties for the HTML element.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1321.html">PAGE 1321</a></h6> <p>Function Description "pageRef()" on page 1344 Returns a marker that will be replaced with the element's page number after pagination. This only works for elements in the section that is currently being merged. "parent()" on page 1345 Returns the parent of the HTML element. "prepend()" on page 1345 Inserts content at the beginning of an HTML element or of each element in a set of HTML elements. "remove()" on page 1348 Removes an HTML element or a set of HTML elements from the document.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1322.html">PAGE 1322</a></h6> <p>add() The add() function adds elements to one or more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395). One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849). The elements returned by a query in the template (see "query()" on page 1275).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1323.html">PAGE 1323</a></h6> <p>} results.replaceWith(chapters); Selector Matched element Matched element after script execution #chapters <p id="chapters">{{chapters}}</p> <h1>Chapter 1</h1> <p>Lorem ipsum...</p> <h1>Chapter 2</h1> <p>Lorem ipsum...</p> <h1>Chapter 3</h1> <p>Lorem ipsum...</p> <h1>Chapter 4</h1> <p>Lorem ipsum...</p> addClass() Adds the specified class(es) to one ore more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1324.html">PAGE 1324</a></h6> <p>Selector Matched element Matched element after script execution p <p>Hello world</p> <p class="foo bar">Hello world</p> The following script adds two class names to a paragraph. results.addClass("foo bar"); Selector Matched element Matched element after script execution p <p>Hello world</p> <p class="foo bar">Hello world</p> after() Inserts content after one or more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1325.html">PAGE 1325</a></h6> <p>Matched element Matched element after script execution <p id="salesrep">Peter Parker</p> <p id="salesrep">Peter Parker</p> <p>Lorem ipsum</p> This script looks up an element with the ID #salesrep, sets its text color to red and inserts a paragraph after it. query("#salesrep").after("<p>Lorem ipsum</p>").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1326.html">PAGE 1326</a></h6> <p>Matched element Matched element after script execution <p>Lorem dolor sit amet, consectetur adipiscing elit.</p> <p>Lorem <span>ipsum</span> dolor sit amet, consectetur adipiscing elit.</p> This script looks up an element with the ID #salesrep and inserts a string after it. The string is automatically enclosed in a span. query("#salesrep").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1327.html">PAGE 1327</a></h6> <p>Examples This script appends a paragraph to the results (the set of HTML elements that match the selector of the script). results.append("<p>Peter Parker</p>"); Selector Matched element Matched element after script execution #box <div id="box"> <h1>Personal information</h1> </div> <div id="box"> <h1>Personal information</h1> <p>Peter Parker</p> </div> This script appends a string to the results (the HTML elements that match the selector of the script).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1328.html">PAGE 1328</a></h6> <p>Selector Matched element Matched element after script execution <h1>Personal information</h1> </div> <div> <h1>Personal information</h1> </div> <h1>Personal information</h1> <p>Peter Parker</p> </div> <div> <h1>Personal information</h1> <p>Peter Parker</p> </div> The following script appends a snippet to a Div element with the ID box. var a = loadhtml('snippets/snippet_name.html'); results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1329.html">PAGE 1329</a></h6> <p>Matched element Matched element after script execution <div id="box"> <h1>Personal information</h1> </div> <div id="box" style="color: red;"> <h1>Personal information</h1> <p>Peter Parker</p> </div> Note: the way the functions append() and css() are used in this script is called 'chaining'. Chaining is optional; the same could be achieved by storing the result of the query in a variable: var box = query("#box"); box.append("<p>Peter Parker</p>"); box.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1330.html">PAGE 1330</a></h6> <p>attr(attributeName, value) Sets the value of the specified attribute of one HTML element or of each element in a result set. attributeName String; the name of the attribute. value String; value for the attribute. Examples This script looks up an image in an element with the ID #calloutbox and sets its alternative text to a value from a data field. var altText = record.fields.FavHobby; query("#callout img").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1331.html">PAGE 1331</a></h6> <p>String, HTML string or result set to insert after the elements. In case a plain text string is provided, it is automatically wrapped in a <span> element to avoid orphan text nodes to appear in the <body> element. Examples This script looks for an element with the ID salesrepand inserts a paragraph before that element. results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1332.html">PAGE 1332</a></h6> <p>Note: the way the functions before() and css() are used in this script is called 'chaining'. Chaining is optional; the same could be achieved by storing the result of the query in a variable: var salesrep = query("#salesrep"); salesrep.before("<p>Lorem ipsum</p>"); salesrep.css("color","red"); The following script searches the results for the string "ipsum" and puts "Lorem " before it. "Lorem " is automatically wrapped in a Span element. results.find("ipsum").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1333.html">PAGE 1333</a></h6> <p>Examples This script retrieves the inner HTML of an element selected from a snippet. var snippet = loadhtml('snippets/snippet.html','#foobar').children (); results.append(snippet); The following script retrieves the inner HTML of the elements and then performs a find/replace. var snippet = loadhtml('snippets/snippet.html','#foobar').children (); snippet.find('@firstname@').text('foobar'); results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1334.html">PAGE 1334</a></h6> <p>// Create the number of rows based on the records in the detail table // We start at 1 so the boilerplate row is used too and there is no need to delete that row for(var r = 1; r < record.tables['detail'].length; r++) { results.parent().append(results.clone()); } // Iterate over the rows and populate them with the data from the accompanying data row query("#table_2 > tbody > tr").each(function(i) { this.find('@ItemNumber@').text( record.tables['detail'][i].fields ["ItemNumber"]); this.find('@ItemOrdered@').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1335.html">PAGE 1335</a></h6> <p>the row). results.hide(); closest() This function gets the first parent element that matches a selector, by testing the element itself and traversing up through its ancestors in the DOM tree. (In HTML, a parent is an element that contains another element.) The function can be used for: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1336.html">PAGE 1336</a></h6> <p>The rows could be colored red within the same statement: results.closest("tr").css('background-color','red'); css() Gets the value of a style property of one HTML element, or sets one or more CSS properties of one or more HTML elements. css(styleName) : String Returns the value of the specified CSS property of an HTML element, which can be: l l l The first element in a set of elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1337.html">PAGE 1337</a></h6> <p>String; the name of the CSS property. value String; value for the CSS property or a map of property-value pairs to set. Examples This script looks up an element with the ID #calloutbox and sets its text color to red. query("#callout p").css('color' , 'red'); The following script does the same, but it only sets the text color to red if in the current record the value of the field 'accounttype' is 'PRO'. if(record.fields.accounttype == "PRO") { query("#callout p").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1338.html">PAGE 1338</a></h6> <p>Examples This script colors the text of the results (the set of HTML elements that match the selector of the script) red and makes it bold. results.css({'color' : 'red', 'font-weight' : 'bold'}); empty() Removes the contents (child elements and inner HTML) from one or more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1339.html">PAGE 1339</a></h6> <p>find() find(textToFind) Performs a deep search for textToFind in the children of each element, and returns a new result set with elements that surround the occurrences. textToFind A String that contains the search text. Example The following piece of code loads a snippet, then looks for placeholders using find(), and replaces them with a text. var mysnippet = loadhtml('snippets/snippet.html'); mysnippet.find('@var1@').text('OL Connect 1'); mysnippet.find('@var2@').html('<i>OL Connect 2</i>').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1340.html">PAGE 1340</a></h6> <p>height() Gets or sets the outer height, including padding and borders, of an HTML element, or of the first element in a result set (see "results" on page 1395), i.e. the set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1275). height(): Number Returns the outer height of this element, including padding and borders, excluding margins. To include margins, call height(true).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1341.html">PAGE 1341</a></h6> <p>results.height( h, true); results.width( w, true); hide() Hides one or more HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395). One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849). The elements returned by a query in the template (see "query()" on page 1275).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1342.html">PAGE 1342</a></h6> <p>l The first element in a set of elements returned by a query in the template (see "query()" on page 1275). html(value) Replaces the inner HTML of an HTML element or of each element in a result set with the supplied value. value A String that may contain HTML tags. Examples The following script loads part of a snippet based on the value of a field, and then inserts the content into the document using html(). var promoTxt = loadhtml('snippets/promo-en.html', '#' + record.fields['YOGA']); results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1343.html">PAGE 1343</a></h6> <p>overflows() The overflows() method returns a boolean value indicating whether an HTML element overflows its box boundaries. This function could for instance be used in a design where content needs to flow separately from the main text flow, or where a new, full-page, multi-column box should be inserted when the current one overflows. Note that when called in a Standard script, this method runs before the pagination of Print output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1344.html">PAGE 1344</a></h6> <p>results.each( function() { // Add elements to the box until it overflows. while ( ! this.overflows() && i < products.length ) { this.append("<p>" + products[i] + "</p>"); i++; } // Go one step back unless we processed all items in our array. if( i < products.length ) { query("p:last-child", this).remove(); i--; } }); pageRef() Returns a marker that will be replaced with the element's page number after pagination. This only works for elements in the section that is currently being merged.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1345.html">PAGE 1345</a></h6> <p>The results object contains the elements that match the selector of the script. So, if the script's selector selects the title of the table of contents, the table of contents will be added after that. The following style rules, added to the style sheet, will align the chapter titles to the left and the page numbers to the right: #toc li { text-align:left; } #toc span { float: right; } Note that these styles use the list's ID, that was defined in the first line of code.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1346.html">PAGE 1346</a></h6> <p>l l l The elements that match the selector of a script (see "results" on page 1395). One element that matches the selector of a script that runs for "Each matched element" (see "this" on page 1317 and "Setting the scope of a script" on page 849). The elements returned by a query in the template (see "query()" on page 1275). See also: "append()" on page 1326.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1347.html">PAGE 1347</a></h6> <p>Selector Matched element Matched element after script execution <h1>Personal information</h1> <p class="name">Peter Parker</p> </div> <h1>Personal information</h1> <p class="name"><b>Name: </b>Peter Parker</p> </div> This script inserts content in multiple <div> elements at the same time. results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1348.html">PAGE 1348</a></h6> <p>This script uses the function query() to find a box. Then it inserts a heading as the first element in that box. query("#box").prepend("<h1>Personal information</h1>"); Matched element Matched element after script execution <div id="box"> <p>Peter Parker</p> </div> <div id="box"> <h1>Personal information</h1> <p>Peter Parker</p> </div> This script uses the function query() to find a box, prepends a heading and sets the text color of the entire box to red. query("#box").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1349.html">PAGE 1349</a></h6> <p>Examples This script removes all Span elements found in the template. results.remove(); Selector Paragraph before script execution Paragraph after script execution span <p>Lorem ipsum <span>dolor sit</span> amet, consectetuer adipiscing elit.</p> <p>Lorem ipsum amet, consectetuer adipiscing elit.</p> The selector of the following sample script is tbody. Before this script runs, the table body consists of a single placeholder row with three cells. After running the script, it contains thirty rows.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1350.html">PAGE 1350</a></h6> <p>// Attach all copies to the DOM as children of tbody results.append(rows); removeAttr() Removes the specified HTML attribute from an element or from each element in a set of elements. To add or change an attribute, use attr() (see "attr()" on page 1329). removeAttr(attributeName) attributeName String; the name of the attribute. Examples This script looks up an email field in a form (which is an <input> with the ID #email1) and removes its readonly attribute. query("#email1").</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1351.html">PAGE 1351</a></h6> <p>replaceWith() Replaces one HTML element or each element in a set of HTML elements. replaceWith(content) Replaces one HTML element or each element in a set of HTML elements. Returns the result set. content A query result. This can be an HTML string or a result set. Examples Replace elements with a snippet The following script loads a snippet and then replaces the elements matched by the script's selector with the snippet. var snippet = loadhtml('snippets/mysnippet.html'); results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1352.html">PAGE 1352</a></h6> <p>(see "this" on page 1317 and "Setting the scope of a script" on page 849). l The elements returned by a query in the template (see "query()" on page 1275). To hide elements (again), use the function "hide()" on page 1341. These functions are used by the Conditional Script Wizard, as you can see when you open a Conditional Script and click the Expand button; see "Showing content conditionally" on page 787.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1353.html">PAGE 1353</a></h6> <p>text() text() : String Returns the text content of an HTML element or of the first element in a result set (see "results" on page 1395). Example This script loads a snippet into a variable and retrieves an element from the snippet using query () and text(). var mysnippet = loadhtml('snippets/text-root-wrapped.html'); var subject = query("#subject", mysnippet).text(); results.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1354.html">PAGE 1354</a></h6> <p>width(): Number Returns the outer width of this element, including padding and borders, excluding margins. To include margins, call width(true). The returned value is the width in pixels, without measurement unit (e.g. 400). width(value): void Sets the outer width of this element, including padding and borders, excluding margins. To include margins, call width(value, true). value Number. Give the width in pixels, but without the measurement unit (e.g. 400, not 400px).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1355.html">PAGE 1355</a></h6> <p>The translate() function gets the translation for a message, provided that a translation entry can be found for it (with the same context, if given). If the text to be translated does not already exist in the template, you can create a translation entry for it by using the Add Empty String button on the "Translations pane" on page 1044.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1356.html">PAGE 1356</a></h6> <p>used in Control Scripts, however. This is because Control Scripts differ from template scripts (see "What Control Scripts are" on page 879). For example, the query() function can't be used in a Control Script because it requires access to the DOM which a Control Script doesn't have. Object Usage channel (see "Channel" on page 1387) The channel for which output is generated. This is registered in the merge object: merge.channel.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1357.html">PAGE 1357</a></h6> <p>Object Usage merge.template.contexts.PRINT.sections["Section EN"]. "template" on page 1383 The template object contains all contexts and sections. It is accessed through the merge object: merge.template. automation This object (of the type: Automation) encapsulates the properties of the PlanetPress Workflow process that triggered the current operation. Note This object is only available in a Web context. Note The automation object available in DataMapper scripts is not of the same type.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1358.html">PAGE 1358</a></h6> <p>Accessing automation properties To access Job Info 1 to 9 (defined in Workflow; see Job Info variables in the Workflow Online Help): automation.jobInfos.JobInfo1; To access ProcessName, OriginalFilename or TaskIndex (defined in Workflow): automation.properties.OriginalFilename; Example Assume that a Workflow process can be triggered when an XML file appears in a certain folder. The XML file contains data that you want to show on a web page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1359.html">PAGE 1359</a></h6> <p>Field Type Description Note: When using merge.context.sections keep in mind that for example 'Section X' might only exist in your Print context, so using merge.context.sections['Section X'] without enclosing it in the if statement if (merge.context.type == ContextType.PRINT) {} will yield an error when the script runs for other contexts. Alternatively, use the template object to access a specific context: merge.template.contexts.PRINT.sections ['Section X'].</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1360.html">PAGE 1360</a></h6> <p>masterpage The masterpage object is used to set a Master Page's header and footer or to replace its entire HTML body. It can only be accessed in Control Scripts (see "Control Scripts" on page 879 and "Control Script API" on page 1355). Trying to access it in another type of script will result in an error. Note that Master Pages are only used in a Print context (see "Master Pages" on page 478).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1361.html">PAGE 1361</a></h6> <p>var mySection = merge.template.contexts.PRINT.sections["Section 1"]; var promoTxt = loadhtml('snippets/promo-' + record.fields['City'] + '.html', ); mySection.html(promoTxt); margins The margins object is used to set a Print section or Master Page's margins in a Control Script (see "Control Scripts" on page 879 and "Control Script API" on page 1355). Note that Master Pages are only used in a Print context (see "Master Pages" on page 478).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1362.html">PAGE 1362</a></h6> <p>Setting the header and footer of a Master Page var masterA = merge.template.masterpages["Master page A"]; masterA.margins.header = "2in"; masterA.margins.footer = "2in"; media The media object can be used to specify, enable and position a stationery's front and back in a Control Script (see "Control Scripts" on page 879 and "Control Script API" on page 1355). Note that Media are only used in Print sections (see "Media" on page 481).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1363.html">PAGE 1363</a></h6> <p>Field Type Description file:///c:/users/Adminstrator/Pictures/My_ Media.jpg. page Number PDF and TIFF files may count more than one page. Specify the page number to use. position "MediaPosition" on page 1388 The position is used to place the stationery on the page (absolute, centered, fit to media). top Measurement The vertical offset from the top of the page, used to position the stationery (only when absolute positioning is selected). This value can be negative.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1364.html">PAGE 1364</a></h6> <p>Field Type Description "context" on page 1392 Context The context rendered by this merge run. If for one record, different contexts need to be output (for example, when the Print context is attached to an email) a record is merged multiple times: once per context. Per merge run, merge.context shows with which context the record is merged. pagination "Pagination" on page 1412 Contains the total page count and sheet count of all sections in the Print context after pagination.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1365.html">PAGE 1365</a></h6> <p>resource() The resource() function returns information about an image resource. This function is useful in a Control Script, for example to check the number of pages or the page height and width before setting it as a background (see "Control Script: Setting a Print section's background" on page 887). This function can also be used to check if a file exists. It returns null if the file does not exist.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1366.html">PAGE 1366</a></h6> <p>Field Type Description width float The width of the current page (in points) Examples This script retrieves the second page of a PDF that is present in the template's resources. var var var var pdf = resource("images/stamp.pdf", 2); height = pdf.height; width = pdf.width; numberOfPages = pdf.pages; In the following script, the function is used to check if a file exists. if(resource("C:/paw.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1367.html">PAGE 1367</a></h6> <p>Example The following script logs the permissions for a PDF. var pdf = resource("images/myPDF.pdf"); var willPrint = pdf.permissions.printingAllowed; var hasPW = pdf.permissions.hasPassword; logger.info('Printing restrictions: ' + willPrint); logger.info('Password-protected: ' + hasPW); section The section object can be used to query and modify how the section (and the related context) will be outputted.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1368.html">PAGE 1368</a></h6> <p>Field Type Description restartPageNumber fields are still effective to define the parts division and page numbering over multiple sections when applicable. The default enabled state for sections (before any control script runs) is as follows: For Web channel requests, the requested Web section is enabled by default. It is possible to redirect to another section by disabling the requested section and enabling another section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1369.html">PAGE 1369</a></h6> <p>Field Type Description example, "2in" sets a margin to two inches. minPages Number Minimum number of pages in the section. The default is 1. name String Used to get or set the name of the section. Note that section names must be unique and that sections cannot have an integer as its name. The name should always include alphanumeric characters. To rename email attachments, use the field part. ownerPassword String Print sections only. Used to set the owner password for a PDF attachment.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1370.html">PAGE 1370</a></h6> <p>Field Type Description same value. See "Control Script: Securing PDF attachments" on page 892.* restartPageNumber Boolean Print sections only. Enables or disables a restart of the page numbering. When generating Print output this can be used to let page numbering continue over multiple sections. The default value is false, meaning that each section will start with page 1 (to emulate behavior of previous versions). "sheetConfig" on page 1377 SheetConfig Print sections only.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1371.html">PAGE 1371</a></h6> <p>Function Description on page 1381 page 889. addAfter() Add a cloned section after this section. addBefore () Add a cloned section before this section. addHeader (key, value) Email sections only. Used to set custom email headers. The function expects a key and a value (both of type string). For examples, see "Adding custom ESP handling instructions" on page 1450. "html (value)" on page 1382 Sets the initial HTML of the body element. "paginate ()" on page 1409 Post Pagination Scripts only.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1372.html">PAGE 1372</a></h6> <p>Selecting different sections for Print output and Email PDF attachment This script selects a different Print section for output, depending on the output channel (Email or Print). var printSections = merge.template.contexts.PRINT.sections; if(merge.channel === Channel.EMAIL){ printSections['Section 1'].enabled = false; printSections['Section 2'].enabled = true; } if(merge.channel === Channel.PRINT){ printSections['Section 1'].enabled = true; printSections['Section 2'].</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1373.html">PAGE 1373</a></h6> <p>merge.context.sections['Section 6'].enabled = true; merge.context.sections['Section 6'].part = "PDFAttach2"; } else if (merge.context.type == ContextType.WEB) { merge.context.sections['default Section'].enabled = false; // disable whatever is the default section merge.context.sections['Section A'].enabled = true; merge.context.sections['Section A'].part = "WebPartA"; merge.context.sections['Section B'].enabled = true; merge.context.sections['Section B'].</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1374.html">PAGE 1374</a></h6> <p>Scaling to Media size var activeSection = merge.template.contexts.PRINT.sections['Section 1']; activeSection.background.source = BackgroundResource.RESOURCE_PDF; activeSection.background.position = MediaPosition.FIT_TO_MEDIA; activeSection.background.url = "images/somepage.pdf"; See also: "BackgroundResource" on page 1386, "MediaPosition" on page 1388 and "Control Script: Setting a Print section's background" on page 887.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1375.html">PAGE 1375</a></h6> <p>var resourceUrl = 'images/policy-' + policy + '.pdf'; var clone = printSections["Policy"].clone(); clone.name = "policy_" + policy; clone.background.url = resourceUrl; clone.enabled = true; printSections["Policy"].addAfter(clone); } background The background object holds the PDF background of a Print section (see "section" on page 1400 and "Control Script: Setting a Print section's background" on page 887). Note Setting a page range using the start and end fields automatically sets background.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1376.html">PAGE 1376</a></h6> <p>Field Type Description scale Number Set the size of the PDF background as a percentage of the original image. source "BackgroundResourc e" on page 1386 Set the source of the PDF background (NONE, Datamapper, PDF Resource). Note Setting the background to NONE does not reset any other option, such as the position and scale of the background. start Number The start page of the PDF to use as a background for the section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1377.html">PAGE 1377</a></h6> <p>Field Type Description A relative path and a URL are expected to be URL encoded. For example, a space needs to be encoded as %20. An absolute Windows-style path does not need to be URL encoded, but in JavaScript any backslashes in a String need to be double-escaped: "C:\\Images\\Image.pdf". Example This scripts sets a background on a Print section using absolute positioning. var activeSection = merge.template.contexts.PRINT.sections['Section 1']; activeSection.background.source = BackgroundResource.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1378.html">PAGE 1378</a></h6> <p>Scripts" on page 879 and "Control Script API" on page 1355). This is especially useful when you need identical sections with different sheet configuration settings. The sheetConfig object can be retrieved via the section object (see "section" on page 1400); see the example below. Fields The fields of the sheetConfig object correspond to settings in the Sheet Configuration dialog; see "Sheet Configuration dialog" on page 990.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1379.html">PAGE 1379</a></h6> <p>Field Type Description tumble Boolean (Only with duplex printing.) When tumble is set to true, pages are printed like in a calendar. (On Portrait output, this would be equivalent to short-edge duplex.) Example This script retrieves a section and changes its sheet configuration settings. let section = merge.template.contexts.PRINT.sections["Section 1"]; section.sheetConfig.duplex = true; section.sheetConfig.omitEmptyBackside = true; section.sheetConfig.facingPages = true; section.sheetConfig.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1380.html">PAGE 1380</a></h6> <p>Field Type Description position) content is allowed. Possible values: l l l l AllowContent.ALL_SIDES AllowContent.FRONT_ONLY (only with duplex printing) AllowContent.BACK_ONLY (only with duplex printing) AllowContent.NONE (not allowed on all, single and middle positions) masterBack String Specifies the Master Page to use on the backside of sheets in this position. masterFront String Specifies the Master Page to use on the front of sheets in this position.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1381.html">PAGE 1381</a></h6> <p>section.sheetConfig.positions.all.masterBack = undefined; // or null, or an empty string The following script ensures that empty backsides of single sheets are omitted. let section = merge.template.contexts.PRINT.sections["Section 1"]; section.sheetConfig.positions.single.omitMasterOnEmptyBackside = true; clone() This function returns a copy of one HTML element or of a set of HTML elements, which can be: l l l The elements that match the selector of a script (see "results" on page 1395).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1382.html">PAGE 1382</a></h6> <p>// Iterate over the rows and populate them with the data from the accompanying data row query("#table_2 > tbody > tr").each(function(i) { this.find('@ItemNumber@').text( record.tables['detail'][i].fields ["ItemNumber"]); this.find('@ItemOrdered@').text( record.tables['detail'][i].fields ["ItemOrdered"]); this.find('@ItemTotal@').text( record.tables['detail'][i].fields ["ItemTotal"]); this.find('@ItemDesc@').text( record.tables['detail'][i].fields ["ItemDesc"]); this.find('@nr@').</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1383.html">PAGE 1383</a></h6> <p>value A String that may contain HTML tags. Examples The following script loads a snippet based on the value of a field, and then replaces the content of a Print section with the snippet using html(). var mySection = merge.template.contexts.PRINT.sections["Section 1"]; var promoTxt = loadhtml('snippets/promo-' + record.fields['City'] + '.html', ); mySection.html(promoTxt); paginate() This method of the section object (see "section" on page 1400) triggers pagination of the current section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1384.html">PAGE 1384</a></h6> <p>Which contexts are available in the template can be queried using merge.template.contexts. To get access to a specific context, you have to specify the ContextType (see "ContextType" on page 1388). Field Type Description contexts Array Array of contexts (see "context" on page 1392) available in the template. The contexts contain the sections (see "section" on page 1400). masterpages Array Array of Master Pages (see "masterpage" on page 1360) available in the template.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1385.html">PAGE 1385</a></h6> <p>properties The properties object inside the template object (see "template" on page 1383) contains all default properties of the template file as well as any custom properties. To view and complement the file properties, select File > Properties on the menu. See "File Properties dialog" on page 931. Following are the default properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1386.html">PAGE 1386</a></h6> <p>BackgroundResource BackgroundResource is an enumeration for the types of background resources for a Print section (see "background" on page 1375 and "section" on page 1400). A Print section can be retrieved in script using merge.template.contexts.ContextType.sections["section name"], for example merge.template.contexts.PRINT.sections["Section EN"]. Field Description DATAMAPPER_ PDF A PDF file retrieved via the active data mapping configuration.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1387.html">PAGE 1387</a></h6> <p>Note To learn how to set a PDF file as a background image on a Print section without a Control Script, see "Using a PDF file or other image as background" on page 464. Channel Channel is an enumeration for the output channels. The active output channel is registered in merge.channel. The channel doesn't change when the output consists of different contexts. When generating email, for example, the channel is EMAIL, even when merging the Print context to attach it to the email.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1388.html">PAGE 1388</a></h6> <p>printSections['Section 2'].enabled = false; } ContextType ContextType is an enumeration for the context types. The type of the context that is going to be merged next can be retrieved via merge.context.type. The context type needs to be specified when retrieving a section with merge.template.contexts.ContextType.sections["section name"], for example merge.template.contexts.PRINT.sections["Section EN"]. Value Description HTML_EMAIL The context is the Email context.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1389.html">PAGE 1389</a></h6> <p>Field Description ABSOLUTE Places the PDF at a specific location on the page. Set the background's top (background.top) and left (background.left) measured from the top and left side of the section. CENTERED Centers the PDF on the page, vertically and horizontally. FIT_TO_ MEDIA Stretches the PDF to fit the page size. Examples This script applies absolute positioning to the background of a Print section. var activeSection = merge.template.contexts.PRINT.sections['Section 1']; activeSection.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1390.html">PAGE 1390</a></h6> <p>Note Post Pagination Scripts only apply to the Print context. These functions and objects cannot be used with other contexts. Tip It is possible to define a function in a Control Script which calls these functions, as long as that function is only invoked from a Post Pagination Script. Object or function Usage merge.context."query (selector)" on page 1393 Call merge.context.query(selector) to run a query across all sections in the Print context. merge.section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1391.html">PAGE 1391</a></h6> <p>Object or function Usage set of a query (see "query(selector)" on page 1393). Other objects that are available to Post Pagination Scripts The list above isn't exhaustive: the objects listed in the Designer API (see "Standard Script API" on page 1250) and in the Control Script API (see "Control Script API" on page 1355) are also available in Post Pagination Scripts. contentitem The contentitem object holds the Print Content Item that will be written to the Connect database when generating Print output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1392.html">PAGE 1392</a></h6> <p>You can replace 'myProperty' and 'myvalue' with whatever name and value best suits the use case. If the name of the property contains a space you'll need to put it between brackets and quotation marks: contentitem.properties['name with spaces'] = 'value'; If the value is a number you don't need to put it between quotation marks: contentitem.properties.custom_property = 123; context In a Control Script, the context object represents one context in the template.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1393.html">PAGE 1393</a></h6> <p>Function Description "query (selector)" below Runs a query across all sections in the Print context. This function is only available in Post Pagination Scripts, which are only applied to the Print context. See "Post Pagination Scripts" on page 894. Example This script checks if the output channel is EMAIL and if the context to be merged is the Print context (which happens if the Print context is attached to an email). If this is the case, it includes and excludes certain Print sections from the output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1394.html">PAGE 1394</a></h6> <p>PaginationInfo The PaginationInfo object is returned by the info() function of the results object (see "info()" on page 1399 and "results" on the next page). It contains information about where an element is located: on which page and which sheet, and the total number of pages and sheets in the page bundle in which the element is located. A page bundle is a group of sections for which the Restart page numbering option is turned off.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1395.html">PAGE 1395</a></h6> <p>results The results object (type: QueryResults) is the result of the query for HTML elements that match the selector of the script. The selector of a script can be specified in the Script Editor and is visible in the second column of the Scripts pane, next to the name of the script. If, for example, a script would have the selector p.onlyCanada, the script would apply to all paragraphs that have the class onlyCanada.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1396.html">PAGE 1396</a></h6> <p>Function Description "add()" on page 1322 Adds elements to a set of HTML elements. "addClass()" on page 1323 Adds the specified class to each element in a set of HTML elements. Has no effect if the class is already present. "after()" on page 1324 Inserts content after each element in a set of HTML elements.. "append()" on page 1326 Inserts content at the end of each element in a set of HTML elements.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1397.html">PAGE 1397</a></h6> <p>Function Description "filter()" on page 1300 Returns a subset of the current result set. "find()" on page 1339 Performs a search for a text in the children of each element in a set of HTML elements, and returns a new result set with elements that surround the occurrences. "get(index)" on page 1302 Returns the element (type: QueryResult) found at the supplied index in a set of HTML elements. "hasClass()" on page 1339 Returns true if the first element in this result set has the specified class.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1398.html">PAGE 1398</a></h6> <p>Function Description "parent()" on page 1345 Returns the parents of the elements in a set of HTML elements. "prepend()" on page 1345 Inserts content at the beginning of an HTML element or of each element in a set of HTML elements. "remove()" on page 1348 Removes an HTML element or a set of HTML elements from the document. "removeAttr()" on page 1350 Removes the specified attribute from each element in this result set.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1399.html">PAGE 1399</a></h6> <p>Function Description page 1353 info() Returns pagination information for one HTML element or for the first element in a result set (see "results" on page 1395) of a query across all sections in a Print context (see "query(selector)" on page 1393). The returned information is of the type PaginationInfo (see "PaginationInfo" on page 1394). This function can only be used in a Post Pagination Script ; see "Post Pagination Script API" on page 1389.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1400.html">PAGE 1400</a></h6> <p>Examples var $box = query("#mybox"); while ( ! $box.overflows()) { //do something } A slightly shorter version: while ( ! query("#mybox").overflows()) { //do something } The following script selects three boxes that all have the class box (selector: .box). It loops over them, inserting as many products from an array as possible into the box. In fact, it inserts one too many and removes the last one before moving on to the next box.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1401.html">PAGE 1401</a></h6> <p>Retrieving a section A section can be retrieved using merge.template.contexts.ContextType.sections["section name"], for example: merge.template.contexts.PRINT.sections["Section EN"]. A section can also be retrieved via merge.context.sections['section name']. Remember, however, that when several contexts need to be merged (for example, when the Print context is attached to an email), the script needs to check if the current context is of the type that contains the desired section (for example: if (merge.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1402.html">PAGE 1402</a></h6> <p>Field Type Description For Email channel requests on the Print context all Print sections are enabled by default. It is possible to enable different or multiple sections to control which sections will be attached to the email. For Email channel requests, the requested section is enabled by default. It is possible to output another section by disabling the requested section and enabling another section. For Print channel requests on the Print context all sections are enabled by default.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1403.html">PAGE 1403</a></h6> <p>Field Type Description be freely viewed, but cannot be manipulated unless the owner password is provided. (Note that the recipient needs Adobe Acrobat to do this, because the Acrobat Reader does not allow users to enter the owner password.) See "Control Script: Securing PDF attachments" on page 892. pagination "Pagination" on page 1410 Post Pagination scripts only. Contains the total page count, sheet count and start/end page numbers of a single section. part String Name for the part.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1404.html">PAGE 1404</a></h6> <p>Field Type Description section. * The password(s) should be set on the first Print section when producing a single attachment, or on the first section of each part when producing multiple attachments. Each of the parts (attachments) may have a different (or no) set of passwords. Passwords set in the Control Script override the password set through the Email PDF password script (see "Email PDF password" on page 509). This allows you to change or remove the password from a specific part.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1405.html">PAGE 1405</a></h6> <p>Function Description page 1382 "paginate ()" on page 1409 Post Pagination Scripts only. Paginates the content of a Print section. Examples Conditionally skipping or printing Print sections This script disables all Print sections and then re-enables one of them, depending on a value in the current record. var printSections = merge.template.contexts.PRINT.sections; printSections['Section EN'].enabled = false; printSections['Section FR'].enabled = false; if(record.fields.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1406.html">PAGE 1406</a></h6> <p>Setting the name of Email PDF attachments This script renames the file name of an attachment by setting the part name of a section (see "Parts: splitting and renaming email attachments" on page 885). var section = merge.template.contexts.PRINT.sections['Section 1']; section.part = 'Invoice ' + record.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1407.html">PAGE 1407</a></h6> <p>Note If the Email PDF Password Script Wizard defines a password, and a template has a Control Script that creates multiple PDF attachments, all the attachments are secured by the same password by default. Using a Control Script, you can set set different passwords for attachments; see "Control Script: Securing PDF attachments" on page 892. Positioning the background of a Print section These scripts both set the background of a Print section to the same PDF, but they position it differently.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1408.html">PAGE 1408</a></h6> <p>var printSections = merge.template.contexts.PRINT.sections; var numClones = record.tables['detail'].length; for( var i = 0; i < numClones; i++){ var clone = printSections["Section 1"].clone(); clone.name = "my_section_clone_" + i; printSections["Section 1"].addAfter(clone); } Cloning a section based on data and assign a background PDF This script clones a section based on data fields. It disables the source section first and then calls the addPolicy function.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1409.html">PAGE 1409</a></h6> <p>Fields Field Type Description bottom left right top String These fields allow to set the bottom, left, right and top of a Print section, using a Measurement string, for example: "2in" (this sets a margin to two inches). footer header String These fields allow to set the header and footer of a Master Page, using a Measurement string. Examples Setting the margins of a Print section var sectionA = merge.template.contexts.PRINT.sections["Section A"]; sectionA.margins.top = "2in"; sectionA.margins.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1410.html">PAGE 1410</a></h6> <p>You only need to call merge.section.paginate() in a Post Pagination Script if the script has added or removed content to such an extent that the page boundaries need to be renewed. For an example see: "Creating a Table Of Contents" on page 896. Pagination The Pagination object that is accessed via the section object (see "section" on page 1400) contains the total page count, sheet count and start/end page numbers for a single section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1411.html">PAGE 1411</a></h6> <p>Script API" on page 1355. Some of the objects are also useful in Post Pagination Scripts; see "Post Pagination Scripts" on page 894 and "Post Pagination Script API" on page 1389. For sample scripts, follow the links to the respective objects. Field Type Description channel "Channel" on page 1387 The final output channel: EMAIL, PRINT or WEB. The channel doesn't change when the output consists of different contexts.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1412.html">PAGE 1412</a></h6> <p>Field Type Description In Post Pagination Scripts, only Print sections are available. "template" on page 1383 Template This object contains the template and all of its contexts. It can be used to find out which contexts are available in the template, using merge.template.contexts (see "context" on page 1392) and to manipulate the sections in those contexts (see "section" on page 1400).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1413.html">PAGE 1413</a></h6> <p>Generating output When merged with a record set, the templates made in the Designer can generate three types of output: Print , Email and Web. You can print and email from the Designer, but if you want to do this in an automated process, or if you want to produce web pages that are not attached to an email, you need to build Workflow processes with OL Connect tasks. For more information, see: "Workflow processes in OL Connect projects" on page 178.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1414.html">PAGE 1414</a></h6> <p>Fax output It is possible to generate Fax output from PlanetPress Connect through a Print output job creating PDF/VT output, with some additional Workflow steps. See "Generating Fax output" on page 1440 for details. Email output The Email context outputs HTML email with embedded formatting to an email client through the use of an email server. The HTML generated by this context is meant to be compatible with as many clients and as many devices as possible.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1415.html">PAGE 1415</a></h6> <p>To learn how to attach other files, see "Email attachments" on page 510. Web output The Web context outputs an HTML web page that contains the HTML text and all the resources necessary to display it. Web output can be generated in two different ways: it can be attached to an Email template when generating Email output (see above), or it can be generated using Workflow; see "Generating Web output" on page 1453.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1416.html">PAGE 1416</a></h6> <p>Note Proof Print generates output directly from the Designer, without using the Print Service. A Proof Print run won't impact upon production printing l File > Print... allows the following printing options: l l l Using the Default output settings. For more details, see "Print using standard print output settings" on page 1418 Using the same settings that were last used to produce printed output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1417.html">PAGE 1417</a></h6> <p>documents and splitting the print jobs into smaller print jobs, as well as the more standard selection of printing options, such as binding, OMR markings and the like. See "Print Presets" on page 1420 for more details. Generating Print output from Workflow If you want to generate Print output via an automated process, this means that you have to design a Print process in the Workflow configuration tool.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1418.html">PAGE 1418</a></h6> <p>l l l l Duplex printing. Duplex printing has to be enabled for a Print section, in order to print that section on both sides of the paper. The same applies to Mixplex printing. See "Enabling double-sided printing (Duplex, Mixplex)" on page 467. Finishing. The Print context , as well as each of the Print sections, can have its own Finishing settings. In printing, Finishing is the way pages are bound together after they are printed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1419.html">PAGE 1419</a></h6> <p>the Last Used printer settings or by using previously created Printing Presets. To learn how to create Printing Presets please see Job Creation Presets and Output Creation Presets. l Configuration Selection Group: l l l Output Creation: Leave the selection at the Default or use the drop-down to select an existing Output Creation Preset. Use the Gear button to edit the currently selected Preset or to reload the list of Presets from the system.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1420.html">PAGE 1420</a></h6> <p>l l Copies: Enter the number of output copies you want. Collate: When printing multiple copies you can check this checkbox to have the record copies printed together. For example in a three record job the records would print out as 1-1-2-2-3-3, rather than 1-2-3-1-2-3. Wizard navigation buttons l Advanced button: Click to open the "Print using Advanced Printer Wizard " on page 1427where you can manually change the printing options.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1421.html">PAGE 1421</a></h6> <p>process. l l A Job Creation Preset is used by the Connect Server after a template and data have been merged. Based on the settings in a Job Creation Preset the server can filter, sort, and group the print content items, add meta data and make finishing settings. The resulting print job is then handed to the Weaver engine for output creation (see also: "Connect: a peek under the hood" on page 125). This engine generates the final print output file, or files.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1422.html">PAGE 1422</a></h6> <p>Job Creation Presets A Job Creation Preset is a file that contains settings for creating a print job. It is used after a template has been merged with data, but before the actual print output file is produced. Merging a template with data results in a set of print content items. Based on the settings in a Job Creation Preset, the Connect server can take a number of actions on a set of print content items. The actions are described below. Select File > Print Presets > Job Creation Settings...</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1423.html">PAGE 1423</a></h6> <p>The remaining items can be sorted, either by the Connect Server, based on data fields, or by some external sorting software (see "Sorting options" on page 1147). Tip External sorting benefits considerably from runtime parameters, defined in the Job Creation Preset (see "Runtime Parameter Options" on page 1139). Grouping While creating a print job, the Connect Server can group Print content items into Jobs, Job Segments and Document Sets (see "Grouping options" on page 1150).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1424.html">PAGE 1424</a></h6> <p>Override finishing options The Print context and Print sections can have their own finishing options (see "Print settings in the Print context and sections" on page 456.) A template could be setup with a glue binding, for example. When the printer doesn't support the chosen finishing options you could override the finishing options, and use staple binding, for instance.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1425.html">PAGE 1425</a></h6> <p>Printer model and output type An Output Creation Preset specifies the type of printer the output should be suitable for, and determines where that output should then be sent: to a folder, LPR queue or Windows printer (see "Print options" on page 1158). Printer definitions A printer model and its capabilities for Connect are defined in a printer model definition file (.OL-printerdef). Connect comes with a number of such files.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1426.html">PAGE 1426</a></h6> <p>Imposition An Output Creation Preset can tell a printer to print multiple pages on a single sheet (Simplex, or Duplex). This is called Imposition, also known as N-Up printing. The two Imposition types are Cut & Stack and Stack by Column (see "Imposition options" on page 1222). With each Imposition type there is a wide range of options to control the exact layout of the output: the number of pages that go on one sheet, their order, the way they are stacked, the stack depth, the margins, markings, etc.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1427.html">PAGE 1427</a></h6> <p>possible when you use Imposition. With Booklet Imposition, however, the output can be separated on all levels. Additional content Via an Output Creation Preset, content - Text, Images, Barcodes and OMR Marks - can be added to the output at the time of output creation. The additional content can be either static or variable (see "Additional Content" on page 1179).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1428.html">PAGE 1428</a></h6> <p>The Wizard can be used to generate once-off print runs (either entirely from scratch, or based upon selected pre-existing Presets). Note: These print runs cannot be saved as presets and can only be replicated in the following print run, using the Last Used option. The output settings are determined by selections made throughout the Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1429.html">PAGE 1429</a></h6> <p>have been customized specifically for your printer(s). 2. Select Create Definition from PPD to add a customizable PostScript Printer Model using the printer manufacturer provided PostScript Printer Definition (PPD) file. This launches the PPD Import Wizard. In the Wizard, do the following. l l Select the printer's PPD file. Once selected details about that specific printer will load in the information box, for confirmation. NOTE: The PPD information extraction and processing can take some seconds.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1430.html">PAGE 1430</a></h6> <p>Print Wizard, then click OK. Splitting printing into more than one file By default, when Connect saves the print output spool file to a directory, it creates one spool file that contains all the generated documents (one document per data record). It is, however, possible to output one spool file per document, or to create groups of documents and store those in separate spool files.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1431.html">PAGE 1431</a></h6> <p>province. Here's how to do that: 1. First, define meta data at the intended separation level. This is done in the Job Creation Preset (see "Include meta data" on page 1423). 2. Then, in the Output Creation Preset, use those meta data in the Job Output Mask (see "Output options" on page 1159). They are inserted into the file name as variables. For example: ${segment.metadata.State} refers to a meta data tag State defined on the job segment level.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1432.html">PAGE 1432</a></h6> <p>This is done by setting a Job Info variable in the Workflow configuration see Job Info variables in the Workflow Online Help) and then referencing it in the "Print options" on page 1158 fields via the variable @automation.JobInfoX@ (where "X" is the number of the Job Info variable). If the output is to be separated into multiple files, some Output content variables can also be used as Output file variables, depending on the level of separation (see "Content variables" on page 1435).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1433.html">PAGE 1433</a></h6> <p>${template.base} expands to My-Invoices-EN . ${template.name} Returns the name of the template file without the path. Example If the template file is C:\Data\My-Invoices-EN.OL-template, then ${template.name} expands to My-Invoices-EN.OL-template. Note that ${template.name} still includes the extension of the template file (.OL-template in the example above). ${template.nr} An automatic sequence number belonging to the current output file.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1434.html">PAGE 1434</a></h6> <p>Example When printing to PDF, ${file} could expand to merged.5852941188491153960_0001.pdf. ${file.base} Expands to a unique, internally generated file name, without a trailing dot or extension. ${file.ext} The extension that corresponds to the chosen output format, for example pdf or ps. Note that ${file.ext} does not include a leading dot. ${file.nr} An automatic sequence number belonging to the current output file.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1435.html">PAGE 1435</a></h6> <p>${job.base} or ${job.name} Returns the name of the applied Job Creation Preset without any extension. Expands to Untitled if no Job Creation Preset was used. ${job.nr} An automatic sequence number belonging to the current output file. It is automatically incremented for each new output file that gets created. Note, that multiple output files are created, for example, when output separation has been selected for output creation. It is possible to format the number using a pattern and locale.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1436.html">PAGE 1436</a></h6> <p>System ${system.time} Displays the current system data and/or time. Can be formatted using the "Formatting date and number values " on page 1439, as seen below. Page ${page.back} True when the page is on the back of the sheet. ${page.front} Boolean indicating whether the page is on the front of the sheet. ${page.height} The page's height (in points). ${page.landscape} True when the page's orientation is landscape. ${page.portrait} True when the page's orientation is portrait. ${page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1437.html">PAGE 1437</a></h6> <p>${sheet.height} The sheet's height (in points). ${sheet.pageDevice} Array specifying the sheet's Type (e.g. Plain), Weight (e.g. 83), Color (e.g. yellow), Width (in points), Height (in points) and Tumble (e.g. false). ${sheet.nr} or ${sheet.sequence.document} Sheet number within the document. ${sheet.sectionName} Name of the Template Section that the Sheet belongs to. ${sheet.sequence.set} Sheet number within the document set. ${sheet.sequence.segment} Sheet number within the job segment.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1438.html">PAGE 1438</a></h6> <p>${document.count.sheets} Total number of sheets in the document. ${document.nr} or ${document.sequence.set} Document number within the document set. ${document.sequence.segment} Document number within the job segment. ${document.sequence.job} Document number within the job. Set ${set.metadata. propertyname} or ${set.metadata ['propertyname']} Value of a meta data property of the Document Set.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1439.html">PAGE 1439</a></h6> <p>propertyname} or ${segment.metadata ['propertyname']} The propertyname must have been defined as a Tag Name on the Job Segement Tags tab of the "Meta Data options" on page 1152 page in the Advanced Print Wizard or Job Creation Preset. Note: this is only available if Separation based on Job Segment or Split At Exactly n Sheets has been selected on the "Separation options" on page 1246 page in the Advanced Print Wizard or Output Creation Preset. ${segment.count.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1440.html">PAGE 1440</a></h6> <p>${ expression,pattern,locale } Apply pattern with the specified country locale ${expression,,locale} Apply a default format with the specified country locale ${system.time, "dd MMMM yyyy", fr} ${system.time,,fr} > 19 décembre 2017 19 décembre 2017 12:30:55 It is possible to enclose the values of the pattern and locale in single or double quotes. This is required for including whitespace in a pattern, or when the ${expression} would otherwise be ambiguous.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1441.html">PAGE 1441</a></h6> <p>l l FaxNumber: The phone number where the fax will be sent. Often part of the data. FaxInfo: The description of the fax in both the PlanetPressFax dialog box and the fax log file. Output Preset Configuration The following settings must be used in the Output Preset: l In the Print Options, a PDF type should be selected, such as Generic PDF.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1442.html">PAGE 1442</a></h6> <p>Job Creation Preset configuration For email output, the following meta data fields must be added to the "Meta Data options" on page 1152 page in the Job Creation Preset: l l l l l ImageSendTo: Add to have PlanetPress Image use the specified field as the E-mail address to which to send the PDF file. ImageSendCc: Add to have PlanetPress Image use the specified field as the E-mail address to which to send the PDF file as a carbon copy (CC).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1443.html">PAGE 1443</a></h6> <p>l The four regular Connect tasks to generate print output: l Execute Data Mapping l Create Print Content l Create Job using the above Job Creation Preset l Create Output using the above Output Creation Preset. The task's Output Management must be set to be Through Workflow. For more information, see "Print processes with OL Connect tasks" on page 184. l The PlanetPress Image connector task set to Passthrough (the first "Document" on the list).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1444.html">PAGE 1444</a></h6> <p>For more information see "Email attachments" on page 510. Before generating Email output l l l l Decide on the use of an Email Service Provider; see "Using an ESP with PlanetPress Connect" on page 1448. Make sure that a data set is loaded, that any necessary files, such as images and attachments, are in place, and that the correct settings are selected (see below).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1445.html">PAGE 1445</a></h6> <p>Email output settings in the Email context and sections The following settings for the Email context and Email sections have an impact on how the actual emails are sent. l An Email To Script must be available in the template and refer to a valid email address; see "Email header settings" on page 503. If any record does not have a valid email, this record is skipped automatically when generating email output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1446.html">PAGE 1446</a></h6> <p>sending a test email. An example of a tool that can facilitate testing to ensure a consistent look and feel is Litmus: https://litmus.com/email-testing. If you have a Litmus account, you can enter your Litmus test address when sending a test email (see "Generating Email output from Connect Designer" below). To narrow down the field of potential email clients by finding out which email clients are most commonly used by your target audience you can use Litmus' analytics tool (see https://litmus.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1447.html">PAGE 1447</a></h6> <p>Note When you send a test email, the Email To Script will not be used; instead, the email will be sent to the address that you specify in the Send Test Email dialog. If you have a Litmus account, you can enter your Litmus test address. To make the test address appear by default, you can set the default test address in the Email Preferences: select Window > Preferences, click the arrow next to Email, click General and type the test address next to Email Test address.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1448.html">PAGE 1448</a></h6> <p>may raise a fatal error from within a script in the template; see "fatalError(message)" on page 1254. When a script calls this function in Preview mode, the script that triggers it is marked with an error icon in the Scripts pane, and the given message is displayed in a hint. When generating output from the Designer, the Designer will log the error and display an error dialog with the given message. Content creation is aborted. When generating output from Workflow, the entire job fails.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1449.html">PAGE 1449</a></h6> <p>Choosing an ESP The first thing to do to use an ESP with PlanetPress Connect is to choose an ESP and create an account. Mandrillapp.com, a popular ESP, used to have a free account but now requires a paid MailChimp account. Luckily there are plenty of alternatives that provide free accounts (often capped to a max number of emails per month and sometimes having throttled output). PlanetPress Connect has been tested with: Mandrillap.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1450.html">PAGE 1450</a></h6> <p>Tip For a detailed description of how to use Mandrill to send and track emails, see the following how-to: Using Mandrill. Adding custom ESP handling instructions Most ESPs allow you to provide custom handling instructions as part of the email message, via custom headers. Typically these include instructions to enable open rate tracking, click through rate tracking and assign tags/categories to messages. Assigning a tag/category allows you to view statistics per email type in the dashboard of the ESP.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1451.html">PAGE 1451</a></h6> <p>Note Sendgrid strips out their mail headers. The results need to be verified via their Dashboards (e.g. the Stats section lets you verify the stats for specific categories). Alternatively one can use their Web API to retrieve stats in JSON format. To view the category stats, log in to Sendgrid and choose: Stats > Category Stats > your category name. MailGun Dashboard: https://mailgun.com/cp/stats Documentation: https://documentation.mailgun.com/api-sending.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1452.html">PAGE 1452</a></h6> <p>"dogs", "animals", "pets", "mammals" ] }; var section = merge.context.sections["Content"]; section.addHeader("X-SMTPAPI", JSON.stringify(headerObj)); Note The Mailgun tag allows you to view the stats per tag. Mailgun has a quick refresh and stats are available almost instantly. MailJet Dashboard: https://app.mailjet.com/dashboard Documentation: https://app.mailjet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1453.html">PAGE 1453</a></h6> <p>To assign a campaign, set a meta tag of the type name with the value X-Mailjet-Campaign and set its content to the name of the campaign (for example: invoices). You can make this setting in the Email section properties (see "Meta information" on page 509). Alternatively you could write a Control Script, for example: merge.context.sections["Content"].addHeader("X-Mailjet-Campaign", "invoices"); Note Mailjet strips out their own mailheaders like X-Mailjet-Campaign.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1454.html">PAGE 1454</a></h6> <p>jQuery and its plugins, or MooTools, are useful when you want to implement special features in the web page. (See "Using JavaScript" on page 538.) Style sheets are also added to the <head> and are used just as they would be used in a regular web page. (Also see: "Styling templates with CSS files" on page 719.) Web output can be generated in two different ways: it can be attached to an Email template when generating Email output, or it can be generated using Workflow.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1455.html">PAGE 1455</a></h6> <p>l For Web output, PNG is the preferred image format. EPS, PDF, SVG and TIFF images in a Web section are automatically converted to PNG to ensure that they can be seen in the browser. Web output settings in the Web context and sections There are a few settings for the Web context and Web sections that have an impact on the actual web page that is generated. These settings are: l l Which Web section is the 'default'; see "Setting a default Web page for output" on page 525.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1456.html">PAGE 1456</a></h6> <p>page 986 for a description of all options. Note When you send a test email, the Email To Script will not be used; instead, the email will be sent to the address that you specify in the Send Test Email dialog. 5. Fill in the dialog and send the emails. Generating Web output from Workflow Generating Web output from Workflow requires you to send a template with a Web context to Workflow; see "Sending files to Workflow" on page 429.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1457.html">PAGE 1457</a></h6> <p>When generating output from Workflow, the entire job fails. Workflow will log the error and execute any follow-up actions that are defined in the On Error tab of the respective OL Connect Content Creation task (All in One, Create Email Content, Create Print Content, Create Preview PDF, Create Web Content and Render Email Content). For more information about how to set up follow-up actions, see Using the On Error tab in the Workflow Help.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1458.html">PAGE 1458</a></h6> <p>l Make sure to use optimized graphic resources. For instance, avoid using images with transparency where no transparency is needed. Images l l Make sure to use optimized graphic resources. For instance, avoid using images with transparency where no transparency is needed. When a template that contains lots of images is merged with a large record set, the many file requests may slow down the process of output generation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1459.html">PAGE 1459</a></h6> <p>page 719) that sets its background image to the image sprite and positions the image. For an explanation and examples of this style rule, see https://www.w3schools.com/css/css_image_sprites.asp. l Dynamically added images are loaded in a script. To retrieve one page from a PDF file in a script, add the page parameter to the file path and set that as the source of the image.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1460.html">PAGE 1460</a></h6> <p>PlanetPress Connect Release Notes This chapter contains the current and previous versions of PlanetPress Connect 2020.1.x release notes. l "OL PlanetPress Connect Release Notes 2020.1" below Previous releases: l "License Update Required for Upgrade to Connect 2019.x" on page 1477 l "License Update Required for Upgrade to Connect 2019.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1461.html">PAGE 1461</a></h6> <p>It is heavily recommended that you first update the OL Update Client, as version 1.2.40 of the Update Client can update your OL License to the required version, then install Connect 2020.1. For further details on how to upgrade the Update Client and update your Connect License see the Update Client 1.2.40 Upgrade Guide. If issues arise, or if you need to renew your OL Care subscription, please contact your local Customer Care group.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1462.html">PAGE 1462</a></h6> <p>l l l PlanetPress Connect is released as a 64 Bit version only (with the exception of the Workflow, Fax, Search and Imaging modules). Full details on installing and licensing PlanetPress Connect and PlanetPress Workflow can be found in the online help, which can be accessed from the software and the installer. Note that both PlanetPress Connect and PlanetPress Workflow come with 30 day trial license by default.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1463.html">PAGE 1463</a></h6> <p>OL Connect 2020.1 Enhancements MySQL update and improvements The database that comes bundled with OL Connect has been updated to the latest version of MySQL (8.0.18), along with the drivers used to connect to it. (SHARED-63665/74191) The new packaged database will only be installed with new installations. This is to avoid any chance of issues that might occur in migrating an existing database to the new version.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1464.html">PAGE 1464</a></h6> <p>Bypassing Content Creation Many OL Connect jobs require making simple changes to print-ready batches of documents: adding OMR marks, commingling jobs, postal sorting, and the like. For those types of jobs, no merging of any data is required and yet, after data mapping is done, you must still go through the Content Creation step before moving on to Job Creation. A new REST API method has now been introduced to allow you to create print content directly from paginated input: DataMiningRestService.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1465.html">PAGE 1465</a></h6> <p>Connect 2020.1 Designer Improvements Improved Table wizard and Nested Tables The 2020.1 release of OL Connect has a revamped Insert Detail Table wizard to help you build more sophisticated tables. (SHARED-56213) It simplifies the process of setting up dynamic tables that show complementary information based on nested detail data. In previous Connect releases you had to write complex scripts to achieve this. The new wizard lets you setup these tables from within the user interface of the application.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1466.html">PAGE 1466</a></h6> <p>that no master page is used. In 2019.2 you needed to pass either "null" or an empty string. (SHARED-74887) l Fixed an issue with scripting that could cause statements like query("<tbody>") or query ("<tr>") to fail. (SHARED-74898) General Designer Improvements l l l l l The underline feature now creates <span> wrappers with text-decoration:underline instead of <u> wrappers. This prevents a preflight warning about the <u> tag not being supported.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1467.html">PAGE 1467</a></h6> <p>Connect 2020.1 DataMapping Improvements XML data files DataMapper improvements A new option to show all nodes of XML data file has been added. It is now possible to extract information from nodes that are outside of the record and come after the last record. (SHARED73728) General DataMapper Improvements l l Improved rename option for PDF sub-fields. It is now possible to rename the field directly from DataModel view. (SHARED-73514) Boundaries "On Change" was not triggered with empty data selection.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1468.html">PAGE 1468</a></h6> <p>Connect 2020.1 Output Improvements PDF Digital Signature Improvements l l The digital signature now includes the signer, the location, the reason for signing and the time of signing (if configured to use a time stamp). (SHARED-73528) Connect used to create digital signatures twice. Once to determine the size of the entire signature (including the timestamp if enabled) in the output file, and once for including the actual signature in the output. As of 2020.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1469.html">PAGE 1469</a></h6> <p>Print Output Improvements l A retry option has been added for when the output file exists but cannot be deleted. (SHARED-74292) l Print Output presets now have all non-relevant entries set to default values. (SHARED74594) l l When a table was split across more than two pages, some table rows would be missing from the output. This issue has now been fixed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1470.html">PAGE 1470</a></h6> <p>Email Output Improvements l l l Added a new CSS inline mode for email. (SHARED-74350) Restored support for email attachment paths containing spaces (which was broken in 2019.2). (SHARED-75050) Fixed a problem with scripted email headers that was introduced in 2019.2, whereby the headers were not reset after each record.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1471.html">PAGE 1471</a></h6> <p>Workflow 2020.1 Improvements New DocuWare connectors We are continuing our focus on connectors to integrate with ECM systems, either in the cloud or on-premise. With Connect 2020.1, we are releasing a connector for uploading documents to DocuWare and another for downloading files from DocuWare.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1472.html">PAGE 1472</a></h6> <p>New Microsoft Office 365 connectors New Office 365 OneDrive and Office 365 Email input/output tasks are now available in Workflow. (SHARED-74333) OneDrive input/output processes allow retrieval from, and posting to, any OneDrive account in the organization’s Office 365 services. The Email input/output tasks allow processes to access any mailbox in the organization’s Office 365.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1473.html">PAGE 1473</a></h6> <p>New File Count option A new Input/Condition File Count task has been added. (SHARED-75389) This task checks if a folder contains a specified number of files before processing. This means a process can now be set to be executed only when all required files are available. Execute Data Mapping plugin improvements A new option to Generate error when validation cannot be performed allows Workflow to continue past a validation error when an invalid data format is detected.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1474.html">PAGE 1474</a></h6> <p>Installation of the Access Database Engine 2016 will be skipped if a later version of Access/Access Database Engine is already present on the machine. (SHARED-68863) Improved efficiency of Input tasks The following Input tasks now react to system events rather than polling for changes: l HTTP Server Input l LPD Input l NodeJS Server Input This reduces CPU usage levels, considerably. Especially in cases where the polling interval was set to 0, which means "check constantly".</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1475.html">PAGE 1475</a></h6> <p>l Allow the use of JSON arrays notation when Retrieving Items by ID. For example use [189,1057,3002] to retrieve those three specific items. (SHARED-71621) l SFTP plugin can now create a folder on FTP server when outputting files. (SHARED-72503) l Legacy version 4 configuration files can now be opened in Workflow. (SHARED-73396) l l l l l SMTP Server ports were previously limited to 9999. This has been increased to allow a maximum port of 65,535. (SHARED-73458) NodeJS Server Input.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1476.html">PAGE 1476</a></h6> <p>OL Connect Send Improvements Authorization for printing The Send client can be configured with an API key for all communications with the server receiving print jobs. This enables the server to reject any print jobs that are not submitted by an authorized client. By having different API keys for each subscriber, service providers can also use these API keys as an additional identification. API keys are widely used for this purpose in industry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1477.html">PAGE 1477</a></h6> <p>Previous Releases License Update Required for Upgrade to Connect 2019.x From OL Connect 2019.1 onwards, only customers with a current OL Care subscription will be able to update Connect. Every Connect license will now contain an end date that represents the last day of OL Care coverage for each customer. Upgrades and updates of Connect will be freely available up until that end date, but will not be available thereafter, unless the OL Care period is extended.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1478.html">PAGE 1478</a></h6> <p>Backup before Upgrading It is recommended that you always backup your existing Connect preferences before upgrading to a new version. This will enable you to revert back to the previous version, in a worst case scenario in which the new version introduces issues with your existing production processes. Whilst the probability of such a worst case scenario is remote, it cannot hurt to take some simple precautions, just in case.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1479.html">PAGE 1479</a></h6> <p>GB of RAM and default to only using one internal Weaver and one internal merge engine on that system. The Server will also run using internal engines.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1480.html">PAGE 1480</a></h6> <p>OL Connect 2019.2 Enhancements Windows Server 2019 now officially supported As of PlanetPress Connect 2019.2, Connect is now officially supported under Windows Server 2019. (SHARED-69995) Performance Scheduling settings simplified and improved Not only have the Performance Scheduling options been greatly simplified in Connect 2019.2, but the installer now dynamically sets the values such that fresh installations should perform a whole lot better out of the box.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1481.html">PAGE 1481</a></h6> <p>We have also introduced Performance setting presets. Each preset caters for a different use case scenario. This vastly simplifies optimizing systems for the included scenarios. Out of the box, OL Connect dynamically matches the setup of the engines with the hardware it is running on, typically giving better performance after a fresh installation. Only users who have a mixed workload with parallel running tasks will need to go beyond choosing a preset.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1482.html">PAGE 1482</a></h6> <p>Saving Connect files for different versions You can now save Connect templates and Datamapper configuration files in previous Connect version formats. (SHARED-71187) Improved PDF Signing We have overhauled OL Connect’s functionality for digitally signing PDFs. Amongst other improvements, Connect now supports signing certificates on secure devices such as USB tokens, and HSM’s. This enables applying digital signatures for use cases where regulations require secure storage of the certificate.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1483.html">PAGE 1483</a></h6> <p>The PDF signing improvements include: l Support hardware security devices (USB tokens, smart cards, and Hardware Security Modules) for digitally signing a PDF. The settings for this can be found in the Preferences dialog. l Storing PDF signing passwords encrypted in output preset files. l More reliable handling of time stamp server requests and responses. l Can now add a timestamp to all types of digital signatures. l Support for invisible signatures.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1484.html">PAGE 1484</a></h6> <p>l Improved default performance, for most users, courtesy of simplified and improved performance settings, and better initial assignment of Engines by the Connect installer. Installer Improvements l l l Issues with license importations have been fixed. (SHARED-67735) The Microsoft Access Database Engine has been updated to version 2016 (ACE 16.0) as the previously used engine (2010) is scheduled for end-of-life in 2020.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1485.html">PAGE 1485</a></h6> <p>Barcode Improvements l Added support for the Royal Mail Mailmark 4-State C and Mailmark 4-State L barcodes. (SHARED-63467/69719) l Several barcode names have been changed to better match how they are referred to in industry.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1486.html">PAGE 1486</a></h6> <p>Connect 2019.2 Designer Improvements Import resources from other Connect jobs Introduced an option to import resources (such as scripts and snippets) and data models from other Connect template files. This makes sharing existing Connect resources much easier.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1487.html">PAGE 1487</a></h6> <p>Simplified use of dynamic background images A new scripting wizard has been introduced, simplifying creation of documents with dynamic background images. These images could be stored in the template, on a local folder on disk or remotely on a web server. (SHARED-67948/71096) Improved white-space behaviour Designer adds an empty paragraph to each HTML editor, to allow easy (keyboard) editing.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1488.html">PAGE 1488</a></h6> <p>Scripting Improvements l l l l l When a master page editor is active in the Designer, the Post Pagination folder in the Designer Scripts panel is now decorated with an icon and a tooltip to clarify that post pagination scripts are not active in a master page editor. (SHARED-68543) Scripts can now differentiate between master pages and sections through an attribute selector. (SHARED-69811) Matches from cross-section queries are now highlighted when the mouse is hovering over a post pagination script.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1489.html">PAGE 1489</a></h6> <p>l Pressing Ctrl+F in the script debugger now starts an "Incremental Find" operation. (SHARED-70147) l l Fixed an issue whereby custom expressions were not always refreshed when stepping through the code. (SHARED-71276) Some cosmetic improvements made in the scripts overview within script debugger. (SHARED-72034) General Designer Improvements l l l l l l To prevent issues it is no longer possible to replace absolute positioned direct child elements with inline elements in the body of Master Pages.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1490.html">PAGE 1490</a></h6> <p>l The Send to Workflow and Package dialogs will now only automatically add the latest job and output preset files when there is a template open with a print context. And only if those preset files where created or modified in the current session of the designer. (SHARED-71361) l l Saving a SASS partial file now auto compiles root level .scss files. (SHARED-72224) Modern, Roman and Script fonts are no longer available in the Designer Font ComboBox since these fonts are no longer supported.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1491.html">PAGE 1491</a></h6> <p>Connect 2019.2 DataMapping Improvements Added option to "Stop data mapping" New “Stop data mapping” option added to the Action Step to stop data processing at the specific record where the selected condition is met. As the data mapping operation then no longer needs to examine any further records, skipping those records can considerably improve performance. (SHARED-70320) General DataMapper Improvements l l Improved field selection for PDF split fields.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1492.html">PAGE 1492</a></h6> <p>l Added a toolbar button to send the currently opened DataMapper configuration to Workflow server. (SHARED-70561) l Improved Tab navigation in DataMapper workflow view. (SHARED-70738) l You can now rename DataMapper fields directly. (SHARED-70940) l Boundary Script changes now activate the 'Save' button in DataMapper. (SHARED-72471) Connect 2019.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1493.html">PAGE 1493</a></h6> <p>Page 1493</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1494.html">PAGE 1494</a></h6> <p>They can also be used as Meta Data fields, or in External Sorting. The fields can be alphanumeric, numeric, Boolean, or even dates. You will also be able to pass runtime parameters to the Connect Workflow Job Creation and All In One plugins.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1495.html">PAGE 1495</a></h6> <p>Add customized PostScript commands to Dynamic PPD PostScript output Added support for customized PostScript commands in Dynamic PPD PostScript printer output. The commands can include metadata values, so dynamic runtime information can be incorporated within the commands. (SHARED-72170) Added bin selection to PCL output Added support for bin selection in certain PCL printer definitions that support bins.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1496.html">PAGE 1496</a></h6> <p>Print Output Improvements l l When using a PDF file with a specific combination of page elements as background in the template ("use PDF from datamapper input as section background") and creating PostScript output, it was possible that some page elements could get positioned incorrectly. This has been fixed. (SHARED-68080) Fixed potential PDF/A or PDF/X compliance issue when outputting multiple channels or both variants simultaneously (as some custom OL Enhance workflows do).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1497.html">PAGE 1497</a></h6> <p>l PPML: Tray options now available for PPML print output. (SHARED-69314) l Reduced memory usage requirements for large impositioned jobs. (SHARED-71177) l l Modern, Roman and Script fonts have been removed from the additional content font combo boxes since these fonts are no longer supported. (SHARED-72464) Ensured that PDF pass through is not active when the output PDF type is not standard PDF.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1498.html">PAGE 1498</a></h6> <p>Email Output Improvements New Workflow Email plugins Several new email related Workflow plugins have been created to improve the email sending performance by simplifying the integration with Email Service Providers (ESP). See "New email plugins" on page 1500 section for further details. General Email improvements l l Improved the scripting API for email headers. Connect now supports multiple headers with the same key.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1499.html">PAGE 1499</a></h6> <p>General Output Improvements l Improved error handling when loading a template during output generation. (SHARED67730) l l TrueType "OS/2" tables in embedded fonts are now passed through as-is, and the output engine will no longer abort if it does not recognize them (for example, a newer version of the format). (SHARED-69378) Fixed a problem with simulating font style (generating styled fonts).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1500.html">PAGE 1500</a></h6> <p>Workflow 2019.2 Improvements New email plugins Several new email related Workflow plugins have been created to improve the email sending performance by simplifying integration with external Email Service Providers (ESP). The original Create Email Content renders email messages and sends these over SMTP in a single run. This limits use to the slower SMTP protocol, which becomes a bottleneck when larger batches are processed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1501.html">PAGE 1501</a></h6> <p>With Connect 2019.2 we also introduce connectors for the Email Service Providers SendGrid and MailJet, to facilitate fast bulk processing. (SHARED-71120/71123) These new connector plugins can be used to send pre-rendered email content (created by the new Render Email Content plugin) to either SendGrid or MailJet for bulk processing. The plugins will be made available via http://help.objectiflune.com.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1502.html">PAGE 1502</a></h6> <p>These stand alone plugins will be available from http://help.objectiflune.com/en/#ppc-plugins. New PDF to Bitmap plugin A new PDF to Bitmap plugin provides functionality for converting page(s) of a PDF to either JPG or PNG image format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1503.html">PAGE 1503</a></h6> <p>Workflow display improvements Process branches and conditions can now be collapsed and expanded to allow a better overall view. (SHARED-63520) CTRL-A now available The CTRL-A (i.e. Select All) keyboard shortcut has been implemented in all edit/memo controls in Workflow, making it easier to select the entire contents of a field.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1504.html">PAGE 1504</a></h6> <p>Passing runtime parameters to Connect plugins It is now possible to pass runtime parameters to the All In One plugin's Job Creation panel as well as to the Job Creation plugin itself.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1505.html">PAGE 1505</a></h6> <p>General Workflow Improvements l l Create Email Content now supports adding both the sender name and sender email address by expressing the email/name combination as "My Name <myemail@myhost.com>" in the Sender Address field. (SHARED-69901) Improved error reporting, as the actual error information is now included as part of the Error process. Whenever an error occurs in a plugin in Debug mode, the error message now appears in the Debug Information panel of the UI under the error.errorlog variable.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1506.html">PAGE 1506</a></h6> <p>They can be found here. License Update Required for Upgrade to Connect 2019.1 From OL Connect 2019.1 onwards, only customers with a current OL Care subscription will be able to update Connect. Every Connect license will now contain an end date that represents the last day of OL Care coverage for each customer. Upgrades and updates of Connect will be freely available up until that end date, but will not be available thereafter, unless the OL Care period is extended.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1507.html">PAGE 1507</a></h6> <p>Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 2019.1 and PlanetPress Workflow 2020.1, as well as some important installation information. Installing PlanetPress Connect 2020.1 and PlanetPress Workflow 2020.1 l l l PlanetPress Connect is released as a 64 Bit version only (with the exception of the Workflow, Fax, Search and Imaging modules).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1508.html">PAGE 1508</a></h6> <p>OL Connect 2019.1 Enhancements Script Debugger Connect 2019.1 introduces a new Script Debugger. This provides options to step through code (i.e. execute the code line by line) and to add breakpoints to pause execution at strategic points, as well as displaying the current state of variables, both local and global. (SHARED-66671) The Script Debugger simulates an output run for all sections in the current context, including section clones.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1509.html">PAGE 1509</a></h6> <p>These Project Wizards create building blocks to kick-start your projects as well as providing samples that explain Connect concepts and capabilities. A Project Wizard generates a pre-configured Workflow configuration and associated Connect Templates, Data Mapper configuration, Job Presets and Output Presets. The Project Wizard creates a folder containing all the resources along with a workspace folder that is ready to be modified, tested and deployed. Connect 2019.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1510.html">PAGE 1510</a></h6> <p>l Capture OnTheGo Timesheets, a set of Workflow processes to deploy and serve COTG Timesheet forms. Additional processes capture the submitted data and illustrate how this information can be stored in JSON, XML and PDF formats. The PDF is generated by merging the data with a Connect template. These new projects are also available from the Welcome screen.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1511.html">PAGE 1511</a></h6> <p>Improved Data Model view l Grouping/Ungrouping items PlanetPress Connect 2019.1 introduces the ability to add and modify logical Groups within the Data Model view. This enhancement doesn't impact on the database structure itself, but it does allow you to manipulate the way the data is presented within Connect . Groups are a purely logical construct and can be nested within other groups, and expanded or contracted as desired.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1512.html">PAGE 1512</a></h6> <p>l Filtering the view Data Model pane now allows filtering the displayed database items via a new Filter box. This narrows the list of displayed items to just those tables, groups or fields whose name contains the typed string.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1513.html">PAGE 1513</a></h6> <p>New Translation feature A multilingual Connect template can handle content and static text elements in more than one language. Traditionally this was done through creating a separate Template or Section for each of the language variants. A new Translation feature in Connect 2019.1 simplifies this process and introduces options to export translation strings in a standardized file format.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1514.html">PAGE 1514</a></h6> <p>Installer Improvements l l l You can now modify your installation choices, when upgrading Connect from an earlier version. (SHARED-67956) The Database Connection Check now displays a progress monitor, which is useful when attempting to connect to remote databases. (SHARED-23309) Now able to connect to a non-Connect-installed instance of MySQL with an encrypted connection using SSL for main Connect application database interactions.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1515.html">PAGE 1515</a></h6> <p>Connect 2019.1 Designer Updates Scripting Improvements l l l Regular JavaScript resources can now have Defer and Async properties set, as was already the case for remote JavaScript resources. (SHARED-67235) Scripts created by the Make Conditional option previously just used the ID and class of an element by default for the selector, but this can now be changed as desired from within the Edit Script dialog.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1516.html">PAGE 1516</a></h6> <p>Barcode Improvements l l Added support for the Japan Post barcode. (SHARED-59708 / 59711) Most barcodes except the 4 state barcodes (Australia Post, Japan Post, Kix and Royal Mail 4 State) and One Code now have an option to enable\disable Tilde Processing. (SHARED-68565) When this option is disabled, notations like "~d009" will no longer add a tab character to the barcode value. Rather the literal value "~d009" will be encoded.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1517.html">PAGE 1517</a></h6> <p>General Designer Improvements and Fixes l l l l Added ability to copy the location of snippets and images, so the locations can be pasted into scripts to simplify using those resources in scripts. (SHARED-33976) We've added filter options to the Package and Send To Worklow dialogs, to make it easier to locate the correct presets. (SHARED-68033) The Package and Send To Worklow dialogs now automatically add the last modified Output Creation and Job Creation configurations to the package.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1518.html">PAGE 1518</a></h6> <p>l l Added a Shared Content Editing option to the View menu with which you can disable/enable the editing of Shared Content in the template. (SHARED-60983) Default section clone names weren't always made unique when creating multiple clones. This could lead to lost clones, when naming conflicts arose. This issue has now been fixed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1519.html">PAGE 1519</a></h6> <p>Connect 2019.1 DataMapping Updates Stepping Improvements In complex Data Mapping configurations, the Steps pane can contain hundreds of steps. This made the interface sluggish when the navigating from step to step. Accordingly, the interface has been modified to redraw much more quickly than it used to. Visually speaking, the dotted lines that used to connect each Step have been reworked to now use full lines that are drawn directly onto the display.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1520.html">PAGE 1520</a></h6> <p>The results are displayed next to the Find box, and one can click on the Next / Previous match buttons to immediately jump to the next/previous step within the list of matches. XML Performance Improvements The XML Viewer has been completely overhauled resulting in a much more responsive interface. It is now possible to scroll through extremely large records (i.e. thousands of elements) as easily as one would a text file. But the changes are not limited to the interface.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1521.html">PAGE 1521</a></h6> <p>XML boundaries XML boundaries now can be split on variable element names. This solution adds the ability to specify an XPATH statement as the boundary, instead of a fixed element name. The XPATH statement supports dynamic values, allowing the boundaries to adjust dynamically to values passed by Workflow. (SHARED-65739) General DataMapping Improvements l l l l Improved compatibility with third-party PDF files.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1522.html">PAGE 1522</a></h6> <p>l Enhanced print job summary in Server logs. A summary of print jobs will now be displayed in the Server logs when either printing to the Server from Designer, using an All-In-One plug-in from Workflow, or by submitting a request to the All-In-One Process. (SHARED-66793) l l l Improved page breaking. This might impact upon some existing templates. (SHARED-68453) Extended the range of allowable Media weights. Media weight now ranges from 25 to 1000 gsm.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1523.html">PAGE 1523</a></h6> <p>l PDF output l l Added support for e-Invoice PDF (PDF/A-3b) output. (SHARED-68209) Redesigned the Digital Signatures section of the PDF output options to use a tree display which better reflects the structure of digital signatures. (SHARED-68364) l Added support for internal hyperlinks within a PDF document. (SHARED-52674) l XMP data now output in Canonical format for PDF/VT output. (SHARED-68483) l It's now possible to control the metadata in PDF output.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1524.html">PAGE 1524</a></h6> <p>General Output Improvements l l l The PDF Preview function and PDF attachments created for Email messages now have the same producer name as standard Connect PDF output. (SHARED-56002) Improved memory footprint of the output engine. (SHARED-67225) Several improvements have been made to the output engine to ensure that output creation terminates even in exceptional circumstances. For example when handling faulty input files or in tight memory situations.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1525.html">PAGE 1525</a></h6> <p>Print Wizard and Preset Wizard Improvements Dynamic Print Control Improvements Improvements have been made to the creation of Dynamic Print Controls. l l l l When working with PPD files to dynamically drive PostScript printers, some printers have fragments called JobPatchFile in their PPD, which are required for the printer to function properly. These are now supported and automatically added to the output if the PPD includes such.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1526.html">PAGE 1526</a></h6> <p>Import multiple Presets You can now import more than one preset at a time in the Job Preset and Output Preset wizards, as well as in the Print dialog. (SHARED-66727) Improved Data Filtering Options The Data Filtering page in the Print Wizard has been totally revamped. It has been enhanced with extra features, and the user interface overhauled. The user interface is now much more consistent with other rule builders available within the Print Wizard.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1527.html">PAGE 1527</a></h6> <p>General Print Wizard Improvements l l l l The Additional Content dialog now uses the selected Designer language's decimal and thousand separators in entry boxes. (SHARED-60881) Sample size preferences for standard and booklet imposition setups are now saved to the output preset.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1528.html">PAGE 1528</a></h6> <p>Workflow 2019.1 Updates PDF/A-3 e-Invoices A number of national standards now rely on PDF/A-3 as a standard for e-Invoicing. Workflow can now add invoice information and set Conformance levels for both the German (ZUGFeRD) and French (Factur-X) PDF/A-3 outputs via the new PDF/A-3 plug-in. More e-Invoice standards will be added in future releases. (SHARED-69195) NodeJS NodeJS now accepts raw content types. It is possible to send a raw JSON, XML, HTML, CSV, CSS, JS, TXT and XHTML body.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1529.html">PAGE 1529</a></h6> <p>Capture/Send emails with SSL support You may now retrieve emails from and send emails through secure online mail servers like Office365 or GMail. Different encryption methods can be specified, with the default (TLS v1.2) working out of the box with Office365 and Gmail. The new Secure Email Input task allows capturing POP3 or IMAP emails with SSL The new Secure Email Output task support. This means Workflow can now process provides an option for sending emails with SSL support.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1530.html">PAGE 1530</a></h6> <p>General Workflow Improvements l You can now specify the color of the highlight for any task to allow color coding of tasks or sections to make them stand out better. (SHARED-61963) This enables you to define personalised color schemes. For instance Scripts could always be highlighted in red, or each Send To Folder task could have a different color, based upon its destination folder. l l Connect resources which have been used are now logged when a Connect plugin finishes.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1531.html">PAGE 1531</a></h6> <p>l l New Workflow specific configuration Preference option introduced to Connect Designer to cater for instances where the Workflow is running on a different machine with a different Windows codepage. (SHARED-69053) New option added to the Workflow preferences to determine whether the current Workflow Configuration should be automatically re-opened when the Workflow application is next started. (SHARED-65133) Known Issues As of PlanetPress Connect 2018.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1532.html">PAGE 1532</a></h6> <p>They can be found here. Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 2018.2.1 and PlanetPress Workflow 2018.2, as well as some important installation information. Installing PlanetPress Connect and PlanetPress Workflow l l l PlanetPress Connect is released as a 64 Bit version only, although the PlanetPress Workflow, Fax, Search and Imaging modules are 32 Bit..</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1533.html">PAGE 1533</a></h6> <p>Upgrading from PlanetPress Connect 1.7 It is highly recommended that you update the Objectif Lune Update Client before upgrading PlanetPress Connect from version 1.7 to version 2018.2. If you do not update the Update Client, an unexpected error might occur whilst updating Connect. This error does not prevent the successful upgrade of Connect to 2018.2, even though it appears as if it might have.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1534.html">PAGE 1534</a></h6> <p>l l l l Backwards compatibility issues with Workflow/REST API processes that incorporate Connect DataMapper configurations connecting to databases. (SHARED-67683) External sort metadata fields were not being catered for properly in the metadata validation code in the Output Preset and Print Wizards. (SHARED-67687) Fixed a problem affecting scripted Section configurations containing different scripted values for different records. The merge engine would sometimes use previously applied scripted values.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1535.html">PAGE 1535</a></h6> <p>Connect 2018.2 Enhancements Sassy CSS PlanetPress Connect 2018.2 introduces Sass CSS preprocessor functionality to the Designer. (SHARED-64625) Sass (Syntactically Awesome Style Sheets) is an extension of CSS that enables you to use things like variables, nested rules, inline imports and more. Maintenance of CSS styles for templates requiring many different style rules can become a tedious undertaking. Stylesheets files keep getting larger and more complex and thus harder to maintain.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1536.html">PAGE 1536</a></h6> <p>Commingling Commingling (creating a job from content sets that were created with different templates) has now been added to PlanetPress Connect as a standard feature, just as it is for PReS Connect. (SHARED-64963) New ERP Template Wizards ERP templates have been added to the Template Wizards. (SHARED-52963) The new wizard allows you to create seven different transactional print documents, all with a uniform style. They all include a datamodel with appropriate scripting embedded.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1537.html">PAGE 1537</a></h6> <p>In Connect 2018.2 new scripting commands have been added to dynamically set Sheet Configuration options from within a Control Script. This allows you to set the Duplex mode dynamically, or do things such as applying a different Master Pages based upon the data, or omitting empty sides from the last sheet, or single sheets. The following Control Script sample enables Duplex mode for "Section 1": let section = merge.template.contexts.PRINT.sections["Section 1"]; section.sheetConfig.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1538.html">PAGE 1538</a></h6> <p>REST API Improvements REST API calls that take resource IDs, whether on the URL or in a JSON payload, have been improved in two ways. 1. The existence of the resource represented by the ID is now verified. If it doesn't exist, a HTTP status code of either 403 or 404 is returned. Previously the result was undefined and varied depending upon the call made.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1539.html">PAGE 1539</a></h6> <p>One change is the introduction of an option to set the Overall Logging Level. By default the logging level is set at the midpoint of Info, but it can be set higher to include more logging (All, Trace, Debug) or lower to reduce the logging (Warning, Error). NOTE: Higher logging settings will have an impact upon Connect production speeds, as well as leading to substantially larger log files. We have also introduced Advanced Logging preferences.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1540.html">PAGE 1540</a></h6> <p>l l The logging format default has changed from dd MMM yyyy (31 May 2018) to yyyy-MM-dd (2018-05-31) to make it easier to sort log files when using tools to merge and view multiple log files together. (SHARED-64233) Connect will now log a warning message in the event that there are insufficient engines currently available for a specific job, leading to the scheduler having to wait.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1541.html">PAGE 1541</a></h6> <p>Connect 2018.2 Designer Updates JSON support added to the Data Model Panel The Designer now allows you to add JSON sample data straight into the Data Model for debugging purposes. (SHARED-61655) This can be done via a new File menu option Or from the Data Model Panel itself, using the new JSON Sample Data button. Invoking this option launches a wizard which allows you to either select a JSON file or paste JSON data copied from a Workflow variable.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1542.html">PAGE 1542</a></h6> <p>Minimum Pages option added to Print Sections Connect 2018.2 introduces a new section property for controlling the minimum number of pages for a Print Section. This can be used to generate pages with only absolute positioned content, simplifying workflows where the number of pages are known up front and you want to draw boxes (absolute positioned divs) on specific pages. (SHARED-10236) The property can be set when the new Template is being created. Or through the Print Section properties.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1543.html">PAGE 1543</a></h6> <p>Color Output option added to Print Contexts For certain full color print jobs, it is important to be able to set black text on top of color areas to overprint. This is of particular importance for small text, because mis-registration problems are more visible with small text. To support this a new Color Output option has been added to the Print Context. (SHARED-62265) The default encoding for the color black has also changed from RGB to CMYK.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1544.html">PAGE 1544</a></h6> <p>Send To Workflow Improved The Send To Workflow option has been simplified and streamlined, and a new Package option has been added. (SHARED-60392) Paste as Plain Text option added Option added to paste content copied from an external editor as plain text. This ensures any unwanted formatting and invisible elements are removed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1545.html">PAGE 1545</a></h6> <p>Scripting Improvements l An overview ruler has been added to the Script Editor. The ruler shows annotations concerning the entire script. These annotations are shown relative to their position in the script and do not move as the user scrolls the script source. Script errors are highlighted by a red icon, and warnings in yellow. The topmost icon will display red if any errors exist in the script at all.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1546.html">PAGE 1546</a></h6> <p>l l l Scripts in Print Context jobs can now attach arbitrary properties to content items generated by Content Creation. The properties are retained in the database, allowing the information to be utilized in Workflow for further processing along with the base record information when retrieved by the Retrieve Items action. (SHARED-65239) Introduced "width" and "height" script functions with the same behaviour as jQuery's "outerWidth" and "outerHeight".</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1547.html">PAGE 1547</a></h6> <p>Business Graphics Improvements l l Color picker options added throughout the Chart Properties dialog. (SHARED-62564) The "Values (y)" table in both the Insert Graph Wizard and the Graph Script dialog can now be filtered to show only numeric fields. This will then limit the display to only Integer, Float and Currency fields in the Data Model.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1548.html">PAGE 1548</a></h6> <p>General Designer Improvements l l Download Remote Resources (CSS stylesheets, JavaScript files, JSON and HTML snippets) to your template through a new context menu in the Resources view. This allows you to keep a link to a centralized file but quickly download a copy to your template without having to separately copy and paste.(SHARED-58949) New Media now defaults to the same paper size as the current Print Section.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1549.html">PAGE 1549</a></h6> <p>l l Media Properties dialog behaviour improved. When any of the media in the Resources tree properties are changed, the "Page Setup" button gets activated and Designer prompts to save the media properties changes. (SHARED-62353) Disabled irrelevant menu items in the View menu when a Snippet editor is active.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1550.html">PAGE 1550</a></h6> <p>Connect 2018.2 DataMapping Updates Ignore Blank Lines Option added to the DataMapper Settings to ignore any blank lines in the data. (SHARED-57790) Dynamic SQL Queries Custom SQL queries now support the use of dynamic elements which can be built using JavaScript syntax. This allows an SQL query to use information passed on by Workflow to dynamically customize the query. (SHARED-34301) For instance, a custom query could contain the following code: =SELECT {automation.variables.FieldList} FROM {automation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1551.html">PAGE 1551</a></h6> <p>Set Data Fields as Not Required Individual data model fields can now be set as required or not required. By default all data base fields are initially set to being required. This new option provides the ability to set individual fields as not required. Non-required fields are indicated in the Data Model panel by a green asterisk ('*') symbol after the field type. (SHARED-60067) Landscape PDF Input Rotated PDF pages are now fully supported in PDF input files.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1552.html">PAGE 1552</a></h6> <p>This would get converted dynamically to something like ./address[@state="California"] based on the value of JobInfo(9). General DataMapping Improvements: l Can now set default values to ExtraData fields, in the same way as other fields. (SHARED61348) l Improvements in the way engines communicate in a multithreaded environment which should see a reduction in the number of times an engine fails to register with the server.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1553.html">PAGE 1553</a></h6> <p>Connect 2018.2 Server Enhancements Engine Setup The settings for the number of Connect Server engines to launch has been removed from the "Scheduling" settings page, which controls how the engines are actually used. They have been moved into a new "Engine Setup" page that controls how many engines of each type are to be launched. This also simplifies the Scheduling preferences page. Automatic Engine Restarts To safeguard server availability restarting the Connect engines periodically is recommended.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1554.html">PAGE 1554</a></h6> <p>and the engines can now be set to use a different port from the primary connection port. This prevents the engines from being starved from connections to the Connect Server if the external connections are not closed fast enough. These settings are located on the new “Connections” page of the Connect Server Configuration. The “Security” preferences page for the Connect Server connection is now a sub page of this new page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1555.html">PAGE 1555</a></h6> <p>Note: When running really large jobs, it often pays to increase Weaver memory allocation, even if only for the duration of the production job(s). Font handling l Additional Content Text improvements When adding text as Additional Content in Output Presets, TrueType Collections (TTC) font files were not supported. TTC fonts allow a single file to hold multiple fonts types. Since TTC fonts can be important for Asian language fonts, we have now added support for these.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1556.html">PAGE 1556</a></h6> <p>To accommodate such, we have provided an alternative font creation method which always creates CID fonts with identity encoding. This results in larger output files, but provides better compatibility with PDF viewers. When generating PDF for non-Western languages, this new option may be the recommended choice. l Asian language PDF output made smaller through improved glyph handling. (SHARED63549) l Further improvements made in handling simulated style fonts for OTF fonts.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1557.html">PAGE 1557</a></h6> <p>Email Output Improvements l l Meta information added to the Email Section Properties This allows viewpoint meta information to be added and configured in the email. This meta information will not be visible to the receiver, but can have an effect on how the email is represented in the email client. (SHARED-64761) Email Script dialog improvements The email Script dialogs have been streamlined and simplified.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1558.html">PAGE 1558</a></h6> <p>the specified conformance level. This has been fixed. (SHARED-61714) l In PDF/A-1b, PDF/X4 and PDF/VT output the document title in the PDF metadata is now derived from the template name, rather than the full path of the output file name. (SHARED61168) General Output Improvements l l l l l Output engine now warns instead of crashing if it encounters text with a non-invertible transformation matrix (such as a zero point size).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1559.html">PAGE 1559</a></h6> <p>Print Wizard and Preset Wizard Improvements Size grouping The ability to group documents by their size has been extended. In addition to grouping documents, you can now also group document sets and job segments by the number of pages. And instead of just using the page count, it is also now possible to use the sheet count for the size of the documents, sets, or segments. This makes size grouping useful for jobs that might contain both simplex and duplex content.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1560.html">PAGE 1560</a></h6> <p>Tip In Output Creation, you could create an output file per job segment, and use ${segment.metadata.ItemSize} in the output file mask to automatically name these files appropriately.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1561.html">PAGE 1561</a></h6> <p>Impositioning We have made a number of improvements to Impositioning, both by improving usability and by adding new features. These changes led to a redesign of the layout of the imposition wizard page, with some options being moved and others renamed. The major improvements are as follows. Visual warning The page layout diagram now displays in red when the selected imposition options do not fit the selected sheet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1562.html">PAGE 1562</a></h6> <p>have added a sample page setting that will be used for both the preview and the validation of the settings. This sample page now defaults to the size and orientation of the first section of a template, instead of its first media. Stack by Column Alongside the existing cut and stack impositioning order, we have introduced an imposition order that is more suited for continuous feed printing when the imposition has multiple rows.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1563.html">PAGE 1563</a></h6> <p>done properly, this causes the roll output by the printer to have the first page on the outside of the roll, allowing the roll to start with the first page. Our existing option to reverse the order of impositioning is reversing the order of the resulting imposition sheets by starting with the last side of the last sheet, and then going backwards. This effectively turns the stack up side down. It also means that, in case of duplex impositioning, all back sides become front sides and vice versa.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1564.html">PAGE 1564</a></h6> <p>Workflow 2018.2 Updates New HTTP Server Input - NodeJS An alternative HTTP server option now ships with PlanetPress Connect Workflow: NodeJS Sever Input. (SHARED-62247) The new implementation is backward-compatible with the existing HTTP Server Input (except for PlanetPress Capture requests), but also introduces several new capabilities. These include: l The ability to serve static resources from several folders. l Redirect requests to other servers using a Proxy list.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1565.html">PAGE 1565</a></h6> <p>Process Grouping Support has been added for nested Process grouping in the Workflow Configuration Components. (SHARED-65457) Groups can be added to existing groups, moved from one group to another or ungrouped within another group. In addition, multiple startup processes can now be defined. (SHARED-65454) This allows you to create startup processes that are specific to certain projects (or groups, or subgroups) and to specify the order in which the processes should run at launch time.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1566.html">PAGE 1566</a></h6> <p>l All-in-One can now accept a Job Preset configuration. The settings for this are contained in the new Job Creation tab. (SHARED-33510) Create Job Improvements l New option has been added to show only those Documents which are included in the job. (SHARED-53893) l All Content Set IDs are now stored in the metadata returned by the Create Job task.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1567.html">PAGE 1567</a></h6> <p>DataMapper Validation Option added to Execute Data Mapping to validate the records without actually extracting them. This provides an elegant option for determining potential data errors prior to actually running the job. (SHARED-57946) When running with this option, the Data Mapping task returns a summary of the data mapping job as well as a list of records that would generate an error, if any.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1568.html">PAGE 1568</a></h6> <p>l l Improved error handling when invalid JSON data is passed to a Create Content task in Workflow. (SHARED-63584) Retrieve items with Record ID list now trims white space from end of Record. (SHARED63603) l l When a Retrieve Items query returns multiple job sets, all the Job Set IDs are now stored in the Workflow Metadata at the Job level. (SHARED-64730) Improved Create Web Content task support for anchors.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1569.html">PAGE 1569</a></h6> <p>l Fixed potential security threats in HTTP Service static resources serving. (SHARED-61144) l Timeout in Connect Send Get Job Data plugin now works as expected. (SHARED-61308) l GetKeySets() command made backwards compatible. Command now retrieves all keys when parameter list is left empty or if the select all character ‘*’ is used. (SHARED-64160) Known Issues As of PlanetPress Connect 2018.1 the Known Issues have moved from the Release Notes to the Connect online Help. They can be found here.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1570.html">PAGE 1570</a></h6> <p>The license allows regular printing via the Print Wizard but runs Email and Web output in demo mode. For more information, please contact your local OL Customer Care or Sales team. Templates Used in Workflow For improved performance we recommend re-saving Workflow templates set up in the previous versions to run with PlanetPress Connect2018.1\Workflow 2018.1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1571.html">PAGE 1571</a></h6> <p>Upgrading from PlanetPress Connect 1.7 It is highly recommended that you update the Objectif Lune Update Client before upgrading PlanetPress Connect from version 1.7 to version 2018.1. If you do not update the Update Client, an unexpected error might occur whilst updating Connect. This error does not prevent the successful upgrade of Connect to 2018.1, even though it appears as if it might have.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1572.html">PAGE 1572</a></h6> <p>Connect 2018.1.6 Enhancements/Fixes Improved Weaver Engine memory usage Weaver Engine memory usage has been considerably improved. These changes have resulted in the Weaver Engines not only requiring fewer system resources but have also improved stability and reduced the need for periodic restarts. (SHARED-65330) Improved font handling l l Improved font style simulation, for when the full font family is not available.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1573.html">PAGE 1573</a></h6> <p>Connect 2018.1.4 Enhancements/Fixes PDF/A-1b compliance broken with Polish text An issue was discovered with Polish text in PDF/A-1b compliant output, whereby the output was missing "CIDSet" font descriptor entries for TrueType-based CID fonts. This error has now been fixed. (SHARED-64536/64816) Issues with text extraction from PDF output Problems were encountered in extracting non-latin and multilingual text from PDF output. These problems have now been addressed. (SHARED-64936) Connect 2018.1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1574.html">PAGE 1574</a></h6> <p>OutOfMemory Errors in PostScript Output When creating PostScript output or using the REST API to run a custom Enhance configuration containing one or more PostScript output channels, "OutOfMemoryError: Metaspace" errors could be encountered. This was due to JavaScript source code in the PostScript printer definition being compiled too often. This issue has now been fixed. (SHARED-64350) Issue with background image URL paths Fixed issues with URL path encoding.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1575.html">PAGE 1575</a></h6> <p>However, it was subsequently found that this could cause issues with previously created templates using the function on PDF files. Consequently, this change was reverted in 2018.1.1. (SHARED-64201) Workflow - Updated GetKeySets() implementation now made backwards compatible The Workflow function to retrieve key values GetKeySets() was updated in Workflow 2018.1 to use the more formerly correct asterisk '*' parameter for retrieving all key sets.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1576.html">PAGE 1576</a></h6> <p>This allows: l l The use of printer features that are not yet supported through the Connect user interface, such as: l switching between color and greyscale printing l selecting output bins Direct control of supported PostScript functionality, such as: l Duplex/Simplex l Print Media selection l Finishing options (e.g.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1577.html">PAGE 1577</a></h6> <p>NOTE: Case sensitivity/insensitivity has not been added as an option in this first cut of the Dynamic Print Control rules editor. This will be added in a subsequent version.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1578.html">PAGE 1578</a></h6> <p>Improved Business Graphics Business Graphics have been greatly enhanced and now display a preview of the data and graph as part of the Pie, Line and Bar chart wizards. The updated wizards simplify data selection and allows you to set and preview graph options dynamically, prior to inserting the graph object.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1579.html">PAGE 1579</a></h6> <p>Refer to the amChart documentation for more information on the numerous configuration options available. NOTE: As a consequence of changes in both the user interface and the underlying technology, Business Graphics made with a version prior to PlanetPress Connect 2018.1 may not display correctly when opened in version 2018.1. See the Business Graphics: Backwards Compatibility section on this page for full details.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1580.html">PAGE 1580</a></h6> <p>Windows Server 2016 now officially supported As of PlanetPress Connect 2018.1, Connect is now officially supported under Windows Server 2016. NOTE: The Objectif Lune Inc. Update Client application might be blocked by enhanced security settings in Windows Server 2016. To fix this, add http://updates.ca.objectiflune.com to the list of trusted web sites on that machine, or lower the internet access rules. Improved Previews The Preview now smooths text, images and line art when rasterizing a page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1581.html">PAGE 1581</a></h6> <p>New Preferences options: l l Scheduling preferences for Merge and Weaver engines now include a preference for specifying the memory (RAM) to be used per engine. (SHARED-44547) Merge and Weaver engine scheduling preferences now include an option for scheduling an engine restart if the total amount of memory (RAM) used by the engine exceeds the specified entry. This is in addition to the time limit setting.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1582.html">PAGE 1582</a></h6> <p>l Log file settings can now be adjusted within the Designer and Server Configuration preference windows. The settings are global to all Connect applications. Settings include log file rollover options (time or size based), and the format of the log messages generated. (SHARED-60043) Installer Improvements: l l l Prerequisites now installed silently when installing Connect using silent installer. (SHARED-59286) Messaging improved for when the Connect installer cannot safely commence uninstallation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1583.html">PAGE 1583</a></h6> <p>l l When using the REST API to execute a +PReS Enhance configuration that logged to a custom log file, the log file could not be deleted at the end of the execution. Repeating the execution of the +PReS Enhance configuration also caused unreadable NUL characters to appear in the log file and log messages were appended to it. This has been fixed and the custom log file now closes at the completion of the Enhance configuration execution. (SHARED-59656) Logging infrastructure has been updated.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1584.html">PAGE 1584</a></h6> <p>Connect 2018.1 Designer Enhancements/Fixes Updated internal browser component The browser component (Mozilla Gecko) used in the WYSIWYG editor of the Designer has been updated. This allows you to use new CSS properties like flexbox. Connect 2018.1 now uses Mozilla Gecko 38 as its HTML rendering engine. (SHARED-42286) NOTE: The update to the Mozilla Gecko engine could lead to increased output file sizes for some PCL jobs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1585.html">PAGE 1585</a></h6> <p>You can also select whether the Print Context should be added as a PDF attachment or not, using the "Attach Print context as PDF" check-box. Rotate and Scale Background Images Section Background images can now be rotated or scaled, either via the Section Properties dialog or via a control script. (SHARED-60244/60855) Align multiple objects You can now select and align several absolute positioned objects at once with the new Align Objects context menu.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1586.html">PAGE 1586</a></h6> <p>Preflight improvements Double-clicking a script warning or error in the Preflight report will now open the offending script within a script editor. (SHARED-60273) Improved language support Disable certain CTRL + ALT + <?> shortcuts in source editors, including source tab, HTML snippet editors and CSS editors.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1587.html">PAGE 1587</a></h6> <p>Scripting improvements: l l Option added to allow Case Sensitivity to be set on or off for any conditional string comparison scripts. (SHARED-56535) Improved support in Text Script Wizards for the custom formatting of Date, Currency, and Numeric fields. (SHARED-60261) The above example shows a custom pattern for a currency value, containing a subpattern for negative values. How the result would appear is shown in the Example field.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1588.html">PAGE 1588</a></h6> <p>l l l l Improved Email Context script selection. All the Email Context scripts are now bundled together in their own sub-menu. (SHARED-56602) Improvements made to the default data field selection logic when adding new Text Scripts. (SHARED-57286) Double clicking a script in the Script Panel with the script editor open will now prompt you to save your changes. (SHARED-47908) Any open Script Editor will now close when another template is opened.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1589.html">PAGE 1589</a></h6> <p>General Designer improvements: l l l Style rule changes can now be saved and applied instantly from within the Edit Rule dialog, via a new Apply button. (SHARED-58595) A new Send to Workflow icon has been added to Designer. It has been added as a new option in the icon toolbar and also to the File menu option. (SHARED-59322) You can now copy/paste or drag/drop images files from the file system or Images folder to the Stylesheets folder.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1590.html">PAGE 1590</a></h6> <p>l l l l l l l l l The New Email and New Print template wizards now open using the last used Template settings. Selections such as page size, page margins and the like will be retained. (SHARED-33982) Improved element insertion rules, to make context menus and dialogs more accurate. For example, the option to add Absolute elements in emails has been removed, as the email format does not support this functionality. (SHARED-60947/61117) Improved support for remote images (http-based URLs).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1591.html">PAGE 1591</a></h6> <p>Connect 2018.1 DataMapping Enhancements/Fixes Standalone DataMapper Engine The DataMapper Engine has been stripped into a separate stand-alone server. This is to make it more efficient and configurable as well as more adaptable in the future. The new DataMapper Engine options can be set via the Connect Server Configuration tool. (SHARED-59696) Improved date field support for Excel datafiles Formatting for date fields in Excel data files has been improved.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1592.html">PAGE 1592</a></h6> <p>Ignore CR/LF in Text records New option added to allow ignore end-of-line CR/LF characters in Text datafiles. This prevents empty trailing records being added to the dataset. (SHARED-62139) Create unique GUID in scripts New DataMapper Script function createGUID() added to the Boundaries and Steps scripts. This function returns a unique GUID. (SHARED-61246) New "No Data" warning A visual warning has been added to the DataMapper when an open table contains no data.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1593.html">PAGE 1593</a></h6> <p>l l It is now possible to add a CSV input file containing just a single column. (SHARED59814) Improved DataMapping performance for XML files containing large numbers of end-of-line CR/LF characters.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1594.html">PAGE 1594</a></h6> <p>Connect 2018.1 Output Enhancements/Fixes Redesigned Additional Content page in the Print Wizard The Additional Content page in the Print Wizard has been re-designed to present all the Additional Content entries in a single table, simplifying Additional Content management. (SHARED-56444) Improved Tray Mapping in Printer Wizard Media attributes can now be imported directly into the output config tray mapping from either the currently open template or from a saved template file.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1595.html">PAGE 1595</a></h6> <p>New Conditional option During Output Creation, it is now possible to determine the template section to which a sheet belongs to using the new sheet.sectionName property. This property has been made available as a conditional option in the Printer Wizard. (SHARED-61275) NOTE: The introduction of this property introduces a slight risk of compatibility issues, but only for cases where an existing custom printer definition or Enhance configuration already has a user-defined property with the exact same name.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1596.html">PAGE 1596</a></h6> <p>Print Output Improvements: l l l l Transparency support for PDF output. (SHARED-61492) Soft mask improvement in PDF. The soft mask is now set by the CTM ("Current Transformation Matrix") when the soft mask is created. (SHARED-58893) Improvements made to generic PCL output for some printers. (SHARED-60019) Booklet Impositioning for mix-plex jobs has been improved, reducing the likelihood of empty pages.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1597.html">PAGE 1597</a></h6> <p>Workflow 2018.1 Enhancements/Fixes Improved Performance The performance of the Execute Data Mapping and Retrieve Items tasks have been improved when setting the options to "Output Records to Metadata". (SHARED-56678) NOTE: The performance update to Retrieve Item is currently only implemented for Data Records. The other entity types will be added in a subsequent release. Retrieve Items by their IDs Option added to the Retrieve Items task to support retrieving items via their associated entity IDs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1598.html">PAGE 1598</a></h6> <p>New option in Create Web Content task An option to "Do not alter HTML" was added to the Create Web Content task. When selected the task shall not add the BASE element to the HTML as it usually does, nor shall it modify the local anchors with JavaScript code. (SHARED-62521) New option in FTP Input task An option to "Search in subfolders" has been added to the FTP Input task.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1599.html">PAGE 1599</a></h6> <p>New Workflow Preferences: l l You can now set the default Workflow scripting language. This defaults to VB Script for backwards comparability. (SHARED-60000) Improved PHP like Array options are now available for the HTTP Service plug-in. (SHARED-50770) Number of email attachments now available The number of email attachments is now available to the Email Input task.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1600.html">PAGE 1600</a></h6> <p>GUID variable introduced A new %U system variable has been introduced to support full GUID values. This new variable is an addition to the pre-existing %u ( a unique 15-char string). The new %U system variable is available in the same locations that the %u system variable is, including in the context menus.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1601.html">PAGE 1601</a></h6> <p>l Options for setting the logging refresh speed have been added. (SHARED-60029) Workflow Data Repository Manager improvements: l Improved Data Repository Key Set editor. (SHARED-59137/60165) l Improved speed when writing to a Data Repository. (SHARED-51564) l l l Instead of throwing an error the lookup() function now returns NODATA when an invalid group and/or key is passed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1602.html">PAGE 1602</a></h6> <p>l Fixed issue whereby Workflow would stop processing PostScript and PDF jobs on some Windows 10 Fall Creators Update machines. (SHARED-62516) Known Issues As of PlanetPress Connect 2018.1 the Known Issues have moved from the Release Notes to the Connect online Help. They can be found here. Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 1.8 and PlanetPress Workflow 8.8, as well as some important installation information.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1603.html">PAGE 1603</a></h6> <p>Upgrading from PlanetPress Connect 1.1 In order to upgrade from Connect Version 1.1 to Version 1.8 via the Update Manager, it is necessary to install a newer version of the Objectif Lune Update Client. The next time you run your current Update Client it will show that there is an update available for itself. Simply click on the download button in the dialog to install the new version of the Update Client. Note that it is no problem in running the update while the Client itself is still open.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1604.html">PAGE 1604</a></h6> <p>Updating stand-alone Workflow Messenger installations If Workflow Messenger was installed stand alone with no other Workflow components installed, the Update Client will be unable to find the Messenger component and thus it will not automatically update to the Workflow 8.8 version. To get around this, download and run the Workflow 8.8 installer manually. Print Only Version A Print Only license is available with version 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1605.html">PAGE 1605</a></h6> <p>Connect 1.8 General Enhancements and Fixes Native support for Microsoft Excel spreadsheet files The Connect DataMapper can now handle Microsoft Excel files natively. The CSV data type has been enhanced to automatically recognize *.XLS and *.XLSX files and use them directly without any additional steps. Both the CSV Wizard and the Add Data options now allow you to pick these file types.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1606.html">PAGE 1606</a></h6> <p>Dynamically set Media Background Images Support has been added for dynamically setting the path of media backgrounds at run time (aka Virtual Stationery). This is achieved via the Control Script API. The path can be set to an image in the Images folder but also to a file on disk (the http:// and https:// protocols are not currently supported). This greatly simplifies template management in situations where a design is shared between different brands.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1607.html">PAGE 1607</a></h6> <p>Installer improvements l Improved error capture, handling and messaging. (SHARED-40209) l Significantly improved logging of Server Service installation. (SHARED-50796) Korean Language Support PlanetPress Connect 1.8 is now available in Korean, in addition to the other languages already supported. Korean is not yet available in PlanetPress Workflow, however. (SHARED-40161) Context Sensitive Help Context Sensitive Help has been added to PlanetPress Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1608.html">PAGE 1608</a></h6> <p>Anchored positioned boxes losing style attributes Absolute positioned (Anchored) elements would lose some style attributes under certain circumstances. These issues would only occur when the absolute positioned element had multiple style attributes that ended with the text "top" or "left". Such as is the case with "padding-top" and "top". If both those attributes were set, then only one of the attributes would be retained. (SHARED-57361) l l Customers upgrading from 1.6.1 to 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1609.html">PAGE 1609</a></h6> <p>Note In the case that all engines are occupied, some changes will only take effect when the job finishes.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1610.html">PAGE 1610</a></h6> <p>Connect 1.8 Designer Enhancements and Fixes Automatically Fit Text to Container (Copy Fit) The Designer can now automatically scale text content to fit the boundaries of a box (inline or absolute positioned <div> ). Scaling text to fit a container is a very popular feature when creating personalized post cards and the like. The option is found in the Content tab of the Box properties dialog and can be set to scale all text or a specific element in that box by entering a CSS selector.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1611.html">PAGE 1611</a></h6> <p>Toggle Comments On/Off via Shortcut Keys Toggle comments off or on in HTML, CSS and JavaScript editors via a keyboard combination. Use Ctrl + / to comment out a single line and Ctrl + Shift + / to comment out multiple lines. (SHARED-56440) Refresh View button added You can now refresh the contents of both Design and Preview views via the new Refresh button or new Refresh selection in the Menu.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1612.html">PAGE 1612</a></h6> <p>Specify Page Range for Preflight You can now optionally perform Preflights on a range of records. (SHARED-35076) Select and adjust multiple Box elements simultaneously Multiple Box elements can now be selected at the same time. Once selected you can either move or resize the selected boxes as a group. You can move them either via the mouse, or by nudging them around a single pixel at a time with the arrow keys. When nudging, the boxes will not snap to guides.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1613.html">PAGE 1613</a></h6> <p>Set Template Locale Previously Connect always assigned the System Locale to new templates. A new option has been added to the preferences to allow the selection of a specific locale. This selection will then apply to all new templates thereafter. It applies to Date and Time fields plus numeric and currency data fields.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1614.html">PAGE 1614</a></h6> <p>General Designer improvements l l l l l l GS1 Datamatrix barcode now supported. (SHARED-55999) Section, Media, and Master resources can now be duplicated by copy-pasting. (SHARED-52261) Reopening a template will put the focus on the section that was active when the template was closed. (SHARED-53199) Keyboard shortcuts to increase (Ctrl + Shift + >) or decrease (Ctrl + Shift + <) text size now work as expected. (SHARED-11660) "Problem" view renamed more accurately as "Preflight Result".</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1615.html">PAGE 1615</a></h6> <p>Connect 1.8 DataMapping Enhancements and Fixes Extracting Variables without using JavaScript Variables are frequently used in data mapping configurations as counters or as a way to concatenate values before extracting the final result to a data model field. Until Connect 1.8, the only way to extract those variables would be to create a Javascript-mode field and to use the appropriate API syntax (e.g. automation.jobinfo.jobinfo1, or sourceRecord.properties.MyVariable).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1616.html">PAGE 1616</a></h6> <p>"Extract all from here" feature added In TXT mode, we’ve often had the request to be able to extract everything after a specific location, regardless of the record length. This would be useful, for instance, when extracting the body of an email which is never fixed-length. Until PlanetPress Connect 1.8, the customary way of proceeding would be to use a Loop step that stores all lines in a variable and an Extract step after the loop to store that variable into a field.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1617.html">PAGE 1617</a></h6> <p>Improvements made for Transactional Style Datafiles. l l l The DataMapper and Output have both been enhanced to better cater for extremely large data records (where thousands of details might be associated with a single record). (SHARED-51691). The Designer has been updated to allow a limit to the maximum number of records to display in preview. Tooltip now displays a warning if detail table exceeds the preview limit.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1618.html">PAGE 1618</a></h6> <p>Connect 1.8 Output Enhancements and Fixes Dynamic Finishing Print Output Finishing has been improved considerably, and is now much more powerful and flexible. In Templates, you could already set finishing for documents and sections. Job Creation would allow you to specify a different kind of Finishing for your documents and Templates. This has been extended to allow Finishing settings on all levels of Job Creation: Document Sets, Job Segments and Jobs.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1619.html">PAGE 1619</a></h6> <p>The reason we call this feature dynamic finishing, is that it includes a brand new rules editor to allow you to choose when to apply a finishing setting: Page 1619</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1620.html">PAGE 1620</a></h6> <p>PDF Pass-through Connect’s output creation (Weaver engine) tries to write content the best way possible, depending on the chosen output format and optimization settings. However, there are cases when this might not be desired, such as when the graphics have already been optimized for the device and you do not want the software to change them. It is now possible to instruct output creation to include PDF resources in the output file as-is.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1621.html">PAGE 1621</a></h6> <p>whether this will be an issue on your specific printer(s) or not. This issue will also be addressed in a later release. Overprint for Spot Colours Overprinting certain content on top of other content is sometimes required. (SHARED-56743) For example: l l To deal with special print applications, such as applying special (invisible) inks that are intended to go on top of coloured areas, for instance printing UV ink or applying varnish to a certain area.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1622.html">PAGE 1622</a></h6> <p>Print Output l l Mixplex support added An option has been introduced to omit empty back sides for the Single and Last sheet positions when Duplex is enabled, resulting in mixplex output. This helps in reducing costs in printing environments where page count or click-charging is applied. (SHARED46965\55459) Improved logging of output generation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1623.html">PAGE 1623</a></h6> <p>Capture OnTheGo (COTG) Enhancements and Fixes New and improved COTG library A new jQuery plugin variant of the COTG.js library introduces events and options for COTG widgets. These concepts greatly simplify event based programming. For example: it allows your code to set a date for a date field and retrieve the geolocation automatically on the drawing of a signature. The COTG jQuery plugin is the successor of the cotg-1.x.js JavaScript library found in COTG forms based on the COTG Starter templates (v1.x).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1624.html">PAGE 1624</a></h6> <p>Workflow 8.8 Enhancements and Fixes Deleting documents from the COTG repository Many COTG customers create documents for which they don’t want to set an expiry date (or a lifespan). They therefore set an expiry date far into the future to make sure the document remains in the repository. However, once the document has been filled they would like to remove it from the repository as soon as possible so it doesn’t clutter the view of the repository.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1625.html">PAGE 1625</a></h6> <p>The Connect Server has its own File Store which it uses for transient files. This File Store is managed by the Cleanup service who takes care of removing obsolete files when those files are not marked as permanent. This greatly reduces the amount of administration required to manage the files. We figured that since there is already a File Store and REST API calls to connect to it, why not turn that into an accessible feature for customer implementations? With Connect 1.8, the Workflow 8.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1626.html">PAGE 1626</a></h6> <p>Generating all contents using JSON instead of data records A number of customer workflows involve generating new versions of documents based on the original one created by Connect. For instance, a Delivery Note might come back with adjusted quantities on certain line items. Or a web-based status page might need to get updated with additional data. However in many cases, the original data must still be left untouched (for reprints, for instance).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1627.html">PAGE 1627</a></h6> <p>Converting XML to JSON and JSON to XML XML is already one of the most popular data formats used with Connect. In many implementations, most notably web-based ones, XML is used to transfer or update information back and forth between Connect and Workflow. However, using XML means the DataMapper must be involved each time the data changes, which impacts performance, especially when all you want is to update a Status web page.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1628.html">PAGE 1628</a></h6> <p>Full Timestamp entries added to Data Repository Added full timestamps to the Repository to allow for more precise information on each key set. The DateC and DateM keys now both contain a full time stamp in the form of: YYYY-MMDDThh:mm:ss.sZ. Please consult the online Help for a full description of the Timestamp. (SHARED-52160) General Workflow fixes and enhancements l Additional Tooltips added to interface. (SHARED-54981) l Improved support for multiple IDs in Retrieve items task.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1629.html">PAGE 1629</a></h6> <p>Known Issues Issues with Microsoft Edge browser The Microsoft Edge browser fails to display web pages when the Workflow's CORS option (in the HTTP Server Input 2 section) is set to "*". This issue will be resolved in a future release.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1630.html">PAGE 1630</a></h6> <p>GoDaddy Certificates When installing Connect offline, dialogs allow installing the GoDaddy certificates. Most users should use the default settings and click Next. In some cases, however, this may not work correctly. For this reason those users should activate Place all certificates in the following store and then select the Trusted Root Certification Authorities as the target certificate store. MySQL Compatibility After installing Connect 1.8 a downgrade to a Connect version earlier than Connect 1.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1631.html">PAGE 1631</a></h6> <p>l Generic PS LEVEL2 (DSC compliant) l Generic PS LEVEL2 (DSC) External Resources in Connect There are certain limitations on how external resources can be used in Connect. For example if you want to link a file (e.g., CSS, image, JavaScript etc.) from a location on the network but you do not want to have a copy of the file saved with the template you need to do the following: 1. The resource must be located where it can be accessed by all Servers/Slaves run as users.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1632.html">PAGE 1632</a></h6> <p>Colour Model in Stylesheets The colour model of colours defined in a stylesheet can sometimes change after editing the stylesheet. This is a known issue and will be addressed in a subsequent release.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1633.html">PAGE 1633</a></h6> <p>Print Limitations when the Output Server is located on a different machine The following limitation may occur when using the Print options from a Designer located on a different machine to the Output Server: l l l The file path for the prompt and directory output modes is evaluated on both the client AND server side. When printing to a network share it must be available to BOTH the Designer and Server for the job to terminate successfully.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1634.html">PAGE 1634</a></h6> <p>Once you have done this, PlanetPress Connect 1.7.1 will become available for download. From Connect Version 1.2 onwards, the newer version of the Update Client was included with the Connect installation. Updating stand-alone Workflow Messenger installations If Workflow Messenger were installed stand alone, with no other Workflow components installed, the Update Client will be unable to find the Messenger component and thus it will not automatically update to the Workflow 8.7 version.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1635.html">PAGE 1635</a></h6> <p>Connect 1.7.1 General Enhancements and Fixes Template Reports added to Connect Generate a report in PDF format containing the most important information about your template. The report lists contexts, sections, master pages, scripts, the data model, graphic files, and any other resources used, along with their properties. This report can be added as part of your project documentation.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1636.html">PAGE 1636</a></h6> <p>Document Properties Document Properties can now be added to both Templates and DataMapper Configurations. This allows you to specify properties such as the document author, the customer name and other important references. You can also add custom key/value pairs. The respective properties can be retrieved in scripting and are thus available as content in your documents. The information is also included in the Template Report feature.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1637.html">PAGE 1637</a></h6> <p>"Enhance with Connect" option added for PDF files in Windows Explorer A Windows Explorer context menu entry "Enhance with Connect" has been added for PDF files. When a user selects this context menu entry, PlanetPress Connect Designer opens with a prefabricated template, that uses the selected PDF file as the background. (SHARED15350/47156) Support added for Remote HTML and JSON Snippets In PlanetPress Connect 1.7.1 we introduce the concept of remote snippet resources.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1638.html">PAGE 1638</a></h6> <p>Handling Nested Detail Data Simplifying the handling nested detail data has been on our agenda for some time. As part of our research into this we have looked at an approach that repeats table rows for nested detail data. This doesn’t create HTML tables in HTML tables but rather clones a base row specified for each level. Consider the following image: At this stage there is no user interface to configure this type of dynamic table but in a separate Technical article.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1639.html">PAGE 1639</a></h6> <p>Installer improvements l l The PlanetPress Connect 1.7.0 installation did not work on machines running Windows 10 build 1703 (i.e. the "Creators Update", released March 2017). This has been fixed for PlanetPress Connect 1.7.1. (SHARED-56800) The silent installation process has been enhanced, and now supports the following: l l l l l l Setting the repository. This can be configured via the "product.repository" entry in "install.properties".</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1640.html">PAGE 1640</a></h6> <p>data fields. An eye icon has been added to the toolbar, and is used to toggle the visibility of the ExtraData field. In addition, you can select and group multiple fields in order to collapse them out of view (and expand them back, obviously), which is particularly useful when dealing with large data models that force you to constantly scroll up and down to bring a specific field into view. (SHARED-45370/54106) The Data Model panel has also been enhanced to allow alphabetical sorting of detail tables.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1641.html">PAGE 1641</a></h6> <p>Page 1641</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1642.html">PAGE 1642</a></h6> <p>Guideline behaviour improved Along with visible/invisible settings, Guidelines can now be locked in place or set to snap to objects, using the new Guides option in the View menu. (SHARED-47159). Warning now displayed when opening templates created in an older version When PlanetPress Connect opens an older template file it is automatically migrated to the template structure of the current version.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1643.html">PAGE 1643</a></h6> <p>These Warnings can be switched on again at any time thereafter, via the "Reset All Warning Dialogs" button in the General Preferences dialog. (SHARED-16962) Option to automatically Delete a dynamic table when the table is empty An option has been added to allow you to automatically delete a dynamic table when the data table is empty. To do so, select the entire table, and then tick the "Hide when empty" checkbox in the Attributes panel.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1644.html">PAGE 1644</a></h6> <p>Replace elements with data-insert-location when inserting HTML elements When inserting an element from an Insert dialog, Connect now checks the data-insertplaceholder attribute. The value of the attribute is then used to set the default value for the Insert Location option within the Insert dialog. If the attribute is not found, things behave as in previous versions. This ticket also introduces the Replace option for the Insert Location drop down.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1645.html">PAGE 1645</a></h6> <p>Scripting improvements l Context menu added to the Edit Script dialog. (SHARED-45381) . l l l l Find and Replace functionality has been added to Script editors. (SHARED-48424) New menu option to rename Scripts or Folders has been added to the Context Menu within the Script panel. (SHARED-48607) Support added for copy and paste of folders and scripts within the Scripts panel.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1646.html">PAGE 1646</a></h6> <p>General Designer improvements l l l l l l l Duplicate and Delete line(s) using shortcuts in the Stylesheet, JavaScript and HTML editors. Use Ctrl+D to duplicate and Ctrl+Shift+D to delete the currently selected lines. (SHARED-46928) Entering geometry values without stating a specific unit type will now automatically assign the default unit type to the entry. (SHARED-50656) When deleting an element (such as a Barcode or a Chart) on a page, a check will now be made for associated scripts.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1647.html">PAGE 1647</a></h6> <p>Capture OnTheGo (COTG) improvements l l l l l Two new form inputs have been introduced to facilitate the retrieval of the document ID and the store ID. (SHARED-53987/54054) Improvements made to updating the COTG library within existing templates. The user will now be prompted as to whether they wish to switch to the new version or not.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1648.html">PAGE 1648</a></h6> <p>Connect 1.7.1 DataMapping Enhancements and Fixes DataMapper can now fetch or update data from remote sources New in PlanetPress Connect 1.7.1 is the ability to create an XMLHTTPRequest object (aka XHR) in DataMapper scripts in order to issue REST/AJAX calls to external servers. This feature allows the datamapping process to complement the extraction process with external data, including data that could be provided by a HTTP process in Workflow.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1649.html">PAGE 1649</a></h6> <p>This yields two immediate and major benefits: l l Data Extraction is much faster since you are only extracting the records you actually want The database will not be cluttered with useless records (potentially numbering in the thousands) that you were not going to use anyway. As a consequence, the automated clean-up process will have much less work to perform when the time comes to delete obsolete entries from the database. This should result in a lighter workload and better overall performance.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1650.html">PAGE 1650</a></h6> <p>the record will still be stored in the database, with un-extracted fields being assigned whatever default value (if any) you defined for them. So if your goal is to completely prevent unwanted records from being stored in the database, you should make sure to implement your filtering conditions early in the data mapping process.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1651.html">PAGE 1651</a></h6> <p>General DataMapper Enhancements and Fixes l l l l l XML Wizard: option added to extract Attributes and to set boundaries on Attribute changes. (SHARED-42251) Improved support for UNC paths to image files. (SHARED-44316) The Extradata fields are now available in the DataMapper to more easily allow setting of field default values. The display of the Extradata fields can be toggled on or off directly from the Data Model panel. (SHARED-51426) New data.findRegExp() function added.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1652.html">PAGE 1652</a></h6> <p>This means that, apart from straightforward cases where we are grouping with or without sorting, it is also possible to create combinations where some fields do alter the sort order and others have no effect. Please note that grouping without sorting also means that any documents that have the same value for the same grouping field (i.e., customer number in the example above), but which are not consecutive in the input data, will not end up in the same group.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1653.html">PAGE 1653</a></h6> <p>Additionally, some settings on the Imposition Options page affect the way that booklets are created. These settings are now editable, so settings such as the gap between pages can now also be set for booklets.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1654.html">PAGE 1654</a></h6> <p>Additional Postal Services Barcodes added to Output Creation Barcodes for postal services are excellent candidates for adding during the Output Creation steps, rather than during Content Creation. Reasons for this include: l l l They often cannot be added during Content Creation because they depend on document size (or weight) and on a sort order that is determined during Job Creation. They need to go in a fixed position, dependent upon the envelope window, rather than document design.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1655.html">PAGE 1655</a></h6> <p>The new barcodes include: l Australia Post 4 State l KIX Code (Dutch postal service - Post.NL) l Royal Mail (UK) l Royal Mail 2D (UK) l USPS IMB (US) l USPS IMPB (US) Some of these barcodes have specific requirements in order for them to be usable. The respective postal services provide specifications and sometimes also the tools for generating the content of these barcodes. The checksums needed for Australia Post 4 State and IMPB are calculated automatically.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1656.html">PAGE 1656</a></h6> <p>Job Output Mask improvements, to simplify working with output file names We have improved the way that output file names can be specified. A new dialog box has been added to the Print Wizard, to simplify the creation of Job Output Masks. While it is still possible to directly type a file name with placeholders in the Output File Mask box, it is now also possible to use the dialog to pick the metadata fields and other variables that can be used to create dynamic file names.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1657.html">PAGE 1657</a></h6> <p>For the Output Preset to know what metadata is available, you can select a Job Preset when creating or modifying an Output Preset: In the Advanced mode of the Print Wizard this new dialog works a bit different, because the metadata can be directly edited in the same wizard instead of having to refer to a Job Preset. Tray Mapping for Multiple Templates For printing to a cutsheet printer, the Output Preset allows mapping of media defined in a template to trays and media known by the printer.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1658.html">PAGE 1658</a></h6> <p>such a way that no conflicting tray mappings can occur within a job, as Job Presets allow filtering by media type. Print Output l Improvements made to the Print Wizard These include: l Improved usability in Inserter dialog. (SHARED-38279) l Data Filtering dialog usability improved.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1659.html">PAGE 1659</a></h6> <p>Workflow 8.7 Enhancements and Fixes Custom Task descriptions The Comments section of each Workflow Task can now be used as the task's description in the Workflow Configuration tool, allowing users to better document the process without having to resort to numerous Comment Tasks. (SHARED-39120) Workflow processes can sometimes become rather complex and thus they require some documentation in order to allow subsequent users to know why they were implemented in one fashion or another.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1660.html">PAGE 1660</a></h6> <p>reason (reprints, produce additional jobs, etc.), you will have to perform the data mapping configuration from scratch. So make sure you only tick the box for true one-off jobs. (SHARED48956/56420) Retrieve Items task now has a JSON Output option The Retrieve Items task can now output the results of its query as a JSON string instead of storing them within the metadata. This allows easy handling of the results either through Workflow Scripting or directly in the Designer.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1661.html">PAGE 1661</a></h6> <p>Note The "Test SMTP Settings" does not work when using TLS. This limitation will be addressed in a later release. General Workflow fixes and enhancements l l l l l l l l l l Improved datamapping speed when outputting records in metadata. (SHARED-38455) Improved performance when creating metadata after Content Creation. (SHARED47150) Processing a Secure PDF as passthrough through CreatePDF will retain the Security options.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1662.html">PAGE 1662</a></h6> <p>Known Issues Issues with Microsoft Edge browser The Microsoft Edge browser fails to display web pages when the Workflow's CORS option (in the HTTP Server Input 2 section) is set to "*". This issue will be resolved in a future release.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1663.html">PAGE 1663</a></h6> <p>MySQL Compatibility After installing Connect 1.7.1 a downgrade to a Connect version earlier than Connect 1.3 or to a MySQL version earlier than 5.6.25 is not seamlessly possible. This is because the database model used in Connect 1.3 and later (MySQL 5.6) is different to that used in earlier versions. If you need to switch to an older version of Connect / MySQL, it is first necessary to remove the Connect MySQL Database folder from "%ProgramData%\Connect\MySQL\data" before installing the older version.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1664.html">PAGE 1664</a></h6> <p>do not want to have a copy of the file saved with the template you need to do the following: 1. The resource must be located where it can be accessed by all Servers/Slaves run as users. Failure to do this will cause the image to appear as a Red X in the output for all documents which were merged by engines which could not access the file. The job will terminate normally and the error will be logged. 2. The file must be referenced via a UNC path e.g.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1665.html">PAGE 1665</a></h6> <p>Online Help Links Point to Introductory Page Context sensitivity for the online help is not yet enabled in Connect. All links and F1 calls point to the introductory page, where you can Search on keywords to bring up Help pages relating to the topic. Context sensitivity will be introduced in a subsequent release of Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1666.html">PAGE 1666</a></h6> <p>model. Fields of other types will not be updated in the database and no error will be raised. This will be fixed in a later release. Print Limitations when the Output Server is located on a different machine The following limitation may occur when using the Print options from a Designer located on a different machine to the Output Server: l l l The file path for the prompt and directory output modes is evaluated on both the client AND server side.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1667.html">PAGE 1667</a></h6> <p>l Note that both PlanetPress and PlanetPress Connect Workflow come with a 30 day trial licenses by default. Updating from PlanetPress Connect 1.1 In order to upgrade from Connect Version 1.1 to Version 1.6.1 via the Update Manager it is necessary to install a new version of the Objectif Lune Update Client. The next time you run your current Update Client it will show that there is an update available for itself.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1668.html">PAGE 1668</a></h6> <p>Reduced Memory Version Note This is not recommended for production. It is now possible to install PlanetPress Connect on a machine with a minimum of 2 GB of RAM. The PlanetPress Connect Designer will automatically detect whether it has been installed on a machine with less than 4 GB of RAM and default to only using one internal Weaver and one internal merge engine on that system. The Server will also run using internal engines.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1669.html">PAGE 1669</a></h6> <p>OL Connect Send OL Connect Send is an application of two components. The first is a Windows printer driver and the second is a set of Workflow plug-ins. In its most basic form, OL Connect Send allows the transmission of print files over the Internet from any Windows Desktop application. OL Connect Send flavors OL Connect Send comes in three flavors. These are: l l l Free of charge: No license required; any user; any domain; no usage limits; no web interaction.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1670.html">PAGE 1670</a></h6> <p>l Supply Chain: Inbound document processing, such as capturing inbound invoices or POs for publication in an ECM. Print to EDI for outbound documents such as invoices. For further information on Connect Send, please refer to the OL Connect Send website and standalone User Guide.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1671.html">PAGE 1671</a></h6> <p>Connect 1.6.1 General Enhancements and Fixes Performance improvements l Changes to the handling of transparency in PDF backgrounds has not only cured some job failures, but has also led to substantial improvements to both output speeds and filesizes. (49680) l Improved processing speed for multiple large detail table documents. (47252/48537) l Improvements made to the clean-up processes, improving overall production speed. l Some memory leaks plugged, improving overall production speed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1672.html">PAGE 1672</a></h6> <p>Connect 1.6.1 Designer Enhancements and Fixes General Designer improvements l Interface improvements such as inclusion of icons for different types of files (js and CSS). l Provided option to configure the script timeout period. (48639) l Minor issues with non-English language translations fixed. l l l l l l Display issues that were sometimes encountered when changing section background images have been fixed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1673.html">PAGE 1673</a></h6> <p>Connect 1.6.1 DataMapping Enhancements and Fixes l Support for Regular Expressions added to database searches. (51694) l Improved Datamapping process reliability. l Improved data record reliability when handling large jobs (those in excess of 50,000 records). l Improved PDF extraction avoids character duplication. l Improved marking of data fields in extraction steps. l l l l l New option added to support multibyte (variable length) encoded data such as Big5, GBK, UTF-8 and Shift-JIS.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1674.html">PAGE 1674</a></h6> <p>Email Output l l l Fixed issue with the email Subject field not being encoded properly when using characters other than Latin characters. (48781) To improve privacy certain Meta tags that were embedded in the output email HTML have been removed. These include "email-reply-to", "email-from", "sender-name" and "sender-address". (49864) The Date field was not always included in the email header. This has been fixed and the Date field should now be present in all email headers.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1675.html">PAGE 1675</a></h6> <p>Connect Workflow 8.6 Enhancements and Fixes General improvements l l l l l l l l A multitude of changes and enhancements made to support new OL Connect Send functionality within Workflow. Support for password protection added to "Create PDF" task. (48380) Generic Data Repository field length extended beyond previous limit of 32 characters. (47734) Added new "Create PDF Preview" task for lightning fast creation of single record PDF. (49497) Minor issues with some language translations fixed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1676.html">PAGE 1676</a></h6> <p>l l Fixed potential out-of-memory error with very large Workflow configuration files. (51621) Fixed crashes encountered when large numbers of data selection calls were issued in highly threaded processes. (50569) HTTP and SMTP Server improvements l Support added for cross-origin HTTP (CORS HTTP) requests, to facilitate the development and testing of web templates. (47014) l Added option to specify SMTP port number in "Create Email Content" task.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1677.html">PAGE 1677</a></h6> <p>Known Issues Installing OL Connect Send on a machine with Connect installed. When OL Connect Send Plug-Ins are installed (either standalone or via a Workflow installation) on the same machine as Connect, an interference between OL Connect Send's internal Database and that of Connect may occur, which will block a browser popup on that same machine. This issue can be fixed by applying a startup wait to the Connect Server Service.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1678.html">PAGE 1678</a></h6> <p>1. Go to the .ini files for the Designer and Server Config: l l C:\Program Files\Objectif Lune\OL Connect\Connect Designer\Designer.ini C:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.ini 2. Change the language parameter to the required one under Duser.language=en | es | de | fr | it | ja | pt | tw | zh Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1679.html">PAGE 1679</a></h6> <p>To add additional printer models click on the settings entry box. button next to the Model selection Note that the descriptions of some of the printers were updated in version 1.2 meaning that if you had version 1.n installed, you may find that the same printer style appears twice in the list, but with slightly different descriptions.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1680.html">PAGE 1680</a></h6> <p>Using Capture After Installing Workflow 8 If PlanetPress Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, Capture can no longer be used within Workflow 7. The plugins are now registered uniquely to Workflow 8 and the messenger for Workflow 7 is taken offline. It is only possible to use Capture from PlanetPress Connect Workflow 8 thereafter.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1681.html">PAGE 1681</a></h6> <p>Merge\Weaver Engines when Printing The print operation in the Designer will automatically detect whether the Merge\Weaver engines are available and display a message for the user to retry or cancel if not. Once the Merge\Weaver engine becomes available and the user presses retry the print operation will proceed as normal.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1682.html">PAGE 1682</a></h6> <p>l When printing via the Server from a remote Designer, the output file remains on the Server machine. This is remedied by selecting “Output Local” in the Output Creation configuration. Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 1.5 and PlanetPress Workflow 8.5. Installing PlanetPress Connect 1.5 and PlanetPress Workflow 8.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1683.html">PAGE 1683</a></h6> <p>Print Only Version A Print Only license is available with version 1.5 of PlanetPress Connect which allows legacy PlanetPress Suite 7 customers on OL Care to upgrade to Connect for a minimal fee. The license allows regular printing via the Print Wizard but runs Email and Web output in demo mode. For more information, please contact your local OL Customer Care or Sales team.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1684.html">PAGE 1684</a></h6> <p>Simplified creation of templates based on existing PDFs l l l Option added to allow the creation of a new print document based on an existing PDF. (SHARED-19220) Improved support for adding PDF files as Section backgrounds. Files can now be referenced from disk or imported into Template. (SHARED-42496) Added support for drag and dropping Data Fields directly onto the page as absolutely positioned textboxes.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1685.html">PAGE 1685</a></h6> <p>l l Barcode improvements made in Preview mode. Support added for resizing and dragging of absolute positioned barcode objects, as well as resizing of inline barcode objects. (SHARED-43641) Barcodes can now have transparent backgrounds. (SHARED-43659) Scripting improvements l l l l l New closest() command added to the Scripting API, to locate closest matching element above it in the Document Object Model (DOM) tree. (SHARED-41789) Script editing improved.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1686.html">PAGE 1686</a></h6> <p>l l l l New scripting options have been added to the COTG.js library to register custom functions for save and restore. (SHARED-40670) Colour picker support has been added to the COTG Starter Template wizards. (SHARED-33561) Improved speed/size of COTG Camera objects. Rather than embedding images in output PDFs, Connect now supports embedding data URLs in COTG templates. (SHARED38575) Documents from the Library now automatically deleted upon successful submission.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1687.html">PAGE 1687</a></h6> <p>Connect 1.5 DataMapping Enhancements and Fixes l l l l l Multiple Conditions step can now evaluate several conditions and branch out accordingly. (SHARED-14329/44435) Performance improvements made when extracting text from PDFs and spool files. (SHARED-43056) Improved default formatting when extracting Date, Float or Currency data fields. (SHARED-43415) An extra field is now appended to every Document record and to every Detail table inside that record.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1688.html">PAGE 1688</a></h6> <p>l l l l l l l New HCF file added that supports “top down wrap around sequence marks”. (SHARED42326) Use PostScript Media name values in the PostScript DSC comments, to improve subsequent searches. (SHARED-42826) Option added to allow storing of job resources on PostScript printer’s own storage medium. (SHARED-43467) OMR marks improved, with support added for Match Numbers (Match Code, MC).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1689.html">PAGE 1689</a></h6> <p>Connect 1.5 General Enhancements and Fixes Installer improvements l l Improvements made to installation robustness. The installer now copes better when encountered permissions issues during installation. (SHARED-43732/43737) The Update Client has been updated to 1.1.9 and has been included in both the Connect 1.5 and Workflow 8.5 installations.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1690.html">PAGE 1690</a></h6> <p>Connect 8.5 Workflow Enhancements and Fixes l l l l l l l l l l Support for PHP-like arrays for COTG or web-based form submissions. (SHARED-41706) New Workflow system variable (%r) added to allow a process to determine which if it is currently running in service or debug mode. (SHARED-43411) Create Output and the Connect All In One tasks can now be added as Output tasks without waiting for the operation's result. (SHARED-43413) The Folder Capture task can now monitor multiple folders.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1691.html">PAGE 1691</a></h6> <p>Known Issues Installation Paths with Multi-Byte Characters When installing the Chinese (Traditional or Simplified) or Japanese versions of Connect, if the user specifies an alternative installation path containing multi-byte/wide-char characters it can break some of the links to the Connect-related shortcuts in the Start Menu and cause an error to appear at the end of the installer. The workaround for the moment is to use the default installation path. The problem will be addressed in a later release.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1692.html">PAGE 1692</a></h6> <p>model used in Connect 1.3 and later (MySQL 5.6) is different to that used in earlier versions. If you need to switch to an older version of Connect / MySQL, it is first necessary to remove the Connect MySQL Database folder from "%ProgramData%\Connect\MySQL\data" before installing the older version. PostScript Print Presets The print presets for PostScript were changed from Version 1.1 onwards meaning that some presets created in Version 1.0 or 1.0.1 may no longer work.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1693.html">PAGE 1693</a></h6> <p>documents which were merged by engines which could not access the file. The job will terminate normally and the error will be logged. 2. The file must be referenced via a UNC path e.g., file:////w2k8r2envan/z%20images/Picture/Supported/JPG/AB004763.jpg l l UNC paths are required because the services will be unable to access mapped network drives (Windows security feature).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1694.html">PAGE 1694</a></h6> <p>Context sensitivity will be introduced in a subsequent release of Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1695.html">PAGE 1695</a></h6> <p>VIPP Output Some templates set up with landscape orientation are being produced as portrait in VIPP. It can also sometimes be the case that text and images can be slightly displaced. These are known issues and will be addressed in a later release of Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1696.html">PAGE 1696</a></h6> <p>the download button in the dialog to install the new version of the Update Client. Note that it is no problem to run the update while the Client is open. It will automatically update itself. Once you have done this, PlanetPress Connect 1.4.n will become available for download. From Connect Version 1.2.0 onwards, the newer version of the Update Client was included with the Connect installation. Print Only Version A Print Only license is available with version 1.4.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1697.html">PAGE 1697</a></h6> <p>Connect 1.4.2 Enhancements and Fixes Designer l l A blank page is no longer added to beginning of templates that use scripting to add pages from PDF files. This problem only appeared when saving to a new file from within Preview mode, or when generating output from Preview mode. (SHARED-44564) Image elements (<img>) referencing a PDF image would multiply when switching back and forth between Live and Preview modes, in both email and web contexts. This has now been fixed.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1698.html">PAGE 1698</a></h6> <p>The language can be selected during the installation of Connect or via the Language Setting options in the Preferences dialog (note that Connect needs to be restarted in order to apply the selected language). At present only the Connect user interface has been translated. Error messages and warnings will be translated for a later release.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1699.html">PAGE 1699</a></h6> <p>Welcome Screen Extended l l The Printer Definition Configs and HCF files available on the OL Connect website are now grouped by manufacturer, to simplify selection. Connect 1.4.1 also introduces Responsive Email Templates. Virtualisation l Connect is now supported on the Microsoft Hyper-V and Hyper-V/Azure environments as well as the VMWare Workstation, Server, Player and ESX infrastructure environments. Modifying Connect Installations l Connect 1.4.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1700.html">PAGE 1700</a></h6> <p>Email Context l Email context sections can be enabled or disabled based upon data value. (SHARED33656) l Email port number can now be specified as part of the host name. (SHARED-38008) l New template wizard for Slate templates by Litmus. (SHARED-36843) Print Context l l Ability added to mirror margins on back pages of Duplex jobs, via Facing Pages selection added in Sheet Configuration dialog. (SHARED-40505) Can now suppress Master Page on duplex back pages, if there are no contents.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1701.html">PAGE 1701</a></h6> <p>l l l Option to generate JSON string from data model fields to pass data record information to client side script. (SHARED-39337) CSS Class name completion suggests CSS classes based upon the current section. (SHARED-36870) CSS Style inspector allows full control over styles. (SHARED-22929) Connect 1.4.1 DataMapping Enhancements and Fixes l l l All fields can now be renamed through the Data Model view. (SHARED-40116) SQL Server data mapping can now use Windows Authentication credentials.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1702.html">PAGE 1702</a></h6> <p>Connect 8.4.1 Workflow Enhancements and Fixes l l l l l Major performance improvements when updating data records. (SHARED-38897) Stand-alone Update Data Record task allows data records to be updated in the database without having to create content. (SHARED-38867) Update Records operations performed in batches, allowing for unlimited number of records. (SHARED-38948) All-In-One task can now return the output file to the Workflow, to allow customising output destination(s).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1703.html">PAGE 1703</a></h6> <p>Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up. GoDaddy Certificates When installing Connect offline, dialogs allow installing the GoDaddy certificates. Most users should use the default settings and click Next. In some cases, however, this may not work correctly.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1704.html">PAGE 1704</a></h6> <p>Note that the descriptions of some of the printers were updated in version 1.2 meaning that if you had version 1.n installed, you may find that the same printer style appears twice in the list, but with slightly different descriptions. For example the following printer types are actually identical: l Generic PS LEVEL2 (DSC compliant) l Generic PS LEVEL2 (DSC) External Resources in Connect There are certain limitations on how external resources can be used in Connect.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1705.html">PAGE 1705</a></h6> <p>Capturing Spool Files After Installing Workflow 8 If PlanetPress Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, the PlanetPress Suite 7 option to capture spool files from printer queues will no longer function. The solution is to use PlanetPress Connect Workflow 8 to capture spool files from printer queues. Colour Model in Stylesheets The colour model of colours defined in a stylesheet can sometimes change after editing the stylesheet.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1706.html">PAGE 1706</a></h6> <p>l If the server is offline and you are not using Proof Print l On some occasions before the Print Wizard opens REST Calls for Remote Services The Server will now accept REST calls for all remote services and will make commands wait indefinitely until the required engines become available. The Server will log when it is waiting for an engine and when it becomes available. Note that there is no way to cancel any commands other than stopping the Server.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1707.html">PAGE 1707</a></h6> <p>Knowledge Base You can find extra information in Connect Knowledge Bases which complement the information contained in this manual.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1708.html">PAGE 1708</a></h6> <p>Legal Notices and Acknowledgements Warning: PlanetPress Connect is protected by copyright law and international treaties. Unauthorized reproduction or distribution of this program, via any means, in part or in whole, may be prosecuted to the full extent of the law. The license agreements for the associated open source third party components can be found in the following installation folder: C:\Program Files\Objectif Lune\OL Connect\Legal Notices This application uses the following third party components: l</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1709.html">PAGE 1709</a></h6> <p>source can be obtained from here: https://wikis.oracle.com/display/GlassFish/Java+EE+7+Maven+Coordinates l Hamcrest Matchers Copyright © 2000-2006, www.hamcrest.org. All rights reserved. l HyperSQL, Copyright © 2001-2010, The HSQL Development Group. All rights reserved. l l l l l l l l l l IcoMoon. Connect uses unmodified icons from IcoMoon (https://icomoon.io/#iconsicomoon) which have been made available under the Creative Commons By 4.0 license (https://creativecommons.org/licenses/by/4.0).</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1710.html">PAGE 1710</a></h6> <p>l l l l l l l l l l l JNA Version 3.5.1 which is distributed under the terms of the GNU Lesser General Public License Version (LGPL) 2.1. The source code for this can be obtained from the following location: https://github.com/twall/jna/releases Logback which is distributed under the terms of the Eclipse Public License (EPL) Version 1.0. The source code for Logback can be obtained from the following location: https://logback.qos.ch/download.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1711.html">PAGE 1711</a></h6> <p>l l l l l Tern which is distributed under the terms of the Eclipse Public License (EPL) Version 1.0. The source code for tern can be obtained from the following location: https://github.com/angelozerr/tern.java Web Services Description Language for Java which is distributed under the terms of the Common Public License v 1.0. The source code for this can be obtained from the following location: http://wsdl4j.cvs.sourceforge.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1712.html">PAGE 1712</a></h6> <p>l Apache Commons Lang l Apache Commons Logging l Apache Commons Pool l Apache Commons Text l Apache Commons Validator l Apache Derby l Apache Felix and dependencies l Apache Geronimo l Apache HttpClient Mime l Apache POI l Apache ServiceMix l Apache Xerces2 Java Parser l Apache XML Graphics l Apache XML Beans l Barcode4j l Google Collections l Google GSON l Hibernate Validator l Jackson JSON processor l Jetty l Liquibase l LMAX Disruptor l Objenesis l OpenCSV</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1713.html">PAGE 1713</a></h6> <p>l Woodstox Eclipse Technology: This Software includes unmodified Eclipse redistributables, which are available at www.eclipse.org. The Eclipse redistributables are distributed under the terms of the Eclipse Public License - v 1.0 that can be found at https://www.eclipse.org/legal/epl-v10.html.</p> </li> <li> <h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2020-1-english/page-1714.html">PAGE 1714</a></h6> <p>Objectif Lune Inc.disclaims all warranties as to this software, whether expressed or implied, including without limitation any implied warranties of merchantability, fitness for a particular purpose, functionality, data integrity or protection. PlanetPress, PReS and PrintShop Mail are registered trademarks of Objectif Lune Inc.</p> </li> </ul> </nav> </div> </section> </section> </main> <footer class="page-footer"> <div class="container flex-column py-3 py-sm-4"> <div class="row mb-1 mb-sm-2 mb-md-5"> <a href="/" class="brand offset-sm-0 col-sm-4 col-md-3 col-lg-2 offset-2 col-8 text-center text-md-start"><img class="logo-small" src="/assets/img/brand-large.png" alt="Manualshelf"/></a> </div> <div class="row"> <dl class="text-center text-sm-start col-sm-3"> <dt class="fw-bold">Who We Are</dt> <dd><a class="text-decoration-none" href="/about">About Us</a></dd> <dd><a class="text-decoration-none" href="/company">Company</a></dd> <dd><a class="text-decoration-none" href="/careers">Careers</a></dd> <dd><a class="text-decoration-none" href="/terms">Terms & Privacy</a></dd> </dl> <dl class="text-center text-sm-start col-sm-3"> <dt class="fw-bold">Resources</dt> <dd><a class="text-decoration-none" href="/brands">List of Manufacturers</a></dd> <dd><a class="text-decoration-none" href="/">Support</a></dd> <dd><a class="text-decoration-none" href="/press">For the Press</a></dd> <dd><a class="text-decoration-none" href="/press#assets">Media assets</a></dd> <dd><a class="text-decoration-none" href="/faq">FAQ</a></dd> </dl> <dl class="text-center text-sm-start col-sm-3"> <dt class="fw-bold">Get in touch</dt> <dd><a class="text-decoration-none" href="#">Blog</a></dd> <dd><a class="text-decoration-none" href="#">Email</a></dd> <dd><a class="text-decoration-none" href="/dmca">DMCA</a></dd> </dl> </div> <div class="row"> <div class="text-center text-sm-start col-sm-4 pe-sm-0"> <a href="https://www.facebook.com/pages/ManualShelf/1488826334681423" class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-facebook-f"></i></a> <a href="https://www.twitter.com/ManualShelf" class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-twitter"></i></a> <a href="https://plus.google.com/+ManualShelf" class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-google-plus-g"></i></a> <a href="http://www.pinterest.com/ManualShelf" class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none"><i class="fab fa-pinterest-p"></i></a> </div> <div class="col col-sm-8 d-flex flex-column align-items-center flex-sm-row flex-wrap flex-sm-nowrap justify-content-center justify-content-sm-end"> <div class="copy w-auto d-flex align-items-center justify-content-center justify-content-sm-end mt-2 mt-sm-0 me-2">ManualShelf © 2013-2025</div> <select class="form-select form-select-sm w-auto mt-2 mt-sm-0"> <option value="usa">USA</option> </select> <div> </div> </div>  <div id='pixel'> <script> googletag.cmd.push(function() { googletag.display('pixel'); }); </script> </div> </footer>  <script src="/assets/js/jquery-3.3.1.min.js"></script> <script src="/assets/js/bootstrap.bundle.min.js"></script> <script src="/assets/js/jquery.autocomplete.min.js"></script>  <script type="text/javascript"> $.extend({ redirectPost: function(location, args) { var form = ''; $.each(args, function(key, value) { form += '<input type="hidden" name="' + key + '" value="' + value + '">'; }); form = '<form id="s1" action="' + location + '" method="POST">' + form + '</form>'; $(document.body).append(form); $("#s1").submit(); } }); $(document).ready(function(){ $("#query").autocomplete({ minChars: 3, groupBy: 'type', paramName: 'q', dataType: 'json', serviceUrl: '/autocomplete', noCache: true, showNoSuggestionNotice: true, noSuggestionNotice: 'Zarro results found', onSelect: function (suggestion) { $.redirectPost(suggestion.data.url, {highlight: encodeURIComponent(JSON.stringify(suggestion.data.hls))}); } }); var toc = $('.toc-selector'); if (toc.length) { var slideParams = { duration: 800, easing: 'linear' }; toc.click(function() { $(this).toggleClass('open'); var section = $('.toc-content'); var isCollapsed = section.attr('data-collapsed') === 'true'; if (isCollapsed) { section.slideDown(slideParams) section.attr('data-collapsed', 'false') } else { section.slideUp(slideParams); section.attr('data-collapsed', 'true') } }); } }); var lastSmall = $(window).width() < 576; $(window).resize(function() { var newSmall = $(window).width() < 576; if (lastSmall != newSmall) { lastSmall = newSmall; window.location.href = window.location.href; } }); </script> </body> </html>