User Guide Version: 2018.
User Guide Version 2018.2 Last Revision: 2019-01-29 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 2018.
The Connect server The Connect database The File Store The engines The REST API Known Issues Job Creation Presets: External Sorting Engine Preferences: Backward Compatibility Issues Business Graphics: Backward Compatibility Issues Known Font issues Minor differences in PCL output introduced in 2018.1 Windows Server 2016 issue Limit of 100MB of image files within a single job Print Output: Booklet Impositioning changes introduced in 2018.
The Workflow server The Connect server The Connect database The File Store The engines The REST API Connect File Types The DataMapper Module DataMapper basics What's next? Data mapping configurations Creating a new data mapping configuration Opening a data mapping configuration Saving a data mapping configuration 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 Cre
Panes Example Example Settings for location-based fields in a Text file Settings for location-based fields in a PDF File Settings for location-based fields in CSV and Database files Settings for location-based fields in an XML File Text and PDF Files CSV and Database Files XML File Text and PDF Files CSV and Database Files XML Files Left operand, Right operand Condition Operators Text file PDF File CSV File XML File JavaScript Toolbar Welcome Screen DataMapper Scripts API Using scripts in the DataMapper Set
Example Text XML Functions The Designer Designer basics What's next? Features Templates Contexts Sections Print Copy Fit 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 Fo
Testing the template Sending the template to the Workflow tool Using COTG data in a template Designing a COTG Template Capture OnTheGo template wizards Using Foundation COTG Elements Using COTG Elements Testing a Capture OnTheGo Template Using the COTG plugin: cotg-2.0.0.
JSON Snippets Styling and formatting Local formatting versus style sheets Layout properties Styling templates with CSS files Styling text and paragraphs How to position elements Rotating elements Styling a table Styling an image Background color and/or image Border Colors Fonts Locale Spacing 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
Optimizing scripts Loading a snippet via a script Loading content using a server's API The script flow: when scripts run Selectors in Connect Control Scripts Post Pagination Scripts Designer User Interface Dialogs Keyboard shortcuts Menus Panes Preferences Toolbars Welcome Screen Print Options Job Creation Presets Output Creation Settings Page breakdown Australia Post 4 State Settings 735 739 742 745 745 751 766 772 773 845 851 863 884 910 915 917 995 1006 1025 1032 Codabar Settings 1034 Code 128 Settin
US Postal Service IMB Settings 1075 US Postal Service IMPB Settings 1078 Designer Script API Standard Script API Examples Examples Examples Examples Examples Examples Examples Examples Examples Examples Examples Examples Examples Example Example Example Example Example Examples Creating a table of contents Example Examples Examples Examples Examples Replace elements with a snippet Replace elements with a set of snippets Example Example Creating a Date object from a string Control Script API Examples 10
Post Pagination Script API Generating output Print output Fax output Email output Web output Generating Print output Saving Printing options in Print Presets Print settings in a template Generating Print output from Workflow Aborting content creation Print Using Standard Print Output Settings Print Using Advanced Printer Wizard Adding print output models to the Print Wizard Splitting printing into more than one file Print output variables Generating Fax output Generating Tags for Image Output Generating Ema
Dynamic Sheet Configuration Settings Performance Improvements Installer Improvements REST API Improvements Logging Improvements Connect 2018.
Selective Inserts Workflow 2018.2 Updates New HTTP Server Input - NodeJS Process Grouping Connect All-in-One Improvements Create Job Improvements DataMapper Validation Improved Logging Connect Workflow Improvements: General Workflow Fixes and Improvements: Known Issues Overview Installing PlanetPress Connect and PlanetPress Workflow Updating stand-alone Workflow Messenger installations Print Only Version Templates Used in Workflow Upgrading from PlanetPress Connect 1.7 Reduced Memory Version Connect 2018.2.
Post Pagination Improvements Barcode Improvements Business Graphics Improvements General Designer Improvements Connect 2018.2 DataMapping Updates Ignore Blank Lines Dynamic SQL Queries Set Data Fields as Not Required Landscape PDF Input Dynamic XPATH values General DataMapping Improvements: Connect 2018.2 Server Enhancements Engine Setup Automatic Engine Restarts Improvements for high workload situations Connect 2018.
Connect 2018.1.6 Enhancements/Fixes Connect 2018.1.5 Enhancements/Fixes Connect 2018.1.4 Enhancements/Fixes Connect 2018.1.3 Enhancements/Fixes Connect 2018.1.2 Enhancements/Fixes Connect 2018.1.1 Enhancements/Fixes Connect 2018.1 General Enhancements Connect 2018.1 Designer Enhancements/Fixes Connect 2018.1 DataMapping Enhancements/Fixes Connect 2018.1 Output Enhancements/Fixes Workflow 2018.1 Enhancements/Fixes Known Issues Overview Connect 1.8 General Enhancements and Fixes Connect 1.
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 2018.2 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 136 l "Server Configuration Settings" on page 111 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 db settings from a previous installation are found, the pre-exising settings will be displayed for the matching db type (for MS SQL settings, this will only work if they were created with Server Config Tool 1.5.0 or later, or the Connect installer 1.6.0 or later).
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. Have a foreign Microsoft SQL running, ready for use with Connect Server. 2. Use the Server Configuration Tool "Database Connection preferences" on page 889 to switch the database to Microsoft SQL. 3.
l It is not possible to uninstall the supplied MySQL in this case via a Connect 1.5 modify. 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.
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 146) 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 2018.2 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.
Note A PDF version of this guide is available for use in offline installations. Click here to download it. PlanetPress Connect 2018.2 is comprised of 2 different installers: one for the PlanetPress Connect software and one for PlanetPress Workflow 2018.2. Where to obtain the installers The installers for PlanetPress Connect 2018.2 and PlanetPress Workflow 2018.
Activation For information on licensing, please see Activating your license. Installation prerequisites l l l l l Make sure your system meets the System requirements. PlanetPress Connect Version 2018.2 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.5 already be installed on the target system. In order to use the automation features in Version 2018.
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 2018.2. 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 2018.2 If you are updating manually you must first upgrade to Version 1.1 before installing 2018.2.
Permissions for PlanetPress Connect Server The PlanetPress Connect Server module, used by the Automation module, requires some special permissions to run. These permissions are set during installation, in the Engine Configuration portion of the Installation Wizard, but it can also be configured later by modifying permissions for the service. To do this: l l l l In Windows, open the Control Panel, Administrative Tools, then Services (this may depend on your operating system).
l GoDaddy Secure Server Certificate (Intermediate Certificate) - G2 - the file is gdig2.crt 2. Install the certificates: Right mouse click -> Install Certificate, and follow the steps through the subsequent wizard. 3.
Installation Wizard Starting the PlanetPress Connect installer The PlanetPress Connect installer may be supplied as an ISO image or on a DVD.
Selecting the required components After clicking the Next button, the component selection page appears, where the different components of PlanetPress Connect can be selected for installation. Currently, the following are available: l l l PlanetPress Connect Designer: The Designer module (see "The Designer" on page 371) 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 .
Note To cater for MySQL requirements, the installation path cannot contain any non ASCII characters (such as Asian language Unicode characters). Nor can it contain 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 will automatically configure the Connect Server to use the supplied password and port. l MySQL user 'root' Password: Enter the password for the 'root', or administration account, for the MySQL server. The password must be at least 8 characters long and contain at least one of each of the following: 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 (@, $, ~ ...
Note This option is required if MySQL Server will need to be accessed from any other 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. It is heavily recommended that your firewall is set to block access to port 3306 from external requests.
l l Server Schema/Table: Enter the name of the MySQL database into which the tables will be created. The Connect standard name is "objectiflune". Test Connection button: Click to verify that the information provide into previous fields is valid by connecting to the database. Note This test does not check whether the remote user has READ and WRITE permissions to the tables under the objectiflune schema. It is solely a test of database connectivity.
l Validate user button: Click to verify that the entered username and password combination is correct and that the service is able to login. This button must be clicked and the user validated before the Next button becomes available. Click Next to start the actual installation process. 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.
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. If the software is activated and the services rebooted too quickly, the database can become corrupted and require a re-installation.
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.username = Localadmin server.runas.
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.
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.product.0 = Connect Server), the database.unlocked property is irrelevant.
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.host = (default value is localhost, otherwise required) database.
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 following properties in the install.properties file: user.language user.
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 Name: Displays the name of the application or module relevant to this activation. The Information button provides detailed information about the application or module 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.
l Resellerscan 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. Accepting the license will activate it, after which the PlanetPress Connect services will need to be restarted. Note that in some case the service may not restart on its own.
l l 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. Migrating to a new workstation The purpose of this document is to provide a strategy for transferring a Connect installation to a new workstation.
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. Technical 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 installed and then re-send them to the Workflow Tools.
l l l l l l l l l l Click on the down pointing triangle under the Uncategorized group l Select Import Plug-in and select the .dll file. Import 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.
l l Reconfigure each of the plugin, 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 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 (.
l Make sure the new workstation can also access network or remote images, JavaScript, CSS, JSON, and HTML resources referenced in the Connect templates. Secondary Software and Licenses The following only apply for specific secondary products and licenses that interacts or is integrated into the main product. Image, Fax and Search Modules l l Reconfigure the Image and Fax outputs with the new host information.
OL Connect Send • Re-install OL Connect Send on the new Workstation. This should reinstall the OL Connect Send plugins in the Workflow Tool • Reconfigure the Server URL and port during the OL Connect Send Printer Driver setup • Re-run the OL Connect Send printer driver setup on client system and select the Repair option to point the clients to the new Server URL. Configuring the Connect Engines Any changes made to the Server preferences require the OLConnect_Server service to be restarted to take effect.
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. Perform the following action on each Server Extension: l l l Stop the OLConnect_ServerExtension service from Control Panel > Administrative Tools > Services > OLConnect_ServerExtension > Stop Open the Server Extension Configuration from: C:\Program Files\Objectif Lune\OL Connect\Connect Server Extension\ServerExt
l Start the Software Activation module on the Extension servers, where applicable l Click on Load License File to import the above same license.OLConnectLicense l l Restart the OLConnect_Server service and restart the OLConnectServer_Extension service on the Extension servers, where applicable The number of Expected Remote Merge and Weaver engines should now be configurable in the Connect Server Configuration module (C:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.
l l l l l If both versions need to be hosted on the same machine, PlanetPress Workflow 2018.2 must always be installed after the legacy PlanetPress® Suite 7.x installation. When uninstalling PlanetPress Workflow 2018.2, you may be prompted to repair your legacy PlanetPress® Suite 7.x installation. If PlanetPress Workflow 2018.2 has been installed alongside PlanetPress® Suite 7, Capture can no longer be used with Workflow 7. The plugins are now registered uniquely to Workflow 2018.
This document provides information on the migration process and the requirements and considerations for existing PlanetPress Suite users to upgrade to the latest generation of our products. Note PlanetPress Connect Print-Only is available for existing users of PlanetPress version 7 or 6 with a valid OL Care agreement. If you are using a previous version or are not covered by OL Care, please contact your reseller or your Objectif Lune Account Manager for more information.
GOOD NEWS: PlanetPress Connect does not need any printer licenses to print from PlanetPress Connect or PlanetPress Suite. It can also print PrintShop Mail 7 and PReS Classic documents if these programs are licensed. You can keep everything you have The first thing to know is that you can keep your current PlanetPress Suite Workflow 7 configuration and your PlanetPress Suite Design documents. When upgrading to PlanetPress Connect, they will remain functional.
l You want to use a more powerful computer with more RAM and more cores to run the Server to achieve maximum performance (see "Performance considerations" on page 31).
email in full HTML glory and/or make them available as native HTML web pages using the latest CSS/JavaScript features. IMPORTANT: If you owned them, you must also upgrade your Imaging modules to use the new PReS version. 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.
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 2018.2 on a different computer, please see "How to perform a Workflow migration" on page 76 for help importing all those settings, if you wish to import them. 6.
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 2018.2 on a new computer? Installing and Activating Workflow 2018.2 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 2018.2 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 2018.2 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 2018.2 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 By allowing one or more Capture OnTheGo servers to be set up, this option anticipates the release of a Capture OnTheGo On Premise Server 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.
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 Hostname: Enter the IP Address or alias of the server where database resides. l Port: Enter Port number. The defaults are those which the vendors use by default.
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. l Custom database parameters table: These are extra parameters which are appended to the database connection URL. The default values are those which have been determined to be useful in connecting to specific vendor databases.
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 417. Bleed box: This color delineates the printable area on a page; see "Page settings: size, margins and bleed" on page 418. Master pages: These edges are only visible on Master pages; see "Master Pages" on page 425. l l l Guides: This is the color for rulers that can help position content correctly; see "Guides" on page 663.
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 826). 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 826).
Service Provider (ESP): Mandrilapp.com, Sendgrid and Mailgun (see "Using an ESP with PlanetPress Connect" on page 1231). 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
