User Guide Version: 2018.
User Guide Version 2018.2 Last Revision: 2020-11-18 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.
Table of Contents Table of Contents 4 Welcome to PReS Connect 2018.
The Workflow server 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, AFPDS and IPDS 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.
Uninstallation Wizard General information 156 157 Connect: a peek under the hood The Workflow server The Connect server The Connect database The File Store The engines The REST API Connect File Types The DataMapper Module 157 158 159 160 160 161 162 163 164 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 Usin
Data Model file structure DataMapper User Interface Keyboard shortcuts Menus 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 Tool
Examples Examples Example Example 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 357 360 36
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 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.
Adding a snippet to the Resources Adding a snippet to a section Creating a snippet Renaming a snippet 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 V
COTG Servers preferences Clean-up Service preferences Database Connection preferences DataMapper preferences Editing preferences Email Preferences Emmet Preferences Engine Setup Language Setting Preferences Log Setting Preferences Print Preferences Saving Preferences Scheduling Preferences Scripting Preferences Web Preferences 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 conten
Output Creation Settings Page breakdown Australia Post 4 State Settings 1019 1039 1046 Codabar Settings 1048 Code 128 Settings 1051 Code 39 Settings 1054 Datamatrix Settings 1057 EAN-128 Settings 1059 EAN-13 Settings 1062 EAN-8 Settings 1065 Interleaved 2 of 5 Settings 1068 KIX Code (Dutch Post) Settings 1070 PDF417 Settings 1072 QR Code Settings 1075 Royal Mail 4 State Settings 1079 Royal Mail 2D Settings 1081 UPC-A Settings 1083 UPC-E Settings 1086 US Postal Service IMB Set
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 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 Abo
Generating Tags for Image Output Generating Email output Email output settings in the Email context and sections Generating Email output from Connect Designer Generating Email output from Workflow Aborting content creation Using an ESP with PReS Connect Generating Web output Web output settings in the Web context and sections Attaching Web output to an Email template Generating Web output from Workflow Aborting content creation Optimizing a template Scripts Images Print Manager Print Manager Introduction Vi
Connect 2018.2 Designer Updates JSON support added to the Data Model Panel Minimum Pages option added to Print Sections Color Output option added to Print Contexts Breadcrumb Improvements Send To Workflow Improved Paste as Plain Text option added Scripting Improvements Post Pagination Improvements Barcode Improvements Business Graphics Improvements General Designer Improvements Connect 2018.
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 PReS Connect and PReS Workflow Updating stand-alone Workflow Messenger installations Templates Used in Workflow Upgrading from PReS Connect 1.7 Reduced Memory Version Connect 2018.2.
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.
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 Connect 2018.1 Print Manager Enhancements/Fixes Workflow 2018.1 Enhancements/Fixes Known Issues Overview Connect 1.
Connect Workflow 8.6 Enhancements and Fixes 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.
Welcome to PReS 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. PReS 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 PReS Connect installation and the different considerations that are important in regards to the installation and use of PReS Connect. l "System and Hardware Considerations" below l "Installation and Activation" on page 35 l "Known Issues" on page 147 l "Server Configuration Settings" on page 113 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 PReS Connect, whether using the MySQL instance provided by the installer, or preexisting (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 PReS 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 738 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.
be supported by Objectif Lune Inc.. Furthermore, using PReS Connect in a Terminal Service environment is an infringement of our End-User License Agreement. Virtual Machine Support PReS 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. This means the virtual machine hosting PReS Connect can be automatically moved from one ESX server to another in a clustered installation.
Antivirus Considerations l l Antivirus software may slow down processing or cause issues if they are scanning in temporary folders or those used by PReS Connect. Please see Antivirus Exclusion for more information. Antivirus software might interfere with installation scripts, notably a vbs script to install fonts. McAfee, in particular, should be disabled temporarily during installation in order for MICR fonts to install and the installation to complete successfully.
Language and Encoding Considerations Please note the following considerations: l Language: l PReS Connect is currently offered in several languages. These languages can be switch between via the Preferences dialog. The current languages include: l English l French l German l Spanish l Italian l Korean l Portuguese l Chinese (Simplified) l Chinese (Traditional) l Japanese. The default language is English.
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 PReS Connect, it is important to determine how best to maximize performance.
Engine configuration As explained in another topic ("Connect: a peek under the hood" on page 157) the Connect Server cooperates with different engines to handle specific tasks. A DataMapper engine extracts data from a data file.A Merge engine merges the template and the data to create Email and Weboutput, or to create an intermediary file for Printed output. The intermediary file is in turn used by a Weaver engine to prepare the Print output.
Hardware configuration When processing speed is important, the following is suggested before looking into Performance Packs to enhance performance (and after addressing the other issues mentioned in this topic). l l l l l l Antivirus exclusions. Sometimes, virus scanners, other security software or indexing services can interfere. It can help to disable those kinds of tools for the areas where Connect stores intermediate files. You could exclude the entire C:\Users\\Connect folder.
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 PReS Connect. Minimum hardware requirements l NTFS Filesystem (FAT32 is not supported) l CPU Intel Core i7-5960X @ 3.
Where to obtain the installers The installers for PReS Connect 2018.2 and PReS Workflow 2018.2 can be obtained on DVD or downloaded as follows: l l If you are a Customer, the installers can be downloaded from the Objectif Lune Web Activations page: http://www.objectiflune.com/activations If you are a Reseller, the installers can be downloaded from the Objectif Lune Partner Portal: http://extranet.objectiflune.
l l PReS Connect requires Microsoft .NET Framework 4.5 already be installed on the target system. In order to use the automation features in Version 2018.2, PReS Workflow 2018.2 will need to be installed. This can be installed on the same machine as an existing PlanetPress® Suite 7.x installation or on a new computer. For more information, please see Information about PReS Workflow. If Workflow installation finds that .NET 4.
included by default with all setups. User accounts and security Connect generally requires only standard Windows user credentials to run, but does require a user with local Windows Administrator when installing the software and when activating the software license. This is to allow read/write access to protected Windows folders and registry entries.
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 PReS Worfklow. Installing PReS Connect on Machines without Internet Access Installing PReS Connect2018.2 in offline mode requires some extra steps. These are listed below.
The Windows certificate validation process not only checks the integrity of a file against its signature, but also usually checks if the certificate itself is still valid. That check is done against the current Certificate Revocation List (CRL), which needs to be retrieved from the internet. However, if the machine in question does not have internet access, the retrieval of the CRL must fail, which will lead to subsequent validation issues.
PReS Connect requires prior installation of Microsoft .NET Framework 3.5. Please refer to https://www.microsoft.com/en-us/download/details.aspx?id=21 for more details on how to install Microsoft .NET Framework 3.5, if this is not already done. If the same version of PReS Connect is already installed on the target machine, you will be presented with options to either Uninstall or Modify the existing instance.
l l PReS Connect Server Extension: A slave server for a PReS Connect Server module. When an slave server is installed it communicates with the master server to shares tasks with it. Only one of the Server or Server Extensions can be installed on a single machine, not both. MySQL Product: A supplied MySQL database used by PReS Connect. The database is used for referencing temporary Connect files and for sorting temporarily extracted data, and similar.
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 setting up clustering, orif 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 PReS 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 l Password: The password associated with the selected user. Validate user button: Click to verify that the entered username and password combination is correct and that the service is able to login. Note This button must be clicked and the user validated before the Next button becomes available.
l Username: The account that the service uses to login. If the machine is on a domain, use the format domain\username. This account must be an existing Windows profile with local administrator rights. This should ideally be the same as the logon domain user account for the OLConnect_Server service on the Connect Master Server. This account must be a local admin account with existing Windows profile on both servers. l l Password: The password associated with the selected user.
l Validate Connection button: Click to verify that the connection details to the Master server database are correct and that the service is able to login to it. This button does not need to be clicked for the Next button to become available, but it is advised that you do so, to confirm the Master/Slave Connection settings. Click Next to start the actual installation process. This process can take several minutes.
Select the desired options and then click OK to query the server and obtain a list of any updates that are available for your software. 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.
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. 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.
Product selection (optional) By default, if nothing is entered for the products to be installed (install.product.X), Silent Installer will install all products which are visible to the user for the respective brand (except for the Server Extension, because only Server or Server Extension can be installed at the same time). PReS defaults install.product.0 install.product.1 install.product.2 install.product.3 = = = = Connect Designer Connect Server Connect Print Manager MySQL Note The values of install.
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.
Case 2: The Connect Server or the Connect Server Extension 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.
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.
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.
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.
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.
license) has expired, the Software Activation dialog should automatically appear. If the application license is still active (either a trial or full license) and has not yet expired, load the Software Activation dialog via the Help > PReS Connect Software Activation ... Menu option. l License Information subsection: l l l Magic Number: Displays the PReS Connect Magic Number. Copy the magic number to the clipboard: Click to copy the Magic Number to the clipboard.
The Software Activation dialog can also be reached through a shortcut located in All Programs > Objectif Lune and is named Connect Software Activation. Since it does not need to load Designer, this is the fastest way to access license activation.
Activating the PReS Connect license requires the user to have local Windows Administration rights. l Using a user profile that has local Windows Administration rights, open the Start Menu l Click on All Programs, then browse to the Objectif Lune folder. l Run the “Connect Software Activation” tool. 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.
l Installation Prerequisites l Antivirus Exclusions Downloading and Installing the Software In order to migrate to a new workstation, the software must already be installed on the new workstation. Follow the Installation and Activation Guide to download and install the newest version of PReS Connect on the new workstation. If using Clustering, please read the Server Clustering page of this documentation for more details relevant to the installation.
l l l l l l l l l l The Workflow configuration file itself is named ppwatch.cfg, and is backed up with the folders. However, it needs to be re-sent to the Service to be used. To do this, rename the file to .OL-Workflow, open the file with the Workflow tool, and send the configuration. Locate Custom Plugins (.dll) from the below folder on the old workstation and import them onto the new workstation C:\Program Files (x86)\Common Files\Objectif Lune\PlanetPress Workflow 8\Plugins To import the plugin
l l Click on Tools in the Workflow Configuration menu bar l Click on Access Manager l Grant necessary permissions to remote machines l Restart the Workflow Messenger service Reconfigure the Workflow Preferences as previously by clicking on the Workflow button on top left corner and clicking on Preferences: l l l l Reconfigure the Server Connection Settings under Behavior > OL Connect For PlanetPress Capture users, reconfigure the PlanetPress Capture options under Behavior > PlanetPress Capture
Other Resources l l l l OL Connect Designer Templates, DataMapper or 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.
l l If Capture was previously using an external MySQL or Microsoft SQL Server, reconfigure the ODBC connection details as previously from the Workflow Preferences by clicking on the Workflow button on top left corner and clicking on Preferences, then reconfigure the PlanetPress Capture options under Behavior >PlanetPress Capture > Use ODBC Database Start the Messenger 8 service on new server from the Workflow menu bar > Tools > Service Console > Messenger > right-click and select Start.
l 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 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.
To apply the license file received from the Activation Team: l Start the PReS Connect, PlanetPress Connect or PrintShopMail Connect Software Activation module: C:\Program Files\Objectif Lune\OL Connect\Connect Software Activation\SoftwareActivation.exe l Click on Load License File to import the license.OLConnectLicense l Start the Software Activation module on the Extension servers, where applicable l Click on Load License File to import the above same license.
PReS Workflow can be installed in parallel on the same machine as an existing PlanetPress® Suite 7.x installation. Note however: l l l l l If both versions need to be hosted on the same machine, PReS Workflow 2018.2 must always be installed after the legacy PlanetPress® Suite 7.x installation. When uninstalling PReS Workflow 2018.2, you may be prompted to repair your legacy PlanetPress® Suite 7.x installation. If PReS 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. What does PReS Connect contain? PReS Connect is comprised of the following modules: l PReS Workflow 2018.2. This is the natural evolution of PlanetPress Suite Workflow 7 (Watch, Office or Production). PReS Workflow 2018.
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 PReS Connect, they will remain functional. Please note that PlanetPress Suite Workflow 7 and PReS Workflow 8 cannot run at the same time. See Information about Connect Workflow 8 for information about these limitations.
l 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. The full version of PlanetPress Connect can open your company to the digital world by enabling you to send HTML responsive emails as well as creating dynamic responses and interactive web pages.
Note If Workflow installation finds that .NET 4.0 is not already installed, it will install that version as part of the setup process. If LaserFiche or the ICR libraries are chosen as part of the Workflow installation, then .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. 4. If you installed PReS Workflow 2018.
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 PReS 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. From now on, if you need to modify your PlanetPress Design documents, simply open PlanetPress Design 6 or 7, edit your document and send the updated version to PReS Workflow 8.
How to perform a Workflow migration What do you need to consider when upgrading from PlanetPress Suite 7 to PReS 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.
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. Do this via the Tools > Printer Utilities menu option.
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 PReS 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 PReS Connect. Using PReS 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 PReS Connect Workflow 2018.2 on the same computer. 3. Do the following for both PlanetPress Suite version 7.6 and PReS Connect Workflow 8. 1. Open Workflow Service Console.
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. Copy the contents of this folder: "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Watch\PGC" to this fo
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 PReS Connect Workflow 2018.2 on new computer. 3. The Anoto PenDirector must be installed. It if is not, you can download it from here and then install it. Note It is strongly recommended that you install the latest version of the PenDirector.
Note These steps must be done for both PlanetPress Suite Workflow 7 and PReS 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 PReS Connect Workflow 2018.2 computer: "C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\capture" and overwrite the existing database. Note Prior to PlanetPress Suite 7.
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. The Preferences dialog is separated into individual tabs, where each tab controls certain aspects of the software.
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. PReS Connect is a multi-threaded application, and the cleanup 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. Note Only a server that has the MySQL module installed should run any of these options, with the exception of Allow orphan file clean-up. This option refers to local files and should be run on each machine in the cluster (however, not at the same time). See "Server Clustering" on page 137.
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. l Database URL: This is a read-only summation of the current database connection settings.
Tip It is considered best practice for this user to have root privileges. l l Password: Enter the password associated with selected username. l Confirm password: Re-enter the user password. 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).
l l l Test Connection: Use to test if current connection settings will connect to the specified database. Restore Defaults: Will restore the settings to PReS Connect HyperSQL standard defaults. Apply: When a database connection is confirmed as correct this button becomes active, and is used to actually apply the database swap. 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.
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. The DataMapper Preferences also provides you with buttons to : l l Restore Defaults. This option restores the preferences to Defaults.
The CSS options relate to the way Sass (.scss) files are compiled in Connect. See also: Compiling a Sass file. l Output style: This setting determines the use of spaces and indentation in the compiled CSS file. For examples of the available output styles, see: Sass reference: Output style. l l l l l Compact: Each CSS rule takes up only one line, with every property defined on that line.
l l l l l Guides: This is the color for rulers that can help position content correctly; see "Guides" on page 673. Margins: This color delineates the content area on a page; see "Pages" on page 429. Bleed box: This color delineates the printable area on a page; see "Page settings: size, margins and bleed" on page 430. Master pages: These edges are only visible on Master pages; see "Master Pages" on page 437.
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 863). 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 863).
Service Provider (ESP): Mandrilapp.com, Sendgrid and Mailgun (see "Using an ESP with PReS Connect" on page 1246). 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
