User Guide Version: 2019.
User Guide Version 2019.1 Last Revision: 2019-06-10 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-2019. 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.
Table of Contents Table of Contents 4 Welcome to PlanetPress Connect 2019.
The Workflow server The Connect server The Connect database The File Store The engines The REST API Known Issues The OL Connect 2019.1 license update does not cater for existing AFP input licenses Page break changes in 2019.1 Progress bar pausing during 2019.1 Content Creation Backend database might require periodic maintenance Windows 10 Search service impacting Connect Job Creation Presets: External Sorting change introduced in 2018.2 Engine Preferences: Backward Compatibility Issues introduced in 2018.
Uninstalling Important Note: Stop any active Anti-Virus software before uninstalling Connect.
Using the wizard for CSV and Excel files Using the wizard for databases Using the wizard for PDF/VT or AFP files 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 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
Condition Operators Text file PDF File CSV File XML File JavaScript Toolbar Welcome Screen DataMapper Scripts API Using scripts in the DataMapper Setting boundaries using JavaScript Objects Example Example Examples Example Example Example Examples Examples Example Example Example Example Text XML Functions The Designer Designer basics What's next? Features Templates Contexts Sections Print Copy Fit 369 369 370 372 373 373 375 375 377 378 381 383 389 393 395 398 400 401 403 406 409 413 413 417 418 419 420 4
Creating a Print template with a Wizard 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 Testing the template Sending the template to the Workflow tool Using COTG data in a template D
Content elements 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 prope
Colors Fonts Locale Spacing Using a Sass file Personalizing content Variable data Conditional content Dynamic images Detail tables Snippets Scripts Loading data Variable Data Formatting variable data Showing content conditionally Conditional Print sections Dynamic Images Detail Table Personalized URL Writing your own scripts Script types Creating a new Standard Script Writing a script Managing scripts Testing scripts Optimizing scripts Loading a snippet via a script Loading content using a server's API The
Exporting and importing translation files Designer User Interface Dialogs Keyboard shortcuts Menus Panes Preferences Toolbars Welcome Screen Print Options Job Creation Presets Output Creation Presets Page breakdown Australia Post 4 State Settings 857 859 860 949 956 968 992 1018 1024 1025 1106 1119 1139 1146 Codabar Settings 1148 Code 128 Settings 1151 Code 39 Settings 1154 Datamatrix Settings 1157 EAN-128 Settings 1159 EAN-13 Settings 1162 EAN-8 Settings 1165 Interleaved 2 of 5 Settings 11
Examples Examples Examples Examples Examples Examples Examples Examples Examples Examples Examples Examples Examples Example Example Example Example Example Examples Creating a table of contents Example Examples Examples Examples Examples Replace elements with a snippet Replace elements with a set of snippets Example Example Creating a Date object from a string Control Script API Examples Post Pagination Script API Setting the margins of a Print section Setting the header and footer of a Master Page Generat
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 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 Email output settings in the Email context and
Simplified access to MS SQL Server Connect 2019.1 Designer Updates Scripting Improvements Barcode Improvements General Designer Improvements and Fixes Connect 2019.1 DataMapping Updates Stepping Improvements Find functionality added to Steps XML Performance Improvements XML boundaries General DataMapping Improvements Connect 2019.
Known Issues Overview Connect 2018.1.6 Enhancements/Fixes Connect 2018.1.5 Enhancements/Fixes Connect 2018.1.4 Enhancements/Fixes Connect 2018.1.3 Enhancements/Fixes Connect 2018.1.2 Enhancements/Fixes Connect 2018.1.1 Enhancements/Fixes Connect 2018.1 General Enhancements Connect 2018.1 Designer Enhancements/Fixes Connect 2018.1 DataMapping Enhancements/Fixes Connect 2018.1 Output Enhancements/Fixes Workflow 2018.1 Enhancements/Fixes Known Issues Overview Connect 1.
Known Issues Overview Connect 1.5 Designer Enhancements and Fixes Connect 1.5 DataMapping Enhancements and Fixes Connect 1.5 Output Enhancements and Fixes Connect 1.5 General Enhancements and Fixes Connect 8.5 Workflow Enhancements and Fixes Known Issues Overview Connect 1.4.2 Enhancements and Fixes Connect 1.4.1 New Features and Enhancements Connect 1.4.1 Designer Enhancements and Fixes Connect 1.4.1 DataMapping Enhancements and Fixes Connect 1.4.1 Output Enhancements and Fixes Connect 8.4.
Welcome to PlanetPress Connect 2019.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.
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 137 l "Server Configuration Settings" on page 112 l Uninstalling System and Hardware Considerations There are a variety of considerations to be aware of.
Antivirus Exclusions Article #: INFO-0002 Product: OL Connect Version: 1.5 and up Description The information on this page is designed to assist IT managers and IT professionals decide what anti-virus strategy to follow with consideration to OL Connect and their internal requirements and needs.
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.
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.
l The SQL instance must be open to access from other computers. This means the bindaddress option should not be set to 127.0.0.1 or localhost. 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.
Note Since PlanetPress Connect version 1.6 the minimum required version of the MS SQL 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.
If the user has installed the Installer Supplied MySQL and then switches to an external Microsoft SQL by using the Server Configuration Tool, the supplied MySQL cannot be switched off. By design the installer adds a service dependency between Connect Server and the 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.
done as outlined above. 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.
on the server where PlanetPress Connect is located, unexpected behaviours may occur and 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.
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 Exclusion for more information. Antivirus software might interfere with installation scripts, notably a vbs script to install fonts.
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. Language and Encoding Considerations Please note the following considerations: l Language: l PlanetPress Connect is currently offered in several languages. These languages can be switch between via the Preferences dialog.
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 For Firewall/Port considerations, please see this article in the Knowledge Base: Connect Firewall/Port Configuration Performance considerations In order to get the most out of PlanetPress Connect, it is important to determine how best to maximize performance.
Improving performance beyond what can possibly be reached by using the methods described below requires purchasing either a Performance Pack or upgrading to PreS Connect (see Performance Packs). For advice please contact your local sales office (see Objectif Lune's Contact page). Engine configuration As explained in another topic ("Connect: a peek under the hood" on page 150) the Connect Server cooperates with different engines to handle specific tasks. A DataMapper engine extracts data from a data file.
Network and internet connections Use a fast network and internet connection or avoid loading external or internet resources. Using images, JavaScript or CSS resources located on a slow network or on a slow internet connection will obviously lead to a loss of speed. While we do our best for caching, a document with 5,000 records which queries a page that takes 1 second to return a different image each time will, naturally, slow output generation down by up to 83 minutes.
System requirements These are the system requirements for PlanetPress Connect 2019.1 Operating system (64-bit only) l Microsoft Windows 2008 R2 Server l Microsoft Windows 2012/2012 R2 Server l Microsoft Windows 2016 Server l Windows 7 l Microsoft Windows 8.1 l Microsoft Windows 10 (Pro and Enterprise versions only) Note Windows Vista, Windows 8.0, Windows 2003 Server and earlier versions of Windows are not supported by PlanetPress Connect.
Installation and Activation This topic provides detailed information about the installation and activation of PlanetPress Connect 2019.1. Note A PDF version of this guide is available for use in offline installations. Click here to download it. PlanetPress Connect 2019.1 is comprised of 2 different installers: one for the PlanetPress Connect software and one for PlanetPress Workflow 2019.1. Where to obtain the installers The installers for PlanetPress Connect 2019.1 and PlanetPress Workflow 2019.
l Installation l Silent Installation l Installation on machines without Internet access Activation For information on licensing, please see Activating your license. Installation Prerequisites l l l l l l Make sure your system meets the System requirements. PlanetPress Connect Version 2019.1 can be installed under a regular user account with Administrator privileges. PlanetPress Connect must be installed on an NTFS file system. PlanetPress Connect requires Microsoft .NET Framework 4.
Permissions for PlanetPress Connect Designer PlanetPress Connect Designer does not require any special permissions to run besides that of a regular program. It does not require administrative rights and only needs permission to read/write in any folder where templates or data mapping configurations are located. If generating Print output, PlanetPress Connect Designer requires permission on the printer or printer queue to send files.
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. Users of Connect 1.1 In order for users of PlanetPress Connect 1.1 to upgrade to any later version through the Update Manager it is necessary to install a later version (1.1.
Installing PlanetPress Connect on Machines without Internet Access Installing PlanetPress Connect2019.1 in offline mode requires some extra steps. These are listed below. Updating Connect Updating to Connect 2019.1 from earlier Connect version In order to update PlanetPress Connect to 2019.1 it is first necessary to update the Connect License. For details on how to upgrade the Connect License offline see the Upgrading Connect on machines with no internet access section in the Update Client 1.2.
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. The integrity of these files is checked at various times by different, context related, methods. One of these checks, done during the installation process, uses the Windows certificate validation check. .
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. Mount the ISO image from within Windows Explorer l If on a DVD, either insert the DVD and initiate the installation from there or copy the contents to a folder on the target computer (keeping the folder structure intact) Navigate to the PlanetPress_Connect_Setup_x64.
capabilities such as production content creation (print output, HTML content for emails and web pages), automation, commingling and picking. l MySQL Product: A supplied MySQL database used by PlanetPress Connect. The database is used for referencing temporary Connect files and for sorting temporarily extracted data, and similar. A pre-existing MySQL or Microsoft SQL server (referred to as an external database, in this documentation) could be used instead, for the same purposes.
l l l l Disk space required: Displays the amount of space required on the disk by the selected components. Disk space available on drive: Displays the amount of space available for installation on the drive currently in the Installation Path. Recalculate disk space: Click to re-check available disk space. This is useful if space has been made available for the installation while the installer was open. Source repository location: Displays the path where the installation files are located.
must be entered or the update will fail. If the password is subsequently forgotten, then the MySQL product must be uninstalled and its database deleted from disk before attempting to reinstall. l l Confirm MySQL user 'root' Password: Re-enter to confirm the password. Both passwords must match for installation to continue. TCP/IP Port Number: The port on which MySQL will expect, and respond to, requests. A check is run to confirm whether the specified TCP\IP Port Number is available on the local machine.
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 Product module was not selected for installation. This page is for setting up the connection to the existing External database. l l l l l l Database Configuration: Select the database type to use for thePlanetPress Connect Engine. Currently only MySQL and Microsoft SQL Server are supported.
l Use Encrypted SSL Connection checkbox: Check to enable encrypted connections to MySQL (v5.6.43, v5.7.25, v8.0.x or later) databases using SSL. The secure connection to MySQL is for the "objectiflune" schema. Note It is not in the scope of the Connect installer to configure the MySQL database Server to accept SSL connections. This must be done prior to the installation of Connect.
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. The user account selection must also be retained for future use, as the "Security Settings" on page 131 dialog can only ever be executed through the user account specified here. l l l Username: The account that the service uses to login.
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. Note: this checkbox may not be available in the event that an issue was encountered during the installation. Show Log...: If an issue was encountered during the installation, click this button to obtain details.
Before activating the software, please wait 5 minutes for the database to initialize. If the software is activated and the services rebooted too quickly, the database can become corrupted and require a re-installation. Running Connect installer in Silent Mode Updating to Connect 2019.1 from earlier Connect version In order to update PlanetPress Connect to 2019.1 it is first necessary to update the Connect License. For details on how to upgrade the Connect License see "Users of Connect prior to 2019.
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. If no product is mentioned, properties must be specified for all valid Connect products. Here is an example of an install.properties file. # Verbose logging logging.verbose = true # Product selection install.product.0 = Connect Designer install.product.1 = Connect Server # Server settings server.runas.
the Server Extension, because only Server or Server Extension can be installed at the same time). PlanetPress defaults install.product.0 = Connect Designer install.product.1 = Connect Server install.product.2 = MySQL Product Note The values of install.product properties must contain the exact product names. Server configuration (required if Server is selected for install) For Server, the following properties need to be provided: server.runas.username = server.runas.
database.unlocked = true or false (the default value is false, optional) Note The unlocked option should only be used when the database requires an external access. If the Silent Installer runs with the default product selection, MySQL Product is included, and hence the database.unlocked = true property may be optionally set if MySQL on this machine is intended to serve as the central database also for remote machines. If the Silent Installer runs with the explicit installation of a stand-alone (install.
required) database.password = (required) database.schema = (default value is objectiflune, optional) 2b: Configuring an external Microsoft SQL Server database Note Since PlanetPress Connect version 1.6 the minimum required version of the MS SQL Server is SQL Server 2012. To configure an external Microsoft SQL Server database, the following properties should be defined: database.type = Microsoft SQL Server (required) database.
(Setup) executable file). If a repository is found, the installer will attempt to install from that repository. 4. As a last resort, the installer will attempt to install from the default Connect Update Site URL. Examples product.repository = http://192.168.79.73/Connect/Version_ 01/repository product.repository = C:\\iso\\2.0.0.39695_unpacked\\repository Locale definition It is possible to define the Locale which affects the installation language and installed locale for Connect products by using the follo
Locale selection by defining user.language and user.country If both user.language and user.country are defined in the install.properties file, the combination must match exactly one of the supported locales, otherwise the Installer will exit with an error. For example, user.language = fr and user.country = CA will cause an error since fr-CA is not in the list of supported Locales. Locale selection by defining only user.language If only user.language is defined in the install.
3. Run this command to unpack the contents of the Connect Setup executable (as a sample, we use the PReS Connect brand): PReS_Connect_Setup_x86_64.exe -nr -gm2 -InstallPath=".\\" 4. In the local folder, the repository subfolder should now be located next to the preinstall.exe, installer.exe and other Installer files. 5. Create the install.properties file for silent installation in the local folder. 6. With a batch file calling preinstall.
:err_preinstall echo "Preinstall error - see preinstall_err.log" goto:eof Activating a License PlanetPress Connect and PlanetPress Workflow both come with individual 30 day trial license periods during which time it is not necessary to have a commercial license to run the applications. This allows time for reviewing the applications and for organizing a commercial license.
l l l l l l l Expiration Date: Displays the date when the activation will expire, or the current date if the product is not activated. End-User License Agreement - Appears only when loading a license file: l l Serial Number: Displays the trial license serial number or the activation serial number if the product has been activated in the past. License: This box displays the EULA. Please note that this agreement is legally binding. I agree: Select to accept the EULA.
Activating PlanetPress Workflow 8 PlanetPress Workflow 8 uses the same licensing scheme as PlanetPress Connect. There are two ways of activating the license for Workflow 8 after saving it to a suitable location: l l If only PlanetPress Workflow 8 is installed, double-click on the license for the PlanetPress Workflow 8 License Activation dialog to open. Applying the license here activates all of the Workflow 8 components.
restarted. Just click OK to proceed. Migrating to a new workstation The purpose of this document is to provide a strategy for transferring a Connect installation to a new workstation. The following guide applies to OLConnect v1.x and Workflow v8.x. Before installing the software Before upgrading to a new version, even on a new workstation, consult the product's release note to find out about new features, bug fixes, system requirements, known issues and much more.
we strongly recommended doing so. It is considered "Best Practice" to convert the documents to the version installed and then re-send them to the Workflow Tools. Backing up Workflow files To save all Workflow-related files, backup the entire working directory: C:\ProgramData\Objectif Lune\PlanetPress Workflow 8 Here are a few important points when transferring these files: l l l l l l If you are upgrading to the latest version of Connect, it is recommended to open each template in Designer, produce a
l l l l l l l Reconfigure local ODBC connections. (i.e. create local copies of databases or recreate required DSN entries) Backup and import other custom configuration files, Microsoft Excel Lookup files, making sure they reflect the same paths as previously.
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 (.OL-outputpreset): C:\Users\ [UserName]\Connect\workspace\configurations\PrinterDefinitionCo nfig OL Connect Print Manager Configuration files (.OL-ipdsprinter) C:\Users\ [UserName]\Connect\workspace\configurations\PrinterConfig OL Printer Definition File
Image, Fax and Search Modules l l Reconfigure the Image and Fax outputs with the new host information. Import the Search Profile and rebuild the database in order to generate the database structure required by the Workflow. Capture l l l l l l Download the latest version of the Anoto PenDirector. Before installing the PenDirector, make sure the pen’s docking station isn’t plugged into the server. Then install the PenDirector.
Configuring the Connect Engines Any changes made to the Server preferences require the OLConnect_Server service to be restarted to take effect.
l l Open the Server Extension Configuration from: C:\Program Files\Objectif Lune\OL Connect\Connect Server Extension\ServerExtension.
To apply the PlanetPress Capture License l l Open the Workflow Configuration Click on Help on the Menu Bar and click on PlanetPress Capture License manager to import your license. Uninstalling PlanetPress Connect from the previous workstation It is recommended to keep the previous install for a few days until everything is completed. However, once your transition is successful and complete, the OL Connect software must be uninstalled from the original server. See "Uninstalling" on page 147.
l l PlanetPress Workflow 2019.1 and PlanetPress® Suite Workflow 7 cannot run simultaneously, since only one version of the Messenger service can run at a time. In fact, no two versions of Workflow can be run simultaneously on the same machine, regardless of versions. It is possible to switch between different versions running by shutting down one version's services and then starting the other. However, this is not recommended.
What does PlanetPress Connect contain? PlanetPress Connect is comprised of the following modules: l PlanetPress Workflow 2019.1. This is the natural evolution of PlanetPress Suite Workflow 7 (Watch, Office or Production). PlanetPress Workflow 2019.1 is very similar to the PlanetPress Suite Workflow 7 version but contains a number of new features and has the ability to run PlanetPress Connect jobs, as well as PlanetPress Suite, PrintShop Mail Suite and PReS Classic documents.
Please note that PlanetPress Suite Workflow 7 and PlanetPress Workflow 8 cannot run at the same time. See Information about Connect Workflow 8 for information about these limitations. The only exception is the PlanetPress Suite Design tool that you can continue to use as it is not part of PlanetPress Connect. For customer upgrading to the full version of PlanetPress Connect, with or without new options, the next year of OL Care will be priced at the value of the new software you upgraded to.
l Even if you don’t recreate your existing PlanetPress Suite documents, you can easily change your workflow to convert your output to PDF, then output them in PCL to any device supporting it. Note If you were a PlanetPress Production user, you retain all functionalities within PlanetPress Workflow 2019.1. These are automatically imported during the activation (see below).
l l Easily create documents with tables that spread over multiple print pages, respecting widow and orphan rules, displaying sub-totals and totals properly. Have text that wraps around images. Upgrade steps 1. To upgrade to PlanetPress Connect, the first step is to stop your PlanetPress Workflow services. You can do so from the PlanetPress Workflow configuration tool or from the Windows Service Management console. 2.
5. If you installed PlanetPress Workflow 2019.1 on a different computer, please see "How to perform a Workflow migration" on page 77 for help importing all those settings, if you wish to import them. 6. To launch the Upgrade wizard, open the PlanetPress Workflow 8 configuration tool and, from the Tools menu, launch the Upgrade Wizard. IMPORTANT: Before you start this process, make sure you have a backup of your current installation/computer.
7.
8. Then select the product from which you wish to upgrade: 9.
10.
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, follow the instructions for the installation using the serial number provided to you. You can activate your license through the Web Activation Manager. 12.
How to perform a Workflow migration What do you need to consider when upgrading from PlanetPress Suite 7 to PlanetPress Connect Workflow 2019.1 on a new computer? Installing and Activating Workflow 2019.1 on a new computer Points to consider: l l l l Before installing, be sure to read the Installation and Activation Guide. There you will find detailed Connect Workflow installation steps as well as system requirements, notes on license activation and much more.
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. If you do not have access to the computer in which PlanetPress Suite was previously installed, print a Status Page for each printer from your Connect Workflow 8 Configuration.
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\PlanetPress Workflow 8\PlanetPress Watch\Documents" 3.
Alternatively, you can download custom plug-ins from this link 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. Missing plug-ins will be represented in Workflow steps through the use of a "?" icon. Such as in the following image, which shows that the "TelescopingSortPlugin" is not installed.
l l l If you are using images from a virtual drive, copy the entire contents of "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PSRIP" and paste them onto the new computer here: "C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PSRIP". Make sure to set the user who will run the PlanetPress Services. This is done by going into Tools/Configure services. The user will need to have local administration rights in order to be able to run the services. For more information, see Users and Configurations.
Note It is recommended that you first update your PlanetPress Suite to version 7.6 before cross-grading to PlanetPress Connect. Using PlanetPress Connect Workflow 2019.1 on the same computer as PlanetPress Suite 7.6 Steps to migrate: 1. Update existing installation to PlanetPress Suite version 7.6 if not already done. 2. Install PlanetPress Connect Workflow 2019.1 on the same computer. 3. Do the following for both PlanetPress Suite version 7.6 and PlanetPress Connect Workflow 8. 1.
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:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\DocumentManager". 6.
Once the Capture database has been transferred to the new computer, any update made 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.
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 2019.1 computer: "C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\c
> 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. Preferences The Preferences dialog is used to modify the general software preferences. Changes made in this dialog affect the software globally, not individual templates and data mapping configurations.
COTG Servers preferences This option allows one or more Capture OnTheGo servers to be set up, in order to be used with the Capture OnTheGo WIM product. l Name: Enter a unique name. l URL: Enter a valid URL (including the protocol, e.g. http://). l Restore Defaults: Removes all custom servers from the list and resets to the default Capture OnTheGo server. The COTG Servers Preferences also provides you with buttons to : l l Restore Defaults. This option restores the preferences to Defaults.
date. i.e. If the Connect job is not going to be re-run. The clean-up can always be set to run outside of business hours (see the Run according to the cron schedule option below), to reduce impact upon Production systems. The values below define when the specified targets are to be set as being ready for deletion, not when they are actually deleted.
which case the clean-up will fail to run). l Database Clean-up Service: l Allow database clean-up service: Select this checkbox to enable the database Clean-up settings, and enable the actual clean-up. l Threads to use for database deletions: The number of Threads to be used in the clean-up. PlanetPress Connect is a multi-threaded application, and the clean-up is likewise. Tip The default number of threads is considered the best compromise for running both clean-up and production jobs simultaneously.
Tip In order to prevent attempts at deleting database objects which might still be in use, it is recommended that all Minimum time retention values should always be set to at least the length of your longest job. Preferably with some extra time added, for good measure. For example, if your longest job takes 45 to 50 minutes to run, then set the retention time to 55 minutes (or 1 hour) to ensure that all the database objects created during job processing survive for the duration of the job.
l Minimum time to retain orphaned files: The minimum time during which orphaned files are kept in the database before being set for deletion. The Clean-up Services Preferences also provides you with buttons to : l l l Run Now: This will run the clean-up service immediately. Restore Defaults. This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences.
settings. Tip If the Test Connection button shows that the database cannot be successfully connected to using the selected settings, then the contents of this field could be used to try to connect to the database outside of PlanetPress Connect. This should help in determining and refining the acceptable connection options. l l Hostname: Enter the IP Address or alias of the server where database resides. Database Instance Name: Enter an existing Microsoft SQL Server's instance name.
l Advanced Connection Settings selections: l Maximum concurrent threads: This option sets the maximum database threads. The maximum setting is determined by the specific capabilities of the machine Connect is installed upon (CPU speed and the amount of cores being the major determinants). Tip Leaving this value set to the default maximum should be the best option in most circumstances. We recommended this entry be left at the default value.
The Database Connection Preferences also provides you with buttons to : l l l Test Connection: This will run a test on the current Database Connection settings. 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.
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. -----------------------------------------------------------------------------------------Editing preferences These preferences define different editing options in the Designer module.
l l l l l Compact: Each CSS rule takes up only one line, with every property defined on that line. Nested rules are placed next to each other with no new line, while separate groups of rules have new lines between them. Compressed: This output style minifies the output. It has no whitespace except that necessary to separate selectors and a new line at the end of the file. It also includes some other minor compressions, such as choosing the smallest representation for colors.
l l l l Margins: This color delineates the content area on a page; see "Pages" on page 478. Bleed box: This color delineates the printable area on a page; see "Page settings: size, margins and bleed" on page 479. Master pages: These edges are only visible on Master pages; see "Master Pages" on page 486. l l l Guides: This is the color for rulers that can help position content correctly; see "Guides" on page 735.
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 928). 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 928).
Service Provider (ESP): Mandrilapp.com, Sendgrid and Mailgun (see "Using an ESP with PlanetPress Connect" on page 1354). l 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.
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 Customization. Emmet Abbreviation Preferences This Preferences tab lets you add and manage custom abbreviations. All standard abbreviations can be found in Emmet's documentation: Abbreviations. If there is no need to transform the text while expanding it, create an Emmet snippet instead (see below).
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.
\n...\n
