Connect Designer. Emmet transforms abbreviations for HTML elements and CSS properties to the respective source code. This is, for example, the abbreviation for a
element with the class row: div.row On pressing the Tab key, this abbreviation is transformed to:
To learn more about Emmet itself, please see their website Emmet.io and the Emmet.io documentation. Emmet is a plugin. All options listed below are Emmet's default options. They are not specifically adjusted for Connect.
l l Pattern: This defines what an abbreviation expands to. Since Emmet is mostly used for writing HTML/XML tags, abbreviation definition uses XML format to describe elements; see Abbreviation types. Automatically insert: This standard option doesn't affect how Emmet works in Connect Designer. l Edit: Edit the currently selected abbreviation. l Remove: Remove the currently selected abbreviation. l l Import: Click to open a browse dialog to import an XML file containing exported abbreviations.
l Automatically insert: This option doesn't affect how Emmet works in Connect Designer. l Edit: Modify the currently selected snippet. l Remove: Remove the currently selected snippet from the list. l l l l Import: Click to open a browse dialog to import an XML file containing exported snippets. The imported snippets are added to the current list. Export: Click to open a Save as dialog to export all the snippets in an XML file that can be shared and re-imported.
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. ------------------------------------------------------------------------------------------ Engines preferences See Engines Preferences.
l l Edit: Edit that information relating to an existing hardware device. This launches the Edit PKCS#11 Module dialog. Delete: Remove an existing hardware device from the list. The Hardware for Digital Signing 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.
Logging preferences PlanetPress Connect logs the activities it undertakes whilst running. New Connect logs are created daily and are held for a period before they are automatically deleted. The settings on this page determine the level of logging and how long the log files should be retained. These log files can be an essential resource when diagnosing issues with OL Support.
l l Size-based logs: Use this setting to restrict log file size, and to keep only a specified number of them. By combining the maximize individual log file size with the amount of log files to retain, this effectively allows a hard disk space usage limitation to be placed upon the logging process. l l l Number of days to retain logs: This value only impacts upon historic (closed) logs. Chose between 1 and 99,999 days.
Warning Higher logging settings will have an impact upon Connect production speeds, as well as leading to substantially larger log files. The Advanced Log Settings should only be set in conjunction with advice from OL support, to ensure that only the most relevant settings are set to the higher logging levels. This Preferences page allows you to add ( ) or remove ( ) individual Connect Packages, or change their logging settings ( ).
l l Selected Printers: Lists the available Printer Definition Files in the system. Note that these are not installed Windows printers or printer queues, but PlanetPress Connect Printer Definition Files. Printer checkbox: This checkbox selects/deselects all printers in the list. Click to check all, click again to uncheck all.
"Guides" on page 760). With this option checked, dragging a guide from a horizontal ruler inserts a vertical guide. The Print preferences also provides you with buttons to : l l l Test Print Server URL. This button is only available for the General Print Preferences. It tests the Print Server URL settings made within that Preferences page. Restore Defaults. This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences.
l l Enable: activate the Auto Save function. Interval (minutes): enter a number of minutes, e.g. 3 to auto-save the template or data mapping configuration every 3 minutes. Auto Backup Connect Designer can automatically create a backup file when you manually save a template or data mapping configuration. The Auto Save function does not cause backup files to be created. l l l Enable: activate the Auto Backup function. Revisions to keep: Enter the maximum number of backup files.
l General: l l Script timeout at design time (sec): In Preview mode or when running the Script Profiler (see the Profile Scripts dialog), a long running script is stopped after the amount of time set here. The default is 2 seconds, the minimum is 1 second. Expanded script quotes style: When the Expand button in a Script Wizard is clicked, the expanded script will use either double (") or single (') quotation marks.
l Insert Form Field Defaults: l Style: Defines how labels are added to input form elements: l l l l l Attach label to input: The label is placed before the input, and refers to it: Use label as placeholder: The label is removed and the text is put as a placeholder, such as: No label: The label value is ignored.
l Apply: This option applies the settings made within the current Preferences page, but does not close the Preferences dialog. ------------------------------------------------------------------------------------------ Server Configuration Settings This chapter describes configuring the PlanetPress Connect Server. The Connect Server settings are maintained by the Connect Server Configuration utility tool which is installed alongside PlanetPress Connect.
l Engines l Automatic Restart l "Hardware for Digital Signing preferences" on page 843 l "Language preferences" on page 844 l Logging Settings l "Parallel Processing preferences" on page 133 Connection preferences Background The Connection preferences are a way to control precisely how to connect to the PlanetPress Connect Connect Server. This preference page was added in Connect 2018.2 to simplify management of HTTP communication with Connect.
Note This does not limit the number of requests that can be received, just how many are processed in parallel. Additional requests are buffered and are processed as capabilities allow. The default setting is twice the number of processing cores available to the computer. This can be expanded, if the limitation is deemed a bottleneck. l Dedicated Internal Connection checkbox: Set the internal connection HTTP communication setting values. These settings are purely for Connect inter-engine communication.
intermediary file is in turn used by a Weaver engine to prepare the Print output. (For more information see: "Connect: a peek under the hood" on page 161). Settings for these engines are made in the Connect Server Configuration tool (see "Server Configuration Settings" on page 121). Connect allows for the parallelization of jobs. This means you can allocate 1 or more engines to process jobs.
l l l Your licence, which imposes a speed quota (see "Speed quota: Pages Per Minute" below). The processing power of your machine. How many cores it has determines how many engines can be launched (see "Launching multiple engines" on the facing page). The size and number of jobs of one kind that need to be handled, sequentially or simultaneously. In other words, your use case.
In situations where Print and Email and/or Web output are created at the same time, only the Merge engines that create Email/Web output count towards the maximum number of Licensed tasks for that type of output. Spare speed units are distributed proportionally Since the number of engines is configurable, and jobs may run concurrently, the number of engines in use may not match the exact number of available Licensed tasks.
1. Open the Connect Server Configuration utility tool (see "Server Configuration Settings" on page 121). 2. Under Parallel Processing, go to the Content Creation tab and set the number of Merge engines for the various tasks. 3. Go to the Output Creation tab and set the Reserved Weaver (Output) engines. See "Deciding how many engines of each type to launch" below. 4. Click Apply or Apply and Close. It is advised that you do not configure more engines than can be backed by actual processing power.
When the database is installed on a system with a slow hard drive, adding a DataMapper engine may not increase the overall performance. Weaver engine Adding extra Weaver (Output) engine(s) might be useful when large Print jobs are to be run simultaneously with smaller Print jobs. Memory per engine By default, each engine is set to use up to a predetermined amount of RAM. To make optimum use of a machine's capabilities it might be useful to increase the amount of memory that the various engines can use.
The first step in this process is to define the size of small, medium and large jobs. Job size Connect lets you define job sizes by setting the maximum number of pages a job can have and still be considered a small job, and what the minimum number of pages a job can have in order to be considered large. Jobs that fall between the small and large jobs are medium jobs.
handled at the same time by that kind of engine, because there are only so many engines (and speed units) available. Note When each individual record in a job is composed of a very large number of pages, the Memory per engine setting and the machine's hard drive speed are probably more important than the number of Merge engines, since one record cannot be split over multiple cores (see "Memory per engine" on page 128).
may have to wait (or wait longer). However, if the server receives many web requests then having engines reserved for HTML output can help performance. l l By reserving a number of parallel engines for Print jobs of a certain size (see "Number of parallel engines per Print job" on page 129). More parallel engines will make them run faster, but they will have to wait (longer) if the required number of engines isn't available when they come in.
Batch processing. In a batch processing situation, jobs don't have to be handled simultaneously. All jobs - whether they are big and small - are processed one after another. Every job should be handled as quickly as possible. It is therefor recommended to assign the maximum number of engines and target speeds to all jobs. Do not reserve engines for certain jobs. Web requests. In online communication, response times are critical.
l l Daily restart period begin: Only available if Daily restart in period selected. Enter the daily start time for the time window in which automatic restarts will be scheduled to occur. Daily restart period end: Only available if Daily restart in period selected. The end of the daily time window in which the automatic restarts are scheduled to occur. Memory limit Enter the memory limit for individual Engines.
Content Creation Tab (Designer Preferences) A Tab with data that relates solely to Content Creation. The options are: l l Total Merge engines configured read only display: This is a read only entry that shows the total number of Merge engines available. To change this value, you must update the Merge Engines in the Engines preferences page. Multi tasking group: When starting a new Content Creation task, the task will immediately commence if there is a Merge engine available.
Note These entries aren't applied instantaneously. There is often a lag. That is why you can reserve a specific number of engines for new jobs, in the options below. Those reservations operate in real time. The default of 100 records was chosen purely because it is an easily multiplied number, not because it has been proven to have any significant value. It means that on an average system (i.e., less than 10 Merge engines) any decently sized task is allowed to use all Merge engines.
l l l Connect Send - Settings optimized for use with Connect Send. Connect Send needs a Merge engine available for on demand web pages, to be able to process on demand print jobs (especially content creation), and have a Weaver engine available for creating the production output. Capture on the Go - Settings optimized for use with Capture on the Go applications. Capture on the Go needs on demand content creation for web pages (the forms), emails (notifications), and PDFs (persistent version of forms).
come in. This option is better suited for batch processing. l Maximize simultaneous tasks: Merge engines will be reassigned from a running task to new tasks when they arrive. To accommodate as many tasks as possible, the server can dynamically reassign Merge engines to new tasks as they arrive. Thus a running Content Creation task need not block other tasks. If multiple Merge engines are processing a task, an engine can be taken from that task and reassigned to a new task.
Note Currently, it’s only the print and PDF content creation tasks that use multiple Merge engines. l Reserve engines for on demand tasks group checkbox: Reassigning engines is not instantaneous when a new task arrives. To avoid inefficiencies, Merge engines will first finish work on their current selection of records, before being reassigned. Reserving engines better ensures that on demand tasks get picked up right away, but it also means that less engines will be available for large tasks.
l l Licensed speed limit (pages per minute): This read only entry shows the current license speed limitations, in pages per minute. The speed limitations are determined by your Connect license. This information is to help you choose what settings would make sense when assigning the “Target speed” values later in the Tab. Licensed tasks limit: This read only entry shows the current license task (or job) limitations. Note The terms "job" and "task" can be used interchangeably.
not required for either though. l l l Small job (engines): Optionally enter the number of Weaver engines you wish to reserve for Small jobs. To make sure large batch jobs get sufficient speed during Output Creation, set a lower target speed for small jobs, this will automatically allow more for the large and medium jobs. Medium job (engines): Optionally enter the number of Weaver engines to reserve for Medium jobs.
The entire licensed speed limit will always be distributed among jobs when running jobs simultaneously. After assigning a target speed, any remaining licensed speed will be distributed throughout any simultaneous jobs by a ration of the target speed. Some general rules of thumb to apply when distributing target speed: n Do you need to change speeds? In many cases there will likely be no need to change the target speed.
Warning It is highly recommended to keep security enabled and change the password on any server that accessible from the web. If these precautions are not taken, data saved in the server may be accessible from the outside! l l l l l Enable server security: Enable to add authentication to the REST server. - When enabled, the same username and password (which cannot be blank) must be entered in any remote Connect Designer that links to this Server.
The Workflow server The Workflow server (also referred to as the 'Watch service') executes processes independently, after a Workflow configuration has been uploaded and the services have been started. The Workflow server can run only one configuration at a time. There are a number of services related to Workflow.
tool. The Workflow Service Console lets you start and stop the different services, except the Connect server, and see their log files (see Workflow Service Console). Note that Workflow isn't limited to Connect functionality. It was originally developed as part of the PlanetPress Suite. Many of the plugins in the Workflow configuration tool are older than Connect. They were left in for compatibility reasons, even though they aren't all useful or usable within Connect.
The Connect Server Configuration tool lets you change the settings for the Connect server, the engines and the service that cleans up the database and the file store. These settings can also be made in the preferences of the Designer. The Connect database The Connect database is the database back-end used by Connect itself when processing jobs. It can be either the MySQL instance provided by the Connect installer, or a pre-existing (external) instance (see "Database Considerations" on page 24).
The engines DataMapper engine/s. A DataMapper engine extracts data from a data file. The number of DataMapper engines is configurable (Engines preferences). Merge engine/s. A merge engine merges data with a template using the scripts in the template, in order to create (Print,Email or Web) content items. The number of merge engines is configurable (see Engines preferences): it can be increased depending on the capacity of the machine that runs the solution (see "Performance considerations" on page 34).
Printing and emailing from the Designer To print or send email from within the Designer, the PlanetPress Connect service has to be running. The service is started automatically when the Designer starts, but it may not be running if the Connect Server and the Designer are installed on different computers. The PlanetPress Connect service can be found on the Services tab in the Task Manager. For a proof print the Connect server is not used. Proof printing is always done locally, by the Designer.
To workaround this issue, we recommend downloading and manually installing the latest Visual C++ Redistributable from https://support.microsoft.com/en-ca/help/2977003/the-latestsupported-visual-c-downloads then re-running the Connect 2019.2 installation. Issues associating PDF files with Connect. Under certain circumstances, Connect Setups prior to 2019.2 would fail when attempting to add the "Enhance with Connect" association with PDF files. This would then cause the setup to appear to fail.
Page break changes in 2019.1 Improved page breaking in Connect 2019.1 might impact upon some existing templates. It is recommended that you check page breaking in existing jobs, where page breaks at a specific location are a known criteria.
Backend database might require periodic maintenance Databases maintain a variety of statistics in order to optimize performance. When high levels of inserts and/or deletions occur, the statistical data keeping can struggle to keep up. Over a period of prolonged and intensive processing this can result in a degradation in performance, with the whole database slowing down as it struggles to clean itself up.
C:\Users\\Connect folder. This issue will be fixed in a later release. Job Creation Presets: External Sorting change introduced in 2018.2 Versions prior to 2018.2 did not correctly save the line end characters for external sort configurations in Job Creation Presets, which meant the job could not be externally sorted. This issue has been fixed in version 2018.2. However, Job Creation Presets created with an earlier version may still have the wrong line end character for external sorting.
The currently known backward compatibility issues are listed here: All charts l l l Legend position: The position of the legend is not converted. It defaults to 'left' in a converted chart. Rows are series/Columns are series: Only one type of data structure for detail tables is supported in the new version: the one that corresponds to the former Columns are series setting (with which charts display one series per record, one bar/point per data field). After conversion to 2018.
Minor differences in PCL output introduced in 2018.1 The browser component (Mozilla Gecko) used in the WYSIWYG editor of the Designer was updated for Connect 2018.1. This allows use of new CSS properties, such as flexbox. However this update could lead to increased output file sizes for some PCL jobs. This is generally not a cause for concern, however there might be some associated increase in processing times, as well as some minor differences in the output.
Print Output: Booklet Impositioning changes introduced in 2018.1 When Booklet Impositioning is enabled, all pages within a document need to be changed to duplex prior to Impositioning . The method for duplexing jobs has been changed to now always combine existing pages into the front and backsides of sheets, rather than adding empty backsides to any simplex pages. The result is that now every document in the job becomes a booklet without any empty pages between the first page and the last page.
l C:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.ini 2. Change the language parameter to the required one under Duser.language=en | es | de | fr | it | ja | ko | pt | tw | zh Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up. GoDaddy certificates When installing Connect offline, dialogs allow installing the GoDaddy certificates. Most users should use the default settings and click Next.
To add additional printer models click on the settings entry box. button next to the Model selection Note that the descriptions of some of the printers were updated in version 1.2 meaning that if you had version 1.n installed, you may find that the same printer style appears twice in the list, but with slightly different descriptions.
Capture can no longer be used within Workflow 7. The plugins are now registered uniquely to Workflow 8 and the Messenger for Workflow 7 is taken offline. It is only possible to use Capture from PlanetPress Connect Workflow 8 thereafter. Capturing spool files after installing Workflow 8 If PlanetPress Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, the PlanetPress Suite 7 option to capture spool files from printer queues will no longer function.
for an engine and when it becomes available. Note that there is no way to cancel any commands other than stopping the Server. Print Content and Email Content in PlanetPress Workflow In PlanetPress Workflow’s Print Content and Email Content tasks, the option to Update Records from Metadata will only work for fields whose data type is set to String in the data model. Fields of other types will not be updated in the database and no error will be raised. This will be fixed in a later release.
Uninstalling This topic provides some important information about uninstalling (removing) PlanetPress Connect2019.2. To uninstall PlanetPress Connect select the application from within the Add/Remove programs option under the Control Panel. This will start the PlanetPress Connect Setup Wizard in uninstall mode. Note The PlanetPress Connect Setup Wizard might take some seconds to appear. Important Note: Stop any active Anti-Virus software before uninstalling Connect.
Uninstallation Wizard The uninstallation is done by running the PlanetPress Connect Setup Wizard in uninstall mode. The Wizard consists of the following pages: 1. PlanetPress Connect Setup: An information page, listing what will be uninstalled, and also warning about impacts upon running Applications and Services. 2. Data Management: A page that provides options for backing up or deleting Connect data.
General information Connect consists of visible and invisible parts. The invisible parts process the Connect job to provide the actual output. They are introduced to you in the topic: "Connect: a peek under the hood" below. For information about Connect logging, see "Log files" on page 166. For a list of all file types used in Connect, see: "Connect file types" on page 168.
The Workflow server The Workflow server (also referred to as the 'Watch service') executes processes independently, after a Workflow configuration has been uploaded and the services have been started. The Workflow server can run only one configuration at a time. There are a number of services related to Workflow.
tool. The Workflow Service Console lets you start and stop the different services, except the Connect server, and see their log files (see Workflow Service Console). Note that Workflow isn't limited to Connect functionality. It was originally developed as part of the PlanetPress Suite. Many of the plugins in the Workflow configuration tool are older than Connect. They were left in for compatibility reasons, even though they aren't all useful or usable within Connect.
The Connect Server Configuration tool lets you change the settings for the Connect server, the engines and the service that cleans up the database and the file store. These settings can also be made in the preferences of the Designer. The Connect database The Connect database is the database back-end used by Connect itself when processing jobs. It can be either the MySQL instance provided by the Connect installer, or a pre-existing (external) instance (see "Database Considerations" on page 24).
The engines DataMapper engine/s. A DataMapper engine extracts data from a data file. The number of DataMapper engines is configurable (Engines preferences). Merge engine/s. A merge engine merges data with a template using the scripts in the template, in order to create (Print,Email or Web) content items. The number of merge engines is configurable (see Engines preferences): it can be increased depending on the capacity of the machine that runs the solution (see "Performance considerations" on page 34).
Printing and emailing from the Designer To print or send email from within the Designer, the PlanetPress Connect service has to be running. The service is started automatically when the Designer starts, but it may not be running if the Connect Server and the Designer are installed on different computers. The PlanetPress Connect service can be found on the Services tab in the Task Manager. For a proof print the Connect server is not used. Proof printing is always done locally, by the Designer.
Every time output is generated, the Designer and/or Connect Server and any engines involved in the operation produce their own log files. Each component writes its log files to a dedicated subfolder of the Log folder. Merge engines write to the logs/Mergeengine folder, Weaver engines to the logs/Weaverengine folder, DataMapper engines to the logs/Datamapperengine folder, Server to the logs/Server folder, and so forth. Note that actions of the Cleanup service are only logged in the Server's log file.
l l The Designer's logging preferences are set via the Designer; see: "Logging preferences" on page 845. The Connect Server's settings are maintained by the Connect Server Configuration utility tool; see "Server Configuration Settings" on page 121. The logging level that is set applies to the Server as well as the engines. The Designer's log messages are also displayed in the Messages pane (see "Preflight Results and Messages" on page 1034).
l l l l .OL-package: A transfer file used to package one or many of the above files (the data model being part of both the template and the data mapping configuration). Created by using the File > Package dialog. (See "Package dialog" on page 960.) .OL-script: One or more Designer scripts. Scripts personalize the output of a template. They are either added via wizards (see "Personalizing content" on page 786) or selfwritten (see "Writing your own scripts" on page 853).
OL Connect projects An OL Connect project is an automated process, or combination of processes, in which the Connect Server and Database are used. (For an overview of the architecture of the OL Connect software, see "Connect: a peek under the hood" on page 161). Typically, an OL Connect project aims at automating (part of) a company's communication with its customers, suppliers, or other parties.
Wizards" on page 973 in the online help or the Project Wizards overview video on the OL Learn website. Typically, in an OL Connect project there is a number of Workflow processes that communicate with the Connect Server, Database and/or File Store through one or more of the specially developed OL Connect tasks. For help on building these Workflow processes see "Workflow processes in OL Connect projects" on page 213 and "OL Connect tasks" on page 215.
There is an introductory Project Wizards overview video on the OL Learn website. For generic information about Connect solutions and their components, see "OL Connect projects" on page 170. Note The projects require that the Connect Server and Connect Workflow be installed on the local machine. These are the projects that can be installed with a wizard. l l Print promotional jobs.
and PDF. In order to create the PDF, the data are merged with a Connect template. (See: "Project Wizard: COTG Timesheets" on page 180.) Project wizard: Basic Email The Basic Email project wizard creates an OL Connect project that sends emails with two attachments: a Return and Refund Policy (PDF) which is the same for all emails, and a delivery note (PDF) which is attached to the email dynamically. The email has a mailto link.
Testing and running the project Once the project wizard has finished the installation, the project is ready to be tested. 1. If the templates and data mapping configurations haven't been sent to Workflow yet, do that first (see "Sending files to Workflow" on page 457). This requires that the Workflow service is running (see Starting the Workflow service in Workflow's Online Help). 2. Locate the Workflow configuration in the project folder and open it in OL Connect Workflow. 3.
Project details The email template The email's design is in the EM_BASIC Email Message template. It contains one Email section (see "Email templates" on page 526). Styling is done via style sheets (see "Local formatting versus style sheets" on page 741). The style rules are in the context_htmlemails_styles.css file. Note how they use HTML tags, IDs and classes to select elements. (See also: "Selectors in Connect" on page 878.
"Variable Data" on page 801.) l l The To and Subject scripts apply to email fields. (Click Email Fields at the top of the email to expand all email fields.) For information about this kind of scripts, see: "Email header settings" on page 530. Finally, there are two custom scripts: l The Personalize Support link script adds the order number to the 'support team' link (which is a mailto link). The Year script puts the current year in the footer.
The data mapping configuration The Workflow process uses a data mapping configuration, made with "The DataMapper" on page 225: EM_BASIC Data. To open the data mapping configuration, open the Designer, select File > Open from the menu and browse to the Configurations\Resources folder. This data mapping configuration will of course only work with the appropriate data files. It was designed for XML files that are structured like this file: Sample Data.xml (in the Configurations\Resources\Data folder).
To see the script, click on the DeliveryNote field in the Data Model pane at the right; then take a look at the Step Properties pane (in the middle). To see where the property is defined, click the Preprocessor step on the Steps pane (at the left); then look at the Properties section on the Step Properties pane. Customizing the project A project is a great starting point for building an OL Connect solution. This part explains how to make changes to the project.
Note If the input data is JSON, you don't need a data mapping configuration: JSON data can be used in a template as is. See: "Adding JSON data from a JSON file" on page 798. However, if you want the data to be saved in the OL Connect database, put the XML/JSON Conversion plugin before the Send to Folder task to convert the JSON to XML, and create an XML data mapping configuration to extract the data.
Workflow configuration The current Workflow configuration is very simple. In reality, a process that generates email output will be part of a larger project, in which, for example, invoices are produced in a separate process, stored in a folder and attached to an email at a later time. For general information about processes in Workflow see About Processes and Subprocesses, in the Online Help of Workflow.
Finally, you need a valid COTG account, Repository ID and password. You could use dummy data to create the Project Wizard and finish the installation, but you won't be able to test the project. For more information about the options, see: "COTG Timesheets - Project Wizard" on page 975. Tip If you own PlanetPress Connect or PReS Connect, free COTG trial licenses may be available to you; see http://www.captureonthego.com/en/promotion/.
Note The process is pre-configured to use the sample data file, which comes with the project, when it runs in Debug mode. Alternatively you could copy the sample data file to the In folder. 5. Launch the COTG app and log in using the COTG account that you entered in the Project Wizard. 6. In the app, open the Repository and download one of the forms. 7. From the app's Library, open the form. 8. Enter data and draw a signature. 9. Submit the form.
Tip Hover over the name of a script in the Scripts pane to highlight parts of the template that are affected by the script. l l l The guid script adds data to the guid field. This is a hidden field. It is only visible in the Source view. The result of the form action script is added to the form's action attribute. To see how that is done, double-click the script; then click Options. The Year script puts the current year in the footer of the page. This is a custom script.
a field that contains the action of the Form. Note that the COTG account is the same in all of the records in the sample data. It is inserted into the sample data by the Project Wizard. COTG Timesheet Report The COTG Timesheet Form data mapping configuration is designed to extract the data that are submitted via the app. It first extracts the common fields, and then the information from the rows in the form, in a loop.
l Finally, the Output to Capture OnTheGo task sends information about the form to the COTG Server. Double-click the task to see how variables are used in its settings. The Delete task is an Output task that does nothing, actually; it doesn't even remove anything. However, this step is useful when running the project step by step in Debug mode. Tasks will only return their output to the process - where it can be viewed - as long as they are followed by another task.
preferences (see "Project Wizard deployment settings" on page 849) before installing the project. The form If you want to add inputs to the form and extract the submitted data, here's how to do that. 1. Open the Web section and add elements to the Web Form (see "Using COTG Elements" on page 593 and "Using Form elements" on page 558). You could also add text, images and other elements (see "Content elements" on page 628) and change the layout of the page (see "Styling and formatting" on page 741). 2.
Tip The saved file can be used to create a data mapping configuration. The report Using different data in the report requires changing the COTG Timesheet Report template (see "Personalizing content" on page 786). Tip The Designer can have one data mapping configuration and one template open at the same time. Use the tabs at the top of the workspace to switch between the two. Click the synchronize button on the Data Model pane to make sure that the Data Models are the same in both.
probably means saving the input as sample data first (see "Saving input as sample data" on page 186). l How the submitted data must be handled depends entirely on what they are used for. You may have to write them to a database and use them in an email, for example. The cotg_ts_generate_report process demonstrates only a few of the things that you can do with the submitted data.
Note In order to use the project, OL Connect Server and OL Connect Workflow must be installed on the local machine. The wizard lets you select the folder in which you want the solution to be installed. In the selected folder, the Project Wizard will create two subfolders: Configurations and Workspace. The project's resource files are saved to the Configurations folder. The Workspace folder is used for debugging or running the solution.
Running the project Having tested the project, you will be ready to send it to the Workflow service; see Saving and sending a Workflow Configuration in Workflow's Online Help. To test the project, which then runs on the server, copy the Sample Data.xml file from the Configurations\Data folder to the Workspace\In folder. The output should appear in the same folder as before. Project details The letter template The promotional letter is designed in the PR_PROM Letter template.
l The sender's address is adjusted depending on where the customer lives. The two different sender's addresses are saved in snippets. (See: "Loading a snippet via a script" on page 872.) Styling is done via CSS. The context_all_styles.css file contains style rules for certain HTML elements (level 1 and 2 headings) and for elements with a certain class or ID. The data mapping The data with which the template is merged come from an XML file: Sample Data.xml.
Configurations\Resources\Output presets folder to select the preset. Note that the Output Type, on the Print Options page in the Output Creation dialog, is set to Prompt for file name. This setting is overruled in the Workflow configuration (see below). Workflow configuration Whenever new input data appears in the Workspace\In folder, the letter template is automatically merged with it and then printed.
Do you intend to expand the project into a solution where Workflow runs on a different machine that also has a different regional setting? Then indicate the desired encoding in the Designer preferences (see "Project Wizard deployment settings" on page 849) before installing the project. Input data Here's how to adjust the project to input data that has a different structure or file type or comes from a different source. 1. Create a new data mapping configuration to match your input data.
l Change the "Master Pages" on page 505 l Add sections (see "Print context" on page 482) In order to further personalize the letter, you need to open your data mapping configuration. (See: "Personalizing content" on page 786.) Tip The Designer can have one data mapping configuration and one template open at the same time. Use the tabs at the top of the workspace to switch between the two. Click the synchronize button on the Data Model pane to make sure that the Data Models are the same in both.
Project Wizard: Print Transactional Jobs The Print Transactional Jobs Project Wizard creates an OL Connect project that produces transactional print output. It prints invoices to: o A single PDF for the entire job (in which the invoices are grouped per customer). o One PDF per customer. o One PDF per invoice. For an introduction to this Project Wizard, see Project Wizards overview video on the OL Learn website (start at 7:56) or on Youtube: Print Transactional Jobs.
1. Locate the Workflow configuration in the Configurations\Workflow folder and open it in OL Connect Workflow. 2. Select the pr_tran_generate_output process. 3. Open the Debug ribbon and click Run. The debugger always skips the first Input task. It needs a sample data file to work with. Normally you'd have to select a sample data file in Workflow. However, the project is preconfigured to use this file: Sample Data.xml (located in the project's Configurations\Data folder).
Scripts Scripts personalize content. Most of the scipts in the Information folder (on the Scripts pane) are made with the Text Script Wizard (see "Using the Text Script Wizard" on page 803). Tip Hover over the name of a script in the Scripts pane to highlight parts of the template that are affected by the script. Text that should be replaced by data is not only surrounded by @ (e.g. @date@) but also wrapped in a span (see "Span" on page 695).
The data mapping configuration The template is merged with data from an XML file: Sample Data.xml. They are extracted from the XML file with a data mapping configuration, made with the DataMapper (see "The DataMapper" on page 225). The data mapping configuration first extracts the common invoice fields, and then the transactional data, in a loop. For information about how to extract transactional data from an XML file, see: "From an XML file" on page 262.
The PR_TRAN PDF per Customer preset outputs one file per customer, separating the output by document set. The last output preset needs the invoices in the job to be grouped in document sets first (by customer number, in this case). That is what the Job Creation Preset does. This preset is used by the Create Job task in the Workflow configuration. Variable file names The Job Creation Preset does something else, too: it attaches extra information - meta data - to the documents and to the document sets.
Do you intend to expand the project into a solution where Workflow runs on a different machine that also has a different regional setting? Then indicate the desired encoding in the Designer preferences (see "Project Wizard deployment settings" on page 849) before installing the project. Input data Here's how to adjust the project to input data that has a different structure or file type or comes from a different source. 1. Create a new data mapping configuration to match your input data.
l Change the "Master Pages" on page 505 l Add sections (see "Print context" on page 482) In order to further personalize the invoice, you need to open your data mapping configuration. (See: "Personalizing content" on page 786.) Tip The Designer can have one data mapping configuration and one template open at the same time. Use the tabs at the top of the workspace to switch between the two. Click the synchronize button on the Data Model pane to make sure that the Data Models are the same in both.
2. Change the Grouping Options by selecting the relevant fields on the Job, Job Segment, and/or Document Set tab. 3. Adjust the Separation Options in the Output Creation Preset accordingly. Tip The Execute Data Mapping task, Create Job and Create Output task may be replaced with the All In One task, with its Output Creation set to None. Using the All In One instead of the separate tasks makes the process a little faster.
The selected folder's path is saved to a global variable in the Workflow configuration (see "The Workflow configuration" on page 205). Testing and running the project Once the Project Wizard has finished the installation, the project is ready to be tested. 1. If the templates and data mapping configurations haven't been sent to Workflow yet, do that first (see "Sending files to Workflow" on page 457).
Tip The saved file can be used to create a data mapping configuration. Project details The web templates Both web pages are designed in the WEB_FORM Web Page template. It contains a Web context with two Web pages: form and thank_you (see "Web pages" on page 547). Styling is done via style sheets (see "Local formatting versus style sheets" on page 741). The style rules are in the context_web_styles.css file. Note that they use the HTML tag (e.g. section), ID (#theID) and/or the class (.
The Workflow configuration The project's Workflow configuration contains just one process: an OL Connect Web process (see "Web processes with OL Connect tasks" on page 222). Its NodeJS Server Input task has two HTTP Action entries: form and thank_you. This means the process will be triggered when the server receives a request that ends with either /form or /thank_you. The request is saved to an XML file, which becomes the job file. The Text Condition task checks if the request's header is thank_you.
Customizing the project A project is a great starting point for building an OL Connect solution. This part explains how to make changes to the project. Do you intend to expand the project into a solution where Workflow runs on a different machine that also has a different regional setting? Then indicate the desired encoding in the Designer preferences (see "Project Wizard deployment settings" on page 849) before installing the project.
Web pages Apart from the form, there are lots of ways to modify the template. You could add text, images and other elements (see "Content elements" on page 628) and change the layout of the web pages (see "Styling and formatting" on page 741). Once the template is ready, send it to Workflow (see "Sending files to Workflow" on page 457). Finally, in Workflow, adjust the process: double-click the Create Web Content task to open it, and select the new template.
Project Wizard: Serving a Web Page The Serving a Web Page Project Wizard creates an OL Connect project that responds to a request by serving a web page. This project extracts data from a parameter in the given URL and shows the value on the web page. For an introduction to this Project Wizard, see Project Wizards overview video on the OL Learn website (start at 12:44) or on Youtube: Serving a Web Page.
To test the project: 1. Send the Workflow configuration to the OL Connect Workflow service; see Saving and sending a Workflow Configuration in Workflow's Online Help. 2. Access the web page by entering the following URL in a browser on the machine that runs Workflow: http://localhost:9090/hello. 3. Follow the instructions on the page to see how values in the URL change the text of the page. Saving input as sample data Testing a process in Debug mode is only possible with a sample data file.
Project details The web template The web page is designed in the WEB_HELLO Web Page template. It contains one Web section (see "Web pages" on page 547). Styling is done via style sheets (see "Local formatting versus style sheets" on page 741). The style rules are in the context_web_styles.css file. Note how they combine the HTML tag, ID and class of elements to select them. (See also: "Selectors in Connect" on page 878.) There are only two scripts in the template, as you can see on the Scripts pane.
The NodeJS Server Input task's HTTP action is set to hello. This means that this process will be invoked whenever someone tries to access the Workflow server with this URL: http:// {server's address}/hello. The Delete task is an Output task that does nothing, actually; it doesn't even remove anything. However, this step is useful when running the project step by step in Debug mode.
Input data If you want to add other parameters to the URL and use those data in the template, here's how to do that: 1. Run the project, add more parameters to the URL and let the process save the input data to a file (see "Saving input as sample data" on page 209). 2. Use the file to create a new data mapping configuration that extracts the additional data. (See "Creating a new data mapping configuration" on page 227.) 3.
same in both. Once the template is ready, send it to Workflow (see "Sending files to Workflow" on page 457). Finally, in Workflow, adjust the process: double-click the Create Web Content task to open it, and select the new template. This is only necessary when the file name has changed. Send the Workflow configuration to the server (see Saving and sending a Workflow Configuration in Workflow's Online Help).
l l l l l l Input tasks look for certain input data on a certain channel and start a process when they find it. The data that enter the process are handed from one plugin to the next in the form of a file: the 'job file'. Process logic tasks help you to control the process, for example by branching it, creating a loop, or referring to another process or a subprocess. Action tasks perform a wide variety of operations.
l COTG processes. The process that creates a form for the Capture OnTheGo app is in essence a web process, but a COTG solution consists of more than one process. The typical COTG processes are described here: "Capture OnTheGo Workflow processes" on page 217. Tip Project Wizards The OL Connect software comes with a number of Project Wizards that generate a Workflow configuration, and any Connect templates, data mapping configurations, and Print Presets required to make the project work.
Email The Create Email Content task creates email content items and sends them to the recipient. See "Email processes with OL Connect tasks" on page 218. Web The Create Web Content task can handle only one record at a time and returns a web page. See "Web processes with OL Connect tasks" on page 222. Print The Create Print Content task generates a set of Print content items in the OL Connect database, but it is not an Output task.
l l The Set Properties task adds properties as tags to items/sets in the OL Connect database. The Retrieve Items task retrieves items (records, or content items, etc.) or sets of items from the OL Connect database, by ID or by property. Note Combined, the Set Properties and Retrieve Items tasks make it possible to batch and commingle Print content items.
l l One process that authenticates and replies to document requests from COTG users. This process returns the actual document directly to the app. It starts with a Server Input task (the NodeJS Server Input task or the older HTTP Server Input task), which returns the final output of the process to the caller. One process that receives and handles the data when a COTG user submits a form. This process starts with a Server Input task as well.
enter an empty JSON string: {}. However, if the template should be merged with data, you will need to add one or more tasks to provide the required data. The Create Email Content task must receive either Metadata containing information regarding a valid Record Set, or JSON data. This can be the output of tasks like: l l An Execute Data Mapping task which retrieves data from the job file (such as the request XML).
Print processes with OL Connect tasks Generating print output from a template via an automated process requires you to design a print process in the PlanetPress Workflow configuration tool. This topic explains which tasks and files are used in a print process. Tip An easy way to setup a print project in OL Connect, including the print process and the files that it needs, is to use a Project Wizard. There are two Project Wizards that create a sample print project. See "Project Wizards" on page 973.
The All In One task is the fastest and most efficient way to create print output. The task exchanges less data with the server than the separate plugins do and it has multi-threading support: it can produce the data set and content items in parallel. Nevertheless, the separate plugins would be used in the following situations: l l l The record set, created by the Execute Data Mapping task, is also needed to create another kind of output in the same process.
All of these files are made with the Designer and need to be sent to PlanetPress Workflow before they can be used in the Workflow process; see "Sending files to Workflow" on page 457. When the necessary files have been created and sent to Workflow, the next step is to create a process in PlanetPress Workflow that generates Print output, using these files. For more information about how to create a process in Workflow, please refer to the Online Help of Workflow.
The Create Web Content task creates an HTML output file from the Web context in a template. Select the Web template in the task's properties. If the Web template doesn't need any data, you can set the Data Source of this task to JSON and enter an empty JSON string: {}, or set it to Record ID and enter 0 (zero). However, if the template should be merged with data, the task needs either a valid Record ID or a JSON object.
The next step is to create a process in PlanetPress Workflow that generates Web output, using these files. For more information about how to create a process in Workflow, please refer to the Online Help of Workflow.
The DataMapper The DataMapper is the tool to create a data mapping configuration. Data mapping configurations are used to extract data and transpose that data into a format that can be shared amongst different layouts and outputs created with the OL Connect Designer and Workflow. The original data, located in a file or database outside of OL Connect, is called a data source.
3. Build the data mapping workflow. A data mapping workflow always starts with the Preprocessor step and ends with the Postprocessor step. You can add as many steps as you like and edit the Data Model of the extracted data as required. See "Data mapping workflow" on page 248 and "The Data Model" on page 286. What's next? Use the data mapping configuration in the Designer module to create templates for personalized customer communications. To learn more, see "The Designer" on page 449.
Creating a new data mapping configuration A new data mapping configuration can be made with or without a wizard. When you open a data file with a DataMapper wizard, the wizard automatically detects a number of settings. You can adjust these settings. Next, the wizard automatically extracts as many data fields (or metadata, in case of a PDF/VT or AFP file) as it can, in one extraction step. Without a wizard you have to make the settings yourself, and configure the extraction workflow manually.
l From the File menu 1. Click the File menu and select New. 2. Click the Data mapping Configuration drop-down and select Files and then the file type: l Comma Separated Values or Excel (CSV/XLSX/XLS), l Microsoft Access l PDF, PS, PCL or AFP l Text l XML. 3. Click Next. 4. Click the Browse button and open the file you want to work with. 5. Click Finish.
the DataMapper won't either. If the original is a PDF, it is recommended to find an alternative way to get it in the system instead of going through a print operation. l Rotated pages in a PDF are supported (if rotated 0/90/180/270 degrees). The Extract step will be able to extract data from horizontal and vertical lines of text on rotated pages.
The steps to take with the wizard depend on the file type. See: l "Using the wizard for CSV and Excel files" on page 232 l "Using the wizard for databases" on page 234 l "Using the wizard for PDF/VT or AFP files" on page 237 l "Using the wizard for XML files" on page 239 Generating a counter Instead of creating a data mapping configuration for a certain type of data file, you may create a data mapping configuration that only contains a series of sequential numbers.
l l l l l l Increment Value: The value by which to increment the counter for each record. For example, an increment value of 3 and starting value of 1 would give the counter values of 1, 4, 7, 10, [...] Number of records: The total number of counter records to generate. This is not the end value but rather the total number of actual records to generate. Padding character: Which character to add if the counter's value is smaller than the width. Width: The number of digits the counter will have.
Using the wizard for CSV and Excel files The DataMapper wizard for CSV and Excel files helps you create a data mapping configuration for such files. The wizard automatically detects delimiters and extracts all data in one extraction step. The wizard interprets each line in the file as a record. If your data file contains transactional data, you will probably want more lines to go in one record and put the transactional data in detail tables. The wizard cannot create detail tables.
Note Excel files saved in "Strict Open XML" format are not supported yet. After selecting the file, take a look at the preview to ensure that the file is the right one and the encoding correctly reads the data. Click Next. For an Excel file you can make the following settings: l l l First row contains field names: Uses the first row of the Excel sheet as headers, which automatically names all extracted fields. Sheet: Select the sheet from which the data should be extracted.
Tip The Sort on option, combined with the Stop data mapping option of the "Action step" on page 283, allows to process only a group of items without having to examine all records. (See also: "Text and PDF Files" on page 369.) Verify that the data are read properly. Finally click Finish. All data fields are automatically extracted in one extraction step. Using the wizard for databases The DataMapper wizard for database files helps you create a data mapping configuration for a database file.
4. Use the drop-down to select the database type. 5. Click Next. Wizard settings for a database file After opening a database file with a wizard there are a number of settings to make, depending on the database type (see below). On the last page of the dialog, click Finish to close the dialog and open the actual data mapping configuration. Note After creating the initial data mapping configuration you may use a custom SQL query via the Input Data Settings; see "Settings for a database" on page 252.
l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text. Microsoft Access l l l Password: Enter a password if one is required. Table name: The selected database is a set of related tables composed of rows and columns corresponding respectively to source records and fields. Select a table from which you want to extract data.
JDBC Note Since JDBC can connect to multiple types of databases, a specific database driver and path to this driver's JAR file must be specified. l l l l l l l l JDBC Driver: Use the drop-down to select which JDBC Driver to use for the database connection. JAR file path: Enter a path to the JAR file that contains the appropriate driver for the database. Server: Enter the server address for the database server.
Tip To extract information from the metadata in the extraction workflow itself, you have to create a JavaScript extraction (see "Using scripts in the DataMapper" on page 399 and "extractMeta()" on page 421). If the PDF doesn't contain any metadata, each page is a new record - in other words, a boundary is set at the start of a new page -, which is exactly what happens when you open the file without a wizard. You can open a PDF/VT or AFP file with a wizard using the Welcome screen or the File menu.
Click Finish to close the dialog and open the actual Data Mapping configuration. On the Settings pane, you will see that the boundary trigger is set to On metadata. The selected metadata fields are added to the Data Model. Note Extracting data from a PDF that comes from a Windows printer queue (a PDF converted to PostScript, converted back to PDF by an Input task in Workflow) might not work (see the Connect Knowledge Base.
3. From the Using a wizard pane, select XML. 4. Click the Browse button and open the XML file you want to work with. Click Next. l From the File menu 1. In the menu, click File > New. 2. Click the Data mapping Wizards drop-down and select From XML File. 3. Click Next. 4. Click the Browse button and open the XML file you want to work with. Click Next. After selecting the file, you have to set the split level and trigger type: l l XML Elements: This is a list of node elements that have children nodes.
This topic's intention is to provide you with a method to make LincPDF take these advanced settings into account, so the generated PDF can be correctly read in the DataMapper. Note The method described in this topic can only be done using PlanetPress Workflow. Requirements To be able to import PCL input files, you will need the PCL Input license, in addition to PlanetPress Connect. To check if you have a PCL Input license: 1. Open the Connect Software Activation module. 2.
1. Add a local variable to your process and name it lincPDFOptions. 2. Add another local variable named workingDir and give it a default Windows path (for example: C:\PCL2PDF\). 3. Add a plugin to capture the PCL File. You may use any input plugin that imports the PCL file into the process, such as Folder Capture, LPD Input, etc. 4. Using the Change Emulation plugin, change the Emulation to ASCII.
(default: 0). PDF Author -dAuthor:$s string PDF document’s author (default: null). PDF Title -dTitle:$s string PDF document’s title (default: filename). 6. Next, use the External Program plugin to convert the PCL to PDF with the above % {lincPDFOptions} options. In the General tab: l l l l l Set the Executable file to: C:\Program Files\Objectif Lune\OL Connect\LPDFConv\Bin\LincPDFC.exe Set the Parameters to: -i"%F" -o"%{workingDir}\Temp\%O.
the Workflow log. 7. Save the output of LincPDFC using the –o folder specifier in the parameter (% {workingDir}\Temp, in this case.) In another Workflow process, import the created PDF with the Folder Capture input plugin, specifying the output folder of the previous process (%{workingDir}\Temp in the example) as input folder, and %O.pdf as the file mask.
Once you have the PDF as job file, you may pass it to the Execute Data Mapping plugin for further processing. LincPDFC Options To view the available options that can be set in LincPDF, run the executable (LincPDFC.exe) in a command prompt window. It will display a help message with available options.
/*Open Windows Command Prompt Change directory cd C:\Program Files\Objectif Lune\OL Connect\LPDFConv\Bin C:\Program Files\Objectif Lune\OL Connect\LPDFConv\Bin\LincPDFC.exe LincPDF for Command-Line, Version 2.6.6.14 Copyright (c) 2001-2007 Lincoln & Co., a division of Biscom, Inc. Usage: LincPDF -iInput.PCL [-oOutput.
-dTitle:$s : PDF Title -dSubject:$s : PDF Subject -dAuthor:$s : PDF Author -dKeywords:$s : PDF Keywords -dVersion:num : PDF Version (multiply by 10) Page Setup: -pWidth:num : Page Width (required only if Page Type is Custom) -pHeight:num : Page Height (required only if Page Type is Custom) -pXOff:num : Page X Offset (see also Measurement) -pYOff:num : Page Y Offset (see also Measurement) -pMeasure:num : Page Measurement (0-inch, 1-mm, 2-point) -pOrient:num : Page Orientation (0-Portrait, 1-Landscape) -pTyp
-yCopyContents : Enable Copying Text and Graphics from Document -yUse128Bit : Use 128-bit Encryption -yAssembleDocument : Enable Assemble Document (128-bit encryption only) -yExtractText : Enable Text and Graphics Extraction (128-bit encryption only) -yLowResolutionPrint : Enable Lower-level Resolution Printing (128-bit encryption only) Tips ---------------------------------------------------. using quotation mark for complicated string, for example, -dKeywords:"key1, key2" .
after the Data Mapping workflow has completed ("Postprocessor step" on page 284). When you create a new data mapping configuration, these steps are added automatically, but they don't actually do anything until you configure them. In between the Preprocessor and Postprocessor step, the workflow can contain as many steps as needed to extract the required data. Adding steps Extracting data is the main way to build a data mapping workflow; see "Extracting data" on page 254.
clipboard. To place the step at its destination, right-click any step and select Paste Step, or use the Paste button in the toolbar. The pasted steps will be positioned below the selected step. Keep in mind that steps may influence each other, so you may have to move other steps as well to ensure that the workflow continues to function properly.
pane at the left. l l l Input Data settings help the DataMapper read the data source and recognize data correctly. Boundaries mark the start of a new record. They let you organize the data, depending on how you want to use them. Data format settings define how dates, times and numbers are formatted by default in the data source. Input data settings (Delimiters) The Input Data settings (on the Settings pane at the left) specify how the input data must be interpreted.
Settings for a PDF File PDF files have a clear and unmovable delimiter: pages. So, the Input Data settings are not used to set delimiters. Instead, these options determine how words, lines and paragraphs are detected when you select content in the PDF to extract data from it. For an explanation of all the options, see: "PDF file Input Data settings" on page 342. Settings for a database Databases all return the same type of information.
See also: "XML File Input Data settings" on page 345. Note The DataMapper only extracts elements for which at least one value is defined in the file. Record boundaries Boundaries are the division between records: they define where one record ends and the next record begins. Using boundaries, you can organize the data the way you want. You could use the exact same data source with different boundaries in order to extract different information.
By default, the user preferences are set to the system preferences. These user preferences become the default format values for any newly created data mapping configuration. To change these preferences, select Window > Preferences > DataMapper > DataMapper default format (see "DataMapper preferences" on page 832). Data format settings defined for a data source apply to any new extraction made in the current data mapping configuration.
Preprocessor step The Preprocessor step allows the application to perform actions on the data file itself before it is handed over to the Data Mapping workflow. In addition, properties can be defined in this step. These properties may be used throughout the extraction workflow. For more information, see "Preprocessor step" on page 274. Adding an extraction In an extraction workflow, Extract steps are the pieces that take care of the actual data extractions. To add an Extract step: 1.
field name stays the same. Drop data on empty fields or on the record itself to add new fields. Special conditions The Extract step may need to be combined with another type of step to get the desired result. l l l Data can be extracted conditionally with a Condition step or Multiple Conditions step; see "Condition step" on page 279 or "Multiple Conditions step" on page 282. Normally the same extraction workflow is automatically applied to all records in the source data.
1. Select the field in the Data Model that contains the extracted lines. 2. On the Step properties pane, under Field Definition, click the drop-down next to Split and select Split lines. Adding fields to an existing Extract step For optimization purposes, it is better to add fields to an existing Extract step than to have a succession of extraction steps. To add fields to an existing Extract step: 1. In the Data Viewer pane, select the data that needs to be extracted.
occurred and all data fields related to subsequent steps will be greyed out. Click the Messages tab (next to the Step properties pane) to see any error messages. To test the extraction workflow on all records that are displayed, you can either: l Click the Validate All Records toolbar button. l Select Data > Validate Records in the menu. If any errors are encountered in one or more records, an error message will be displayed.
To resize a data selection, click and hold one of the resize handles on the borders or corners, move them to the new size and release the mouse button. To move the data selection, click and hold anywhere on the data selection, move it to its new desired location and release the mouse button. Note In a Text or PDF file, when you move the selection rectangle directly after extracting data, you can use it to select data for the next extraction.
an XML document. Extracting transactional data Promotional data are data about customers, such as addresses, names and phone numbers. In Connect, each record in the extracted record set represents one recipient. The number of fields that contain promotional data is the same in each record. These data are stored on the root level of the extracted record.
For more information about detail tables, multiple detail tables and nested detail tables, see "Example " on page 335. From a CSV file or a Database The transactional data (also called line items) appear in multiple rows. 1. Select a field in the column that contains the first line item information. 2. Right-click this data selection and select Add Repeat. This adds a Repeat step with a GoTo step inside it.
The extraction step is placed inside the Repeat step, just before the GoTo step. From an XML file The transactional data appears in repeated elements.
1. Right-click one of the repeating elements and select Add Repeat. This adds a Repeat step to the data mapping configuration. By default, the Repeat type of this step is set to For Each, so that each of the repeated elements is iterated over. You can see this on the Step properties pane, as long as the Repeat step is selected on the Steps pane. In the Collection field, you will find the corresponding node path.
2. (Optional.) Add an empty detail table via the Data Model pane: right-click the Data Model and select Add a table. Give the detail table a name. 3. Select the Repeat step on the Steps pane. 4. Extract the data: inside a repeating element, select the data that you want to extract. Then right-click the selected nodes and select Add Extraction, or drag & drop them in the Data Model. When you drag & drop data on the name of a detail table in the Data Model pane, the data are added to that detail table.
1. Select an element in the first line item. 2. Right-click on the selection and select Add Goto. The Goto step will move the cursor to the start of the first line item. 2. Add a Repeat step where the loop must stop. 1. In the line under the last line item, look for a text that can be used as a condition to stop the loop, for example "Subtotals", Total" or "Amount". 2. Select that text, right-click on it and select Add Repeat. The Repeat step loops over all lines until the selected text is found. 3.
1. Select the start of the Repeat step on the Steps pane. 2. Look for something in the data that distinguishes lines with a line item from other lines (or the other way around). Often, a "." or "," appears in prices or totals at the same place in every line item, but not on other lines. 3. Select that data, right-click on it and select Add Conditional. Selecting data - especially something as small as a dot - can be difficult in a PDF file.
4. (Optional.) Add an empty detail table to the Data Model: right-click the Data Model and select Add a table. Give the detail table a name.
5. Extract the data (see "Adding an extraction" on page 255). When you drag & drop data on the name of a detail table in the Data Model pane, the data are added to that detail table. Dropping the data somewhere else on the Data Model pane, or using the contextual menu in the Data Viewer, creates a new detail table, with a default name that you can change later on (see "Renaming a detail table" on page 331).
Note In a PDF or Text file, pieces of data often have a variable size: a product description, for example, may be short and fit on one line, or be long and cover two lines. To learn how to handle this, see "Extracting data of variable length" on the facing page. 6. Extract the sum or totals. If the record contains sums or totals at the end of the line items list, the end of the Repeat step is a good place to add an Extract step for these data.
Extracting data of variable length In PDF and Text files, transactional data isn't structured uniformly, as in a CSV, database or XML file. Data can be located anywhere on a page. Therefore, data are extracted from a certain region on the page. However, the data can be spread over multiple lines and multiple pages: l l Line items may continue on the next page, separated from the line items on the first page by a page break, a number of empty lines and a letterhead.
Using a Condition step or Multiple Conditions step Using a Condition step ("Condition step" on page 279) or a Multiple Conditions step ("Multiple Conditions step" on page 282) one could determine how big the region is that contains the data that needs to be extracted. In each of the branches under the Condition or Multiple Conditions step, an Extract step could be added to extract the data from a particular region. The Extract steps could write their data to the same field.
Page 272
Using a script A script could also provide a solution when data needs to be extracted from a variable region. This requires using a Javascript-based field. 1. Add a field to an Extract step, preferably by extracting data from one of the possible regions; see "Extracting data" on page 254. To add a field without extracting data, see "JavaScript-based field" on page 292. 2. On the Step properties pane, under Field Definition, select the field and change its Mode to Javascript.
Note that this script replicates exactly what can be done in a Condition step. In cases like this, it is recommended to use a Condition step. Only use a script when no steps are sufficient to give the expected result, or when the extraction can be better optimized in a script. Steps In the DataMapper, steps are part of an extraction workflow (see "Data mapping workflow" on page 248). They contain a specific instruction for the DataMapper, for example to extract data, create a loop, or apply a condition.
could be created to be added to each record in the output for integrity checks later on, or a time stamp could be added to create reports. A tag could be added to process certain records differently. A preprocessor could remove certain records altogether. One example of how a preprocessor could be used is given in a How-to: Using Preprocessors in DataMapper. Properties To add a property: 1. Select the Preprocessor step on the Steps pane. 2.
Configuring the Preprocessor step For an explanation of the settings for preprocessors, see: "Preprocessor step properties" on page 357. Extract step The Extract step is essential in each and every data mapping configuration. It extracts data from the data source, based on their location (a row and column in CSV or tabular data, an XPath in XML, or a region of the page in PDF and Text) or on JavaScript code. The data is stored in the record set that is the result of the extraction workflow.
Adding an Extract step To add an Extract step, first select the step on the Steps pane after which to insert the Extract step. Then: l l In the Data Viewer, select some data, right-click that data and choose Add Extraction, or drag & drop the data in the Data Model. For more detailed information and instructions, see: "Extracting data" on page 254. Alternatively, right-click the Steps pane and select Add a Step > Add Extraction. Make the required settings on the Step properties pane.
avoid an infinite loop, except with XML data. When you select a node in an XML file and add a Repeat step on it, the Repeat step will automatically loop over all nodes of the same type on the same level in the XML file. Adding a Repeat step To add a Repeat step: 1. On the Steps pane, select the step after which to insert the Condition step. 2. Make sure that the cursor is located where the extraction loop must start.
Note The Goto step isn't used in XML extraction workflows in most cases. The DataMapper moves through the file using Xpath, a path-like syntax to identify and navigate nodes in an XML document. Adding a Goto step To add a Goto step: l l On the Steps pane, select the step after which to insert the Goto step. In the Data Viewer, select some data, right-click that data and choose Add Goto, to add a Goto step that moves the cursor to that data.
Adding a Condition step To add a Condition step: l On the Steps pane, select the step after which to insert the Condition step; then, in the Data Viewer, select some data, right-click that data and choose Add Conditional. In the Step properties pane, you will see that the newly added Condition step checks if the selected position (the left operand) contains the selected value (the right operand). Both operands and the operator can be adjusted.
(in the Step properties pane).Make a selection in the Data Viewer and click the Use selected text button in the Right Operand section. You will now be able to see whether or not the proper text is extracted by the current selection. Repeat this until you are satisfied that the proper data is being extracted.Click on the Use selection button in the Left Operand section to fill out the coordinates.The point of origin of each character is at the bottom left of each of them and extends up and to the right.
Rules are by default combined with AND. To change the way rules are combined, right-click "AND" in the Rule Tree, on the Step properties pane, and select OR or XOR instead. (XOR means one or the other, but not both.) Renaming a rule To rename a rule, double-click its name in the Rule Tree and type a new name. Multiple Conditions step The Multiple Conditions step is useful to avoid the use of nested Condition steps: Condition steps inside other Condition steps.
Adding a Multiple Conditions step To add a Multiple Conditions step, right-click the Steps pane and select Add a Step > Add Multiple Conditions. To add a case, click the Add case button to the right of the Condition field in the Step properties pane. Configuring a Multiple Conditions step For information about how to configure the Multiple Conditions step, see "Left operand, Right operand" on page 385. The settings for a Case are the same as for a Condition step; see "Condition step properties" on page 381.
l l l l Execute JavaScript code. Set the value for a record property. Record properties are defined in the Preprocessor step; see "Preprocessor step" on page 274. Stop the processing of the current record and move on to the next one. Normally an extraction workflow is automatically executed on all records in the source data. By stopping the processing of the current record, you can filter out some records or skip records partially.
To add a postprocessor: l Select the Postprocessor step on the Steps pane. l On the Step properties pane, under Postprocessor, click the Add button l . Under Postprocessor definition, add the script. Postprocessor tasks must be written in JavaScript (see "Using scripts in the DataMapper" on page 399 and "DataMapper Scripts API" on page 396). Configuring the Postprocessor step For an explanation of the settings for postprocessors, see "JavaScript" on page 392.
The Data Model The Data Model is the structure of records into which extracted data are stored. It contains the names and types of the fields in a record and in its detail tables. A detail table is a field that contains a record set instead of a single value. The Data Model is shown in the Data Model pane, filled with data from the current record. The Data Model is not related to the type of data source: whether it is XML, CSV, PDF, Text or a database does not matter.
Creating a Data Model A Data Model is created automatically within each data mapping configuration, but it is empty at the start. To fill it you could use another Data Model (see "Importing/exporting a Data Model" below) or start creating a data mapping workflow (see "Data mapping workflow" on page 248). To learn how to add and edit fields, see "Fields" on page 291.
as the DataMapper immediately discards non-required fields that are not referenced by any Extract step. Editing the Data Model The Data Model is generally constructed by extracting data; see "Extracting data" on page 254. Editing fields You can modify the fields in the Data Model via the contextual menu that opens when you rightclick on something in the Data Model pane. For an explanation of the options in this menu, see "Data Model contextual menu" on page 328.
Alternatively, you can right-click the field, group or detail table and select one of the options in the Move menu, to move it up or down within the list or group. Fields cannot be moved into another table. However, inside a table they can be moved up or down. Grouping fields To group one or more fields, select the field(s), right-click and select Add group. It is also possible to create groups within groups; this is done in the same way.
Adding fields and data via Workflow The Data Model is not extensible outside of the DataMapper. When it is used in Workflow - as part of a data mapping configuration - the contents of its fields can be updated but not its structure. There are a number of instances however, where fields may need to be added to the data model after the initial data mapping operation has been performed.
Note Many of these actions can also be performed using REST calls. Please refer to PlanetPress Connect Workflow documentation for more information about the plugins involved. Fields Extracted data are stored in fields in the Data Model (see "The Data Model" on page 286). Fields can be present on different levels: on the record level or in a detail table (see "Example " on page 335). They can be moved up or down and put in groups (see below).
JavaScript-based field JavaScript-based fields are filled by a script: the script provides a value. Note that the last value attribution to a variable is the one used as the result of the expression. There is a number of ways to add a Javascript based field. Via the Steps pane 1. Make sure there is no data selection in the Data Viewer. 2. Right-click on an Extract step on the Steps pane and select Add a Step > Add Extract Field. (To add a new Extract step, select Add a Step > Add Extraction first.) 3.
Property-based field A property-based field is filled with the value of a property. Objects such as the sourceRecord and steps have a number of predefined properties. (For an explanation of the objects to which the properties belong, see "DataMapper Scripts API" on page 396.) Custom properties can be added via the Preprocessor step; see "Preprocessor step" on page 274. A property-based field cannot be added directly.
Renaming and reordering fields in an extraction step The names of fields, as well as the order of fields in an extraction step, can be changed via the properties of the Extract step that they belong to. 1. Select the Extract step that contains the fields that you want to rename. To do this you could click on one of those fields in the Data Model, or on the step in the Steps pane. 2. On the Step properties pane, under Field Definition, click the Order and rename fields button. 3.
Setting the data type Fields store extracted data as a String by default. The data type of a field can be changed via the properties of the Extract step that the field belongs to. 1. Select the Extract step that contains the field. You can do this by clicking on the field in the Data Model, or on the step in the Steps pane that contains the field. 2. On the Step properties pane, under Field Definition, set the Type to the desired data type. See "Data types" on page 304 for a list of available types.
Post function On the Step properties pane, under Field Definition, you can enter a script in the Post function field to be run after the extraction. (Click the Use JavaScript Editor button to open the Script Editor dialog if you need more space.) A Post function script operates directly on the extracted data. Its results replace the extracted data. For example, the Post function script replace("-", ""); replaces the first dash character that occurs inside the extracted string.
2. In the Step properties pane, under Field Definition, click the Remove Extract Field button next to the Field List drop-down. Detail tables A detail table is a field in the Data Model that contains a record set instead of a single value. Detail tables contain transactional data. They are created when an Extract step is added within a Repeat step; see "Extracting transactional data" on page 260. In the most basic of transactional communications, a single detail table is sufficient.
Creating multiple detail tables Multiple detail tables are useful when more than one type of transactional data is present in the source data, for example purchases (items with a set price, quantity, item number) and services (with a price, frequency, contract end date, etc). To create more than one detail table, simply extract transactional data in different Repeat steps (see "Extracting transactional data" on page 260).
Page 299
Nested detail tables Nested detail tables are used to extract transactional data that are relative to other data. They are created just like multiple detail tables, with two differences: l l For the tables to be actually nested, the Repeat step and its Extract step that extract the nested transactional data must be located within the Repeat step that extracts data to a detail table. In their name, the dot notation (record.services) must contain one extra level (record.services.charges).
a number of "details" such as movie rentals or long distance calls.
The services can be extracted to a detail table called record.services. The "charges" and "details" can be extracted to two nested detail tables.
The nested tables can be called record.services.charges and record.services.details.
Now one "charges" table and one "details" table are created for each row in the "services" table. Data types By default the data type of extracted data is a String, but each field in the Data Model can be set to contain another data type. To do this: 1. In the Data Model, select a field. 2. On the Step properties pane, under Field Definition choose a data type from the Type drop-down. Changing the type does not only set the data type inside the record.
l "HTMLString" on page 311 l "Integer" on page 311 l "Float" on page 310 l "Currency" on the facing page l "Date" on page 307 l "Object" on page 312 Note The Object data type is only available in the DataMapper module. It can be used for properties in the Preprocessor step, but not for fields in the Data Model. Boolean Booleans are a simple true/false data type often used in conditions and comparisons.
l JavaScript Expression: Set the desired value to either true or false . Example: record.fields["isCanadian"] = true; Note The value must be all in lowercase: true , false . Any variation in case (True, TRUE) will not work. Boolean expressions Boolean values can be set using an expression of which the result is true or false. This is done using operators and comparisons. Example: record.
l Extraction: l In the Data Model, select a field. l On the Step properties pane, under Field Definition set the Type to Currency. Under Data Format, specify how the value is formatted in the data source (see Extract Step; for the default format settings, see "Data source settings" on page 250). The field value will be extracted and treated as a Float. l l JavaScript Expression: Set the desired value to any Float value. Example: record.fields["PreciseTaxSubtotal"] = 27.
Extracting dates To extract data and have that data interpreted as a Date, set the type of the respective field to Date: 1. Select the field in the data model. 2. On the Step properties pane, under Field Definition, specify the Type as Date. 3. Make sure that the date in the data source is formatted in a way that matches the expectations of the DataMapper. If the date doesn't match the format that the DataMapper expects, it cannot be interpreted as a date.
l l l mm: Numeric representation of the month (i.e. 1, 09, 12) D: Short version of the weekday name ( i.e. Mon, Wed). These values are based on the current regional settings. DD: Long version of the weekday name (i.e. Monday, Wednesday). These values are based on the current regional settings. l dd: Numeric representation of the day of the month (i.e.
Value in raw data Mask to use Tuesday, June 25, 2013 @ 7h31PM DD, MM dd, yyyy @ hh\hnnap Entering a date using JavaScript In several places in the DataMapper, Date values can be set through a JavaScript. For example: l l In a field in the Data Model. To do this, go to the Steps pane and select an Extract step. Then, on the Step properties pane, under Field Definition click the Add JavaScript Field button (next to the Field List drop-down). Type the JavaScript in the Expression field.
Defining Float values l Preprocessor: l l l In the Step properties pane, under Properties, add or select a field. Specify the Type as Float and set a default value as a number with decimal points, followed by a semicolon; for example 546513.879;. Extraction: l In the Data Model, select a field. On the Step properties pane, under Field Definition set the Type to Float. The field value will be extracted and treated as a Float. l l JavaScript Expression: Set the desired value to any Float value.
Defining Integer values l l Preprocessor: l In the Step properties pane, under Properties, add or select a field. l Specify the Type as Integer and set a default value as a number, such as 42. Extraction: l In the Data Model, select a field. On the Step properties pane, under Field Definition set the Type to Integer. The field value will be extracted and treated as an integer. l l JavaScript Expression: Set the desired value to any Integer value. Example: record.
Defining Object values l Preprocessor: l In the Step properties pane, under Properties, add or select a field. l Specify the Type as Object and set a default value as a semi-colon. String Strings contain textual data. Strings do not have any specific meaning, which is to say that their contents are never interpreted in any way. Defining String values l Preprocessor: l l l In the Step properties pane, under Properties, add or select a field.
l l It is possible to put more than one string, as well as variables containing strings, by concatenating them with the + operator. For example, "Hello " + sourceRecord.property.FirstName + ", nice to meet you!". Adding more data to an existing string variable or field is possible using a combination of concatenation and assignment.
version="1" xmlns="http://www.objectiflune.com/connectschemas/DataModelConfig" xsi:schemaLocation="http://www.objectiflune.com/connectschemas/Data ModelConfig http://www.objectiflune.com/connectschemas/DataModelConfig/1_0_0_ 3.xsd" xmlns:xsi="http://www.w3.
version="1" xmlns="http://www.objectiflune.com/connectschemas/DataModelConfig" xsi:schemaLocation="http://www.objectiflune.com/connectschemas/Data ModelConfig http://www.objectiflune.com/connectschemas/DataModelConfig/1_0_0_ 3.xsd" xmlns:xsi="http://www.w3.
Keyboard shortcuts This topic gives an overview of keyboard shortcuts that can be used in the DataMapper. Keyboard shortcuts available in the Designer for menu items, script editors and the data model pane can also be used in the DataMapper; see "Keyboard shortcuts" on page 1009. Although some of the keyboard shortcuts are the same, this isn't a complete list of Windows keyboard shortcuts. Please refer to Windows documentation for a complete list of Windows keyboard shortcuts.
Key combination Function displays the corresponding menu.) The menu can then be browsed using the Enter key, arrow up and arrow down buttons.
Key combination Function Ctrl + Shift + S Save all Ctrl + Shift + W or Ctrl + Shift + F4 Close all Ctrl + F5 Revert Ctrl + F7 Next view Ctrl + Shift + F7 Previous view Ctrl + F8 Next perspective Ctrl + Shift + F8 Previous perspective Ctrl + F10 Save as Ctrl + F12 Send to Workflow / Package files F4 Ignore step/Reactivate step F6 Add an Extract step F7 Add a Goto step F8 Add a Condition step F9 Add a Repeat step Page 319
Key combination Function F10 Add an Extract field F11 Add an Action step F12 Add a Multiple Conditions step Alt + F12 Add a Case step (under a Multiple Conditions step) Home Go to the first step in the workflow End Go to the last step in the workflow Alt + V Validate records Shift + F10 or Ctrl + Shift + F10 Open context menu Viewer pane The following key combinations activate a function in the Viewer.
Key combination Function Ctrl + + Zoom in Ctrl + Shift + E Switch to Editor Ctrl + F6 Next editor (when there is more than one file open in the Workspace) Ctrl + Shift + F6 Previous editor (when there is more than one file open in the Workspace) Data Model pane Key combination Function PageUp Go to previous record PageDown Go to next record Alt + CR Property page Alt + PageDown Scroll down to the last field Alt + PageUp Scroll up to the first field Steps tab Key combination Function
Edit Script and Expression windows The following key combinations have a special function in the Expression and in the Edit Script windows (expanded view). Key combination Function Ctrl + space Content assist (auto-complete) Ctrl + A Select all Ctrl + D Duplicate line Ctrl + I Indent (Tab) Ctrl + J Line break Ctrl + L Go to line; a prompt opens to enter a line number.
File Menu l l l l l l l l l l New...: Opens the dialog to create a new data mapping configuration; see "Creating a new data mapping configuration" on page 227. Open: Opens a standard File Open dialog. This dialog can be used to open Templates and data mapping configurations. Open Recent: List the most recently opened Templates and configurations. Clicking on a template will open it in the Designer module, clicking on a data mapping configuration will open it in the DataMapper module.
Edit Menu l Undo: Undoes the previous action. l Redo: Redoes the last action that was undone. l l l l Cut Step: Removes the currently selected step and places it in the clipboard. If the step is a Repeat or a Condition, all steps under it are also placed in the clipboard. If there is already a step in the clipboard, it will be overwritten. Copy Step: Places a copy of the currently selected step in the clipboard. The same details as the Cut step applies.
l l l l l l Add Goto Step: Adds a Goto step that moves the selection pointer to the beginning of the data selection. For instance if an XML node is selected, the pointer moves to where that node is located. Add Condition Step: Adds a condition based on the current data selection. The "True" branch gets run when the text is found on the page. Other conditions are available in the step properties once it has been added.
l l Reset Perspective: Resets all toolbars and panes to the initial configuration of the module. Preferences: Click to open the Preferences dialog. Help Menu l l l Software Activation: Displays the Software Activation dialog. See Activating your license. Help Topics: Click to open this documentation. Contact Support: Click to open the Objectif Lune Contact Page in the default system Web browser. l About PlanetPress Connect Designer: Displays the software's About dialog.
Filter To find a certain table, group or field in a large Data Model, start typing characters in the Filter box. This immediately narrows down the list of displayed items to all tables, groups and fields whose name contains the characters that were typed. Note that the filtering is case-insensitive. Data Model toolbar buttons : Import Data Model: Click to browse to a file that contains a Data Model. This may l be: l A Data Model file (*.OL-datamodel). l A JSON file (*.json; see the note below).
l l l l : Synchronize Fields and Structure: Click to synchronize the Data Model fields and structure in the currently loaded template and data mapping configuration. If you click this button when working on the data mapping configuration, the Data Model gets updated to the one in the template. If you click it when working on the template, the Data Model gets updated to the one in the data mapping configuration. : Show the ExtraData field. Note that this field is not meant to be filled via an extraction.
Note Rename, Delete and Set Type are only available for Data Model fields or detail tables that are not filled via an extraction. Fields and detail tables that are filled via an Extract step are to be changed (renamed, deleted etc.) via the properties of that Extract step; see: "Editing fields" on page 293 and "Renaming a detail table" on page 331. l l Rename: Click to rename the selected table, field or group. Enter the new name and click OK to rename.
l l l l l l l l The column on the left displays the name of the field. The column on the right displays the current value of the extracted field based on the record shown in the Data Viewer, if an Extract step has an extraction for this field (see "Extracting data" on page 254). The icon to the left of the name indicates the data type of the field (see "Data types" on page 304). A field name with an asterisk to the right indicates that this field is required.
l l l l Previous Record: Go to the previous record in the data sample. This button is disabled if the first record is shown. Current Record: Displays the current record or table entry. Type a record number and press the Enter key to display that record. The number has to be within the number of available records in the data sample. Next Record: Go to the next record in the data sample. This button is disabled if the last record is shown. Last Record: Go to the last record in the data sample.
3. Click somewhere else on the Step Properties pane to update the Data Model. You will see the new name appear. Creating multiple detail tables Multiple detail tables are useful when more than one type of transactional data is present in the source data, for example purchases (items with a set price, quantity, item number) and services (with a price, frequency, contract end date, etc).
and you will have to rename the detail table created in each Extract step to pull the detail tables apart (see "Renaming a detail table" on page 331).
Nested detail tables Nested detail tables are used to extract transactional data that are relative to other data. They are created just like multiple detail tables, with two differences: l l For the tables to be actually nested, the Repeat step and its Extract step that extract the nested transactional data must be located within the Repeat step that extracts data to a detail table. In their name, the dot notation (record.services) must contain one extra level (record.services.charges).
Example An XML source file lists the services of a multi-service provider: Internet, Cable, Home Phone, Mobile. Each service in turn lists a number of "charges", being service prices and rebates, and a number of "details" such as movie rentals or long distance calls.
The services can be extracted to a detail table called record.services. The "charges" and "details" can be extracted to two nested detail tables.
The nested tables can be called record.services.charges and record.services.details.
Now one "charges" table and one "details" table are created for each row in the "services" table. The Data Viewer The Data Viewer is located in the middle on the upper half of the DataMapper screen. It displays the data source that is currently loaded in the DataMapper, specifically one record in that data. Where one record ends and the next starts is determined in the Data Source settings (see "Record boundaries" on page 253).
l l l Hide/Show datamap : Click to show or hide the icons to the left of the Data Viewer which displays how the steps affect the line. Hide/Show extracted data : Click to show or hide the extraction selections indicating that data is extracted. This simplifies making data selections in the same areas and is useful to display the original data. Lock/Unlock extracted data : Click to lock existing extraction selections so they cannot be moved or resized.
Messages pane The Messages pane is shared between the DataMapper and Designer modules and displays any warnings and errors from the data mapping configuration or template. At the top of the Message pane are control buttons: l Export Log: Click to open a Save As dialog where the log file (.log) can be saved on disk. l Clear Log Viewer: Click to remove all entries in the log viewer. l Filters: Displays the Log filter (see "Log filter" below).
Settings pane Settings for the data source and a list of Data Samples and JavaScript files used in the current data mapping configuration, can be found on the Settings tab at the left. The available options depend on the type of data sample that is loaded. The Input Data settings (especially Delimiters) and Boundaries are essential to obtain the data and eventually, the output that you need. For more explanation, see "Data source settings" on page 250.
l l Ignore unparseable lines: Ignores any line that does not correspond to the settings above. Skip empty lines: Ignore any line that has no content. Note that spaces are considered content. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text.
average character in the font. l l l l Line spacing: Determines the spacing between lines of text. The default value is 1, meaning the space between lines must be equal to at least the average character height. Paragraph spacing: Determines the spacing between paragraphs. The default value is 1.5, meaning the space between paragraphs must be equal to at least 1.5 times the average character height to start a new paragraph. Magic number: Determines the tolerance factor for all of the above values.
l l l Encoding: Defines what encoding is used to read the Data Source ( US-ASCII, ISO8859-1, UTF-8, UTF-16, UTF-16BE or UTF-16LE ). Sort on: Allows to select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the sorting column has numbers, it will be sorted as a text. With a Custom Query, this option is not available. Skip empty lines: Ignore any row that has no content, e.g. only nulls or empty strings.
l On text: Triggers a new page in the Data Sample when a specific string is found in a certain location. l Word to find: Compares the text value with the value in the data source. l Match case: Activates a case sensitive text comparison. l l l Location: Choose Selected area or Entire width to use the value of the current data selection as the text value. Left/Right: Use the spin buttons to set the start and stop columns to the current data selection (Selected area) in the record.
l Any other curly brackets that are not part of the JavaScript code must be escaped with a backslash. Single line comments (//...) in the code are not supported. Note that since the XPath is a string, the return value of the JavaScript statement will be interpreted as a string. l Note Currently, XPaths that select elements based on an attribute, attribute value, node value, node counter or node index are not supported.
l Trigger: Defines the type of rule that controls when a boundary is set, creating a new record. l Record(s) per page: Defines a fixed number of lines in the file that go in each record. l l On change: Defines a new record when a specific field (Field name) has a new value. l l l Records: The number of records (lines, rows) to put in each record. Field name: Displays the fields in the top line. The boundaries are set on the selected field name.
l On text: Defines a boundary on a specific text comparison. l l l l l Start coordinates (x,y): Defines the left and top coordinates of the data selection to compare with the text value. Stop coordinates (x,y): Defines the right and bottom coordinates. Use Selection: Select an area in the Data Viewer and click the Use selection button to set the start and stop coordinates to the current data selection. Note: In a PDF file, all coordinates are in millimeters.
l On delimiter: Defines a boundary on a static number of pages. l l Occurrences: The number of times that the delimiter is encountered before fixing the boundary. For example, if you know that your documents always have four pages delimited by the FF character, you can set the boundaries after every four delimiters. On text: Defines a boundary on a specific text comparison.
l l l Use selected text button: copies the text in the current selection as the one to compare to it. Match case: Makes the text comparison case sensitive. On script: Defines the boundaries using a custom JavaScript. For more information see "Setting boundaries using JavaScript" on page 401. XML file boundaries The delimiter for an XML file is a node. The Boundaries determine how many of those nodes go in one record.
A number of buttons let you manage the Data Samples. In addition to using the buttons listed below, you can right-click a file to bring up the context menu, which offers the same options plus the Copy and Paste options. Tip Data samples can be copied and pasted to and from the Settings pane using Windows File Explorer. l l l l l Add : Add a new Data Sample from an external data source. The new Data Sample will need to be of the same data type as the current one.
l l Current Locale Settings: Shows dates and times as formatted by Windows using the current Locale of the system on which Connect runs. All values are shown as a date including a time. ISO 8601 (UTC): Uses the ISO 8601 (UTC) format to display dates and times. All values are shown as a date including a time, taking the time zone into account. Note that when no time was specified with a date in the original file, the default time (12.00 AM) is used and converted; this may influence the displayed date.
l Negative Sign Before : A negative sign will be displayed before any negative value. l Decimal Separator : Set the decimal separator for a numerical value. l Thousand Separator : Set the thousand separator for a numerical value. l Currency Sign : Set the currency sign for a currency value. 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).
Using variables and properties in an SQL query When you use variables and properties in an SQL query, the selection will be dynamically adjusted each time the data mapping configuration is actually used in a Workflow process. To create a dynamic SQL query: l l The query must start with = Any variable or property must be enclosed in curly brackets: { ... }. This effectively inserts a JavaScript statement in the query. Note that all other curly brackets must be escaped with a backslash.
Example = SELECT {automation.variables.FieldList} FROM {automation.jobInfo.JobInfo9} If the Workflow variable defined as FieldList contains the value "id,name" and Job Info 9 contains the value "MyTable", then this custom query, once parsed, yields the following SQL statement: SELECT id,name FROM MyTable which is then executed. Steps pane The Steps tab displays the data mapping workflow: the process that prepares and extracts data.
You can also click on the Preprocessor step to select all the steps in the workflow to show a complete map of all the extracted data. Window controls The following controls appear at the top of the Steps pane: l Zoom In (CTRL +) l Zoom Out (CTRL -) : Click to zoom in by increments of 10% : Click to zoom out by increments of 10% Contextual menu You can access the contextual menu using a right-click anywhere inside the Steps pane. l Add a Step: Adds a step to the process.
Step properties pane The Step Properties pane is used to adjust the properties of each Step in the process (see "Steps" on page 274). The pane is divided in a few subsections depending on the Step and the data type. It always contains a subsection to name and document the selected Step. Other subsections allow you to edit or delete fields that belong to the Step (see "Fields" on page 291) or change the expected data format (see "Data Format" on page 366), for example.
Name: The name of the step. This name will be displayed on top of the step's icon in the Steps pane. Comments: The text entered here will be displayed in the tooltip that appears when hovering over the step in the Steps pane. Fixed Automation Properties The Fixed automation properties subsection lists all the fixed properties available from PlanetPress Workflow. These properties are equivalent to data available within the PlanetPress Workflow process.
PlanetPress Workflow. To access this property inside of any JavaScript code within the data mapping configuration, use automation.properties.ProcessName. In scripts, fixed automation properties are retrieved via the automation object (see "Objects" on page 406), for example automation.jobInfo.JobInfo9 or automation.properties.OriginalFilename.
{MyLocalVar} use only MyLocalVar, and for %{global.MyGlobalVar} use MyGlobalVar. If a global and a local variable have the same name ( %{myvar} and %{global.myvar} ), the local variable's value is used and the global one is ignored. To access a Workflow variable inside of any JavaScript code within the data mapping configuration, use automation.variables.variablename . l l Type: The data type of the property. For more information see "Data types" on page 304.
Preprocessor definition l Expression: Enter the JavaScript code to be performed on the data file. See "DataMapper Scripts API" on page 396. Extract step properties The Extract step takes information from the data source and places it in the record set that is the result of the extraction workflow. For more information see "Extract step" on page 276 and "Extracting data" on page 254. Description This subsection is collapsed by default in the interface, to give more screen space to other important parts.
to make further settings for that field. Tip To change the name of a field quickly, right-click it in the Data Model and select Rename. l l Add Unique ID to extraction field: Check to add a unique numerical set of characters to the end of the extracted value. This ensures no two values are identical in this field in the record set. Mode: Determines the origin of the data. Fields always belong to an Extract step, but they don't necessarily contain extracted data.
l Properties: The value of the property selected below will be the value of the selected field. l l l Property: This drop-down lists all the currently defined properties (including system properties). Custom properties can be defined in the Preprocessor step; see "Preprocessor step" on page 274. For an explanation of the objects to which the properties belong, see "DataMapper Scripts API" on page 396.
A Post function script operates directly on the extracted data, and its results replace the extracted data. For example, the Post function script replace("-", ""); would replace the first dash character that occurs inside the extracted string. l Use JavaScript Editor: Click to display the Script Editor dialog. l Trim: Select to trim empty characters at the beginning or the end of the field.
the data format that the DataMapper expects matches the actual format of the data in the data source; see "Data Format" on the facing page. l Split: l l l Split lines: Separate a multi-line selection into individual fields . Join lines: Join the lines in the selection with the Concatenation string defined below. Concatenation string: The (HTML) string used to concatenate lines when they are joined.
l XPath: The path to the XML field that is extracted. l Use selection: Click to use the value of the current data selection for the extraction. Note If the selection contains multiple lines, only the first line is selected. l Post Function: Enter a JavaScript expression to be run after the extraction. For example replace("-","") would replace a single dash character inside the extracted string. l l Use JavaScript Editor: Click to display the Script Editor dialog.
l l Date Language : Set the date language for a date value (ex: If English is selected, the term May will be identified as the month of May). Treat empty as 0 : A numerical empty value is treated as a 0 value. Order and rename fields dialog The Order and rename fields dialog displays the extracted fields in the currently selected Extract step. To open it, first select an Extract step on the Steps pane.
Note The order of fields in an extraction step isn't necessarily the same as the order of those fields in the Data Model; see "Ordering and grouping fields in the Data Model" on page 288. Action step properties The Action step can run multiple specific actions one after the other in order; see "Action step" on page 283 for more information. The properties of an Action step become visible in the Step properties pane when the Action step is selected on the Steps pane.
fields are stored as usual. If no fields were extracted prior to encountering the Action step, then no trace of the record is saved in the database at run time. l Stop data mapping: the extraction workflow stops processing the data. If fields of the current record were already extracted prior to encountering the Action step, then those fields are stored as usual, but the rest of the data is skipped.
l JavaScript : The result of the JavaScript Expression written below the drop-down will be the value of the extracted field. If the expression contains multiple lines, the last value attribution (variable = "value";) will be the value. See "DataMapper Scripts API" on page 396. l l l l Expression: The JavaScript expression to run. Use JavaScript Editor: Click to display the Edit Script dialog (see "Using scripts in the DataMapper" on page 399 and "DataMapper Scripts API" on page 396).
CSV and Database Files l Property: Displays a list of record properties set in the Preprocessor step (see "Preprocessor step" on page 274). l Type: Displays the type of the property. Read only field. l Based on: Determines the origin of the data. l Location: The contents of the data selection set below will be the value of the extracted field. The data selection settings are different depending on the data sample type.
l Use selection: Click to use the value of the current data selection for the extraction. Note If the selection contains multiple lines, only the first line is selected. l Data Format: Data format settings tell the DataMapper how certain types of data are formatted in the data source. Make sure that this format matches the actual format of the data in the data source. l Negative Sign Before : A negative sign will be displayed before any negative value.
Note If the selection contains multiple lines, only the first line is selected. l l Trim: Select to trim empty characters at the beginning or the end of the field JavaScript : The result of the JavaScript Expression written below the drop-down will be the value of the extracted field. If the expression contains multiple lines, the last value attribution (variable = "value";) will be the value. See "DataMapper Scripts API" on page 396. l l l l Expression: The JavaScript expression to run.
l Thousand Separator : Set the thousand separator for a numerical value. 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. Run JavaScript Running a JavaScript expression offers many possibilities.
Name: The name of the step. This name will be displayed on top of the step's icon in the Steps pane. Comments: The text entered here will be displayed in the tooltip that appears when hovering over the step in the Steps pane. Repeat Definition l Repeat type: l l l l While statement is true: The loop executes while the statement below is true. The statement is evaluated before the loop so the loop may not run at all. Until statement is true: The loop executes until the statement below is true.
[@lastname="{automation.jobInfo.JobInfo1}"]. In order to use JavaScript: l The XPath must start with = l The JavaScript statement must be enclosed in curly brackets: { ... } l l All other curly brackets that are not part of the JavaScript code must be escaped with a backslash. Single line comments (//...) in the code are not supported. Note that since the XPath is a string, the return value of the JavaScript statement will be interpreted as a string.
Text and PDF Files Note The Repeat Step expects lines of text in a PDF file to be horizontal (regardless of the orientation of the page). Vertical text will cause an error. l Based On: l Position: The data in the specified position for the comparison. l l l l l l l l Top offset: The vertical offset from the current pointer location in the Data Sample (Viewer). Height: The height of the selection box. Use Selection: Click to use the value of the current data selection for the extraction.
l l l l l Data Property: The value of a data-level property set in the Preprocessor step (see "Preprocessor step" on page 274). Record Property: One of the local variables that you can create and that are reset for each document as opposed to data variables that are global because they are initialized only once at the beginning of each job. Automation Property: The current value of a Document-level property set in the Preprocessor step (see "Preprocessor step" on page 274).
l l l l l l l l l l Value: The text value to use in the comparison. Use selected text: Uses the text in the current data selection as the Value. If multiple lines or elements are selected, only the first one is used. Field: The Extracted Record field to use in the comparison. JavaScript : The result of a JavaScript Expression. l l Trim: Select to trim empty characters at the beginning or the end of the field. Field: The contents of a specific field in the Extracted Record.
l Operators: l l l l l l is equal to: The two specified value are identical for the condition to be True. contains: The first specified value contains the second one for the condition to be True. is less than: The first specified value is smaller, numerically, than the second value for the condition to be True. is greater than: The first specified value is larger, numerically, than the second value for the condition to be True. is empty: The first specified value is empty.
l l l l l Data Property: The value of a data-level property set in the Preprocessor step. Record Property: One of the local variables that you can create and that are reset for each document as opposed to data variables that are global because they are initialized only once at the beginning of each job. Automation Property: The current value of a Document-level property set in the Preprocessor step.
Description This subsection is collapsed by default in the interface, to give more screen space to other important parts. Name: The name of the step. This name will be displayed on top of the step's icon in the Steps pane. Comments: The text entered here will be displayed in the tooltip that appears when hovering over the step in the Steps pane.
l Based On: l Position: The data in the specified position for the comparison. l l Right (Txt and PDF only): The end position for the data selection. l Height (Txt and PDF only): The height of the selection box. l l l l l l l l Top offset: The vertical offset from the current pointer location in the Data Sample (Viewer). Use Selection: Click to use the value of the current data selection for the extraction. Trim: Select to trim empty characters at the beginning or the end of the field.
l l l Record Property: One of the local variables that you can create and that are reset for each document as opposed to data variables that are global because they are initialized only once at the beginning of each job. Automation Property: The current value of a Document-level property set in the Preprocessor step (see "Preprocessor step" on page 274). Extractor Property: The value of an internal extractor variable: l l l Counter: The value of the current counter iteration in a Repeat step.
Name: The name of the step. This name will be displayed on top of the step's icon in the Steps pane. Comments: The text entered here will be displayed in the tooltip that appears when hovering over the step in the Steps pane. Condition Left operand, Right operand The Left and right operand can be Based on: l Position: The data in the specified position for the comparison. l l Right (Txt and PDF only): The end position for the data selection.
l l l l l l l Expression: The JavaScript line that is evaluated. Note that the last value attribution to a variable is the one used as a result of the expression. See also: "DataMapper Scripts API" on page 396. Use JavaScript Editor: Click to display the Edit Script dialog (see "Using scripts in the DataMapper" on page 399). Use selected text: Inserts the text in the current data selection in the JavaScript Expression. If multiple lines or elements are selected, only the first one is used.
l l l l l l is equal to: The two specified value are identical for the condition to be True. contains: The first specified value contains the second one for the condition to be True. is less than: The first specified value is smaller, numerically, than the second value for the condition to be True. is greater than: The first specified value is larger, numerically, than the second value for the condition to be True. is empty: The first specified value is empty.
Text file l Target Type: Defines the type of jump. l Line: Jumps a certain number of lines or to a specific line. l l l l Current Position: The Goto begins at the current cursor position. l Top of record: The Goto begins at line 1 of the source record. Move by: Enter the number of lines or pages to jump. Page: Jumps between pages or to a specific page.
l Left: The starting column, inclusively. l Right: The end column, inclusively. l l l l Use selection: Click while a selection is made in the Data Viewer to automatically set the left and right values to the left and right edges of the selection. Expression: Enter the text or Regex expression to look for on the page. Use selection: Click while a selection is made in the Data Viewer to copy the contents of the first line of the selection into the Expression box.
l Left: The starting column, inclusively. l Right: The end column, inclusively. l l Use selection: Click while a selection is made in the Data Viewer to automatically set the left and right values to the left and right edges of the selection. Next occurrence of: Jumps to the next occurrence of specific text or a text pattern, either anywhere on the line or in specific columns.
XML File l Destination (XML files): Defines what type of jump to make: l l l l l Sibling element: Jumps the number of siblings (nodes at the same level) defined in the Move byoption. Sibling element with same name: Jumps the number of same name siblings (nodes at the same level of which the node is the same name) defined in the Move byoption. Element, from top of record: Jumps to the specified node. The XPATH in the Absolute XPATHoption starts from the root node defined by /.
Postprocessor The Postprocessor subsection defines what postprocessors run on the Data Sample at the end of the data mapping workflow. Each Postprocessor runs in turn, using the result of the previous one as an input. l Name: The name to identify the Postprocessor. l Type: The type of Postprocessor. Currently there is a single type available. l JavaScript: Runs a JavaScript Expression to modify the Data Sample. See "DataMapper Scripts API" on page 396.
Open: Displays the Open dialog to open an existing data mapping configuration. l l Save: Saves the current data mapping configuration. If the configuration has never been saved, the Save As... dialog is displayed. Step manipulation Note All steps except the Action step require an active data selection in the Data Viewer (see "Selecting data" on page 258 and "The Data Viewer" on page 338). l l l l l l l Add Extract Step: Adds an Extract Step with one or more extract fields.
l l l l l Cut Step: Removes the currently selected step and places it in the clipboard. If the step is a Repeat or a Condition, all steps under it are also placed in the clipboard. If there is already a step in the clipboard, it will be overwritten. Copy Step: Places a copy of the currently selected step in the clipboard. The same details as the Cut step applies. Paste Step: Takes the step or steps in the clipboard and places them after the currently selected step.
To go back from the Welcome Screen to the template or data mapping configuration that you were working on: l Close the Welcome Screen by clicking the cross next to the text 'Welcome' at the top. Contents l Resources l l l Documentation: Opens this documentation. Training: Opens Learn: the Objectif Lune e-Learning Center, with its tutorials, forum, and how-tos. l Support: Opens the support page in the PlanetPress Connect website.
l New DataMapper Configuration: Lets you build a data mapping configuration from a file or with a wizard; see "Data mapping configurations" on page 226. DataMapper Scripts API This page describes the different features available in scripts created inside DataMapper. See "Using scripts in the DataMapper" on page 399.
Name Description Available in scripts of type "record" on page 427 The current record in the main data set. Extract, Condition, Repeat and Multiple Conditions steps "region" on page 428 An object that defines a subsection of the input data. Boundaries "sourceRecord" on page 431 An object containing properties specific to the current source record being processed.
Name Description page 438 alphanumeric, lower case characters and four hyphens (format: 84-4-4-12). Example: 123e4567-e89b-12d3-a456-426655440000. "createHTTPRequest ()" on page 438 Creates a new HTTP Request Object. createTmpFile() Creates a file with a unique name in the temporary work folder and returns a file object. deleteFile() Deletes a file. execute() Calls an external program and waits for it to end. newByteArray() Returns a new byte array. newCharArray() Returns a character array.
Using scripts in the DataMapper In the DataMapper every part of the extraction process can be customized using scripts. A script can be used to set boundaries for a data source (see "Setting boundaries using JavaScript" on page 401). The script determines where a new record starts. Scripts can also be used in different steps in the extraction workflow.
Keyboard shortcuts for the script editor are listed in the following topic: "Keyboard shortcuts" on page 1009. Syntax rules In the DataMapper, all scripts must be written in JavaScript, following JavaScript syntax rules. For example, each statement should end with ; and the keywords that can be used, such as var to declare a variable, are JavaScript keywords. There are countless tutorials available on the Internet to familiarize yourself with the JavaScript syntax.
Setting boundaries using JavaScript As soon as you select the On Script option as the trigger for establishing record boundaries (see "Record boundaries" on page 253), you are instructing the DataMapper to read the source file sequentially and to trigger an event each and every time it hits a delimiter. (What a delimiter is, depends on the source data and the settings for that data; see "Input data settings (Delimiters)" on page 251).
l Compare the contents of one region with another. l Etc. To access this data in the script, use the get() function of the boundaries object. This function expects different parameters depending on the type of source file; see "Example" on page 410. Getting access to other data Data that is not passed with the event, but that is necessary to define the record boundaries, can be stored in the boundaries object using the setVariable function (see "boundaries" on page 408 and "Example" on page 413).
Note The first line is just the header with the names of the CSV columns. The data is already sorted per year, per artist, and per album. Your goal is to examine two values in each CSV record and to act when either changes. The DataMapper GUI allows you to specify a On Change trigger, but you can only specify a single field. So for instance, if you were to set the record boundary when the "Released" field changes, you'd get the first four lines together inside a single record.
simply the column name. The region is passed as a parameter to the get() method, which reads its contents and converts it into an array of strings (because any region, even a CSV field, may contain several lines). l l l To "remember" the values that were processed the last time the event was triggered, we use variables that remain available in between events. Note that these variables are specific to the Boundary context and not available in any other scripting context in the DataMapper.
The purpose of the script, again, is to set the record boundary when EITHER the year OR the artist changes. The script would look like this: /* Read the values of both columns we want to check */ var zeBand = boundaries.get(region.createRegion(1,1,30,1)); var zeYear = boundaries.get(region.createRegion(61,1,65,1)); /* Check that at least one of our variables holding previous values have been initialized already, before attempting to compare the values */ if (boundaries.
since PDF pages do not have a grid concept of lines and columns, the above parameters would instead be specified in millimeters relative to the upper left corner of each page. So for instance, to create a region for the Year, the code might look like this: region.createRegion(190,20,210,25) which would create a region located near the upper right corner of the page.
Property Description properties Returns a ScriptableAutomation object containing additional information (file name, process name and task ID) from PlanetPress Workflow. variables Returns a ScriptableAutomation object containing the list of local and global variables defined by the user in PlanetPress Workflow. Note that there is no way to distinguish local variables from global ones (local variables take precedence over global variables).
automation.properties.OriginalFilename; To access Workflow variables (declared in the "Preprocessor step" on page 274 properties): automation.variables.Same_as_workflow; boundaries Returns a boundaries object encapsulating properties and methods allowing to define the boundaries of each document in the job. This object is available when triggering document boundaries On script. Properties The following table lists the properties of the boundaries object.
Method Description Script type getVariable () Retrieves a value of a variable stored in the boundaries object. Boundaries set() Sets a new record boundary. (See: "Record boundaries" on page 253.) Boundaries setVariable () Sets a boundaries variable to the specified value, automatically creating the variable if it doesn't exist yet. Boundaries find() Method of the boundaries object that finds a string in a region of the data source file.
The in_Region region can be created prior to the call to find() with the region.createRegion() method. It depends on the type of data source how a region is defined; see "Example" on page 430. When used to search through a Text file, the find() method returns a different region object (see "region" on page 428) whose range property is adjusted to point to the exact physical location where the match was found. This will always be a subset of the in_Region.range property.
getVariable() Method that retrieves the value currently stored in a variable. Note Boundary variables are carried over from one iteration of the Boundaries script to the next, while native JavaScript variables are not. getVariable(varName) varName String name of the variable from which the value is to be retrieved. If the variable does not exist, the value null is returned.
Example This script sets a boundary when the text TOTAL is found on the current page in a PDF file. The number of delimiters is set to 1, so the boundary is set on the next delimiter, which is the start of the next page. if (boundaries.find("TOTAL", region.createRegion (10,10,215,279)).found) { boundaries.
Note Boundary variables are carried over from one iteration of the Boundaries script to the next, while native JavaScript variables are not. setVariable(varName, varValue) Sets variable varName to value varValue. varName String name of the variable of which the value is to be set. varValue Object; value to which the variable has to be set. Example This script examines a specific region and stores its contents in a variable in the boundaries. var addressRegion = region.
Property Description Return type the preprocessor step (see Preprocessor Step Properties for details). the Preprocessor step with the data scope (i.e. statically set at the start of the job). Methods The following table lists the methods of the data object. Method Description Script type File type "Examples" on page 416 Extracts the text value from a rectangular region. Extract, Condition, Repeat, and Action steps All "extractMeta ()" on page 421 Extracts the value of a metadata field.
extract() Extracts the text value from selected data: a node path, column, or rectangular region, depending on the type of data source. This method always returns a String. extract(left, right, verticalOffset, regionHeight, separator) Extracts a value from a position in a text file. Coordinates are expressed as characters (horizontally) or lines (vertically). left Number that represents the distance, measured in characters, from the left edge of the page to the left edge of the rectangular region.
is a line break in HTML and Designer templates are actually HTML files. l Setting the regionHeight to 0 makes it possible to extract a variable number of lines at the end of a record. Examples Example 1: The script command data.extract(1,22,8,1,"
"); means that the left position of the extracted information is located at character 1, the right position at character 22, the offset position is 8 (since the line number is 9) and the regionHeight is 1 (to select only 1 line).
Example 2: The script command data.extract(1,22,9,6,"
"); means that the left position of the extracted information is located at 1, the right position at 22, the offset position is 9 (since the first line number is 10) and the regionHeight is 6 (6 lines are selected). Finally, the "
" string is used for concatenation. extract(xPath) Extracts the text value of the specified node in an XML file. xPath String that can be relative to the current location or absolute from the start of the record.
Example The script command data.extract('./CUSTOMER/FirstName'); means that the extraction is made on the FirstName node under Customer. extract(columnName, rowOffset) Extracts the text value from the specified column and row. columnName String that represents the column name. rowOffset Number that represents the row index (zero-based), relative to the current position. To extract the current row, specify 0 as the rowOffset.
Example The script command data.extract('ID',0); means that the extraction is made on the ID column in the first row. extract(left, right, verticalOffset, lineHeight, separator) Extracts the text value from a rectangular region in a PDF file. All coordinates are expressed in millimeters. left Double that represents the distance from the left edge of the page to the left edge of the rectangular region.
Double that represents the distance from the left edge of the page to the right edge of the rectangular region. verticalOffset Double that represents the distance from the current vertical position. lineHeight Double that represents the total height of the region. separator String inserted between all lines returned from the region. If you don't want anything to be inserted between the lines, specify an empty string (""). Tip "
" is a very handy string to use as a separator.
extractMeta() Method that extracts the value of a metadata field on a certain level in a PDF/VT. This method always return a String. extractMeta(levelName String, propertyName String) levelName String, specifying the PDF/VT's level. Case sensitive. propertyName String, specifying the metadata field. fieldExists() Method of the data object that returns true if a certain metadata field, column or node exists. (See "data" on page 413.
fieldExists(levelName, propertyName) This method returns true if the given metadata field exists at the given level in a PDF file. levelName String that specifies the metadata field. propertyName String that specifies the level. fieldExists(fieldName) This method returns true if the specified column exists in the current record in a CSV file. fieldName String that represents a field name (column) in a CSV file.
Partial matches are not allowed. The entire string must be found between the two constraint parameters. The data.find() function only works on the current page. If the record contains several pages, you must create a loop that will perform a jump from one page to another to do a find() on each page. Note Calling this method does not move the current position to the location where the string was found.
Left=26,76, Top=149.77, Right=40,700001, Bottom=154.840302 These values represent the size of the rectangle that encloses the string in full, in millimeters relative to the upper left corner of the current page. findRegExp() Finds the first occurrence of a string that matches the given regular expression pattern, starting from the current position.
matching can be enabled by specifying the UNICODE_CASE flag (u) in conjunction with this flag. s: Enables dotall mode. In dotall mode, the expression . matches any character, including a line terminator. By default this expression does not match line terminators. L: Enables literal parsing of the pattern. When this flag is specified, then the input string that specifies the pattern is treated as a sequence of literal characters.
Examples data.findRegExp(/\d{3}-[A-Z]{3}/,"gi",50,100); or data.findRegExp("\\d{3}-[A-Z]{3}","gi",50,100);}} Both expressions would match the following strings: 001-ABC, 678-xYz. Note how in the second version, where the regular expression is specified as a string, some characters have to be escaped with an additional backslash, which is standard in JavaScript. db Object that allows to connect to a database. Methods The following table describes the methods of the db object.
user String that represents the user name for authentication. password String that represents the password for authentication. logger Global object that allows logging messages such as error, warning or informational messages. Methods The following table describes the methods of the logger object.
Property Return Type index The one-based index of this record, or zero if no data is available. tables The details table that belong to this record. You can access a specific table using a numeric index or the table name. Example See this How-to for an example of how the current record index, and/or the total number of records in the record set, can be displayed in a document: How to get the record index and count. region The region object defines a sub-section of the input data.
Property/method Description Return Type range Read-only object containing the physical coordinates of the region. Physical location of the region: x1 (left), y1 (top), x2 (right), y2 (bottom), expressed in characters for a text file or in millimeters for a PDF file. For a CSV file, it is the name of the column that defines the region. createRegion() Creates a region by setting the physical coordinates of the region object. A region that has the specified coordinates.
Example The following script attempts to match ((n,m)) or ((n)) against any of the strings in the specified region and if it does, a document boundary is set. var myRegion = region.createRegion(170,25,210,35); var regionStrings=boundaries.get(myRegion); if (regionStrings) { for (var i=0;i
l l For a PDF file, the range() method contains the physical coordinates of the region: x1 (left), y1 (top), x2 (right), y2 (bottom), expressed in millimeters. For a CSV file, the range contains the name of the column that defines the region. sourceRecord Returns a sourceRecord object containing properties specific to the current source record being processed. Properties sourceRecord.properties.
1. Enter the property's name. 2. Select Each record from the Scope drop-down list. 3. Select a Type for the Property. steps Returns a steps object encapsulating properties and methods pertaining to the current DataMapper process. This object is available in an Extract, Condition, Repeat or Multiple Conditions step script. Methods and properties The following table lists the methods and properties of the steps object.
Method Description File type currentPageWidth The width of the current page in millimeters. PDF moveTo() Moves the pointer in the source data file to another position. All moveToNext() Moves the position of the pointer in the source data file to the next line, row or node. The behavior and arguments are different for each emulation type: text, PDF, tabular (CSV), or XML. All totalPages An integer value representing the total number of pages inside the current record.
Example In this example, an extraction area is assigned to the variable curLine each time the current page value has changed. curPage = steps.currentPage; for(i=0;i<100;i++) { if(steps.currentPage > curPage) { let curLine = data.extract(51, 88, 0, 1, "").trim(); curPage++; } } moveTo() Moves the position of the pointer in the source data file. This is a method of the steps object (see "steps" on page 432).
With the scope set to 2, verticalPosition is not used. The position is moved to the next line after the current position that contains any text. Example The following line of code moves the current position in a text file 14 lines down from the current vertical position (steps.currentPosition) of the pointer in the data, as long as it is on the same page. if(steps.currentPage > curPage) { steps.moveTo(0, steps.
String that defines a node in the XML file. Tip The XML elements drop-down (on the Settings pane, under Input Data) lists xPaths defining nodes in the current XML file. moveTo(row) Moves the current position in a CSV file to the given row number. row Number that represents the index of the row, relative to the top of the record. moveToNext() Moves the position of the pointer in the source data file to the next line, row or node.
steps.moveToNext(2); XML scope Number that may be set to: l l 0 or steps.MOVENODE: the current position is set to the next parent node in the XML hierarchy. 1 or steps.MOVESIBLING: the current position is set to the next sibling node in the XML hierarchy. moveToNext(left, right) Moves the current position in a PDF file to the next line that contains any text, the search for text being contained within the left and right parameters, expressed in millimeters.
Example This script copies the file test.txt from c:\Content into the c:\out folder. copyFile("c:\Content\test.txt","c:\out\") createGUID() This function returns a unique 36-character string consisting of 32 alphanumeric, lower case characters and four hyphens. Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (8-4-4-4-12 characters). Example: 123e4567-e89b-12d3-a456-426655440000.
Supported properties l response l status l statusText l timeout (ms). Default: 1 minute. Supported methods create() l l open(String method, String url, String user, String password) open(String verb, String url, String userName, String password, String[] headers, String[] headervalues, String requestBody) l send() l send(String requestBody) Creates a new instance of ScriptableHTTPRequest. Opens a HTTP request. Note If you don't use a user name and password, pass empty strings: request.
getResponseBody() Returns the full response body of the last HTTP request. setRequestBody(String requestBody) Sets the HTTP request body (for POST and PUT). getPassword() Gets the password for HTPP basic authentication setPassword(String password) Sets the password for HTPP basic authentication getTimeout() Gets the time to wait for the server's response setTimeout(int timeout) Sets the time (in ms.) to wait for the server's response.
try{ // Open a reader var reader = openTextReader(data.filename); // Create a temporary file var tmpFile = createTmpFile(); // Open a writer on the temporary file var writer = openTextWriter(tmpFile.getPath()); try{ var line = null; // Current line /* read line by line and readLine will return null at the e the file */ while( (line = reader.readLine()) != null ){ // Edit the line line = line.toUpperCase(); // Write the result in the temporary file writer.write(line); // add a new line writer.
Examples 1. Deleting a file in a local folder: deleteFile("c:\Content\test.txt"); 2. Deleting the sample data file used in the DataMapper: deleteFile(data.filename); execute() Function that calls an external program and waits for it to end. execute(command) Calls an external program and waits for it to end. command String that specifies the path and file name of the program to execute. newByteArray() Function that returns a new byte array.
newDoubleArray() Function that returns a new double array. newDoubleArray(size) Returns a new Double array of the specified number of elements. size Integer that represents the number of elements in the new array. newFloatArray() Function that returns a new float array. newFloatArray(size) Returns a new Float array of the specified number of elements. size Integer that represents the number of elements in the new array. newIntArray() Function that returns a new array of Integers.
Integer that represents the number of elements in the new array. newStringArray() Function that returns a new string array. newStringArray(size) Returns a new String array of the specified number of elements. size Integer that represents the number of elements in the new array. openBinaryReader() Function that opens a file as a binary file for reading purposes. The function returns a DataInputStream (see DataInputStream).
end. openTextReader(filename,encoding) filename String that represents the name of the file to open. encoding String that specifies the encoding of the file to read (UTF-8, ISO-8859-1, etc.). Example In the following example, the openTextReader() function is used to open the actual data sample file in the DataMapper for reading. var var var var fileIn = openTextReader(data.filename); tmp = createTmpFile(); fileOut = openTextWriter(tmp.getPath()); line; while((line = fileIn.readLine())!=null){ fileOut.
Property/method Description close() Closes the stream and releases resources. open(inStream, inEncoding) Creates a reader from an input stream. Parameters: open(inFileName, inEncoding) parseCharset (inEncoding) l inStream: the input stream to read l inEncoding: the encoding to use when reading the file Creates a reader on the specified file. Parameters: l inFilename: the path of the file to read l inEncoding: the encoding to use when reading the file Returns a character set (Charset).
openTextWriter(filename, encoding, append) filename String that represents the name of the file to open. encoding String specifying the encoding to use (UTF-8, ISO-8859-1, etc.).. append Boolean parameter that specifies whether the file pointer should initially be positioned at the end of the existing file (append mode) or at the beginning of the file (overwrite mode).
Property/method Description close() Close the stream. newLine() Creates a new line in the file. open(filename) Creates a new writer on a file to write at the beginning of the file. Parameters: l open(inFilename, inEncoding, append) filename: the path of the file to open Creates a new writer on a file.
The Designer The Designer is a WYSIWYG (what you see is what you get) editor that lets you create templates for various output channels: Print, Email and Web. A template may contain designs for multiple output channels: a letter intended for print and an e-mail variant of the same message, for example. Content, like the body of the message or letter, can be shared across these contexts. Templates are personalized using scripts and variable data extracted via the DataMapper.
page 451. 2. Fill the template Add text, images and other elements to the template and style them. See "Content elements" on page 628 and "Styling and formatting" on page 741. 3. Personalize the content Personalize the content using variable data. See "Personalizing content" on page 786. 4. Generate output Adjust the settings, test the template and generate output: letters, emails, and/or web pages. See "Generating output" on page 1408.
l "Print" on page 474. This topic helps you design and fill sections in the Print context. l "Email" on page 515. This topics helps you design an email template. l "Web" on page 540. This topic helps you design a web page. "Sections" on page 470. Sections in one context are designed for the same output channel. "Content elements" on page 628. Elements make up the biggest part of the content of each design. "Snippets" on page 737.
There are Wizards for the three types of output channels, or contexts as they are called in the Designer: Print, Email and Web. See: l "Creating an Email template with a Wizard" on page 520 l "Creating a Print template with a Wizard" on page 477 l "Creating a Web template with a Wizard" on page 541 Tip The quickest way to create a Print template based on a PDF file is to right-click the PDF file in the Windows Explorer and select Enhance with Connect.
Warning A template created in an older version of the software can be opened in a newer version. However, opening and saving it in a newer version of the software will convert the template to the newest file format. The converted template can't be opened in older versions of the software. Opening a package file Templates can also be stored in a package file (see "Creating package files" on page 457). To open a package file, switch the file type to Package files (*.OL-package) in the Open File dialog.
Saving older templates Saving a template in a newer version of the software will convert the template to the newest file format. This makes it unreadable to older versions of the software. The warning message that is displayed in this case can be disabled. To re-enable this message (and all other warning dialogs), go to Window > Preferences > General, and click the Reset All Warning Dialogs button at the bottom.
Backup files have the same name as the original template with two underscores and a progressive number (without leading zeros) at the end: originalname__1.OL-template, originalname__2.OL-template, etc. Note The Auto Save function does not cause backup files to be created. File properties On the menu, select File > Properties to view and complement the file properties. See "File Properties dialog" on page 936. The file properties can also be used in scripts; see "template" on page 1379.
To create a package file, select File >Send to Workflowand choose File in the Destination box. For the other options, see "Sending files to Workflow" on the next page. The package file has the extension .OL-package and can be opened in the Designer (see "Opening a package file" on page 453). Exporting a template report A template report can be used for archiving purposes or to provide information about the template to people who do not have access to Connect.
To test a template first, select Context > Preflight. Preflights execute the template without actually producing output and it displays any issues once it's done (see also: "Testing scripts" on page 862). Sending files to Workflow Workflow can generate output from a template in automated processes. For this, the template has to be sent to Workflow. Alternatively you may create a Package file (see "Creating package files" below) and import that into Workflow.
Creating a Web template with a Wizard With the Designer you can design Web templates and output them through Workflow or as an attachment to an email when generating Email output. Capture On The Go templates are a special kind of Web templates; see "Capture OnTheGo template wizards" on page 579. A Web Template Wizard helps you create a Web page that looks good on virtually any browser, device and screen size.
l Jumbotron l Thank You If you don't know what template to choose, see "Web Template Wizards" on page 461 further down in this topic, where the characteristics of each kind of template are described. 3. Click Next and make adjustments to the settings. The wizard remembers the settings that were last used for a Foundation Web template. l Section: l l l Description: Enter the description of the page. This is the contents of a HTML tag.
l l l l A Web context with one web page template (also called a section) in it. The web page contains a Header, a Section and a Footer element with dummy text, and depending on the type of web page, a navigation bar, button and/or Form elements. Resources related to the Foundation framework (see "Web Template Wizards" on the next page): style sheets and JavaScript files. The style sheets can be found in the Stylesheets folder on the Resources pane.
Web Template Wizards Foundation With the exception of the most basic one, all Web Template Wizards in the Designer make use of the Zurb Foundation front-end framework. A front-end framework is a collection of HTML, CSS, and JavaScript files to build upon. Foundation is a responsive framework: it uses CSS media queries and a mobile-first approach, so that websites built upon Foundation look good and function well on multiple devices including desktop and laptop computers, tablets, and mobile phones.
A Capture OnTheGo Form is actually just a Web Form, that you could add without a wizard, but the COTG Template Wizards include the appropriate JavaScript files for the Capture OnTheGo app, and styles to create user-friendly, responsive forms. They are built upon the Foundation framework. Foundation With the exception of the most basic one, all Web Template Wizards in the Designer make use of the Zurb Foundation front-end framework.
2. Select a template. There are 8 types of Web Template Wizards: l l l l l l l l Blank. The Blank COTG Template has some basic design and the appropriate form, but no actual form or COTG elements. Bill of Lading. The Bill of Lading Template is a transactional template that includes a detail table with a checkmark on each line, along with Signature and Date COTG elements. Use this wizard as a way to quickly start any new Zurb Foundation based form for Capture OnTheGo. Event Registration.
Do the same for the background color of the navigation bar at the top and for the buttons on the Form. 4. Click Next to go to the next settings page if there is one. 5. Click Finish to create the template. The Wizard creates: l l l A Web context with one web page template (also called a section) in it. The web page contains an 'off-canvas' Div element, Header, a Section and a Footer element with dummy text, and depending on the type of web page, a navigation bar, button and/or Form elements.
Filling a COTG template Before inserting elements in a COTG Form, have the design ready; see "Designing a COTG Template" on page 575. In a Capture OnTheGo form, you can use special Capture OnTheGo Form elements, such as a Signature and a Barcode Scanner element. For a description of all COTG elements, see: "COTG Elements" on page 705. To learn how to use them, see "Using COTG Elements" on page 593.
Tip Click the Edges button on the toolbar t emporarily adds a frame to certain elements on the Design tab. These will not .Print or output. Tip If you have started creating your Capture OnTheGo template using a COTG Template Wizard, you can find ready-made elements in the Snippets folder on the Resources pane. Resources This page clarifies the difference between Internal, External and Web resources that may be used in a template, and explains how to refer to them in HTML and in scripts.
When refering to them, normally you would simply use the path directly with the file name. The structure within those folders is maintained, so if you create a "signatures" folder within the "Images" folder, you need to use that structure, for example in HTML: 
. In scripts, you can refer to them in the same way, for example: results.loadhtml("snippets/en/navbar.
Web resources Web resources are simply accessed using a full URL. This URL needs to be publicly accessible: if you type in that URL in a browser on the server, it needs to be visible. Authentication is possible only through URL Parameters (http://www.example.com/data.json?user=username&password=password) or through HTTP Basic Auth (http://username:password@www.example.com/data.json).
with an Email Template Wizard; see "Creating an Email template with a Wizard" on page 520. Outputting and combining contexts All three contexts can be present in any template and they can all be used to output documents; see "Generating Email output" on page 1438, "Generating Print output" on page 1410 and "Generating Web output" on page 1448. They can even be combined in output. If present in the same template, a Print context and a Web context can be attached to an Email context.
Warning If you don't have a backup of the template, the only way to recover a deleted section, is to click Undo on the Edit menu, until the deleted section is restored. After closing and reopening the template it is no longer possible to restore the deleted context this way. In the Saving Preferences you can set whether a backup file should be created when you save the template; see "Save preferences" on page 850. Sections Sections are parts of one of the contexts in a template: Print, Emailor Web.
Editing a section To open a section, expand the Contexts folder on the Resources pane, expand the respective context (Print, Emailor Web) and double-click a section to open it. Each section can contain text, images and many other elements (see "Content elements" on page 628), including variable data and other dynamic elements (see "Personalizing content" on page 786). To preview a section, open the Preview tab in the Workspace (see "Workspace" on page 1049). Copying a section To copy a section: 1.
Tip The easiest way to copy a section to another template, is to use the Import Resources dialog in the other template. See: "Import Resources dialog" on page 942. Deleting a section To delete a section: l On the Resources pane, expand the Contexts folder, expand the folder of the respective context, right-click the name of the section, and then click Delete. Warning No backup files are maintained in the template.
Applying a style sheet to a section In order for a style sheet to be applied to a specific section, it needs to be included in that section. There are two ways to do this. Drag & drop a style sheet 1. Click and hold the mouse button on the style sheet on the Resources pane. 2. Move the mouse cursor within the Resources pane to the section to which the style sheet should be applied. 3. Release the mouse button. Using the Includes dialog 1. On the Resources pane, right-click the section, then click Includes.
Arranging sections Changing the order of the sections in a context can have an effect on how they are outputted; see: "Print sections" on page 487, "Email templates" on page 526 and "Web pages" on page 547. To rearrange sections in a context: l On the Resources pane, expand the Contexts folder, expand the folder of the respective context, and then drag and drop sections to change the order they are in. Alternatively, right-click a section and click Arrange.
l PCL l PDF l PostScript (including the PPML, VIPP and VPS variants) With the Designer you can create one or more Print templates and merge the template with a data set to generate personal letters, invoices, policies, or any other type of letter you can think of. The Print context is the folder in the Designer that can contain one or more Print sections. Print templates (also called Print sections), are part of the Print context.
See "Pages" on page 497 for an overview of settings and elements that are specific for pages. Headers, footers, tear-offs and repeated elements (Master page) In Print sections, there are often elements that need to be repeated across pages, like headers, footers and logos. In addition, some elements should appear on each first page, or only on pages in between the first and the last page, or only on the last page.
talker. This feature is only available with Box and Div elements in Print sections. For more information about this feature see "Copy Fit" on page 757. Creating a Print template with a Wizard A Print template may consist of various parts, such as a covering letter and a policy. Start with one of the Template Wizards for the first part; other parts (called 'sections') can be added later. Print template wizards can be found in the Welcome screen and on the File menu.
Use the Attributes pane at the right to see the current element's ID, class and some other properties. Use the Styles pane next to the Attributes pane to see which styles are applied to the currently selected element. Basic Print template wizards There are two 'basic' Print Template wizards: one for a formal letter, and one for a postcard. Postcard The Postcard Wizard lets you choose a page size and two background images, one for the front and one for the back of the postcard.
Formal letter The Formal Letter Wizard first lets you select the page settings, see "Page settings: size, margins and bleed" on page 498. These settings are fairly self-explanatory, except perhaps these: l l l l Duplex means double-sided printing. The margins define where your text flow will go. The actual printable space on a page depends on your printer. The bleed is the printable space around a page. It can be used on some printers to ensure that no unprinted edges occur in the final trimmed document.
l Selectors for variable data, for example: @Recipient@. You will want to replace these by the names of fields in your data. See "Variable Data" on page 801. The Wizard opens the Print section. You can add text and other elements; see "Content elements" on page 628. The formal letter template already has an address on it. The address lines are paragraphs, located in one cell in a table with the ID address-block-table. As the table has no borders, it is initially invisible.
After clicking Next, you can change the settings for the page. The initial page size and bleed area are taken from the selected PDF. When you click Finish, the Wizard creates: l l l A Print context with one section in it; see "Print context" on the facing page and "Print sections" on page 487. The selected PDF is used as the background of the Print section; see "Using a PDF file as background image" on page 492. For each page in the PDF one page is created in the Print section. One empty Master Page.
l l l Enter your contact details. Click the Browse button to select a logo, or select to use a placeholder logo or no logo at all. Select a PDF file with the letterhead stationery. Also see "Media" on page 508. Tip Nice to know: your info and preferences are saved and will be reused the next time you create an ERP template. When you click Finish, the Wizard creates: l l l l A Print context with one section in it; see "Print context" below and "Print sections" on page 487. One Master Page.
output" on page 1410). The Print context can also be added to Email output as a PDF attachment; see "Generating Email output" on page 1438. When generating output from the Print context, each of the Print sections is added to the output document, one after the other in sequence, for each record.
or only on pages in between the first and the last page, or only on the last page. Examples are a different header on the first page, and a tear-off slip that should show up on the last page. This is what Master Pages are used for. Master Pages can only be used in the Print context. See "Master Pages" on page 505.
Printing on both sides To print a Print section on both sides of the paper, that Print section needs to have the Duplex printing option to be enabled; see "Enabling double-sided printing (Duplex, Mixplex)" on page 495. This setting can not be changed in a Job Creation Preset or an Output Creation Preset. Note Your printer must support duplex for this option to work.
Setting the bleed The bleed is the printable space around a page. It can be used on some printers to ensure that no unprinted edges occur in the final trimmed document. The bleed is one of the settings for a section. See "Page settings: size, margins and bleed" on page 498. Overprint and black overprint Normally, when two colors overlap in Print output, the underlying color is not printed.
1. Right-click the Print context in the Resources pane and select Color Output. 2. Enable the Keep RGB black in output option. In Connect versions prior to 2018.2, RGB black was not automatically converted to CMYK black. Therefore, this option is by default enabled in templates made with an earlier version. In new templates, this option is disabled by default. Print sections Print templates (also called Print sections), are part of the Print context.
See "Master Pages" on page 505 for an explanation of how to fill them and how to apply them to different pages. Using stationery (Media) When the output of a Print context is meant to be printed on paper that already has graphical and text elements on it (called stationery, or preprinted sheets), you can add a copy of this media, in the form of a PDF file, to the Media folder. Media can be applied to pages in a Print section, to make them appear as a background to those pages.
to be printed out on paper. When a Print template is created (see "Creating a Print template with a Wizard" on page 477 and "Print context" on page 482), only one Print section is added to it, but you can add as many print sections as you need. To add a section to a context: l On the Resources pane, expand the Contexts folder, right-click the Print context , and then click New section. Note that the new section automatically gets the same properties as the first section.
Tip If you need a whole Print section to be visible in the output only under certain conditions, consider using the Conditional Print Section script wizard; see "Conditional Print sections" on page 813. You can use the Conditional Content script wizard to hide parts of the content of a section; see "Showing content conditionally" on page 810. Importing a Print section To import a section from another template, click File > Import Resources... in the menu. See: "Import Resources dialog" on page 942.
output in the order in which they appear on the Resources pane, so changing the order of the sections in the Print context changes the order in which they are outputted to the final document. To rearrange sections in a context: l l On the Resources pane, expand the Print context and drag and drop sections to change the order they are in. Alternatively, on the Resources pane, right-click a section in the Print context and click Arrange.
gives it less weight. In case of conflicting rules, style sheets read later will override previous ones. Note Style sheets are applied in the order in which they are included in a section. The styles in each following style sheet add up to the styles found in previously read style sheets. When style sheets have a conflicting rule for the same element, class or ID, the last style sheet ‘wins’ and overrides the rule found in the previous style sheet. Note Style sheets that are linked to (i.e.
file that was used as input file, or another type of input file, converted to a PDF file. With this option you don't need to make any other settings; click OK to close the dialog. 3. For a PDF resource, you have to specify the path. Clicking the Select Image button opens the Select Image dialog (see "Select Image dialog" on page 993). 4. l Click Resources, Disk or Url, depending on where the image is located. l l l Resources lists the images that are present in the Images folder on the Resources pane.
images need to be available when the template is merged with a record set to generate output, and that their location should be accessible from the machine on which the template's output is produced. External images are updated (retrieved) at the time the output is generated. 5. Select the PDF's position: l Fit to page stretches the PDF to fit the page size. l Centered centers the PDF on the page, vertically and horizontally. l Absolute places the PDF at a specific location on the page.
Dynamic backgrounds To make the background change based on the value of a data field, you may use the Dynamic Background Script Wizard; see "Dynamic Print section backgrounds" on page 816. Alternatively you could write your own Control Script to set the background; see "Control Script: Setting a Print section's background" on page 893. The settings in a script take precedence over the settings made in the Print Section Properties dialog.
Note Your printer must support Duplex for this option to work. To enable Duplex or Mixplex printing: 1. On the Resources pane, expand the Print context, right-click the print section and click Sheet configuration. 2. Check Duplex to enable content to be printed on the back of each sheet. 3. When Duplex printing is enabled, further options become available. l Check Omit empty back side for Last or Single sheet to reset a page to Simplex if it has an empty back side.
Scripts" on page 885 and "Control Script API" on page 1351). This is especially useful when you need identical sections with different settings. Pages Unlike emails and web pages, Print sections can contain multiple pages. Pages are naturally limited by their size and margins. If the content of a section doesn't fit on one page, the overflow goes to the next page. This happens automatically, based on the section's page size and margins; see "Page settings: size, margins and bleed" on the facing page.
l Detail tables can be used in all contexts, but transport lines are only useful in a Print context; see "Detail Table" on page 818. Positioning and aligning elements Sometimes, in a Print template, you don't want content to move up or down with the text flow. To prevent that, put that content in a Positioned Box. See "Content elements" on page 628. When it comes to positioning elements on a page, Guides can be useful, as well as Tables. See "How to position elements" on page 758.
Whitespace elements: using optional space at the end of the last page Print sections with conditional content and dynamic tables (see "Personalizing content" on page 786) can have a variable amount of space at the bottom of the last page. It is useful to fill the empty space at the bottom with transpromotional material, but of course you don’t want extra pages created just for promotional data. 'Whitespace elements' are elements that will only appear on the page if there is enough space for them.
page 505. To insert a page number, select Insert > Special character > Markers on the menu, and then click one of the options to decide with what kind of page number the marker will be replaced: l l l l l l Page number: The current page number in the document. If a page is empty or does not display a page number, it is still added to the page count. Page count: The total number of pages in the document, including pages with no contents or without a page number.
Creating a table of contents A table of contents can only be created in a script. If you are looking to create a short, simple table of contents in one section, you could add a Standard Script that uses the pageRef() function. For an example, see "Creating a table of contents" on page 1317. For a multi-page, cross-section table of contents you must use a Post Pagination Script; see "Creating a Table Of Contents" on page 902.
Preventing widows and orphans Widows and orphans are lines at the beginning or at the end of a paragraph respectively, dangling at the bottom or at the top of a page, separated from the rest of the paragraph. By default, to prevent orphans and widows, lines are moved to the next page as soon as two lines get separated from the rest of the paragraph. The same applies to list items (in unordered, numbered and description lists).
1. Open the Formatting dialog. To do this, you can: l l Select the paragraph using the breadcrumbs or the Outline pane (next to the Resources pane) and then select Format > Paragraph in the menu. Right-click the paragraph and select Paragraph... from the contextual menu. 2. After Widows and Orphans, type the minimum number of lines that should be kept together.
Inserting a page break To insert a page break before or after a certain element, set the page-break-before property or the page-break-after property of that element (a paragraph for example; see also "Styling text and paragraphs" on page 753): 1. Select the element (see "Selecting an element" on page 632). 2. On the Format menu select the respective element to open the Formatting dialog. 3. In the Breaks group, set the before or after property.
Alternatively you could set this property on the Source tab in the HTML (for example:
), or add a rule to the style sheet; see "Styling your templates with CSS files" on page 747. Adding blank pages to a section How to add a blank page to a section is described in a how-to: Create blank page on field value. Master Pages In Print sections, there are often elements that need to be repeated across pages, like headers, footers and logos.
l On the Resources pane, right-click the Master pages folder and click New Master Page. l Type a name for the master page. l l Optionally, set the margin for the header and footer. See "Adding a header and footer" on the next page. Click OK. Initially, the master page that has been created together with the Print context will be applied to all pages in the Print section.
Adding a header and footer Headers and footers are not designed as part of the contents of a Print section, but as part of a Master Page, which is then applied to a page in a print section. To create a header and footer: 1. First insert elements that form the header or footer, such as the company logo and address, on the Master Page; see "Editing a Master Page" on the previous page. 2. Next, define the margins for the header and footer.
check Tumble to duplex pages as in a calendar, and Facing pages to have the margins of the section switch alternately, so that pages are printed as if in a magazine or book. 3. If the option Same for all positions is checked, the same Master Page will be applied to every page in the print section (and to both the front and the back side of the page if duplex printing is enabled). Uncheck this option. 4.
For further explanation about how to apply Media to different pages, see "Applying Media to a page in a Print section" on page 512. Media will not be printed, unless you want them to; see below. Per Media, a front and back can be specified and you can specify on what kind of paper the output is meant to be printed on. This includes paper weight, quality, coating and finishing; see "Setting Media properties" below.
type of image file) for both the front and the back of the Media, and you can determine how the virtual stationery should be positioned on the page. This is done as follows: 1. On the Resources pane, expand the Contexts folder, expand the Media folder, rightclick the Media and click Properties. 2. Now you can change the name and page size of the Media. Note that it isn't possible to change the page size once the Media is applied to a section. Media can only be applied to sections that have the same size. 3.
not selected, the Select Image dialog automatically adds the filetype parameter with the file extension as its value (for example: ?filetype=pdf (if it is the first parameter) or &filetype=pdf). The filetype, page and nopreview parameters are not sent to the host; they are used internally. Therefore, URLs that rely on one of these parameters cannot be used. l With an external image, you can check the option Save with template.
Setting the paper's characteristics To set a Media's paper characteristics: 1. On the Resources pane, expand the Contexts folder, expand the Media folder, and right-click the Media. Click Characteristics. 2. Specify the paper's characteristics: l l l l l l l Media Type: The type of paper, such as Plain, Continuous, Envelope, Labels, Stationery, etc. Weight: The intended weight of the media in grammage (g/m2).
To apply Media to specific page positions in a Print section: 1. On the Resources pane, expand the Print context; right-click the Print section, and click Sheet configuration. 2. Optionally, check Duplex to enable content to be printed on the back of each sheet. Your printer must support duplex for this option to work.
1. On the Resources pane, expand the Contexts folder, expand the Print context, rightclick the print section and click Sheet configuration. 2. Decide which pages should have dynamically switching media: every first page in the Print section, every last page, one of the pages in between (a 'middle page'), or a single page. (Uncheck the option Same for all positions, to see all page positions.) 3. In the area for the respective sheet position, click the Edit script button next to Media.
Note l l Any Virtual Stationery settings made for the Media also influence how the Media is displayed in each section (see "Setting Media properties" on page 509). Section backgrounds are rotated separately (see "Using a PDF file as background image" on page 492). If in the Media properties, the Virtual Stationery position is set to Absolute, any offset given by the Top and Left values will be applied after rotation.
HTML email that displays properly on a variety of devices and screen sizes is challenging. Building an email is not like building for the web. While web browsers comply with standards (to a significant extent), email clients do not. Different email clients interpret the same HTML and CSS styles in totally different ways.
Designing an Email template With the Designer you can design Email templates. It is strongly recommended to start creating an Email template with an Email Template Wizard, because it is challenging to design HTML email that looks good on all email clients, devices and screen sizes that customers use when they are reading their email.
Email templates: Slate and others The most obvious solution offered in the Designer is to use one of the templates provided with the Designer; see "Creating an Email template with a Wizard" on page 520. The layout of these templates has been tested and proven to look good in any email client, on any device and screen size. The Tables in these templates are nested (put inside another table) and they have no visible borders, so readers won't notice them.
All standard abbreviations can be found in Emmet's documentation: Abbreviations. To learn more about Emmet, please see their website: Emmet.io and the Emmet.io documentation: http://docs.emmet.io/. Preferences To change the way Emmet works in the Designer, select Window > Preferences, and in the Preferences dialog, select Emmet; see "Emmet preferences" on page 840.
Do not capture your email in one big image Most e-mail clients do not automatically download images, so do not capture your email in one big image. The recipient initially sees a blank message and probably deletes it right away. Do not resize images in your email Many mail clients do not support image resizing and will show the image in its original dimensions. Resize the images before you link to or embed them.
1. In the Welcome screen that appears after startup: l l Choose Browse Template Wizards. Scroll down until you see the Email Template Wizards. There are three types of Email Template Wizards: l Basic Email templates l Banded Email templates l Slate: Responsive Email templates by Litmus. Or choose Create a New Template and select the Email template. This starts the Basic Action Email wizard. Alternatively, on the File menu, click New, and: l l Select Email Template.
on which Template Wizard was used. The style sheets can be found in the Stylesheets folder on the Resources pane. The Wizard opens the Email section, so that you can fill it with text and other elements; see "Content elements" on page 628, "Email context" on page 524, and "Email templates" on page 526. Tip Use the Outline pane at the left to see which elements are present in the template and to select an element.
More than 50% of emails are opened on mobile. These five responsive HTML email templates are optimized for small screens and they look great in any inbox. They’ve been tested in Litmus and are completely bulletproof. Tip After creating the email template, click the Responsive Design View icon of the workspace to see how the email looks on different screen sizes. at the top The only thing you can set in advance for a Slate template is the color of the call-to-action button.
page 774. l The web address where the recipient of the email will be taken after clicking the button in the email. Type the URL in the Link field. In addition, for an Invoice email you can change the following content settings: l l Show Welcome Message. Check this option to insert a salutation and one paragraph with dummy text in the email. Detail Table Name. Type the name of a detail table to fill the lines of the invoice with data.
Sending email When the template is ready, you can generate Email output; See "Generating Email output" on page 1438. To test a template, you can send a test email first. This allows you to override the recipient address. Output, generated from an Email template, can have the following attachments: l The contents of the Print context, in the form of a single PDF attachment. (Compression options for PDF attachments can be specified in the Email context's properties; see "Compressing PDF attachments" below.
1. On the Resources pane, expand the Contexts folder; then right-click the Email context and select PDF Attachments. Alternatively, select Context > PDF Attachments on the main menu. This option is only available when editing an Email section in the Workspace. 2. Change the properties of the PDF file that will be attached when the Print context is attached to the email. Lossless is the maximum quality. Note that this will produce a larger PDF file. Uncheck this option to be able to set a lower quality.
An Email context can contain multiple templates. When generating output from the Email context, however, only one of the Email templates can be merged with each record. Set the 'default' Email section (see below) before generating Email output; see also "Generating Email output" on page 1438. For information about attachments see "Email attachments" on page 537.
Note that when the imported Email section replaces an Email section in your template, the PDF attachments settings are imported as well. (See: "Compressing PDF attachments" on page 525.) Deleting an Email template To delete an Email section: l On the Resources pane, expand the Contexts folder, expand the Email context, rightclick the name of the section, and then click Delete.
In order for a style sheet to be applied to a specific section, it needs to be included in that section. There are two ways to do this. Drag & drop a style sheet 1. Click and hold the mouse button on the style sheet on the Resources pane. 2. Move the mouse cursor within the Resources pane to the section to which the style sheet should be applied. 3. Release the mouse button. Using the Includes dialog 1. On the Resources pane, right-click the section, then click Includes. 2.
Setting a default Email template for output An Email context can contain multiple templates. When generating output from the Email context, however, only one of the Email templates can be merged with each record. To select the Email section that will be output by default: l On the Resources pane, expand the Email context, right-click a section and click Set as Default.
Note Using a variable email address requires you to load dataor a data mapping configuration first; see "Loading data" on page 788. The Email Script Wizard In addition to the drag and drop method, you can use the Email Script Wizard to add data to an email header field. It lets you choose one or more data fields and enter a prefix and/or suffix (per data field). There are two ways to open the Email Script Wizard: l l Via the Email Fields.
Default SMTP settings can be specified in the Preferences dialog: select Window > Preferences, expand the Email preferences and click SMTP. You can add as many presets as needed, for example for different Email Service Providers (see "Using an ESP with PlanetPress Connect" on page 1442). To do this, click the Add button at the right. Then fill out the following settings: l l l l l Name: The name of the preset. This will show up in the Send Email dialog.
To add variable data to the subject of an email section, drag and drop a data field into the Subject field at the top of the workspace. Two things will happen: l A placeholder for the data field appears in the subject line (for example: @email@). l A new script, named Subject, is added to the Scripts pane. You can add as many data fields to the subject as you like.
to make the script work for all email sections. Recipients: To, CC and BCC To specify recipients for Email output, you can simply drag and drop a data field that contains an email address into the To field at the top of the workspace. A new script, named To, will be added to the Scripts pane. Note that you can add only one data field to the email field this way. When you drag another data field into the email field the existing script will be replaced..
Tip A dynamic From address is often used when sending email campaigns and to do tracking of email replies. Include the recipient's email address in a dynamic From address to enable automatic detection and removal of undeliverable e-mail addresses. (This technique is called VERP; see Wikipedia.
4. For a name-type meta tag, enter the value. 5. Enter the content. Example When you add a name meta tag with the value viewport and content width=320, the following will be added to the email header: . For more information on tags, see W3Schools - HTML meta tag.
Note Via a Control Script it is possible to set a different user password and owner password, see "Control Script: Securing PDF attachments" on page 898, "Control Scripts" on page 885 and "Control Script API" on page 1351. Email attachments Output, generated from an Email template, can have the following attachments: l The contents of the Print context, in the form of a single PDF attachment.
This topic explains how to attach files other than those generated by the Print or Web context. Note A plain-text version of the HTML is added to each email if the option is checked in the Email section's properties (see "Properties tab" on page 987). With new templates this is always the case. Attaching files Selecting and adding files as attachments If you want all recipients to get the same attachments with their email, you can add the attachments to the Email section(s).
2. A new script called Attachments has appeared in the list. Double-click to open it. 3. Choose an Email section from the Section drop-down list. 4. Fill in the different parts of which the file name is composed: l l l Prefix. The first prefix contains the base path (or at least the first, static part of the path). For example:C:\Attachments\, C:/Attachments/, or file:///C:/Attachments/. Data field/s. The selected data field/s will be evaluated. If a data field is empty, the entire row is skipped.
If you want to write your own email attachment scripts, there is a how-to that you may find helpful: How to add custom email attachments. Renaming attachments Print and Web sections that are attached to an email can only be renamed via a Control Script; see "Parts: splitting and renaming email attachments" on page 890. Renaming dynamic attachments Dynamic attachments can be renamed via the script that attaches them to the email. Doubleclick the script to open it and click the Expand button.
Capture OnTheGo app (see "Capture OnTheGo" on page 569). They are stored in the Web folder as well. The Web context outputs one HTML web page. In addition to the HTML text it contains either the resources or references to the resources necessary to display it. JavaScript files are added to the
in the generated HTML file. JavaScript toolboxes like jQuery and its plugins, or MooTools, are useful when you want to implement special features in the web page. (See "Using JavaScript" on page 564.
Capture On The Go templates are a special kind of Web templates; see "Capture OnTheGo template wizards" on page 579. A Web Template Wizard helps you create a Web page that looks good on virtually any browser, device and screen size. Foundation With the exception of the most basic one, all Web Template Wizards in the Designer make use of the Zurb Foundation front-end framework. A front-end framework is a collection of HTML, CSS, and JavaScript files to build upon.
3. Click Next and make adjustments to the settings. The wizard remembers the settings that were last used for a Foundation Web template. l Section: l l l Description: Enter the description of the page. This is the contents of a HTML tag. Top bar group: l l l l Name: Enter the name of the Section in the Web context. This has no effect on output.
JavaScript folder on the Resources pane, in a Foundation folder. l l A collection of Snippets in the Snippets folder on the Resources pane. The Snippets contain ready-to-use parts to build the web page. Double-click to open them. See "Snippets" on page 737 for information about using Snippets. Images: icons, one picture and one thumbnail picture. Hover your mouse over the names of the images in the Images folder on the Resources pane to get a preview.
and function well on multiple devices including desktop and laptop computers, tablets, and mobile phones. Foundation is tested across many browsers and devices, and works back as far as IE9 and Android 2. See http://foundation.zurb.com/learn/about.html. Jumbotron The name of the Jumbotron template is derived from the large screens in sports stadiums. It is most useful for informative or marketing-based websites.
l l The Web context is created and one Web page or section is added to it. You can see this on the Resources pane: expand the Contexts folder, and then expand the Web folder. See "Web pages" on the next page to learn how to fill a web page template in the Designer. Although only one web page can be generated per record when generating Web output, the Web context can contain multiple sections.
that this option is only available when editing a Web section in the Workspace.) For further explanation see: "Includes dialog" on page 943. To make this setting for a particular Web section, right-click the section on the Resources pane and select Includes. Web pages Web pages (also called Web sections) are part of the Web context (see "Web Context" on page 545) in a template. The Web context outputs one HTML web page.
To provide alternative content for the web page, you could use Conditional Content (see "Showing content conditionally" on page 810), or Snippets and a script (see the Help topics "Snippets" on page 737 and "Loading a snippet via a script" on page 872, and this how-to: Multi-page Web template.) Tip For an example of how to serve different web pages using snippets, see the following how-to: Creating a multi-page Web template.
save the template; see "Save preferences" on page 850. Filling a Web page Many of the content elements that are available for all three contexts are particularly suitable for web pages; see "Content elements" on page 628. Do not use Positioned Boxes and Tables to position elements, however; use Inline Boxes instead. Forms and Form elements are only available in a Web context; see "Forms" on page 713 and "Form Elements" on page 718.
In order for a style sheet to be applied to a specific section, it needs to be included in that section. There are two ways to do this. Drag & drop a style sheet 1. Click and hold the mouse button on the style sheet on the Resources pane. 2. Move the mouse cursor within the Resources pane to the section to which the style sheet should be applied. 3. Release the mouse button. Using the Includes dialog 1. On the Resources pane, right-click the section, then click Includes. 2.
Note Which style sheets are included can also be set for the Web context as a whole: in step 1, right-click the Web context, instead of a section. Setting a default Web page for output When generating output from the Web context, only one of the Web templates can be merged with each record. To select the Web section that will be output by default: l On the Resources pane, expand the Web context, right-click a section and click Set as Default.
Setting the title, meta data and a shortcut icon Each Web section has a set of properties to define the title of the web page, the shortcut icon and the meta tags appearing in the web page's head (with the HTML tag:
, see https://www.w3schools.com/tags/tag_head.asp). To change these properties: 1. On the Resources pane, expand the Web context, right-click the section and click Properties. 2. Enter the Page Title. The contents of this field will go in the HTML tag.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-553.html">PAGE 553</a></h6>
<p>2. Change the name of the script, so that it reflects what the script does. Note Scripts can only have the same name when they are not in the same folder. 3. Choose the option Selector and in the Selector field, type head. 4. Write a script that appends an element to the <head> of the web page. Example The following script adds a <base> element to the head of a web page. results.append("<base href='https://www.w3schools.com/images/' target='_blank'>"); Forms Web templates can contain Forms.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-554.html">PAGE 554</a></h6>
<p>the Form's properties, validation method and location, but doesn't allow you to specify fields. If you choose this method, skip step 8 and 9 of this procedure and add fields after inserting the Form (see "Adding elements to a Form" on page 558). 3. Add an ID and/or a class. ID's and classes are particularly useful with regard to variable data (see "Personalizing content" on page 786) and styling (see "Styling templates with CSS files" on page 743). 4.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-555.html">PAGE 555</a></h6>
<p>validation as it is browser independent. The necessary JQuery files will be added to the JavaScript folder on the Resources pane when the form is inserted. 8. Under Fields, click the Add button and click on the desired field type to add a field of that type; see "Form Elements" on page 718. Note A Fieldset is not available in the Form Wizard, because a Fieldset itself can contain multiple different fields. Add the Fieldset after inserting the Form; see "Adding elements to a Form" on page 558. 9.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-556.html">PAGE 556</a></h6>
<p>Note: HTML has some restrictions as to which types of elements are allowed as children of other elements. For example, a paragraph element is not allowed to have children that are block level elements - like a Div or a Table. If inserting content at the selected location would produce invalid HTML the final result may be different than expected. For example, when you insert a Div into a paragraph, the paragraph gets split in two. This means you end up with two paragraphs with the Div in between. 12.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-557.html">PAGE 557</a></h6>
<p>Changing a Form's validation method In Connect PlanetPress Connect, there are two ways in which a Form's input can be validated: l l The Browser validation method leaves it up to the browser to validate the user input. When adding fields to the Form (see the next step) you can only make fields required and set the maximum length as an additional requirement for some fields. JQuery Validation validates input using JQuery scripts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-558.html">PAGE 558</a></h6>
<p><input id="email1" name="email1" data-custom-message="Enter a valid email address." type="email" required=""> Validation in Connect 1.0.0 In Connect 1.0.0, the validation method of the template was stored using the names "standard" and "custom". Standard has changed to "browser" and custom is now "jquery-validation". When you open a template made with that version of the software, the template will be migrated to use the new attribute values for the data-validation-method attribute of the <form> element.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-559.html">PAGE 559</a></h6>
<p>1. Add an ID (required) and, optionally, a class. Note The ID will be copied to the name attribute of the element. The name attribute is what identifies the field to the receiving server-side script. To change the name, select the element after inserting it and type the new name on the Attributes pane. ID's and classes are also useful with regard to variable data (see "Personalizing content" on page 786) and styling (see "Styling templates with CSS files" on page 743). 2.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-560.html">PAGE 560</a></h6>
<p>Tip For other Form elements, you can set the default value to be the value of a field in the record set; see "Specifying a default value" on the next page. l l For a Checkbox or Radio Button you can check checked or selected respectively for the element to initially be checked/selected when the web page is shown.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-561.html">PAGE 561</a></h6>
<p>Adding new HTML5 elements HTML5 added several new input element types that can't be found in the Designer menu. To add such an element to a template you can do the following: 1. Add an input element from the menu, for example a Text or Button. 2. Select the element in the template. 3. On the Attributes pane, select the desired input type from the Type drop-down list.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-562.html">PAGE 562</a></h6>
<p>Note To enable submitting arrays, you need to check the Use PHP arrays or Use enhanced PHP arrays option in the HTTP Server user preferences in Workflow; see Workflow Online Help. A simple method to create arrays in the job data file is to use two pairs of square brackets in the name of the form inputs. Put the name of the array between the first pair of square brackets. Between the second pair of square brackets, define the key to which the value belongs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-563.html">PAGE 563</a></h6>
<p></pinElm1> </values> With the Use enhanced PHP arrays option, the XML looks similar, but in this case, the value between the first pair of square brackets is expected to consist of two parts, separated by an underscore (e.g. row_0). The first part becomes the element's name. All content after the first underscore (preferably an integer) is given as an attribute of the element (e.g. <row _idx=0>). The above HTML results in the following XML: <values count="4"> <user_account>pparker@eu.objectiflune.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-564.html">PAGE 564</a></h6>
<p><input type="hidden" name="status_1" value="0" /> <input type="checkbox" id="status_1" name="status_1" value="1" /> When multiple fields with the same name are encountered, the previous value is overwritten. This way the values for unchecked checkboxes and radio buttons can be processed easily. Tip The Capture OnTheGo (COTG) plugin automatically adds a hidden field for every unchecked checkbox on a Form when the Form is submitted.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-565.html">PAGE 565</a></h6>
<p>Adding JavaScript files to the Resources Adding a JavaScript file To add a JavaScript file to the resources: 1. Add the file: l l l Right-click the JavaScript folder on the Resources pane, and click New JavaScript. Double-click it to open and edit it. Alternatively, drag and drop the JavaScript file from the Windows Explorer to the JavaScript folder on the Resources pane. Or import one or more JavaScript files from another template; see "Import Resources dialog" on page 942. 2.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-566.html">PAGE 566</a></h6>
<p>When generating Web output, these files are referenced in the web page's header and are served by the remote server, not by the Connect Server module. There are a few advantages to using remote resources: l l These resources are not served by your server, saving on space, bandwidth and processing. Using a popular CDN takes advantage of caching - a client having visited another website using that same CDN will have the file in cache and not re-download it, making for faster load times for the client.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-567.html">PAGE 567</a></h6>
<p>option to download and embed all remote resources. (See Workflow Help: Create Web Content.) Tip After adding the remote file, you may right-click it and select Download Resource. This allows you to maintain a central file, from which you can quickly download a copy to your template without having to copy & paste. Note that a local copy of a remote resource is a snapshot; it is not automatically kept in sync with its remote content.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-568.html">PAGE 568</a></h6>
<p>Note Any JavaScript files included in a section run after the scripts in the Scripts pane. Using JavaScript in other contexts Email clients do not support JavaScript. Therefore, Email contexts cannot include JavaScript resources. When a JavaScript file is included in a Print section, the Designer itself acts as the browser. When generating Print output, it runs the JavaScript after generating the main page flow contents and the pagination.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-569.html">PAGE 569</a></h6>
<p>the browser compatibility table at the bottom of the Mozilla documentation for "let": Mozilla documentation.) Capture OnTheGo With the Designer you can create Capture OnTheGo templates. COTG templates are used to generate forms for the Capture OnTheGo mobile application. For more information about the application refer to these websites: Capture OnTheGo and Capture OnTheGo in the Resource Center.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-570.html">PAGE 570</a></h6>
<p>however, to start the COTG Template using one of the COTG Template Wizards. They all include the appropriate JavaScript files and style sheets to create user-friendly, responsive forms; see "Capture OnTheGo template wizards" on page 579. Before starting to create a COTG Form, take some time to structure the design process and to get familiar with the principles of form design, as explained in the topic "Designing a COTG Template" on page 575.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-571.html">PAGE 571</a></h6>
<p>In a Capture OnTheGo form, you can use special Capture OnTheGo Form elements, such as a Signature and a Barcode Scanner element. For a description of all COTG elements, see: "COTG Elements" on page 705. To learn how to use them, see "Using COTG Elements" on page 593. Tip If you have started creating your Capture OnTheGo template using a COTG Template Wizard, you can find ready-made elements in the Snippets folder on the Resources pane.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-572.html">PAGE 572</a></h6>
<p>Using JavaScript COTG plugin Capture OnTheGo widgets do not function without the COTG plugin: cotg-2.0.0.js. This plugin also makes it possible to add COTG Elements dynamically, set defaults for COTG elements, react to events that occur when a user interacts with a COTG element, etc. For more information see: "Using the COTG plugin: cotg-2.0.0.js" on page 605.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-573.html">PAGE 573</a></h6>
<p>Next, you can start building a Workflow configuration that receives and handles the submitted data. The configuration should start with a HTTP Server Input task (see Workflow Help: HTTP Server Input) of which the HTTP action is the one specified in the COTG Form's action. Using COTG data in a template When a user submits a COTG Form, a Workflow configuration may store the information in a database and/or push it into other Workflow processes, for example to send a letter or an email receipt.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-574.html">PAGE 574</a></h6>
<p>2. Create a data mapping configuration Use the resulting XML file to create a data mapping configuration (see "Data mapping configurations" on page 226). 1. Choose File > New > Data mapping Wizards > From XML file. 2. Select the XML data file as its source and click Next. 3. Set the XML Elements option to /request/values. This will automatically add an extraction step for the submitted form fields. 4. Click Finish.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-575.html">PAGE 575</a></h6>
<p>1. Click the Insert Inline Box icon on the toolbar. The Insert Inline Box dialog appears. 2. Enter an ID for the box (anything will do, as long as it helps you identify the box) and click OK. The box is added to the text flow and can be resized if needed. 3. Switch to the Source tab and replace the content of the box: <p> Div content goes here </p> by this text: <img id="camera" src="" width="100%"> 4. Switch back to the Design tab. You will see a small, empty rectangle inside at the top of the inline box.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-576.html">PAGE 576</a></h6>
<p>company actually needs will prove to be well worth your time. Creating specifications up front prevents discussions, reduces rework and therefore saves time. 2. Listing the input fields that are needed, their type, and possible input constraints. Think of how the information should be visually grouped.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-577.html">PAGE 577</a></h6>
<p>Tip If the COTG Form replaces a paper form, it can be tempting to stick to the original layout for the sake of recognizability. Don't fall into that trap. In the end, the users - customers and employees will be happier with a user-friendly form that adapts to different screen sizes and looks like it was designed for the web. Most design guidelines for web forms apply to COTG forms as well. Two key concepts are responsive design and usability.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-578.html">PAGE 578</a></h6>
<p>Usability Usability defines the ease of use of a form. Is the layout intuitive? Are the form elements easy to tap on a mobile device? A visually consistent design allows the user to follow the flow while filling out the form. Below are some key usability aspects to keep in mind when designing forms. Provide clear labels. Many modern web sites show labels inside the actual form inputs while they are empty. This saves space on the form, but once the user has entered data the label is no longer visible.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-579.html">PAGE 579</a></h6>
<p>Forms for offline use Capture OnTheGo forms can be used offline. This is the case even when the form relies on remotely stored source files like JavaScript files and style sheets, provided that the option Use cached Capture OnTheGo resource is checked when adding them to the form. Capture OnTheGo template wizards With the Designer you can create Capture OnTheGo (COTG) templates. COTG templates are used to generate forms for the Capture OnTheGo mobile application.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-580.html">PAGE 580</a></h6>
<p>user-friendly as possible. See "Designing a COTG Template" on page 575. Creating a COTG template using a wizard To create a COTG template with a template wizard: 1. l l In the Welcome screen that appears after startup and when you click the Home icon at the top right, choose Browse Template Wizards. Scroll down until you see the Capture OnTheGo Starter Template Wizards. Alternatively, on the File menu, click New, expand the Template folder, and then expand the Capture OnTheGo Starter folder. 2.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-581.html">PAGE 581</a></h6>
<p>3. Click Next and make adjustments to the settings. The wizard remembers the settings that were last used for a COTG template. l l l l Create Off-Canvas navigation menu: an Off-Canvas menu is a Foundation component that lets you navigate between level 4 headings (<h4>) in the form. Check this option to add the menu automatically. Submit URL: enter the URL where the form data should be sent. The URL should be a server-side script that can accept COTG Form data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-582.html">PAGE 582</a></h6>
<p>The action of a Capture OnTheGo form should specify the Workflow HTTP Server Input task that receives and handles the submitted data. The action will look like this: http://127.0.0.1:8080/action (8080 is Workflow's default port number; 'action' should be replaced by the HTTP action of that particular HTTP Server Input task). The method of a Capture OnTheGo form should be POST to ensure that it doesn't hit a data limit when submitting the form.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-583.html">PAGE 583</a></h6>
<p>Tip Use the Outline pane at the left to see which elements are present in the template and to select an element. Use the Attributes pane at the right to see the current element's ID, class and some other properties. Use the Styles pane next to the Attributes pane to see which styles are applied to the currently selected element. Tip Click the Edges button on the toolbar t emporarily adds a frame to certain elements on the Design tab. These will not .Print or output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-584.html">PAGE 584</a></h6>
<p>Capture OnTheGo and Jumbotron template wizards automatically add the Foundation files v. 5.5.1 to the resources of the template. In a future version of PlanetPress Connect, Foundation 6 will be included. If you'd rather start using the newest Foundation files right away, you have two options: l l Download the Foundation files (from http://foundation.zurb.com/sites/download.html/) and add them to the template manually. Use remote Foundation files from a CDN, such as https://cdnjs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-585.html">PAGE 585</a></h6>
<p>These classes can be combined, so that depending on the screen size, a Div can take more or less space in a row. Separate the class names with a space. Tip Start with the class for small screens. For example: <div class="small-3 large-6" columns>. Larger devices will inherit those styles (thanks to the mobile-first approach of Foundation's style sheet). Customize for larger screens as necessary.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-586.html">PAGE 586</a></h6>
<p>To add Grid rows and columns quickly, you could also use the Grid snippets or Row snippets, found in the Snippets folder on the Resources pane after using a wizard to create a Foundation web page or a Capture OnTheGo template. For more information about Snippets, see "Snippets" on page 737. For more information about template wizards, see "Creating a Web template with a Wizard" on page 541 and "Capture OnTheGo template wizards" on page 579.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-587.html">PAGE 587</a></h6>
<p>OnTheGo form elements. For more information about the application refer to these websites: Capture OnTheGo and Capture OnTheGo in the Resource Center. Capture OnTheGo (COTG) elements can only be added within a Form element in a Web context; see "COTG Forms" on page 569. For information about how to add and use COTG Elements, see "Using COTG Elements" on page 593.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-588.html">PAGE 588</a></h6>
<p>l l l Take now: Opens the device's default Camera application to take a picture using the device's camera. Capture OnTheGo has no impact on the device's applications, so the features available (quality, orientation, filters) are dependent on the device itself. You can, however, set the format, quality and scaling for images that are submitted by the Camera element, as explained below.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-589.html">PAGE 589</a></h6>
<p>and edit the Image properties: l Format: The image format can be PNG or JPG. l Quality: Set the compression in a percentage. l Scale Image: Check this option to enable image scaling. Then set the maximum width and height of images before they are sent to the server. Note that only the smallest of these is applied and the size ratio is always maintained. Time stamp A time stamp can be added to each picture taken.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-590.html">PAGE 590</a></h6>
<p>Date and Formatted Date The Date element and the Formatted Date element display the current date on the device when the form is first opened. When the element is touched, a date selector appears so the user can modify this date. The Formatted Date element displays dates in a format that depends on the locale of the device on which the user is viewing the form. A Date Element displays dates in the ISO 8601 format: YYYY-MM-DD. When the form is submitted, the date data is sent as plain text.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-591.html">PAGE 591</a></h6>
<p>Geolocation The Geolocation Element adds a button to read the device's current GPS coordinates and save them in a form field. When the button is pressed, the GPS coordinates are requested and saved. When the form is submitted, the Geolocation data is sent in plain text. High accuracy By default, devices attempt to retrieve a position using network-based methods.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-592.html">PAGE 592</a></h6>
<p>Repository ID The Repository ID element retrieves the repository ID (read only) from the app based on the currently logged on COTG user. You could put the Repository ID in a hidden input, so that when the form is submitted, the Repository ID is submitted as well. This information can be used on the server side to take specific actions, such as sending properly branded emails. Signature The Signature Element adds a signature box to a COTG form.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-593.html">PAGE 593</a></h6>
<p>form is available to many different users, to detect who submitted it. If desired the field can be hidden; it will still be submitted. Using COTG Elements Capture OnTheGo (COTG) elements are Web Form elements that are specially designed to be used in a Capture OnTheGo Form (see "Capture OnTheGo" on page 569). This topic explains how to add these elements to a Capture OnTheGo Form or and how to prepare them so that when the Form is submitted, they provide valid data that can be handled easily.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-594.html">PAGE 594</a></h6>
<p>l l Use label as placeholder inserts the given label text in the placeholder attribute of the field. No style omits the label altogether. Note The first two label styles ensure that when the user clicks the label, the input element gets the focus. When you add a Capture OnTheGo (COTG) element to a template that you didn't start with a COTG template wizard, the Designer will automatically add the necessary JavaScript files: the jQuery library and the COTG library: cotg-2.0.0.js.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-595.html">PAGE 595</a></h6>
<p>All COTG elements have a role attribute. This attribute is not supposed to be edited: without the correct role attribute, the element won't function. As noted, the name attribute is what identifies the element after submitting the form. Tip Use the Outline pane at the left to see which elements are present in the template and to select an element. Use the Attributes pane at the right to see the current element's ID, class and some other properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-596.html">PAGE 596</a></h6>
<p>{"timeout":6000}">. Settings in the HTML override the default settings for that element. They are applied to the widget when the Form is created and cannot be changed afterwards. For a complete list of options see the Capture OnTheGo API: "Capture OnTheGo API" on page 616. Settings for a dynamically added element can be made in code; see "Dynamically adding COTG widgets" on page 608.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-597.html">PAGE 597</a></h6>
<p><input type="text" name="pinElm1[pin_1][left]" value="361"> <input type="text" name="pinElm1[pin_1][top]" value="341"> <input type="text" name="pinElm1[pin_1][type]" value="dent"> With the Use PHP arrays option enabled in Workflow, the above HTML results in the following XML: <values count="4"> <user_account>pparker@eu.objectiflune.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-598.html">PAGE 598</a></h6>
<p><top>341</top> <type>dent</type> </pin> </pinElm1> </values> This option makes it easier to select all elements on the same level in a data mapping configuration, and to convert the XML to a JSON object. You can try out this feature with the COTG Time Sheet template, as explained in this how-to: Using The PHP Array Option. The COTG Fields Table element (see "Fields Table" on page 709) in that template has an Add button to add rows to a table, and groups data following this approach.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-599.html">PAGE 599</a></h6>
<p>Previewing the form On a PC A Capture OnTheGo template can be previewed on a PC in two different ways. Note that Capture OnTheGo form elements will not be functional unless they are sent to a device. l l Within PlanetPress Connect Designer. You can open the Preview tab or the Live tab in the Workspace. This displays the output HTML along with any variable data being added.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-600.html">PAGE 600</a></h6>
<p>1. Go to the Capture OnTheGo Repository Login: https://config-us.captureonthego.com/. 2. Login with your Repository ID and Password. 3. Go to the Users page. 4. Add a new user. The user name should be in the form of an email address. Next, make sure that the Capture OnTheGo mobile application is installed and that it is logged on as a known user of the Capture OnTheGo Repository. Now, with your Capture OnTheGo template open in the Connect Designer module, click on the Send COTG Test… button in the toolbar.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-601.html">PAGE 601</a></h6>
<p>validation method" on page 717 and "How to make COTG elements required" on page 595). Get Job Data File on Submit It is possible to test a COTG Form in the Designer and get access to an XML file that contains the submitted data, without having a Workflow configuration to handle the data. This option requires that: l l Workflow has been installed on the local machine, and the Workflow HTTP/Soap Service has been started.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-602.html">PAGE 602</a></h6>
<p>4. Save the XML file to disk. You can view it, create or update a data mapping configuration for it (see "Data mapping configurations" on page 226), and insert the data in a template, using the data mapping configuration (see "Personalizing content" on page 786). Note Checkboxes and Radio buttons that are unchecked will not be submitted to the job data. This is standard behavior in HTML.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-603.html">PAGE 603</a></h6>
<p>Capture On The Go input dummy data values Input Dummy Value Signat ure Receives SVG signature data and the onscreen presentation of that data. Camer a A dummy foto is added, and a (SVG) annotation if that option is set for the widget. Note that the script doesn't look at the PNG/JPG or resolution options, the only option it considers is the annotation option.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-604.html">PAGE 604</a></h6>
<p>Input Dummy Value widget Locale widget en-US * Note that the formatted date and time can be different from the values that the COTG app provides. In the COTG app the formatted date comes from the COTG API, and the formatted date and time normally depend on the locale/region settings on the mobile device. The ISO date and time should be the same as when using the COTG app.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-605.html">PAGE 605</a></h6>
<p>Get submitted data via Workflow Eventually, when a user submits a Capture OnTheGo Form, the data are received by the Workflow HTTP Server Input task (see Workflow Help: HTTP Server Input) that has the same HTTP action as the one specified in the Form's action (see "COTG Forms" on page 569). The Workflow configuration should then handle the submitted data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-606.html">PAGE 606</a></h6>
<p>Form. If you are new to it, spend a few minutes on learning it - it's that easy. For more information, see: https://jquery.com/. and http://learn.jquery.com/. Adding the plugin When you create a template with a COTG Template Wizard (see "Capture OnTheGo template wizards" on page 579), the Designer automatically adds the jQuery library and the COTG library: cotg-2.0.0.js. This also happens when you add a Capture OnTheGo (COTG) element to a template that you didn't start with a COTG template wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-607.html">PAGE 607</a></h6>
<p>Example The following code sets the default timeout and accuracy for Geolocation objects. and the default maximum height and width for Camera widgets. $.fn.cotgGeolocation.defaults.timeout = 6000; // 6 secs $.fn.cotgGeolocation.defaults.enableHighAccuracy = true; $.fn.cotgPhotoWidget.defaults.width = 1024; $.fn.cotgPhotoWidget.defaults.height = 768; $.fn.cotgPhotoWidget.defaults.quality = 60; Reacting to, or triggering, widget events The new COTG plugin introduces custom events for COTG controls.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-608.html">PAGE 608</a></h6>
<p>$('#date1').trigger("show-date-picker.cotg", new Date("2018 01")); }); }); Dynamically adding COTG widgets Capture OnTheGo (COTG) widgets can be added to a Form dynamically, via jQuery. For example: a new Camera element could be added when the user clicks an Add button. This topic explains how to implement this. It is assumed that you have a basic understanding of HTML forms, CSS, JavaScript, and jQuery.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-609.html">PAGE 609</a></h6>
<p>}); }); Creating the widget Now you can start writing the code that constructs, adds and initializes the widget. This code has to be based on jQuery. Constructing the HTML A widget basically is an HTML element with certain attributes and contents. The HTML structure of a widget can be seen on the Source tab after adding the widget to a Form in the Designer. In code, reconstruct the HTML. Make sure to give the new element an ID.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-610.html">PAGE 610</a></h6>
<p>Optionally, while initializing an element, you can make settings for this specific element. These settings get prevalence over the options already specified in the HTML and over the default settings specified in the COTG plugin. The code snippet below initializes a new Camera element (with the ID myCamera) with a number of settings: $('#myCamera').</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-611.html">PAGE 611</a></h6>
<p>addCameraWidget(cameraID); }); }); function getCameraIndex(){ return $("input.camera-dyn").length; } function addCameraWidget(cameraID, value) { if(typeof value == 'undefined') { value = ''; } var html = '<label>Camera' + '<div id="' + cameraID + '" role="cotg.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-612.html">PAGE 612</a></h6>
<p>Adding event listeners In the process of closing and opening a Form two important events are triggered by the COTG library: l l olcotgsavestate. This event is meant for custom scripts to save information when the user closes or submits the Form. It occurs after the state of all static input fields has been saved. olcotgrestorestate. This event allows custom scripts to do something when the Form is reopened. It occurs after all static inputs have been restored.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-613.html">PAGE 613</a></h6>
<p>Note You should not register for these events after the document has loaded (e.g. on the $(document).ready() event), because these events might get triggered before the document is ready. Place your code in a separate JavaScript file and make sure to include that file in the Web context or in the Web section that contains the COTG Form (see "Including a JavaScript file in a Web context" on page 567). For this file, the order in which JavaScript files are included in the template doesn't matter.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-614.html">PAGE 614</a></h6>
<p>Note When you've used jQuery to register for the events - $(window).on() - you must use event.originalEvent in the event handler functions, for example: $(window).on("olcotgsavestate", function(event) { event.originalEvent.detail.state["mywidget"] = "test"; }); Restoring widgets When a COTG Form is reopened, the app restores all input fields and widgets that were already present in the original Form (i.e. the Form deployed via Workflow or sent as test using the Designer).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-615.html">PAGE 615</a></h6>
<p>When a user takes or selects a picture with a Camera widget, the COTG app stores the path to the image that was taken or selected in a hidden input. This is the path to the image on the device that runs the COTG app. On submitting the Form the COTG app replaces this value - the path - with the actual image data. In this example the hidden fields of dynamically added Camera elements have got the .cameradyn class.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-616.html">PAGE 616</a></h6>
<p>'<div class="panel" role="control-wrapper" style="position:relative;">' + '<img role="photo" src="">' + '<input role="photo-data" class="camera-dyn" name="' + cameraID + '" type="hidden" value="' + value + '">' + '</div>' + '<button class="small" role="take-button" type="button">Take now</button>' + '<button class="small" role="pick-button" type="button">Library</button>' + '<button class="small" role="clear-button" type="button">Clear</button>' + '</div></label>'; $('#cameras').</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-617.html">PAGE 617</a></h6>
<p>Event Description clear.cotg Removes the scanned Barcode data. scan.cotg Opens the scanner. The Barcode Scanner broadcasts the following events. Event Description set.cotg This event is fired after Barcode data has been set to the value of the input. Camera cotgPhotoWidget([options]) options Optional. An array containing the desired settings, e.g. {quality: 50, height: 1024, width: 1024}. For any unspecified options the default settings will be used.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-618.html">PAGE 618</a></h6>
<p>Option Description Type Default height The maximum height in pixels Number 864 width The maximum width in pixels. Number 1152 source Which buttons are enabled: Take now (take), Library (pick), or both (takeandpick). String 'takeandpick' scaleimage Scales the image to fit the maximum width or height. The aspect ration is maintained. Boolean true quality Quality of the saved image, expressed as a range of 0-100, where 100 is full resolution with no loss from file compression.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-619.html">PAGE 619</a></h6>
<p>Option Description Type Default stampFontSize The time stamp's font size: small, medium, or large. String 'medium' Events The Camera listens for the following custom events. Event Description clear.cotg Removes the picture. savestate.cotg Saves the path of the current picture to the local storage of the COTG app. restorestate.cotg Restores the state of the widget when the form is reopened in the COTG app, after the app has restored previously entered values of static input fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-620.html">PAGE 620</a></h6>
<p>Events The Date and Formatted Date elements listen for the following custom events. Event Description clear.cotg Removes the date. set.cotg Sets the given date. The date should be given as a Date object, for example: $("#date").trigger("set.cotg", new Date()); // set current date show-datepicker.cotg Opens the Date picker. Optionally, you can provide a date (as a Date object) for the Date picker to be opened with, for example: $('#date1').trigger("show-date-picker.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-621.html">PAGE 621</a></h6>
<p>Event Description set.cotg This event is fired during initialization of the element, after setting its info to the current device. Document ID cotgDocumentId() Initializing a new Document ID puts the current Document ID in the hidden input of the element. Example: $('#myDocID').cotgDocumentId(); Events The Document ID element listens for the following event. Event Description clear.cotg Removes the Document ID. The Document ID element broadcasts the following event. Event Description set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-622.html">PAGE 622</a></h6>
<p>(){ $(this).closest('tr').cotgDeleteRow(); }); Geolocation cotgGeolocation([options]) options Optional. An array containing the desired settings, e.g. {enableHighAccuracy: true, timeout: 3000}. For any unspecified options the default settings will be used. Call cotgGeolocation([options]) on the new Geolocation element with any settings that you want to be different from the defaults. Example: $('#myGeolocation').</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-623.html">PAGE 623</a></h6>
<p>Event Description clear.cotg Removes the Geolocation data. restorestate.cotg Restores the state of the widget when the form is reopened in the COTG app, after the app has restored previously entered values of static input fields. update.cotg Sets the element to the current geolocation. Image & Annotation cotgNoteOnImage() Initializing a new Image & Annotation element prepares it for user interaction. Example: $('#myNoteOnImage').</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-624.html">PAGE 624</a></h6>
<p>Event Description savestate.cotg Saves the annotations. The Image & Annotation element broadcasts the following events. Event Description set.cotg Fired after an annotation has been made. Locale cotgLocale() Initializing a new Locale element sets it to the device's locale. Example: $('#myLocale').cotgLocale(); Events The Locale element listens for the following event. Event Description clear.cotg Removes the Locale data. The Locale element broadcasts the following event.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-625.html">PAGE 625</a></h6>
<p>Repository ID cotgRepositoryId() Initializing a new Repository ID puts the current Repository ID in the hidden input of this element. The Repository ID is based on the currently logged on COTG user. Example: $('#myRepID').cotgRepositoryId(); Events The Repository ID element listens for the following custom events. Event Description clear.cotg Removes the Repositiory ID data. The Repository ID element broadcasts the following event. Event Description set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-626.html">PAGE 626</a></h6>
<p>Field Description draw.cotg Draws the signature on the form (e.g. after a set.cotg or restore-state.cotg event). restorestate.cotg Called when the form is reopened in the COTG app, after the app has restored previously entered values of static input fields. savestate.cotg Saves the signature data to the local storage of the COTG app. set.cotg Sets the given signature. The signature should be given as an SVG string, for example: $(“#signature”).trigger(“set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-627.html">PAGE 627</a></h6>
<p>Events The Time and Formatted Time elements listen for the following custom events. Event Description set.cotg Stores the given time (specified in a Date object). clear.cotg Removes the set time. show-timepicker.cotg Opens the Time Picker. If no time is provided (specified in a Date object), the current time will be shown. User Account cotgUserAccount() Initializing a new User Account element puts the account of the current user in the hidden input of this element. Example: $('#myUser').</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-628.html">PAGE 628</a></h6>
<p>Content elements Once you have created a template, it can be filled with all kinds of elements, from text to barcodes and from tables to fields on a web form. All types of elements are listed on this page. There are several ways to insert elements, see "Inserting an element" on page 631. Each element can have an ID and a class, as well as a number of other properties, depending on the element's type.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-629.html">PAGE 629</a></h6>
<p>see "Using the Text Script Wizard" on page 803 and "Styling and formatting" on page 741. l "Hyperlink and mailto link" on page 721 l "Barcode" on page 634 l Web "Forms" on page 713 and Web "Form Elements" on page 718 l l l l "Whitespace elements: using optional space at the end of the last page" on page 499 (Print context only) "Page numbers " on page 499 (Print context only) Article, Section, Header, Footer, Nav and Aside are HTML5 semantic elements; see https://www.w3schools.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-630.html">PAGE 630</a></h6>
<p>breadcrumbs show the HTML tag of the clicked element, as well as the HTML tags of other elements to which the clicked element belongs. The clicked element is at the end of the line. To edit the HTML text directly: l In the workspace, toggle to the Source tab. On this tab you can view and edit the content of the template in the form of plain text with HTML tags (note the angle brackets: <>). You may add and edit the text and the HTML tags, classes, ID’s and other attributes.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-631.html">PAGE 631</a></h6>
<p>For each type of element, a small selection of attributes is visible on the Attributes pane at the top right. In a multilingual template, the proprietary data-translate attribute marks an element for translation. For more information see "Translating templates" on page 907 and "Tagging elements for translation" on page 909. Changing attributes via script Many attributes can be changed via the user interface. Another way to change attributes is by using a script.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-632.html">PAGE 632</a></h6>
<p>4. Use the Location drop-down (if available) to select where to insert the element. l l l l l l At cursor position inserts it where the cursor is located in the template. Before element inserts it before the HTML element in which the cursor is currently located. For example if the cursor is within a paragraph, the insertion point will be before the <p> tag.* After start tag inserts it within the current HTML element, at the beginning, just after the start tag.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-633.html">PAGE 633</a></h6>
<p>Tip Click the Edges button on the toolbar t emporarily adds a frame to certain elements on the Design tab. These will not .Print or output. There are two more ways to select an element in the content: l Using the Breadcrumbs at the top of the workspace. Breadcrumbs show the HTML tag of the clicked element, as well as the HTML tags of 'parent elements': elements inside of which the clicked element is located. The clicked element is at the end of the line.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-634.html">PAGE 634</a></h6>
<p>Styling and formatting an element Format elements directly Images and other graphical elements can be resized by clicking on them and dragging the resize handles. There are toolbar buttons to color, indent or style text. Other toolbar buttons can left-align, right-align, or rotate graphical elements. The toolbar buttons only represent a selection of the formatting options for each element. There are no toolbar buttons to change an element's margins, or to add a border to it, for example.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-635.html">PAGE 635</a></h6>
<p>Adding a Barcode Note When generating Print output, you can add extra barcodes and OMR marks. The reason why you would do this, is that at merge time more information is available about the actual output document. The page count, for example, is not available at design time. To add barcodes and OMR marks on the fly when generating Print output, select File > Print and check the option Add additional content (see "Page breakdown" on page 1195) in the Print Wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-636.html">PAGE 636</a></h6>
<p>l l After element inserts it after the element in which the cursor is currently located. For example if the cursor is within a paragraph, the insertion point will be after the end tag of the paragraph (</p>).* Replace inserts it in place of the currently selected element. (This option is not available when inserting content in a Master Page.) * If the current element is located inside another element, use the Elements drop-down to select which element is used for the insertion location.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-637.html">PAGE 637</a></h6>
<p>A barcode is always added with the barcode type's default properties and dimensions, but they can easily be changed; see "Barcode type and properties" below. Changing a barcode Barcode script The barcode script determines which value is fed to the barcode generator. Double-click the script on the Scripts pane to change which field or fields are added to the barcode value.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-638.html">PAGE 638</a></h6>
<p>l Code 11, see "Code 11, Code 93, Industrial 2 of 5, Interleaved 2 of 5, Matrix 2 of 5" on page 670 l "Code 39" on page 646 l "Code 39 extended" on page 647 l Code 93, see "Code 11, Code 93, Industrial 2 of 5, Interleaved 2 of 5, Matrix 2 of 5" on page 670 l "Code 93 extended" on page 651 l "Code 128" on page 653 l "Data Matrix" on page 655 l EAN-8, EAN-13, see "UPC-A, UPC-E, EAN-8, EAN-13" on page 688 l "GS1 DataMatrix" on page 660 l "GS1-128" on page 662 l l Industrial 2 of 5, see "C</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-639.html">PAGE 639</a></h6>
<p>Australia Post, Japan Post, KIX, USPS IMb Australia Post, Japan Post, KIX and USPS IMb are some of the types of barcodes that can be added to a template; see "Barcode" on page 634. In PlanetPress Connect versions prior to 2019.2 the USPS IMb barcode was called "OneCode". The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 635. Initially the barcode will have the barcode type's default properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-640.html">PAGE 640</a></h6>
<p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-641.html">PAGE 641</a></h6>
<p>Configuration type Use the drop-down to select the format type used when creating the barcode: only full range format, only compact formats, or any format. Preferred configuration Use the drop-down to select the preferred format for the barcode. Note that the barcode generator may choose a different format if the data cannot be represented by the preferred format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-642.html">PAGE 642</a></h6>
<p>Tilde processing Check this option to process tilde characters in the data as special characters. (See the Java4less Barcodes Guide to learn what the tilde character can be used for.) Note that with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-643.html">PAGE 643</a></h6>
<p>Barcode properties This topic lists the properties of the Codabar barcode. For the properties of other barcode types, see "Barcode type and properties" on page 637. Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Start Char and Stop Char Use the drop-down to select the start and stop character for the barcode, which defines the encoding mode. Available characters are A, B, C.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-644.html">PAGE 644</a></h6>
<p>w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-645.html">PAGE 645</a></h6>
<p>For the properties of other barcode types, see "Barcode type and properties" on page 637. Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-646.html">PAGE 646</a></h6>
<p>l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. Code 39 Code 39 and Code 39 extended are two of the barcode types that can be added to a template.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-647.html">PAGE 647</a></h6>
<p>l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height. l Proportionally: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching. Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-648.html">PAGE 648</a></h6>
<p>The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 635. Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-649.html">PAGE 649</a></h6>
<p>Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated. Tilde processing Check this option to process tilde characters in the data as special characters. (See the Java4less Barcodes Guide to learn what the tilde character can be used for.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-650.html">PAGE 650</a></h6>
<p>Code 11, Code 93, Industrial 2 of 5, Interleaved 2 of 5, Matrix 2 of 5 Code 11, Code 93, Industrial 2 of 5, Interleaved 2 of 5, and Matrix 2 of 5 are a few of the barcode types that can be added to a template. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 635. Initially the barcode will have the barcode type's default properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-651.html">PAGE 651</a></h6>
<p>l Proportionally: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching. Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-652.html">PAGE 652</a></h6>
<p>Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu. Barcode properties This topic lists the properties of the Code 93 extended barcode. For the properties of other barcode types, see "Barcode type and properties" on page 637.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-653.html">PAGE 653</a></h6>
<p>The font size is given in points (pt). Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-654.html">PAGE 654</a></h6>
<p>Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-655.html">PAGE 655</a></h6>
<p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-656.html">PAGE 656</a></h6>
<p>Guide to learn what the tilde character can be used for). Any tilde that needs to be included in the output must be escaped by adding another tilde (either "~~", or "7E7E" if the Hex input option is enabled). This can be done with a replace() call in the Barcode script, after expanding the script. Hex Input For optimized mailings, German Post requires the supplied data for the Data Matrix barcode to be hexadecimal input. Check this option if your input data is a hexadecimal code.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-657.html">PAGE 657</a></h6>
<p>l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height. l Proportionally: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching. Tilde processing Check this option to process tilde characters in the data as special characters. (See the Java4less Barcodes Guide to learn what the tilde character can be used for.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-658.html">PAGE 658</a></h6>
<p>Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu. Note that these barcode types process tilde characters in the data as special characters. See the Java4less Barcodes Guide to learn what the tilde character can be used for.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-659.html">PAGE 659</a></h6>
<p>supplement data will be skipped and the additional barcode will not be rendered. Note When the chosen supplement type doesn't match the data, the supplement data will be skipped and the additional barcode will not be rendered. l l Height Factor: This is the relative height of the supplement's bars compared to the normal bars. Space Before : Defines the space between the main symbol and the supplement, in cm.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-660.html">PAGE 660</a></h6>
<p>GS1 DataMatrix GS1 DataMatrix is one of the types of barcodes that can be added to a template; see "Barcode" on page 634. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 635. Initially the barcode will have the barcode type's default properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-661.html">PAGE 661</a></h6>
<p>l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height. Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated. Tilde processing Check this option to process tilde characters in the data as special characters.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-662.html">PAGE 662</a></h6>
<p>w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-663.html">PAGE 663</a></h6>
<p>l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height. Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated. Tilde processing Check this option to process tilde characters in the data as special characters.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-664.html">PAGE 664</a></h6>
<p>Code 11, Code 93, Industrial 2 of 5, Interleaved 2 of 5, Matrix 2 of 5 Code 11, Code 93, Industrial 2 of 5, Interleaved 2 of 5, and Matrix 2 of 5 are a few of the barcode types that can be added to a template. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 635. Initially the barcode will have the barcode type's default properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-665.html">PAGE 665</a></h6>
<p>l Proportionally: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching. Add Checksum When checked, PlanetPress Connect will calculate a Checksum character and add that to the result of the Barcode script. If the value to be encoded is longer than 10 digits, a second check character will be calculated.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-666.html">PAGE 666</a></h6>
<p>Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu. Note that barcodes of these types process tilde characters (~) in the data as special characters. See the Java4less Barcodes Guide to learn what the tilde character can be used for.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-667.html">PAGE 667</a></h6>
<p>Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size. The font size is given in points (pt). Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-668.html">PAGE 668</a></h6>
<p>Note that barcodes of these types don't process tilde characters (~) in the data as special characters. Barcode properties This topic lists the properties of the barcode types Australia Post, Japan Post, KIX and UPS IMb. For the properties of other barcode types, see "Barcode type and properties" on page 637. Height, width and spacing The height, width and spacing of the barcode are all measured in pixels (38 dpi). l Bar height: The height of the (shorter) bars.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-669.html">PAGE 669</a></h6>
<p>l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. Australia Post, Japan Post, KIX, USPS IMb Australia Post, Japan Post, KIX and USPS IMb are some of the types of barcodes that can be added to a template; see "Barcode" on page 634. In PlanetPress Connect versions prior to 2019.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-670.html">PAGE 670</a></h6>
<p>Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l l None: The barcode is rendered based on the module width. Proportional: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching. Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-671.html">PAGE 671</a></h6>
<p>Note that barcodes of these types process tilde characters (~) in the data as special characters. See the Java4less Barcodes Guide to learn what the tilde character can be used for. Barcode properties This topic lists the properties of the following barcode types : l Code 11 l Code 93 l Industrial 2 of 5 l Interleaved 2 of 5 l Matrix 2 of 5 For the properties of other barcode types, see "Barcode type and properties" on page 637. Module width Specifies the width of the narrow bars in centimeters.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-672.html">PAGE 672</a></h6>
<p>The font size is given in points (pt). Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-673.html">PAGE 673</a></h6>
<p>Mode PlanetPress Connect supports several modes; for an explanation of these modes see the MaxiCode page on Wikipedia. Tilde processing Check this option to process tilde characters in the data as special characters. (See the Java4less Barcodes Guide to learn what the tilde character can be used for.) Note that with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-674.html">PAGE 674</a></h6>
<p>Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-675.html">PAGE 675</a></h6>
<p>Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. PDF417 PDF417 is one of the types of barcodes that can be added to a template; see "Barcode" on page 634.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-676.html">PAGE 676</a></h6>
<p>level 8 (maximum error correction). Recommended error correction levels are between level 2 and 5, but the optimal value depends on the amount of data, printing quality of the PDF417 symbol and decoding capabilities of the scanner. Nr. of Columns The number of data columns can vary from 3 to 30. Nr. of Rows A PDF417 bar code can have anywhere from 3 to 90 rows. Bar height Defines the height of the bars for a single row measured in pixels drawn.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-677.html">PAGE 677</a></h6>
<p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-678.html">PAGE 678</a></h6>
<p>Module width Specifies the width of the narrow bars in centimeters. Changing this value to a higher value will make the barcode bigger when Scale is set to None. Bar height You can set the height (in cm) of the short bars and the tall bars in the Postnet barcode. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-679.html">PAGE 679</a></h6>
<p>l PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. QR Code A QR Code is one of the types of barcodes that can be added to a template; see "Barcode" on page 634. The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 635. Initially the barcode will have the barcode type's default properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-680.html">PAGE 680</a></h6>
<p>l l Numeric: 10 bits per 3 digits, with a maximum of 7089 numerical characters. Alphanumeric: 11 bits per 2 characters, with a maximum of 4296 alphanumerical characters. l Byte: 8 bits per character, with a maximum of 2953 characters. l Kanji: 13 bits per character, with a maximum of 1817 characters. Extended Channel Interpretation (ECI) This setting enables data using character sets other than the default set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-681.html">PAGE 681</a></h6>
<p>Tilde processing Check this option to process tilde characters in the data as special characters. (See the Java4less Barcodes Guide to learn what the tilde character can be used for.) Note that with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-682.html">PAGE 682</a></h6>
<p>The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 635. Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-683.html">PAGE 683</a></h6>
<p>Color The Color group allows you to choose a different Barcode color (instead of black) and Background color (instead of white), by typing a hexadecimal color value (see for example w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-684.html">PAGE 684</a></h6>
<p>Height, width and spacing The height, width and spacing of the barcode are all measured in pixels (38 dpi). l Bar height: the height of the (shorter) bars. l Extended bar height: the total height of the extended bars. l Bar width: the width of the bars. l Spacing: the distance between the bars. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-685.html">PAGE 685</a></h6>
<p>Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-686.html">PAGE 686</a></h6>
<p>l l None: The barcode is rendered based on the module width. Proportional: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching. Human Readable Message When this option is checked, PlanetPress Connect shows a human readable text below or above the barcode, as defined using the Text Position, using the specified font and font size. The font size is given in points (pt).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-687.html">PAGE 687</a></h6>
<p>Barcode properties This topic lists the properties of the barcode types Royal Mail 4-State Mailmark C and Royal Mail 4-State Mailmark L. For the properties of other barcode types, see "Barcode type and properties" on page 637. Height, width and spacing The height, width and spacing of the barcode are all measured in pixels (38 dpi). l Bar height: The height of the (shorter) bars. l Extended bar height: The total height of the extended bars. l Bar width: The width of the bars.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-688.html">PAGE 688</a></h6>
<p>Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format. This has a slightly lower quality than SVG but is usually generated faster and will display properly in Email output. UPC-A, UPC-E, EAN-8, EAN-13 UPC-A, UPC-E, EAN-8 and EAN-13 are a few of the barcode types that can be added to a template.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-689.html">PAGE 689</a></h6>
<p>Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l None: The barcode is rendered based on the module width. l Fit to box: The barcode is stretched to fit the parent box in both width and height. l Proportionally: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching. Supplement UPC-A, UPC-E, EAN-13, and EAN-8 may all include an additional barcode to the right of the main barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-690.html">PAGE 690</a></h6>
<p>w3school's color picker). When black is a composite of CMYK or RGB values, it may incur a color click charge on some printers. Check the Output in Grayscale option to make sure that pure black is used. Output format Defines how the barcode is output on the page. There are two possible formats: l l SVG: Vector format. This is usually of higher quality, but may take longer to generate and is not compatible with Email output. PNG: Binary rasterized format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-691.html">PAGE 691</a></h6>
<p>l Bar height: The height of the (shorter) bars. l Extended bar height: The total height of the extended bars. l Bar width: The width of the bars. l Spacing: The distance between the bars. Scale Defines if and how the rendered barcode is scaled in relation to the parent element: l l None: The barcode is rendered based on the module width. Proportional: The barcode is stretched up to where it fits either the width or height of the parent box, whichever requires the less stretching.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-692.html">PAGE 692</a></h6>
<p>The barcode can be added either using the Barcode toolbar button or through selecting Insert > Barcode on the menu; see "Adding a Barcode" on page 635. Initially the barcode will have the barcode type's default properties. To change those properties, such as the scale and color, open the Barcode properties dialog: right-click the barcode (on the Design tab in the Workspace) and select the Barcode... option in the context menu.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-693.html">PAGE 693</a></h6>
<p>Tip Wrapping elements in a box (or in a semantic HTML element) makes it easier to target them in a script or in a style sheet. Place the cursor in the element or select multiple elements. Then, on the menu, click Insert > Wrap in Box. You can now use the wrapper element as a script's or style's selector; see "Using the Text Script Wizard" on page 803 and "Styling and formatting" on page 741. Tip With the Copy fit feature, text can automatically be scaled to the available space in a Box or Div.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-694.html">PAGE 694</a></h6>
<p>Dynamically changing the position A Positioned Box has the following attributes: l anchor defines the page number (starting by 0) the box is placed on l offset-x defines the horizontal position of the box relative to its container l offset-y defines the vertical position of the box relative to its container. These attributes can be set in a script. The following script dynamically changes the position of a Positioned Box in a Print context by setting the offset-x and offset-y values. results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-695.html">PAGE 695</a></h6>
<p>Adding an Inline Box To insert an inline box, use the icon on the toolbar. Inline Boxes can be resized using the handles on the sides and corner. They can be styled using the Format > Box menu item, through the CTRL+M keyboard shortcut or through the CSS files; see "Styling and formatting" on page 741 and "Styling templates with CSS files" on page 743. Positioning an Inline Box Initially an Inline Box will float to the left.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-696.html">PAGE 696</a></h6>
<p>Div The Div is the element used to create both Positioned Boxes and Inline Boxes. By default, a Div element reacts pretty much like a paragraph (<p>) or an inline box set to 'no float' except that it can be resized directly. Just like Positioned Boxes and Inline Boxes, Div elements can be styled using the Format > Box menu item, through the CTRL+M keyboard shortcut or through the CSS files; see "Styling and formatting" on page 741 and "Styling templates with CSS files" on page 743.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-697.html">PAGE 697</a></h6>
<p>underlying configuration: Programmatically configure a Chart object. For another example see this How-to: Put one slice per detail record in a Pie Chart. Note As of PlanetPress Connectversion 2018.1, the way charts can be compiled and presented has been greatly improved. As a consequence, charts made with a version of Connect prior to 2018.1 may not be converted correctly when opened in a later version.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-698.html">PAGE 698</a></h6>
<p>l l l Before end tag inserts it within the current HTML element, at the end, just before the end tag.* After element inserts it after the element in which the cursor is currently located. For example if the cursor is within a paragraph, the insertion point will be after the end tag of the paragraph (</p>).* Replace inserts it in place of the currently selected element. (This option is not available when inserting content in a Master Page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-699.html">PAGE 699</a></h6>
<p>l A Div element. It has a data-amchart attribute, as you can see when you select the chart and open the Source view in the Workspace. The data-amchart attribute contains settings for how the data is displayed. These settings are made via the chart's properties (see "Enhancing a charts' design" on page 702). l A script. The script determines which data are displayed in the chart, with which colors and labels. The script can be edited any time; see "Selecting data for a Business Graphic" below.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-700.html">PAGE 700</a></h6>
<p>1. Use the Input Type drop-down to select the source of the data for the Chart: l l Data Fields: The data originate from data fields in the main record. The chart will have the same number of items for each record. Data Table, the data are taken from a detail table that you select using the Detail Table drop-down. Note In Pie Charts, only data from the first record in the detail table are used.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-701.html">PAGE 701</a></h6>
<p>5. Select a color for each of the selected fields. Click on the color to open the Edit Color dialog (see "Color Picker" on page 931). Note Colors defined in the Chart Properties dialog override the colors set in the script. To open the Chart Properties dialog, right-click the chart after adding it, and select Chart.... See: "Enhancing a charts' design" on the facing page. 6. Use the Move Up and Move Down buttons to change the order of the fields, which is reflected in the chart.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-702.html">PAGE 702</a></h6>
<p>When creating a data mapping configuration (see "Data mapping workflow" on page 248), it is recommended to arrange data in a detail table in such a way that it matches this 'one series per record, one bar/point per data field' approach. Occasionally you may find that data in a detail table does not match this approach, and that it would be a better fit if the chart had one series of bars/points for each selected detail data field instead, and one bar/point for each record.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-703.html">PAGE 703</a></h6>
<p>Start by opening the Chart Properties dialog. Right-click the chart (in the template, or in the Outline pane) and select Chart. Every tab menu in the Chart Properties dialog, except the last one, gives direct access to a number of layout options.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-704.html">PAGE 704</a></h6>
<p>"rotate": true, ... } Properties of the Legend (listed here: https://docs.amcharts.com/3/javascriptcharts/AmLegend) should go in the legend section in the JSON: ... "legend": { "position": "right" }, The Source tab also lets you change properties that are available in either the Script Wizard or other tabs of the Chart Properties dialog.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-705.html">PAGE 705</a></h6>
<p>Using themes The amCharts library supports working with themes. The default themes are: light, dark, black, patterns, and chalk. All except the 'patterns' theme can be used in Connect templates. Here's how to do that. 1. Add the theme to the top of the JSON on the Source tab of the Chart Properties diaog. For example: { "theme": "light", ... This setting overrides any color settings made in the Chart Script wizard and on the other tabs of the Chart Properties dialog. 2.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-706.html">PAGE 706</a></h6>
<p>Barcode Scanner The Barcode Scanner element adds a button to trigger the device to scan a barcode. A very large variety of barcode types are supported. Once the barcode has been scanned, the data from the barcode will be added to the COTG Form and submitted along with it. Note Using the Barcode Scanner element requires the installation of the ZXing Barcode Scanner application on Android devices. The application returns the barcode data after scanning.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-707.html">PAGE 707</a></h6>
<p>To omit the Take now or Library button, edit the Camera element's properties: right-click the Camera element after adding it to the form, select Camera properties and then use the Source drop-down to select which buttons will be available: Take, Pick from library, or both. Annotations Annotations can make a picture much more informative: an arrow, showing in which direction a car was driving; a circle, where the car has been damaged...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-708.html">PAGE 708</a></h6>
<p>Time stamp A time stamp can be added to each picture taken. Right-click the Camera element after adding it to the form, select Camera properties, and then check Add Time Stamp. The time stamp will be added to the bottom left of the picture, with medium font size, and long date format (for example: 6/15/2009 1:45 PM). These settings can only be changed via the Source tab or in code; see "Using the COTG plugin: cotg-2.0.0.js" on page 605 and the Capture OnTheGo API: "Camera" on page 617.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-709.html">PAGE 709</a></h6>
<p>When the form is submitted, the date data is sent as plain text. A Formatted Date element submits the date in two formats: in the format that depends on the device's regional and language settings and in the ISO format mentioned above (using a hidden field). A Date element sends the date in the ISO format only. Device Info The Device Info Element adds a field that contains some information about the device (phone or tablet) that is submitting the COTG Form.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-710.html">PAGE 710</a></h6>
<p>High accuracy By default, devices attempt to retrieve a position using network-based methods. To tell the framework to use more accurate methods, such as satellite positioning, the High Accuracy setting has to be enabled on the Geolocation element. To make this setting, right-click the Geolocation element (or select it on the Outline pane) after adding it to the form, select Geolocation properties and check the High Accuracy option.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-711.html">PAGE 711</a></h6>
<p>Signature The Signature Element adds a signature box to a COTG form. These signatures are filled in via touch input, either with a finger or capacitive pen. Touching the signature box opens up a fullscreen box used to sign (generally more useful in Landscape mode depending on the device); after confirming, the dialog saves the data into the Form. Signature data is transmitted in SVG plain text format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-712.html">PAGE 712</a></h6>
<p>Date The Date element inserts the current system date, optionally making it dynamic so that it updates whenever the template is viewed or produces output. Adding a date To add a Date element, use the Insert > Date option in the menus. A dialog appears with the following controls: l l l Language: Use the drop-down to select which language the date should be displayed in. Update Automatically: Check to update the date automatically when the template is viewed or produces output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-713.html">PAGE 713</a></h6>
<p>Formatting an automatically updating date The script added to automatically update the date uses the short date format. To change this: 1. Double-click the date script in the Scripts pane. 2. Delete the first line of the script. 3. On the second line, delete what comes after format and change format to formatter (see "formatter" on page 1331). 4.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-714.html">PAGE 714</a></h6>
<p>the Form's properties, validation method and location, but doesn't allow you to specify fields. If you choose this method, skip step 8 and 9 of this procedure and add fields after inserting the Form (see "Adding elements to a Form" on page 558). 3. Add an ID and/or a class. ID's and classes are particularly useful with regard to variable data (see "Personalizing content" on page 786) and styling (see "Styling templates with CSS files" on page 743). 4.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-715.html">PAGE 715</a></h6>
<p>validation as it is browser independent. The necessary JQuery files will be added to the JavaScript folder on the Resources pane when the form is inserted. 8. Under Fields, click the Add button and click on the desired field type to add a field of that type; see "Form Elements" on page 718. Note A Fieldset is not available in the Form Wizard, because a Fieldset itself can contain multiple different fields. Add the Fieldset after inserting the Form; see "Adding elements to a Form" on page 558. 9.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-716.html">PAGE 716</a></h6>
<p>Note: HTML has some restrictions as to which types of elements are allowed as children of other elements. For example, a paragraph element is not allowed to have children that are block level elements - like a Div or a Table. If inserting content at the selected location would produce invalid HTML the final result may be different than expected. For example, when you insert a Div into a paragraph, the paragraph gets split in two. This means you end up with two paragraphs with the Div in between. 12.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-717.html">PAGE 717</a></h6>
<p>Changing a Form's validation method In Connect PlanetPress Connect, there are two ways in which a Form's input can be validated: l l The Browser validation method leaves it up to the browser to validate the user input. When adding fields to the Form (see the next step) you can only make fields required and set the maximum length as an additional requirement for some fields. JQuery Validation validates input using JQuery scripts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-718.html">PAGE 718</a></h6>
<p><input id="email1" name="email1" data-custom-message="Enter a valid email address." type="email" required=""> Validation in Connect 1.0.0 In Connect 1.0.0, the validation method of the template was stored using the names "standard" and "custom". Standard has changed to "browser" and custom is now "jquery-validation". When you open a template made with that version of the software, the template will be migrated to use the new attribute values for the data-validation-method attribute of the <form> element.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-719.html">PAGE 719</a></h6>
<p>Text The Text element is a simple <input> element with the type text. It accepts any alphanumerical characters, including special characters. The string is HTML-encoded before it is submitted to the server. Email The Email element is a text input field that accepts only email addresses in a valid format. URL The URL element is a text input field that accepts only URLs (a web page address) in a valid format. Password The Password element is a password field that accepts any alphanumerical characters.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-720.html">PAGE 720</a></h6>
<p>element, you can add a label to that element; see "Adding elements to a Form" on page 558. To change a label after inserting the Form, simply click it and start typing. Checkbox A Checkbox element sends information to the server whether it is checked (true) or not (false). When adding a Checkbox you can set its initial state and its value. The contents of the value property do not appear in the user interface.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-721.html">PAGE 721</a></h6>
<p>The submit name of a Radio Button indicates to which Radio Button Group the Radio Button belongs. Select A Select element is a drop-down list with multiple entries from which the user can select only one option. When adding a Select to a Form you can type the options to be given in the dropdown list and the values related to them. Only the value of the selected option will be sent to the server on submitting the form.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-722.html">PAGE 722</a></h6>
<p>Note Hyperlinks - both external and internal - are not preserved when printing multiple pages on the same sheet (see "Imposition options" on page 1181). HTML element: a When you add elements, such as text, images or a table, to the content of a template, you are actually constructing an HTML file. It is possible to edit the source of the HTML file directly in the Designer; see "Editing HTML" on page 629. The HTML tag of a hyperlink or mailto-link is <a>. This is sometimes called an anchor tag.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-723.html">PAGE 723</a></h6>
<p>4. For a URL: l URL: o External hyperlink: Enter a valid, well-formed URL to link to. It must start with the protocol, such as http:// or https://. o Internal hyperlink: Enter an ID, preceded by a hash; for example: #myID. The link will point to an element with that ID. Note An internal hyperlink may point to an element in another section. Just make sure that there is only one element in the document with the specified ID. l Target: use the drop-down or type in the target for the link.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-724.html">PAGE 724</a></h6>
<p>How to add or modify a hyperlink is described in a how-to; see How to dynamically insert a hyperlink. This implies writing a script. For information about scripts, see "Writing your own scripts" on page 853. Adding a personalized link Personalized URLs (pURLs) are links that are tailor-made for a specific purpose, generally for individual clients.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-725.html">PAGE 725</a></h6>
<p>Ways to use images In templates, both imported images and external images can be used (see "Adding images" on the facing page and "Resources" on page 466). Once added to the content of a template, an image can be resized (see "Resizing an image" on page 768) and alternate text can be linked to it (see "Setting an alternate text" on page 730). Tip Using images in an Email template? See "Using images in email campaigns: tips" on page 519.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-726.html">PAGE 726</a></h6>
<p>Filling optional whitespace Conditional content and dynamic tables, when used in a Print section, may or may not leave an empty space at the bottom of the last page. To fill that space, if there is any, an image or advert can be used as a 'whitespace element'; see "Whitespace elements: using optional space at the end of the last page" on page 499. HTML tag: img When you add elements, such as text, images or a table, to the content of a template, you are actually constructing an HTML file.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-727.html">PAGE 727</a></h6>
<p>Imported or external images In templates, both imported images and external images can be used. Imported images are images that are saved within the template file. To import images into a template and add them to the content, you can use the drag-and-drop method or the Select Image dialog (both are explained below). External images are either located on a specific website (URL), or in a folder on a hard drive that is accessible from your computer.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-728.html">PAGE 728</a></h6>
<p>1. Position the cursor in the content where you want the image to be inserted. 2. On the Insert menu, click Image. Or, click the Insert Image button on the toolbar. The Select Image dialog appears. l Click Resources, Disk or Url, depending on where the image is located. l l l Resources lists the images that are present in the Images folder on the Resources pane. Disk lists image files that reside in a folder on a hard drive that is accessible from your computer.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-729.html">PAGE 729</a></h6>
<p>which the template's output is produced. External images are updated (retrieved) at the time the output is generated. 3. If the image is a PDF file that consists of more than one page, select the desired page. Note The number of pages in a PDF file cannot be determined via the HTTP and HTTPS protocols. If you wish to use a page other than page 1 in a remote PDF, check the option Save with template; then click OK and reopen the dialog. Next, on the Resources tab, select the PDF, and select a page. 4.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-730.html">PAGE 730</a></h6>
<p>Moving an image An image that is added to a section behaves like a character and is part of the text flow. To move it, simply click the image and drag and drop it somewhere else in the text flow. To learn how to wrap text around it, see "Wrapping text around an image" on page 769. How to make an image stay at a certain position (like any image added to a Master Page) is explained here: "Pulling an image out of the text flow" on page 769.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-731.html">PAGE 731</a></h6>
<p>To set an alternative text, click the image and enter the alternate text in the Alternate text field on the Attributes pane at the top right. Using a CSS gradient to create an image CSS gradients are a new type of image added in the CSS3 Image Module. CSS gradients let you display smooth transitions between two or more specified colors, while repeating gradients let you display patterns. This way, using image files for these effects can be avoided, thereby reducing download time and bandwidth usage.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-732.html">PAGE 732</a></h6>
<p>The HTML tag of a Table is <table>. Tables are divided into table rows with the <tr> tag. Table rows are divided into table data with the <td> tag. A table row can also be divided into table headings with the <th> tag. The tags <thead>, <tbody> and <tfoot> can be used to group the header, body, or footer content in a table, respectively. For information about HTML tables and a list of attributes, see https://www.w3schools.com/html/html_tables.asp. Inserting a Table 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-733.html">PAGE 733</a></h6>
<p>l l After element inserts it after the element in which the cursor is currently located. For example if the cursor is within a paragraph, the insertion point will be after the end tag of the paragraph (</p>).* Replace inserts it in place of the currently selected element. (This option is not available when inserting content in a Master Page.) * If the current element is located inside another element, use the Elements drop-down to select which element is used for the insertion location.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-734.html">PAGE 734</a></h6>
<p>Deleting a header or footer To delete a header or footer, simply right-click the header or footer and select Row > Delete on the shortcut menu. If the deleted element was targeted by a script, you will be asked if you want to delete the script as well. Rows and columns Adding a row or column To add a row or column to an existing Table, click in a cell.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-735.html">PAGE 735</a></h6>
<p>for which resizing is allowed. l l If the position of the Table isn't absolute, right-click the Table and on the shortcut menu, select Convert to absolute. (This option isn't available for Tables on a Master Page, as they must always have an absolute position, or be located inside another element with an absolute position.) Select the Table (see "Selecting an element" on page 632) and then, on the Attributes pane, check the option Allow resizing.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-736.html">PAGE 736</a></h6>
<p>l Press Enter to insert a new paragraph. l Press Shift+Enter to insert a line break. Alternatively, use the Insert Lorem Ipsum toolbar button to insert dummy text, or copy-paste text into the template. Select Paste as Plain Text from the Edit menu or the contextual menu to insert the text without any HTML styles or formatting. Text that precedes or follows the value of a data field can be added by the Text Script Wizard; see "Using the Text Script Wizard" on page 803.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-737.html">PAGE 737</a></h6>
<p>HTML element: p, h, li and others When adding elements, such as text, images or a table, to the content of a template, you are actually constructing an HTML file, which you can see and edit on the Source tab (see also: "Editing HTML" on page 629). In HTML, text can be contained in many different elements: paragraphs, span elements, line items and table cells, for example. The HTML tag of a paragraph is <p>. The paragraph should be followed by a closing tag: </p>.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-738.html">PAGE 738</a></h6>
<p>Tip It is possible to open and edit any HTML or JSON file in the Designer: select File > Open, select All files (*.*) as the file type and then select a HTML or JSON file. About JSON Snippets JSON Snippets are snippets that contain pieces of JSON data instead of HTML. Just like HTML snippets, JSON snippets are stored in the Snippets folder on the Resources pane, but their file name should end in '.json'.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-739.html">PAGE 739</a></h6>
<p>To add a remote snippet: 1. Right-click the Snippets folder on the Resources pane, and click New Remote Snippet. 2. Enter a name for the file as it appears in the Snippets folder. This name is shown in the Snippets folder with the .rhtml file extension. 3. Enter the URL for the remote resource. This must be a full URL, including the http:// or https:// prefix, domain name, path and file name. Note Remote snippets may contain other resources, such as images.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-740.html">PAGE 740</a></h6>
<p>Creating a snippet To turn a part of a letter, email or web pageinto a snippet for reuse in the content of a template: 1. Open the section and select the part or parts that should be saved to a snippet. 2. Right-click the selection, point to Snippet and click Create to copy the selected part to a new snippet, or Create Shared Content to create the new snippet and replace the selected part with a reference to the new snippet. 3. Give the snippet a name.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-741.html">PAGE 741</a></h6>
<p>Renaming a snippet To rename a snippet, right-click it on the Resources pane in the Snippets folder and select Rename. If you rename a snippet that was inserted into a section as shared content, you need to update the reference to the snippet manually: 1. Open the section in which the snippet is used. 2. Switch to Source view. 3. Look for the <article> element in the HTML and replace the old snippet name with the new name in the source attribute.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-742.html">PAGE 742</a></h6>
<p>Whether applied through style sheets or through local formatting, behind the scenes all layout properties in the Designer are CSS properties. When you format an element locally, an inline style rule is added to the element. Note that where local formatting conflicts with a formatting rule for the same element in one of the style sheets, the local formatting rule gets priority; the rule in the style sheet will be ignored. It is highly recommended to use style sheets in templates right from the start.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-743.html">PAGE 743</a></h6>
<p>The locale setting influences how dates, numbers and amounts of money are displayed; see "Locale" on page 782. Styling templates with CSS files The Layout toolbar and the Format menu offer many possibilities to style every piece of a template. However, styling every single element, one after another, is a lot of work and, more importantly, can result in a template with a messy mix of styles that isn’t easy to maintain and lacks consistent design.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-744.html">PAGE 744</a></h6>
<p>On this tab you can view and edit the content of the template in the form of plain text with HTML tags (note the angle brackets: <>). You may add and edit the text and the HTML tags, classes, ID’s and other attributes. To learn more about HTML, see for example https://developer.mozilla.org/enUS/docs/Web/Guide/HTML/Introduction and http://www.w3schools.com/html/default.asp. Many video courses and hands-on courses about HTML (and CSS) are offered on the Internet as well, some for free.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-745.html">PAGE 745</a></h6>
<p>Adding CSS files To add a CSS file of your own, open an Explorer window, drag the file to the Resources pane and drop it on the Stylesheets folder. In case the CSS file has references to specific images, you can drag/drop or copy/paste those images into the Stylesheets folder as well. To create a new CSS file, right-click the Stylesheet folder on the Resources pane and select New Stylesheet. You can also import one or more CSS file from another template using the "Import Resources dialog" on page 942.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-746.html">PAGE 746</a></h6>
<p>1. Right-click the Stylesheet folder on the Resources pane, and click New Remote Stylesheet. 2. Enter a name for the file as it appears in the Stylesheet resources. For better management, it's best to use the same filename as the remote resource. 3. Enter the URL for the remote resource. If the file is located on an external web server, this must be a full URL, including the http:// or https:// prefix, domain name, path and file name.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-747.html">PAGE 747</a></h6>
<p>Tip To refresh the remote resources in a Designer view, use the Refresh option in the menu (View > Refresh) or the Refresh button at the top of the Workspace. Using a Sass file A CSS preprocessor is a CSS extension language that allows you to enhance CSS with code (variables, for example) and then compile it into plain CSS. CSS Preprocessor Sass is integrated in Connect. For more information about Sass, see: Sass website.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-748.html">PAGE 748</a></h6>
<p>preceded by a dot, e.g. .small. l An ID: #id. An ID is always preceded by #, e.g. #sender. When you create an ID, choose a name that indicates what the ID is used for, e.g. #sender would refer to the HTML element with information about the sender. Note Each ID should be unique and can only be used once in each section. Note Do not give an element the ID 'pages' or the class name 'dynamic'. These are reserved words. Using them as an ID or class name leads to undesirable effects.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-749.html">PAGE 749</a></h6>
<p>Editing plain CSS l l Click the button Advanced in any property sheet to open a CSS property editor. Type CSS properties at the left and values at the right. In the Resources pane at the left, double-click the global stylesheet or the stylesheet for the relevant context. The file opens in the workspace in the middle. A list of all CSS properties and their possible values can be found here: https://www.w3schools.com/cssref/. Note Block comments (/* ...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-750.html">PAGE 750</a></h6>
<p>Adding a class or ID to an HTML element 1. Select the element (see "Selecting an element" on page 632). 2. On the Attributes pane, type the ID and/or class. Type the ID without the preceding # and class names without a dot. Note Note: Elements can have multiple classes. Separate the class names with a space (eg. “red small”). Alternatively, after selecting an element, you can click the Source tab at the bottom of the workspace. The selected element will be highlighted in the source.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-751.html">PAGE 751</a></h6>
<p>gives it less weight. In case of conflicting rules, style sheets read later will override previous ones. Note Style sheets are applied in the order in which they are included in a section. The styles in each following style sheet add up to the styles found in previously read style sheets. When style sheets have a conflicting rule for the same element, class or ID, the last style sheet ‘wins’ and overrides the rule found in the previous style sheet. Note Style sheets that are linked to (i.e.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-752.html">PAGE 752</a></h6>
<p>A crossed-out style rule signals that it was overruled by another style rule. This happens when: l l A more specific, and therefore more important rule, is encountered for the same element. See "Using a more specific CSS rule" below to learn more about the specificity of style rules. A rule with the same importance is read after the first rule. Not only is the order of the rules in a CSS file important, but also the order in which the style sheets are read.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-753.html">PAGE 753</a></h6>
<p>Rules for HTML elements (p, table, li etc.) are general rules. Rules for classes, pseudo classes, and elements with a certain attribute (.class, :hover, [target]) are more specific. Rules for elements with a certain ID are even more specific. The most specific are inline styles.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-754.html">PAGE 754</a></h6>
<p>Tip With the Copy fit feature, text can automatically be scaled to the available space in a Box or Div. See "Copy Fit" on page 757. Formatting text and paragraphs locally An intuitive way of formatting text locally is by using the toolbar buttons: select some text, or an element that contains text (see: "Selecting an element" on page 632) and click one of the toolbar buttons to make it bold, center it, create a numbered or bulleted list, etc.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-755.html">PAGE 755</a></h6>
<p>l l The spacing between letters and words and the way the text is wrapped: l l l l Background color: Specify the background color of the text: select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 931). Alternatively you could type a name or value in the Color field directly.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-756.html">PAGE 756</a></h6>
<p>style tag containing the selected setting(s). Click the Advanced button to add CSS properties and values to the inline style tag of the Span directly. For more information about CSS, see "Styling and formatting" on page 741. Formatting a paragraph Through the Paragraph Formatting dialog you can set the line height and first indent of a paragraph, and specify how to handle page breaks before, in and after the paragraph.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-757.html">PAGE 757</a></h6>
<p>styles are applied to that element. The link behind the style will take you to the place (the Source tab, or a CSS file) where that style is defined. Copy Fit Copy Fit is a feature to automatically scale text to the available space: the name of a person on a greeting card for example, or the name of a product on a shelf talker. This feature is only available with Box and Div elements in Print sections.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-758.html">PAGE 758</a></h6>
<p>Tip To give an element a class or ID, select it and add the class or ID on the Attributes pane. An ID is meant to be used once in each section, while a class can be shared between several elements. 7. Click Apply or OK. Note that the effect of the Copy Fit feature can only be seen in Preview mode. If it is impossible to make a text fit within the box with the given minimum and maximum font size, this will be reported as an error during a preflight (see "Testing scripts" on page 862).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-759.html">PAGE 759</a></h6>
<p>In the Web context, Inline Boxes are the preferred way to position elements; see "Boxes" on page 692. Tables should only be used to display data in a tabular format, not to position text and images. Tables used in web pages to position elements (and often, Positioned Boxes) make those pages less accessible to users with disabilities and to viewers using smaller devices.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-760.html">PAGE 760</a></h6>
<p>Guides Guides are horizontal and vertical lines used to help in designing templates, for example when positioning absolute positions boxes over a PDF background. They can only be used in Print sections. l Select View > Guides > Show guides to show or hide the guides and margins. To add a guide, press the Insert Horizontal Guide or Insert Vertical Guide buttons on the Toolbar. To move a guide, click and drag it to a new location.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-761.html">PAGE 761</a></h6>
<p>For an explanation of all values that the position property can possibly have, see https://www.w3schools.com/css/css_positioning.asp. Where to use it In Print sections, setting the position property to absolute can be very useful. It takes the element out of the text flow, so that the element stays where it is on the page. On Master Pages (which are only used in Print sections) elements are always positioned absolutely; if not, they must be located inside an element that has an absolute position.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-762.html">PAGE 762</a></h6>
<p>Rotating elements In any type of template, boxes, images, tables, text and other elements can be rotated. The toolbar buttons Rotate Clockwise and Rotate Counter Clockwise rotate the element in which the cursor is located 90 degrees at a time. To rotate an element into another angle position, use the 'angle' CSS property of the element. In most cases, this can be done in the element's Formatting dialog. In other cases, such as with text, you have to enter the CSS property and value manually.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-763.html">PAGE 763</a></h6>
<p>l l With local formatting. This means styling the table directly, using the Formatting dialog. Via Cascading Style Sheets (CSS). In a style sheet, style rules are declared for elements with different HTML tags, ID's and classes. These two methods are described below. See "Styling and formatting" on page 741 for background information about these two methods. Selecting a table, row or cell There are several ways to select a table or row: l l l Click in the table or row.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-764.html">PAGE 764</a></h6>
<p>To style all cells in a table or row at the same time via the Formatting dialog, you have to select the table or row first; see "Selecting a table, row or cell" on the previous page. Next, to open the Formatting dialog, choose Format > Table Cell. The settings that you make now will be applied to all cells in the selected row or table. For information about specific options in the formatting dialogs, see "Table Formatting dialog" on page 1001 and "Table Cell Formatting dialog" on page 1005.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-765.html">PAGE 765</a></h6>
<p>In CSS, refer to the table, row or cell with #ID (where ID should be replaced with the actual ID) or with .class (where class should be replaced with the actual class). Styling the first, last and nth rows The CSS pseudo-classes :first-child, :last-child and :nth-child() are very useful for styling table rows, especially in Detail Tables. A CSS pseudo-class follows a selector to specify a special state of that selector. It always starts with a colon.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-766.html">PAGE 766</a></h6>
<p>:nth-child(odd) matches child elements 1, 3, 5, 7, etc. The keyword odd substitutes the expression 2n+1, which in other words says: 'take every second element, starting at 1'. :nth-child(even) matches child elements 2, 4, 6, 8, etc. The keyword even substitutes the expression 2n+0, or simply 2n. :nth-child(3n) matches child elements 3, 6, 9, 12 etc. :nth-child(3n+1) matches child elements 1, 4, 7, 10 etc., so every third element, starting at 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-767.html">PAGE 767</a></h6>
<p>This script loops over a detail table, evaluating the field Shipped. If the value of that field is 1, it looks up the corresponding row in the results (the object that contains the selected detail table) and colors the text of that row green. (See also: "query()" on page 1349 and "Examples" on page 1309.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-768.html">PAGE 768</a></h6>
<p>Applying local formatting to an image To apply local formatting to an image, either: l right-click the image and select Image... from the contextual menu l click the image and select Format > Image... from the menu. For an explanation of the available options, see "Image Formatting dialog" on page 939. Applying style rules to an image To format an image via a style sheet, first give the image an ID or class: select the image, and enter the ID or class on the Attributes pane.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-769.html">PAGE 769</a></h6>
<p>Positioning an image Wrapping text around an image Initially, when an image is inserted into a paragraph, it behaves as if it were a character. Text isn't wrapped around an image automatically. To make that happen, you have to change the float property of the image to left or right. This anchors the image to the left or right, allowing text to be wrapped around it.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-770.html">PAGE 770</a></h6>
<p>around an image" above), is a relative positioning property, since it specifies the position of the element relative to its container. This means it is incompatible with the position:absolute property. In the Formatting dialog (see "Applying local formatting to an image" on page 768) the position property can be found on the Image tab, under Positioning.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-771.html">PAGE 771</a></h6>
<p>mode: RGB or CMYK. For an explanation of these two modes, see "Background color and/or image" on the previous page; for an explanation of the other options in this dialog, see "Color Picker" on page 931. You could also type a name or value in the Color field directly. It must be a valid color name (see color names on w3schools), a hexadecimal color code (see w3school's color picker), RGB color value, for example rgb(216,255,170) or CMYK color value, for example cmyk(15%, 0%, 33%, 0%).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-772.html">PAGE 772</a></h6>
<p>8. Set the position of the image in the box. 9. Finally, click OK. Note It is also possible to set an element's background in a style sheet; see "Styling templates with CSS files" on page 743. When referring to images or fonts from a CSS file, refer to a path that is relative to the current path, which is css/. For example: #header { background-image: url('../images/image.jpg'); }. Border In any type of template, boxes, tables and table cells, paragraphs, images and other elements can have a border.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-773.html">PAGE 773</a></h6>
<p>Note It is also possible to set an element's border in a style sheet; see "Styling templates with CSS files" on page 743. Rounding corners Any element in a template can have rounded corners. For boxes and images, this option is available in the Formatting dialog. For other elements, you have to create a CSS rule to set the border-radius of the element (or class of elements). Boxes, images and tables To round the corners of a box, image or table: 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-774.html">PAGE 774</a></h6>
<p>including the rounded corners. Table cells can have rounded corners as well, just as any other elements; see below. Other elements To round the corners of elements other than boxes and images, or to have different roundings on different corners, you have to make use of the CSS property: border-radius; see https://www.w3schools.com/css/css3_borders.asp. This is, for example, how you could round the corners of a paragraph: 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-775.html">PAGE 775</a></h6>
<p>Defining colors, spot colors and tints Color selectors, such as the drop-down list on the toolbar, initially contain a small set of colors. Add your own colors so that they can be used throughout the templates, in all contexts and in color selector dialogs as well as with their names in style rules (see "Styling and formatting" on page 741). Defining colors To define colors: 1. Select Edit > Colors on the menu. 2. Add a color. There are two ways to do this: l l Click the New button (the green plus).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-776.html">PAGE 776</a></h6>
<p>For information about the Spot color and Overprint options see "Defining a spot color" below. 6. Drag the slider bars to set the values for the color and click OK or Apply. Defining a spot color A spot color is any color generated by an ink (pure or mixed). Note that spot colors can only be used on certain printers.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-777.html">PAGE 777</a></h6>
<p>6. Check Use opacity if you want to set the Tint slider to use Opacity instead. 7. Use the slider to set the percentage of the tint or opacity, or type the percentage directly in the input box and finally click OK. Applying a color Colors can be applied to elements in your templates locally or through style sheets. Using colors in style sheets It is highly recommended to use style sheets in templates right from the start.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-778.html">PAGE 778</a></h6>
<p>Coloring text Instead of using a style sheet (see above), you can color text locally: 1. Select text or an HTML element that contains text (see "Selecting an element" on page 632). 2. On the menu, select Format > Color, or click the black triangle on the Text color toolbar button. 3. Select one of the colors in the list, or click Other to set all aspects of the text style, including text color and/or background color.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-779.html">PAGE 779</a></h6>
<p>Fonts In templates for personalized customer communications you can use the operating system's fonts, including imported fonts. When you are using a font that is not installed on your machine (for example, the bold or italic variant of a regular font) Windows tries to simulate the font in the Designer. Likewise, PlanetPress Connect tries to simulate the font in the output. It is however not guaranteed that the output will be exactly as shown in the Designer.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-780.html">PAGE 780</a></h6>
<p>Note The reason for specifying more than one font in a style sheet for web pages andemails is that the font might not be available on the device on which they are viewed. Order the font names by preference. The last one should be the generic font family (either serif or sans-serif). Importing a font To import a font into a template: l Drag the appropriate font files into the Fonts folder on the Resources pane. Note Font software may have specific restrictions for copying and redistribution.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-781.html">PAGE 781</a></h6>
<p>2. Open the Font Manager: from the menu, select Edit > Fonts. 3. Combine each of the styled fonts with a font effect: a. Select the font and click the Edit button. b. Select the appropriate font effect (e.g. Font Weight: Bold, or Font Style: Italic). c. Change the name of the styled font. It should have the same name as the regular font. 4. Close the Font Manager.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-782.html">PAGE 782</a></h6>
<p>body { font-family: 'MyWebFont', Arial, sans-serif; } Using remote fonts In order to use a remote font, you have to add a remote style sheet that points to a web font style sheet, for example https://fonts.googleapis.com/css?family=Roboto+Slab. For instructions see "Using a remote style sheet" on page 745. Remote fonts can be applied to content in a Master page, section, or Snippet. They may be used in a style sheet and they are automatically added to the Fonts drop-down on the toolbar.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-783.html">PAGE 783</a></h6>
<p>Changing the locale By default, the locale is the same as the operating system's locale setting. To change this setting for the currently open template: 1. On the menu, select Edit > Locale. 2. Use the drop-down to select how the locale is to be set for the current template: l l l Select System Locale to use the operating system's locale settings. The operating system's locale is set in the Region settings of the control panel.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-784.html">PAGE 784</a></h6>
<p>Tip Use a negative left margin to create a hanging paragraph or image. To set the spacing: 1. Right-click the element and click the respective element on the shortcut menu. Alternatively, select the element (see "Selecting an element" on page 632) and on the Format menu click the respective element. 2. Click the Spacing tab. Note All settings in the Formatting dialog are in fact CSS style rules. Click the Advanced button to manually add CSS properties (at the left) and values (at the right).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-785.html">PAGE 785</a></h6>
<p>Adding a Sass file To add a Sass file: 1. Right-click the Stylesheet folder on the Resources pane, and click New Stylesheet > SCSS file. 2. Enter a name for the file as it appears in the Stylesheet resources. When the name of Sass file begins with an underscore, it is considered a partial .scss file (e.g. _mySass.scss). Partial files are typically imported in a base .scss file. They may include Sass variables or other directives declared in the base file, and they cannot be compiled.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-786.html">PAGE 786</a></h6>
<p>Personalizing content Variable-data printing is a form of digital printing in which elements such as text and graphics may be changed using information from a database or data file. It prints unique documents with customized messages for each customer. This is exactly what you can do with Connect: using variable data you can personalize your company's communications (including but not limited to printed matter).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-787.html">PAGE 787</a></h6>
<p>field in your data on the basis of which a condition can be set. See "Showing content conditionally" on page 810. Conditional Print sections Entire Print sections can be included in or omitted from the output on the basis of one or more values in variable data. See "Conditional Print sections" on page 813. Dynamic images and Print section backgrounds Dynamic Images are dynamic in the sense that they are replaced by another image when a data field contains a certain value.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-788.html">PAGE 788</a></h6>
<p>The basics of script-writing in the Designer are explained in the following topic: "Writing your own scripts" on page 853. Control Scripts When output is generated from a template, Control Scripts run before all other scripts, when a record is merged with a context. They determine how different sections of the context are handled. They can, for example, make the page numbering continue over all Print sections, split Email attachments, or omit Print sections from the output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-789.html">PAGE 789</a></h6>
<p>When you open a data file or a database, the Data Model will be derived from it unless there already is an open data mapping configuration; in that case, the current data mapping configuration will try to retrieve data from the file or database, using its own Data Model and extraction logic. After opening a data mapping configuration or opening a data file or database, the Data Model pane at the right hand bottom shows the data fields that occur in the data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-790.html">PAGE 790</a></h6>
<p>a data mapping configuration you can, among other things: l l l l l Use Workflow to automate the extraction of data from this kind of data file. Load transactional or structured data. If there are detail lines, transactions, or any variable number of items to put into the template, you need a data mapping configuration to extract them. Format, transform, conditionally include/exclude and enhance data from the source file. Use other field types.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-791.html">PAGE 791</a></h6>
<p>Note The ExtraData field that appears as the first field in each record and in each detail table is automatically added to the Data Model by the DataMapper. It offers the possibility to add extra data to existing data records in a Workflow process. The ExtraData field can be used in a template just like any other data field (see "Variable Data" on page 801). When it contains a JSON string, this value can be read with a script using JSON.parse().</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-792.html">PAGE 792</a></h6>
<p>Excel (XLS/XLSX) file options l l First row contains field names: Check this option to use the first line of the Excel file as headers. This option automatically names all extracted fields. Sheet: Only one sheet can be selected as the data source. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-793.html">PAGE 793</a></h6>
<p>l Encoding: Use the drop-down to select the encoding with which to read the data in the table. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text. XML File options Select what level of XML elements defines a record. The Trigger is what triggers the creation of a new record.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-794.html">PAGE 794</a></h6>
<p>page.) All metadata fields that belong to the chosen level and higher levels in the tree structure will be listed. The lower the chosen level is in the tree structure, the more records you will get and the more metadata fields will appear in the list. Select metadata fields to add them to your data. Their property names will be used as field names in the Designer's data model.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-795.html">PAGE 795</a></h6>
<p>MySQL 1. Enter the appropriate information to connect to the database: l l l l l Server: Enter the server address for the MySQL database. Port: Enter the port to communicate with the MySQL server. The default port is 3306. Database name: Enter the exact name of the database from where the data should be extracted. User name: Enter a user name that has access to the MySQL server and specified database. The user only requires Read access to the database.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-796.html">PAGE 796</a></h6>
<p>l Encoding: Use the drop-down to select the encoding with which to read the data in the table. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text. 3. Click Finish to open the database. SQL Server 1. Enter the appropriate information to connect to the database: l Server: Enter the server address for the SQLServer database.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-797.html">PAGE 797</a></h6>
<p>2. Click Next and enter the information for the source table. l l l Connection string: Displays the full path to the database. Table: Use the drop-down to select the appropriate table or stored query to retrieve the appropriate data set. Encoding: Use the drop-down to select the encoding with which to read the data in the table. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-798.html">PAGE 798</a></h6>
<p>l Encoding: Use the drop-down to select the encoding with which to read the data in the table. l Sort on: Select a field on which to sort the data, in ascending (A-Z) or descending (Z-A) order. Note that sorting is always textual. Even if the selected column has numbers, it will be sorted as a text. 3. Click Finish to open the database. Oracle 1. Enter the appropriate information to connect to the database: l Server: Enter the server address for the Oracle database.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-799.html">PAGE 799</a></h6>
<p>Adding JSON data from a JSON file JSON data can either be added to, or replace the Data Model in a template. Importing JSON data into the Data Model makes it easier to test templates that are meant to be merged with JSON data in a Workflow configuration. Tip Workflow's OL Connect Create Content tasks can use JSON as their data source; see Create Email Content, Create Print Content, and Create Web Content.) To add data from a JSON file: 1. Select File > Add Data > JSON sample data, from the menu.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-800.html">PAGE 800</a></h6>
<p>4. Select the Replace Data Model option if you want the JSON to replace the existing Data Model. Otherwise, the JSON data will be mapped to corresponding fields in the existing Data Model, and data that cannot be mapped to any field will be discarded. 5. Click Finish. Add a counter using the Generate Counter Wizard Generating a counter is useful for numbered tickets or any other template requiring sequential numbers but no variable data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-801.html">PAGE 801</a></h6>
<p>Tip While the Generate Counter script is really useful for things like raffle tickets, it's unusable in combination with a data file or database, as it cannot complement that data automatically. This can only be done with a script. A script that adds a counter to data, using the current record index to calculate the current counter value, can be found in this how-to: Manual counter in designer. Variable Data Variable data are data from a database or data file that are used to personalize documents.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-802.html">PAGE 802</a></h6>
<p>1. Open the section you want to add the data field to. 2. Drag and drop a data field from the Data Model pane at the bottom right into the content of your template. To select and insert multiple data fields at the same time, press Shift or Ctrl, whilst selecting fields in the Data Model pane. What happens is that: o A placeholder for the value of the data field shows up in the text. It looks as follows: @FIELDNAME@. o A text script appears in the Scripts pane at the bottom left.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-803.html">PAGE 803</a></h6>
<p>Tip Press the Alt key while dragging, to wrap the placeholder in a span, give the span an ID and have that ID used as the script's selector. Press the Ctrl key while dragging, to wrap the placeholder in an absolute positioned box (a div) at the cursor position. A unique ID is assigned to the box and used as the script's selector. This method is particularly useful when the document mainly consists of a PDF used as the background image of a section (see "Using a PDF file as background image" on page 492).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-804.html">PAGE 804</a></h6>
<p>l Select a word in the content. Right-click the selection and on the shortcut menu, choose Text Script. The Text Script Wizard appears. 2. Change the name of the script to make clear what it does. Note Scripts can only have the same name when they are not in the same folder. 3. The selector states the text to be found in the template. The results can be replaced by the script. Tip Hover over the name of a script in the Scripts pane to highlight parts of the template that are affected by the script.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-805.html">PAGE 805</a></h6>
<p>l An HTML/CSS selector: n HTML elements, such as a paragraph. In the Text Script Wizard, click Selector and type the HTML tag without the angle brackets, for example: p. n HTML elements with a specific class. In the Text Script Wizard, click Selector and type the class name, including the preceding dot, for example: p.green for all paragraphs with the class 'green' or .green for all kinds of HTML elements that have the class 'green'.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-806.html">PAGE 806</a></h6>
<p>pointing arrow and select one of the formats. For an explanation of the formats see "Formatting variable data" on page 807. 7. Add as many data fields as you need, following the same procedure. 8. Optionally, you can click Options to specify where and how the script inserts its results: l l l As HTML. HTML elements in the results are processed and displayed as HTML elements. For instance, <b>this is bold</b> will be displayed as this is bold. This is the default setting. As text.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-807.html">PAGE 807</a></h6>
<p>of the content to move up or down. If, in a Print context, you don't want the result of the script to be part of the text flow (for example, when a letter is going to be sent in an envelope with a window), put the placeholder for the script in a positioned box (see "Boxes" on page 692 and "How to position elements" on page 758). Tip l l An example of how to create an address block using the Text Script Wizard is described in a how-to; see How to create an Address Block.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-808.html">PAGE 808</a></h6>
<p>Date Dates in variable data can be displayed as long, medium and short dates with different time displays. There are quite a few presets, but you can also enter a custom format mask. 1. Open the Text Script Wizard: double-click to open an existing script in the Scripts pane or create a new Text Script using the Text Script Wizard; see "Using the Text Script Wizard" on page 803. 2. Click a data field that contains text, or add such a data field to the script with the Add field button on the right. 3.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-809.html">PAGE 809</a></h6>
<p>l l l l Long Time displays a time in hours, minutes and seconds in two digits each, and adds a time zone, for example 00:00:00 EDT. Short Date/Time displays the date as a short date and the time as a short time, for example 01.04.16 00:00. Medium Date/Time displays the date as a medium date and the time as a medium time, for example 01.04.2016 00:00:00 (This is also the value of the Default Date/Time.) Long Date/Time displays the date as a medium date and the time as a medium time, for example 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-810.html">PAGE 810</a></h6>
<p>2. Click the data field that contains the numeric value that you want to display differently, or add the data field to the script with the Add field button on the right. 3. Under Format choose one of the following settings: l l l l l l l Custom Pattern: allows you to enter a custom format mask. For example, the pattern 000000 means that the number should count six digits; leading zeros are added to numbers shorter than six digits.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-811.html">PAGE 811</a></h6>
<p>Showing or hiding elements using the Conditional Content Script wizard 1. Right-click the element and click Make Conditional. Alternatively click the black triangle on the New button on the Scripts pane at the bottom left of the window, and click Conditional Content Script. The Conditional Content Script wizard opens. 2. Rename the script so that it reflects what the script does. Note Scripts can only have the same name when they are not in the same folder. 3. Type a Selector.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-812.html">PAGE 812</a></h6>
<p>The selected action will be performed if the condition evaluates to true with one of the given values. If, conversely, the condition evaluates to false, and the option Toggle Visibility is checked, the opposite action will be performed. Note If you need more complex conditions, click Expand and edit the code of the script. See "Writing your own scripts" on page 853. 9. Click Apply or OK. 10.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-813.html">PAGE 813</a></h6>
<p>1. Select the part of the text that you want to make conditional. 2. Right-click the selected text and click Wrap in span. 3. Type an ID and/or a class. An ID is fine if this is the only thing that should be shown or hidden on a given condition. Use a class if there is more that should be shown or hidden on the same condition. 4. Start creating a conditional content script from the Scripts pane. Use the ID or class as the selector of the script.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-814.html">PAGE 814</a></h6>
<p>print or skip a section only for customers living in Québec. With these values: Québec Ontario the section will be printed if the Province field reads Québec OR Ontario. Note More complex conditions can be written in the Script Editor: click Expand and edit the code of the script. See "Control Scripts" on page 885. 8. Click Apply or OK. 9. To see the result, toggle to the Preview tab at the bottom of the workspace (or select View > Preview View on the menu).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-815.html">PAGE 815</a></h6>
<p>1. Add one image to the template. See "Adding images" on page 726. 2. Right-click the image and click Dynamic Image. Or select the image and click Source (not the field, but the label before the field) in the Attributes pane. The Dynamic Image Script Wizard opens. The image's ID is used as the script's selector. If the image did not have an ID, it is automatically generated. 3. Select the location of the files: l l l Select Resources if the images reside in the Images folder on the Resources pane.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-816.html">PAGE 816</a></h6>
<p>this how-to: Dynamic signatures. How to insert dynamic images if there are no data fields with the actual names of the images is described in another how-to: Dynamic image that doesn't contain the data field value. Note An image with an unknown file extension is represented by a red cross in the output, but no error is logged unless the image refers to a local file that does not exist on disk.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-817.html">PAGE 817</a></h6>
<p>l l l One or more data fields contain values on the basis of which the PDFs can be switched. There is an appropriate PDF for each case. It is important that the PDFs are named after the various possible values of the related data field. All PDFs are stored in one folder (the Images folder on the Resources pane, or an external folder). Otherwise, adding a dynamic background requires a self-made script (for help on this, see "Control Script: Setting a Print section's background" on page 893).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-818.html">PAGE 818</a></h6>
<p>Select the data field to be evaluated. If you want the file name to be composed of the value of several data fields, simply click in the next row or click the Add button. This adds a row. Note that the rows will be concatenated to compose one file name. Only the last suffix should contain the file extension (.pdf). 5. Click Apply or OK. The script assigns the resulting file name, including the path and file extension, to the URL of the section's background. 6.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-819.html">PAGE 819</a></h6>
<p>1. Open the Insert Detail Table dialog. There are several ways to do that: l Drag the data field that contains the name of the detail table into the template. l On the menu select Insert > Table > Detail. l On the toolbar, click the Insert detail table button. 2. Enter the table's desired attributes: l l l ID: A unique identifier for the table. IDs are used to access the table from scripts and as CSS selectors for style rules. Class: A class identifier for the table.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-820.html">PAGE 820</a></h6>
<p>content at the selected location would produce invalid HTML the final result may be different than expected. For example, when you insert a Div into a paragraph, the paragraph gets split in two. This means you end up with two paragraphs with the Div in between. 3. Click Next and select which fields should show up in the Detail Table. The order of the fields indicates in which order columns are displayed in the Detail Table, from left to right.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-821.html">PAGE 821</a></h6>
<p>Adding a row to the header or footer of a Detail Table Sometimes you'll want to add one or more rows to the header or footer of a Detail Table: to add taxes and/or the total of the invoice to the table, for example, or to add a custom message. A header or footer row can be added to a Detail Table as follows. 1. In the workspace, open the Design tab. 2. If the table already has a header/footer: a.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-822.html">PAGE 822</a></h6>
<p>Styling a Detail Table The Insert Detail Table wizard lets you select a style, but if you want to apply a different style to the table, choose No Style when creating the table. Then the style of a Detail Table is completely customizable: you can change the font, font size and color, the borders, the cell padding (the distance between the edge of the cell and its content), and the background color or image of the table and its cells. See "Styling a table" on page 762.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-823.html">PAGE 823</a></h6>
<p>output they might end up on a next page without any other visible content, which would still be printed because lines and paragraphs must be treated as content, even when they are empty. Hiding an empty Detail Table The number of rows in a Detail Table is variable, as it depends on a detail table in the data. You might want the Detail Table to be hidden when there are no data to display. There are two ways to achieve that. l l When creating a Detail Table, you can check the option Hide when empty.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-824.html">PAGE 824</a></h6>
<p>l l data-breakable: this attribute is added to every copied row (in preview mode or when creating output), in each of them with a unique ID as its value. This is required by the pagination routines of Connect to split the table across pages. data-column-resize, if present, indicates that the columns may be resized (datacolumn-resize=""). Personalized URL Personalized URLs (pURLs) are links that are tailor-made for a specific purpose, generally for individual clients.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-825.html">PAGE 825</a></h6>
<p>Secondly, the pURL must contain the data that Workflow needs in order to create the personalized response (be it a web page or other file). For instance, creating a personalized page that shows a client's invoice may require the Invoice Number to be present in the pURL, which is then used by Workflow to retrieve the invoice data, generate the invoice in PDF or HTML format using a template, and then return it to the browser. The data needs to be included in the URL. In this URL, for example: http://www.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-826.html">PAGE 826</a></h6>
<p>5. Type the code that wraps the span in a <a> element (a hyperlink). In the link, the host should be followed by the action with which the corresponding Workflow process is triggered and the data with which Workflow will be able to create a personalized response. Sample script Let's assume: l l l A Workflow process is triggered by the HTTP action: MakePDF. The template that outputs the pURL is to be merged with a record that contains a data field invoice_UUID.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-827.html">PAGE 827</a></h6>
<p>General preferences The General Preferences are as follows: l Always run in background: This option correlates with the "Always run in background" option selectable in the "Document Boundaries Refresh" dialog and "Print via Print Server" dialog. When either of these dialogs is used and the option is checked, it will also be checked here. To prevent the refresh boundaries and print via print server dialogs to automatically run as background, uncheck this option.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-828.html">PAGE 828</a></h6>
<p>------------------------------------------------------------------------------------------ Clean-up Service preferences The Clean-up Service defines how the Connect database and the temporary files created during Connect production runs are cleaned up after the production run has finished. As part of the job production process PlanetPress Connect uses a database for intermediate storage and also creates various temporary "managed" files.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-829.html">PAGE 829</a></h6>
<p>l l Run at application start up: Click to start the clean-up service when the Designer module is opened, or the Managing Service is started. Run according to the cron schedule: Enter the interval at which the Clean-up service runs. To understand how to write a cron job schedule, please refer to the Quartz Scheduler tutorial. Note If the Product managing the service is set to Designer, then the Designer must be running at the time that the cron job is scheduled, for the Clean-up to run.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-830.html">PAGE 830</a></h6>
<p>running both clean-up and production jobs simultaneously. If experience suggests that the clean-up is not running efficiently, then upping the number of threads here would be recommended. Conversely, if production appears to be suffering courtesy of the clean-up process, then reduce the number of threads here. In general, higher end machines (those with multiple cores) will allow a higher numbers of threads, whilst low end machines will perform better with a lower number of threads.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-831.html">PAGE 831</a></h6>
<p>all the content items it contains) is retained within the database before being set for deletion. l l l l Minimum time to retain Managed Files: The minimum time file references (to files such as data mapping configurations and templates) are retained within the database before being set for deletion.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-832.html">PAGE 832</a></h6>
<p>DataMapper preferences DataMapper XML l Display New Line Character as ¶ : Check to show line returns as ¶ in the Data Viewer, when XML files are shown. If the option is unchecked, you will not see spaces and line returns after element names in the Data Viewer. Default Format DataMapper stores user preferences for the Date, Number and Currency formats. By default, the user preferences are set to the system preferences.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-833.html">PAGE 833</a></h6>
<p>Database Connection preferences Dialog used to change the PlanetPress Connect back-end Database. This dialog supports the swapping of the back-end database between various vendor databases. Note, however, that the alternate vendor database(s) must already be installed and available in order to swap to them. This is not a migration tool. It is a simple connection tool, that enables shifting to a different back-end database.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-834.html">PAGE 834</a></h6>
<p>l Database Instance Name: Enter an existing Microsoft SQL Server's instance name. This option only applies to existing Microsoft SQL Server instances, and not for MySQL. l Port: Enter Port number. The defaults are those which the vendors use by default. l Schema: The individual database schema, within the vendor database. Note If a previously non-existent schema were chosen here, then a new schema of that name will be created within the database when the back-end database swap is applied.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-835.html">PAGE 835</a></h6>
<p>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. For example, in order to use Integrated Authentication with Windows, specify the property integratedAuthentication with the value true, which adds integratedAuthentication=true to the URL. l Property: These are free field text fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-836.html">PAGE 836</a></h6>
<p>Editing preferences These preferences define different editing options in the Designer module. l l Object Resizing for <div> elements: This defines in which contexts to enable the resizing of <div> elements (including Positioned and Inline boxes). Resizing <div> elements may cause layouts to produce undesirable results especially when using Foundation templates. l Enable for Print Context: Check to enable <div> resizing in the Print contexts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-837.html">PAGE 837</a></h6>
<p>l l l Expanded: This is the default output style. Each property and rule take up one line. Properties are indented within the rules, but the rules aren't indented in any special way. Nested: Each property has its own line, but the indentation isn't constant. Each rule is indented based on how deeply an element is nested in the HTML and CSS structure. Auto compile on saving .scss files: When this option is checked, a .scss file is compiled into a .</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-838.html">PAGE 838</a></h6>
<p>l l l l l l Shared Content: This color highlights shared content, such as shared snippets; see "Snippets" on page 737. Guides: This is the color for rulers that can help position content correctly; see "Guides" on page 760. Margins: This color delineates the content area on a page; see "Pages" on page 497. Bleed box: This color delineates the printable area on a page; see "Page settings: size, margins and bleed" on page 498.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-839.html">PAGE 839</a></h6>
<p>Email preferences Email (General) preferences l Default From Group: l l l Name: Enter the name that is set by default in the "From name" field in the Send Email and Send Test Email dialogs ("Send (Test) Email" on page 991). 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 991).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-840.html">PAGE 840</a></h6>
<p>Service Provider (ESP): Mandrilapp.com, Sendgrid and Mailgun (see "Using an ESP with PlanetPress Connect" on page 1442). 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.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-841.html">PAGE 841</a></h6>
<p>l l Upgrade web editors: This Emmet option doesn't affect how Emmet works in Connect Designer. 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.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-842.html">PAGE 842</a></h6>
<p>Emmet Output preferences The Output Preferences dialog is used to control how the expanded (output) code behaves when expanding abbreviations and snippets. There are 6 different dialogs to control output and, while they all have identical options, they control different output types: CSS, HAML, HTML, XML, XSL and the "Default" one controlling the rest of the types. These options are equivalent to Emmet's syntaxProfiles.json feature.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-843.html">PAGE 843</a></h6>
<p>In the example above, ${lang} is used to refer lang variable defined in variables below. If your primary language is, for example, Russian, you can simply override lang variable with ru value and keep the original snippets. Also, you can override variable values with inline abbreviation attributes: html:5[lang=ru]. l Name: The name of the variable. This should be a single alphanumeric string with no spaces or special characters. For example, the myVar name is referred to as ${myVar}.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-844.html">PAGE 844</a></h6>
<p>1. Connect user wanting to create digital signatures using a secure device have to configure the DLL for using the secure device, so Connect can find the DLL when a digital signature is necessary. 2. The Connect administrator wanting the configuration of DLLs loaded by Connect Server, Designer, and their engines to happen outside of Presets, Templates, or other resources.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-845.html">PAGE 845</a></h6>
<p>Default Locale The Default Locale preferences are only available in the Designer Preferences. This setting determines the locale for new templates. By default this is the system's locale. Select System Locale to use the operating system's locale settings.Select Explicit Locale to choose a specific locale from the drop-down Explicit Locale list.The Locale can be changed on a per template basis. See "Locale" on page 782.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-846.html">PAGE 846</a></h6>
<p>Warning Higher logging settings will have an impact upon Connect production speeds, as well as leading to substantially larger log files. We recommended leaving the logging level to Info and only using the higher levels of logging in conjunction with advice from OL support. l Rollover policy selection: Chose whether to retain Connect log files for a certain number of days (Daily logs) or based upon some predetermined hard disk usage limitations (Size-based logs).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-847.html">PAGE 847</a></h6>
<p>Warning We recommend leaving the Logging pattern to the default value. If you do need to change the Logging pattern, please see the Pattern Formatting guide for help in doing so. l Log message preview display: This displays a real time example of the format and content of individual log file entries, based upon the Logging pattern setting. Advanced settings The Advanced settings over-ride the Overall logging settings, and provide a greater level of logging granularity.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-848.html">PAGE 848</a></h6>
<p>Parallel Processing preferences See "Parallel Processing preferences" on page 133. ------------------------------------------------------------------------------------------ Print preferences Available Printers preferences The Available Printers preferences control which printer definitions are available when generating print output or creating Output Presets.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-849.html">PAGE 849</a></h6>
<p>l l l Username: Enter the username to authenticate to the Print Server. Default is ol-admin. This is set on the server's "Security Settings" on page 141. Password: Enter the password to authenticate to the Print Server. Default is secret. Confirm Password: Re-enter the password above. Print Measurements preferences l l Units: Use the drop-down to specify the default measurements system used for dimensions of the template and boxes. In addition it defines the coordinates/position of box elements.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-850.html">PAGE 850</a></h6>
<p>page, Workflow may be unable to correctly interpret all the characters that are used in the configuration file (in path or file names, for example). To prevent this, you may select an encoding from the list.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-851.html">PAGE 851</a></h6>
<p>l l Restore Defaults. This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences. Apply: This option applies the settings made within the current Preferences page, but does not close the Preferences dialog. ------------------------------------------------------------------------------------------ Scripting preferences The Scripting preferences define different options related to scripting within PlanetPress Connect.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-852.html">PAGE 852</a></h6>
<p>Web preferences Web Form preferences These preferences define the default behavior of some form elements.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-853.html">PAGE 853</a></h6>
<p>l Workflow URL: The default URL is: http://127.0.0.1:8080/_ getSampleFormData_ The Web 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. Apply: This option applies the settings made within the current Preferences page, but does not close the Preferences dialog.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-854.html">PAGE 854</a></h6>
<p>Control Scripts When output is generated from a template, Control Scripts run before all other scripts, when a record is merged with a context. They determine how different sections of the context are handled. They can, for example, make the page numbering continue over all Print sections, split Email attachments, or omit Print sections from the output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-855.html">PAGE 855</a></h6>
<p>Tip Content added by a script isn't visible in Design mode, but is visible and can be inspected in Preview mode. Post Pagination Scripts Post Pagination Scripts are run in a Print context after the content has been paginated. Because they can search through the output of all Print sections, and modify Print sections (one at a time), they may be used to create a Table Of Contents (TOC), as explained in the topic: "Creating a Table Of Contents" on page 902.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-856.html">PAGE 856</a></h6>
<p>l l A selector (HTML/CSS): n HTML elements of a certain type, such as a paragraph: <p>. In the Script Wizard, click Selector and type the HTML tag in the Selector field without the angle brackets: p. n HTML elements with a specific CSS class (eg. green). In the Script Wizard, click Selector and type the class name in the Selector field , preceded by a dot: .green. n An HTML element with a specific ID (eg. intro).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-857.html">PAGE 857</a></h6>
<p>Writing a script 1. Create a new script (see: "Creating a new Standard Script" on page 855, " Adding a Control Script" on page 886 or "Adding a Post Pagination Script" on page 901), or double-click an existing script in the Scripts pane on the bottom left. If the script was made with a Script Wizard, you have to click the Expand button before you can start writing code. This will change the Script Wizard into an editor window.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-858.html">PAGE 858</a></h6>
<p>Two basic code examples Writing a script generally comes down to modifying the piece(s) of content collected from the template with the script's selector, using values, or depending on values of the record that is being merged to the template at the moment the script runs. Modifying the template To access and change the results of the query that is carried out with the selector (in other words: to modify the output), use the object results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-859.html">PAGE 859</a></h6>
<p>Tip For more examples of using conditions, see this how-to: Combining record-based conditions. If an expanded script contains errors or if there are warnings, icons appear in the overview ruler on the right hand side of the editing area. These icons are shown relative to their position in the script and do not move as you scroll down. You can click on an icon to quickly jump to the error or warning. Script errors are highlighted by a red icon, and warnings in yellow.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-860.html">PAGE 860</a></h6>
<p>They can not be excluded from execution for a specific context or section, using the execution scope of a folder; see "Execution scope" on the next page. What you can do is disable the script or the containing folder; see "Enable/disable scripts" on the next page. Script folders Scripts can be organized in folders. Why would you do that? For three reasons: l l l Folders have an execution scope. You can specify for which contexts and sections the scripts in a folder have to run.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-861.html">PAGE 861</a></h6>
<p>execution scope of a folder; see "Execution scope" below. What you can do is disable the script or the containing folder; see "Enable/disable scripts" below. Execution scope A particular script may be used in one context or section, but not in other contexts or sections.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-862.html">PAGE 862</a></h6>
<p>To enable or disable a script or a folder: l On the Scripts pane, right-click the script or the folder and click Disable (if the script or folder was enabled) or Enable (if the script or folder was disabled). Tip For more ways to optimize scripts, see "Optimizing scripts" on page 867. Import/export scripts The easiest way to import scripts into another template is to open the template and use the Import Resources dialog; see "Import Resources dialog" on page 942.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-863.html">PAGE 863</a></h6>
<p>You can even do this while creating a new script, either with a Script Wizard or in the expanded script editor. Click Apply at the bottom of the script editor to see the effect of the script on the Preview tab of the Designer. Note that scripts that use values of data fields can only be effective when a data file or data mapping configuration is open. See "Loading data" on page 788. Note Post Pagination Scripts run only when a Print section is previewed or outputted.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-864.html">PAGE 864</a></h6>
<p>executed, assuming the script is enabled. l l The warning icon (!) appears, for example, when a script refers to an unknown field in the record set, or when ; is missing after a statement. The error icon (x) displays when the script results in an error, for example, when it uses an undeclared variable. If an expanded script contains errors or if there are warnings, icons appear in the overview ruler on the right hand side of the editing area.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-865.html">PAGE 865</a></h6>
<p>Note An image with an unknown file extension is represented by a red cross in the output, but no error is logged unless the image refers to a local file that does not exist on disk. Image file extensions that the software recognizes are: AFP, BMP, EPS, GIF, JPG/JPEG, PCL, PDF, PNG, PS, SVG, and TIF/TIFF. Using the Script Debugger The Designer's Script Debugger allows you to set breakpoints in scripts and step through them.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-866.html">PAGE 866</a></h6>
<p>After running the Script Profiler you can see in which sections the script has run: l Hover the mouse over a value in the column Count to see the number of times that the script has run, per section. You can also see the breakdown of the execution time across different execution stages: l l Hover the mouse over a value in the column Elapsed to see the time elapsed (in milliseconds) since the start of the session.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-867.html">PAGE 867</a></h6>
<p>Script Profiler settings Number of runs By default, the Script Profiler runs on 1000 instances of all the scripts. To test on a higher or lower number of instances: 1. On the menu, select Window > Preferences. 2. Click Scripting. 3. Set a number of iterations (maximum one billion) and click OK. Sorting In the Scripts Profiler, the scripts are by default sorted based on the values in the Elapsed column, from high to low. Click any of the columns to sort the scripts according to the values in that column.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-868.html">PAGE 868</a></h6>
<p>This topic presents a number of other ways to speed up script execution by optimizing the scripts. Use an ID as selector Scripts (except Control Scripts) start with a query. The selector in the second column in the Scripts pane is what a script looks for in the template. If you've used the drag-and-drop method (without pressing the Alt or Ctrl key) to insert a data field in a template, the selector is a small text: the name of the data field surrounded by @ signs, @firstname@ for example.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-869.html">PAGE 869</a></h6>
<p>Try avoiding DOM modifications, especially within loops. Storing the content in a variable and appending the information after the loop is more efficient: this way, the template will be touched only once. Example The following example loads a snippet into a variable and uses the find() and text() commands of the Designer scripting API. var labelElm = loadhtml('snippets/label.html'); for(var i = 0; i < record.tables.products.length; i++) { var label = labelElm.clone(); label.find('@ProductLabel@').</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-870.html">PAGE 870</a></h6>
<p>A QueryResult allows you to perform DOM manipulations like adding and removing elements, adding and removing CSS classes etc. When the required manipulations are limited to find/replace actions, you could change the QueryResult into a string. This allows you to replace text using the replace() method. For this, you could use toString(): var labelSnippet = loadhtml('snippets/label.html').toString(); Or you could copy the HTML of the QueryResults to a variable: var block = results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-871.html">PAGE 871</a></h6>
<p>In this example, @product@ is a pattern (to be used in a search) and g is a modifier (to find all matches rather than stopping after the first match). For more information about possible regular expressions, see https://www.w3schools.com/js/js_regexp.asp. The script in this how-to: Translate and replace script uses the replace() method with a regular expression.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-872.html">PAGE 872</a></h6>
<p>block = block.replace('@customercode@', data.customercode); … results.html(block); The first line retrieves the HTML of the promo block and stores it in a variable called block. To make the code more readible, the fields from the record are stored in a variable named data. After replacing the placeholders by values, the script replaces the HTML of the promoblock with the personalized string. Other resources There are also many resources online to help learn about JavaScript performance and coding mistakes.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-873.html">PAGE 873</a></h6>
<p>l l Drag a snippet into the script window. The function that loads the script loadhtml() or loadjson(), depending on the file type - will automatically be added, including the file name. Right-click a snippet and select Copy Resource Location to copy the relative path of the snippet to the clipboard. It may then be pasted into a script. Remote snippets are retrieved in the same way, except that the file extension should be .rhtml instead of .html. If it is a remote JSON snippet, the file extension is .</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-874.html">PAGE 874</a></h6>
<p>Loading part of a snippet, based on the value of a data field When a snippet contains a part that can be identified by a selector, that selector can be used to load that part of the snippet into a template. It is possible to do this, based on the value of the data field. This is easiest when the selector matches the value of a data field. Example The following script reads the value of the LANGUAGE field in the record and uses that value as the selector in the function loadhtml().</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-875.html">PAGE 875</a></h6>
<p>Loading content using a server's API Content in a template is usually static (apart from being personalized) and part of the main text flow. It can also be located in a snippet (see "Snippets" on page 737). It is also possible to include content that is served by another server. Many servers provide an API to fetch publicly available content from their site. That content may even be dynamic: the most recent blog posts on a Wordpress website, for example, or the current weather forecast for a certain city.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-876.html">PAGE 876</a></h6>
<p>Note that interactive content, such as an interactive map, can only be used in Web templates, and cannot be output on Print or Email contexts (even though they will show up in Preview mode!). Step 3: Writing a script The final step is to write a script that retrieves the content and inserts it into the template (see "Writing your own scripts" on page 853). Use the element or the ID of the element that you added in Step 2 as the script's selector.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-877.html">PAGE 877</a></h6>
<p>Inserting content in the template To insert the content after the selected element, use results.after(). To replace the element with the new content, use results.html() or results.replaceWith(). Example: recent posts The following script loads five posts from Mozilla's blog and inserts their titles as links in a template. Mozilla's blog is a WordPress website.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-878.html">PAGE 878</a></h6>
<p>First all Control Scripts are executed, in the order in which they appear in the Scripts pane. Control scripts don't touch the content of the sections themselves, but they change the way a template is outputted, for example by selecting or omitting sections from the output (see "Control Scripts" on page 885). Then the Standard scripts are executed, once for each section, in the order in which they appear in the Scripts pane. Standard scripts can change the contents of the current section in a template.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-879.html">PAGE 879</a></h6>
<p>"Personalizing content" on page 786 and "Writing your own scripts" on page 853). Using selectors for scripting can increase the speed with which a template and data are merged; see "Use an ID as selector" on page 868. Standard CSS selectors l l l l l l Selectors are made up of one or more of the following components: An HTML element. Type the HTML tag without the angle brackets (e.g. p) to select all elements of that type (pselects all paragraphs). A class. Type the class name, preceded by a dot, e.g.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-880.html">PAGE 880</a></h6>
<p>Warning Avoid using classes with the __ol prefix in your selectors. These dynamically added class names may change in future releases of the software. Section selector The Designer writes the name of each section to the section attribute of the <html> element. This attribute can be used in selectors.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-881.html">PAGE 881</a></h6>
<p>Master Page selector The Designer writes the name of each Master Page to the masterpage attribute of the <html> element. This attribute can be used in selectors. Example This rule adds a box to the body of every Master Page. [masterpage] body results.html('<div style="background:red;width:1in;height:2in">Hello World</div>'); The following rule adds the box only to the Master Page called "Master Page 1". [masterpage="Master page 1"] body results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-882.html">PAGE 882</a></h6>
<p>.frontside h1 { color: green; } The next style rule is a bit more specific: it colors <h1> elements on a Master Page when that Master Page is applied to the front of a sheet in Section 1: [section='Section 1'] .frontside h1 { color: green; } The following rule hides <h1> elements on the back of a sheet on which no content (from the main text) is allowed. .backside.nocontentpage .</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-883.html">PAGE 883</a></h6>
<p>3. Master Page elements Using the .page_mediabox selector, you could change this stacking order and place the section background on top of the elements on the Master Page. Set the z-index property to a value larger than 0 (zero) and add !important to make this style rule override the inline style declaration that normally puts the section background behind the Master Page elements: .page_mediabox img.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-884.html">PAGE 884</a></h6>
<p>document. .DESIGN .address-block { outline: 1px dashed purple; } Adding a background pattern The Postcard template wizard (in the Basic Print templates group) uses the .DESIGN class to mark areas that are reserved for postal use and should not contain text or images. These areas were added to the Master Page as absolute positioned boxes that have been given the class clearzone. The following style rule assigns a background pattern to elements with that class in the Design view: .DESIGN .</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-885.html">PAGE 885</a></h6>
<p>Control Scripts When output is generated from a template, Control Scripts run before all other scripts, when a record is merged with a context. They determine how different sections of the context are handled. They can, for example, make the page numbering continue over all Print sections, split Email attachments, or omit Print sections from the output. Some knowledge of JavaScript is needed to edit Control Scripts, just as for any other self-made scripts; see "Writing your own scripts" on page 853.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-886.html">PAGE 886</a></h6>
<p>Adding a Control Script To add a Control Script: 1. On the Scripts pane at the bottom left, click the black triangle on the New button and click Control Script. A new script appears in the list. 2. Double-click the new script to open it. The script editor appears. 3. Change the name of the script so that it reflects what the script does. Note Scripts can only have the same name when they are not in the same folder. 4. Write the script; see the "Control Script API" on page 1351.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-887.html">PAGE 887</a></h6>
<p>Task See topic Field/function of section object Change the page numbering of Print sections "Control Script: Page numbering" on the facing page restartPageNumbering Set the background image of a Print section "Control Script: Setting a Print section's background" on page 893 background.source, background.url, background.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-888.html">PAGE 888</a></h6>
<p>Task See topic Field/function of section object Set the margins of a Print section or Master Page "Setting the margins of a Print section" on page 1403 margins Set a Master Page, Media, or Duplex printing for a Print section "sheetConfig" on page 1373 sheetConfig Control Script: Page numbering This topic explains how to write a Control Script that changes the page numbering in Print sections.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-889.html">PAGE 889</a></h6>
<p>Tip If you are looking to create a short, simple table of contents in one section, you could add a Standard Script that uses the pageRef() function. For an example, see "Creating a table of contents" on page 1317. For a multi-page, cross-section table of contents you must use a Post Pagination Script; see "Creating a Table Of Contents" on page 902.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-890.html">PAGE 890</a></h6>
<p>Disabled section When a section is disabled, it will not be outputted, but its restartPageNumber flag will still be taken into account for composing the page number sequences. So, if the restartPageNumber flags are set as follows: 1. Section A (1 page) restartPageNumber = true 2. Section B (2 pages) restartPageNumber = false 3. Section C (3 pages) restartPageNumber = true, enabled = false 4. Section D (4 pages) restartPageNumber = false In code: if (merge.context.type == ContextType.PRINT) { merge.context.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-891.html">PAGE 891</a></h6>
<p>Defining parts Defining parts is done by setting the part field on a section, for example: merge.template.contexts.PRINT.sections['Section 2'].part = "PDF_Attachment2";. (Also see "section" on page 1395 and "Control Script API" on page 1351.) l l If a part name is given, then that delimits the start of a new part (even if the part name is the same as the previous one). Following sections that don't define a part name, will be added to the previous part.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-892.html">PAGE 892</a></h6>
<p>Note For Web sections, a part always consists of only the given section. Web pages cannot be appended to form a single part. It is however possible to attach multiple Web pages to one email; see the following example. Controlling multiple Email attachments The following script attaches the following sections to an email: l Print section 3 + 4 as attachment with continued page numbers l Print section 6 as separate attachment l Web sections A and B as separate attachments if (channel == Channel.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-893.html">PAGE 893</a></h6>
<p>Control Script: Setting a Print section's background In the Print context, a PDF file can be used as a Print section's background; see "Using a PDF file as background image" on page 492. If you want the section background to be switched automatically, depending on the value of a data field, you need a Control Script. There is a Script Wizard that can generate that script for you, provided that certain conditions are met; see: "Dynamic Print section backgrounds" on page 816.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-894.html">PAGE 894</a></h6>
<p>var resourceUrl = 'images/policy-' + record.fields.policy + '.pdf'; merge.template.contexts.PRINT.sections['Policy'].background.url = resourceUrl; Note An image with an unknown file extension is represented by a red cross in the output, but no error is logged unless the image refers to a local file that does not exist on disk. Image file extensions that the software recognizes are: AFP, BMP, EPS, GIF, JPG/JPEG, PCL, PDF, PNG, PS, SVG, and TIF/TIFF.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-895.html">PAGE 895</a></h6>
<p>Tip You could use the resource() function to check the number of pages or for example the page height and width before setting it as a background (see "resource()" on page 1360). Example This scripts sets a background on a Print section using absolute positioning. var activeSection = merge.template.contexts.PRINT.sections['Section 1']; activeSection.background.source = BackgroundResource.RESOURCE_PDF; activeSection.background.url = "images/somepage.pdf"; activeSection.background.position = MediaPosition.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-896.html">PAGE 896</a></h6>
<p>var printSections = merge.template.contexts.PRINT.sections; var clone = printSections["Section 1"].clone(); printSections["Section 1"].addAfter(clone); Cloned sections have the same properties as normal sections, but they cannot call section functions. Note that with multiple clones, the next clone is always added after the previous clone. With addBefore(), the code original.addBeforeclone1); original.addBefore(clone2); will result in "clone1, clone2, original". With addAfter() the code original.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-897.html">PAGE 897</a></h6>
<p>[section="my_section_clone_0"] h1 { color: red; } [section="my_section_clone_1"] h1 { color: green; } [section="my_section_clone_2"] h1 { color: blue; } The same selector could be used in personalization scripts: Selector: [section="my_section_clone_0"] h1 Script: results.css('color','red'); Inside a Standard Script, cloned sections can be found using merge.section: if (merge.section == "my_section_clone_0") { results.html("Clone!"); } else { results.html("Original.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-898.html">PAGE 898</a></h6>
<p>if(record.fields.policy_a == 1) { addPolicy('a'); } if(record.fields.policy_b == 1) { addPolicy('b'); } function addPolicy(policy){ var resourceUrl = 'images/policy-' + policy + '.pdf'; var clone = printSections["Policy"].clone(); clone.name = "policy_" + policy; clone.background.url = resourceUrl; clone.enabled = true; printSections["Policy"].addAfter(clone); } Control Script: Securing PDF attachments The Print context can be attached to an email in the form of a PDF file and secured with a password.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-899.html">PAGE 899</a></h6>
<p>When producing a single attachment, the password(s) should be set on the first Print section. When producing multiple attachments, it should be set on the first section of each part. Password types PDF allows for two types of passwords to be set on a secured PDF file: a user password and owner password. The user password allows a limited access to the file (e.g. printing or copying text from the PDF is not allowed). The owner password allows normal access to the file.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-900.html">PAGE 900</a></h6>
<p>} } Post Pagination Scripts Post Pagination Scripts are run in a Print context after the content has been paginated. Because they can search through the output of all Print sections, and modify Print sections (one at a time), they may be used to create a Table Of Contents (TOC), as explained in the topic: "Creating a Table Of Contents" on page 902. This topic explains what a Post Pagination Script is and how to add it to a template.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-901.html">PAGE 901</a></h6>
<p>What to use a Post Pagination Script for After all Print sections have been paginated, Post Pagination Scripts may search through the rendered document and collect information about elements (for instance, which page they reside on) and sections (for instance, whether they are enabled). With this information, a Post Pagination Script can do two things: l l Modify the output. The script may modify the output of a section.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-902.html">PAGE 902</a></h6>
<p>Note Post Pagination Scripts run only when a Print section is previewed or outputted. To verify the results of Post Pagination Scripts on a certain Master Page, preview the Print section to which that Master Page is applied. Creating a Table Of Contents This topic explains how to create a multi-page, cross-section Table Of Contents (TOC) using a Post Pagination Script. For information about Post Pagination Scripts in general, see "Post Pagination Scripts" on page 900.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-903.html">PAGE 903</a></h6>
<p>// Build the TOC var toc = ''; merge.context.query("h1, h2").each(function() { var pageNo = this.info().pageNo; var text = this.text(); var level = this.tagName(); toc toc toc toc += += += += '<p class="toc-entry ' + level + '">'; '<span class="text">' + text + '</span>'; '<span class="dots"></span>'; '<span class="number">' + pageNo + '</span></p>'; }); results.html( toc ); // Repaginate the result merge.section.paginate(); // Update the page numbers var $numbers = query('.number'); merge.context.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-904.html">PAGE 904</a></h6>
<p>Note that the info() function can also be used to get an element's sheet number, the section it is located in, and the total page count and sheet count of that section (see "PaginationInfo" on page 1388 and "info()" on page 1393). In this case only the page number is used. Then the callback function adds an entry to the variable that holds the table of contents, using the retrieved info.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-905.html">PAGE 905</a></h6>
<p>merge.context.query("h1, h2"). The callback function in each() retrieves the heading's new page number. It then uses the index number of the heading in the result set to get the corresponding entry in the TOC: var entry = $numbers.get( index ); (see "get(index)" on page 1313), and replaces it with the new page number. Excluding headings Often there are certain headings that you don't want to appear in the table of contents. The title of the table of contents itself, for example.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-906.html">PAGE 906</a></h6>
<p>This code takes the element's ID. If an element doesn't have an ID, the script generates a new, unique ID for it. 3. Replace the line: toc += '<span class="text">' + text + '</span>'; with this line: toc += '<a class="text" href="#' + anchorId + '">' + text + '</a>'; The new line adds a hyperlink: <a ... href> with the element's ID to the table of contents.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-907.html">PAGE 907</a></h6>
<p>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . "; } p.toc-entry .number { flex-shrink: 1; text-align: right; font-weight: bold; } These styles make use of the CSS Flexbox Layout Module. For more information about that, see W3schools: CSS Flexbox. Translating templates OL Connect has a built-in feature to automatically generate output and previews from one template in different languages, and to pluralize certain words in the output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-908.html">PAGE 908</a></h6>
<p>These file types are widely used in translation software, so you can team up with a professional translator or translation agency to translate your templates, or you can do it yourself using a free online tool, such as the Poedit software. Other ways to translate a template The built-in translation feature is easy to use for labels and short texts in for instance invoices, web forms, transaction email messages, and pack lists.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-909.html">PAGE 909</a></h6>
<p>Translating content that is inserted by a script Personalization scripts may add content to the output. OL Connect will apply translations to that content at the moment it is added to the template, for example with the html() or replaceWith() function. Translations are applied if that content is marked for translation, and if there is a matching translation entry (see "Tagging text that is inserted by a script" on page 911).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-910.html">PAGE 910</a></h6>
<p>Note Changing the text in a tagged element will break the relationship with the translation entry. This means that the text will not be translated. Edit the entry in the Translations pane or use the Sync button on the "Translations pane" on page 1048 to restore the connection. Same text, different translation Should the same text be translated differently in different locations? Then you need to add a 'context' to the translation entry: 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-911.html">PAGE 911</a></h6>
<p>Tagging text that is inserted by a script OL Connect will also apply translations to content that is inserted by personalization scripts, but only if that content is marked for translation, and if there is a matching translation entry. 1. On the Translations pane, click on the New Empty String button to create the translation entry. 2. Make sure that any element in which the text is inserted, are tagged for translation.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-912.html">PAGE 912</a></h6>
<p>One way to avoid this is to split the text around and inside HTML tags into separate chunks, no matter how short. Select the respective text in the template and select Wrap in Span from the contextual menu. Subsequently tag the new <span> element for translation. Alternatively you could also add a comment explaining that the HTML tag should not be changed. To add a comment, simply double-click the entry in the Translations pane and enter your comment in the Comments field.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-913.html">PAGE 913</a></h6>
<p>1. Double-click the respective entry on the Translations pane. 2. Check the Pluralization option. 3. Select the data field that holds the number. Note Pluralization cannot be based on a data field in a detail table. 4. Now there are two possibilities: l l Click OK. Proceed with the translation process after you've created all translation entries and enabled pluralization as needed. For further instructions see "Translating templates" on page 907. Enter the singular and plural and click OK.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-914.html">PAGE 914</a></h6>
<p>Tip Translation tools are capable of combining .pot files. Combining .pot files may also result in .po files that contain translations for entries in multiple templates. This can be an interesting feature, especially when there are multiple templates in a project, as this eliminates the need to maintain individual .po files for each template. For information about the translation process, see "Translating templates" on page 907. Exporting a file for translation (.pot) A .</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-915.html">PAGE 915</a></h6>
<p>Updating an imported .po file OL Connect Designer monitors the .po file on disk (in the folder from which it was last imported) for changes. When a .po file on disk has changed, the respective .po file in the template gets a small asterisk behind its name. Right-click the file in the Translations folder and select Update from the contextual menu to import the latest changes. Using a remote .po file In order to use a remote .po file, you must add the URL to the Translations folder on the Resources pane. 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-916.html">PAGE 916</a></h6>
<p>l "Styles pane" on page 1047 l "Translations pane" on page 1048 l "Workspace" on page 1049 (Source, Design and Preview tabs) l "Data Model pane" on page 1031 l "Scripts pane" on page 1044 l "Preflight Results and Messages" on page 1034 Dialogs Dialogs can allow you to perform a command or make settings. They can also ask you a question or provide you with information or progress feedback.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-917.html">PAGE 917</a></h6>
<p>Attachments dialog The Attachments dialog lets you add and remove static Email attachments. For more information about email attachments, see: "Email attachments" on page 537. l l l Add: Click this button to open the Select File dialog (see below). Delete: Deletes the file from the list of attachments. It doesn't remove any files from the template's resources.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-918.html">PAGE 918</a></h6>
<p>and their location should be accessible from the machine on which the template's output is produced. External files are updated (retrieved) at the time the output is generated. Bar Chart Properties dialog The Bar Chart dialog appears when a Bar Chart object is right-clicked and the Chart... option is clicked. It determines how the Bar Chart is displayed in output and in Preview mode (see "Business graphics" on page 696).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-919.html">PAGE 919</a></h6>
<p>property; see: fontFamily.) l l l Size: Enter the size of the font. Defaults to 11. (Equivalent to the fontSize property; see: fontSize.) Color: Select the color in which to display text: click the colored square to open the Color Picker dialog ("Color Picker" on page 931), or enter a valid hexademical color (HTML Hex Color) or a predefined CSS color (CSS color names). (Equivalent to the color property; see: color.) 3D Group: Creates a 3D effect if both settings in this group are higher than 0.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-920.html">PAGE 920</a></h6>
<p>property; see: titleFontSize.) l Grid group: l l l Opacity: Enter the opacity percentage of the grid. Default is 15%. 100 is fully opaque, 0 is transparent. (Equivalent to the gridAlpha property; see: gridAlpha.) l Thickness: Enter a thickness for the grid lines. Default is 1. (Equivalent to the gridThickness property; see: gridThickness.) l Tick Length: Length of the tick marks. (Equivalent to the tickLength property; see: tickLength.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-921.html">PAGE 921</a></h6>
<p>in rotated charts. (Equivalent to the labelsEnabled property of the ValueAxis ; see: labelsEnabled.) l Frequency: Defines per how many grid lines a label will be placed. (Equivalent to the labelFrequency property of the ValueAxis ; see: labelFrequency.) Category Axis tab Settings on the Category Axis tab correspond to properties of the CategoryAxis class in the amCharts library; see: CategoryAxis.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-922.html">PAGE 922</a></h6>
<p>names). (Equivalent to the gridColor property; see: gridColor.) l l l Opacity: Enter the opacity percentage of the grid. Default is 15%. 100 is fully opaque, 0 is transparent. (Equivalent to the gridAlpha property; see: gridAlpha.) Thickness: Enter a thickness for the grid lines. Default is 1. (Equivalent to the gridThickness property; see: gridThickness.) Position: Specifies if a grid line is placed on the centre of a cell or on the beginning of a cell.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-923.html">PAGE 923</a></h6>
<p>section on the Source tab: "labelFrequency": "2" (replace 2 by the desired number of grid lines). l Axis group: l l l l Color: Select a color for the value axis: click the colored square to open the Color Picker dialog ("Color Picker" on page 931), or enter a valid hexademical color (HTML Hex Color) or a predefined CSS color (CSS color names). (Equivalent to the axisColor property; see: axisColor.) Opacity: Enter the opacity in percentage for the axis. 100 is fully opaque, 0 is transparent.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-924.html">PAGE 924</a></h6>
<p>l l l l Rotation: Rotation of the data labels. Supported notations: 0.0 , 0.0° or 0.0 deg . (Equivalent to the labelRotation property; see: labelRotation.) Offset: Vertical offset of the data labels. A positive offset moves the data labels up. A negative value moves them down. (Equivalent to the labelOffset property; see: labelOffset.) Anchor: Select whether the start, middle or end of a data label should be anchored to the bar. This setting moves the labels horizontally.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-925.html">PAGE 925</a></h6>
<p>l l l l l l l Position: Use the drop-down to select where the legend is shown: at the Right, Left, Top or Bottom. (Equivalent to the position property; see: position.) Align: Use the drop-down to select how to align the text in the labels: Left, Middle or Right. (Equivalent to the align property; see: align.) Horizontal Space: Horizontal space between legend items, in pixels. (Equivalent to the spacing property; see: spacing.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-926.html">PAGE 926</a></h6>
<p>property; see: markerType.) l l l l l Size: Enter the size (in pixels) for the Markers to be displayed. (Equivalent to the markerSize property; see: markerSize.) Label Gap: Enter the distance (in pixels) between the legend marker and legend text. (Equivalent to the markerLabelGap property; see: markerLabelGap.) Border Width: Use the drop-down to define the thickness of the border added to the Markers. The default value (0) means the line will be a "hairline" (1 px).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-927.html">PAGE 927</a></h6>
<p>files, they are styled with CSS. To learn how to use CSS in the Designer, see "Styling and formatting" on page 741 and "Styling templates with CSS files" on page 743. For information about specific properties and their options, see W3Schools CSS Reference. Note When no unit is added to a geometry value, such as the width, height, top or margin, the default unit will be added to the value; see "Print preferences" on page 848.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-928.html">PAGE 928</a></h6>
<p>l Text wrap group: l l l Float: Use the drop-down or type in the value for how to float the box, if the box is not in an absolute position (see Position, below). Equivalent to the CSS float property. Clear: Use the drop-down or type in the value for clearing pre-existing alignments. Equivalent to the CSS clear property. Positioning: Note that it depends on both the Context and the type of Box, which settings are available. For information about the different types of Boxes, see "Boxes" on page 692.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-929.html">PAGE 929</a></h6>
<p>l General group: l l Color: Specify the color of the box background: select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 931). Alternatively you could type a name or value in the Color field directly.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-930.html">PAGE 930</a></h6>
<p>Border tab For information about borders see "Border" on page 772. l l Same for all sides: Defines the border properties for all sides using the Top properties. Equivalent to the CSS border property. Top, Left, Bottom, Right: Each group defines the following properties: l l l Width: Specify the thickness of the border. Equivalent to the CSS borderwidthproperty. Style: Specify the style of the border such as solid, dashed or dotted. Equivalent to the CSS border-style property.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-931.html">PAGE 931</a></h6>
<p>l Child (optional): When specified, the Copy Fit feature will only be applied to the given child element (an element inside the Box or Div). Specify the element by giving its ID, for example: #product, or class, for example: .product - note the dot. Color Picker The Color Picker dialog appears when creating a color in the formatting dialogs of certain elements, for example border colors in boxes and paragraphs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-932.html">PAGE 932</a></h6>
<p>Colors Properties The Colors Properties defines and sets named colors used in the template; see "Colors" on page 774. Named colors can be used throughout the templates, in all contexts. They are visible in color selector dialogs and useable with their names in style sheets; see "Styling and formatting" on page 741. l l l l Color Type Selector: Click and use the drop-down to display which color types to show in the list: All, RGB, CMYK or Spot colors.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-933.html">PAGE 933</a></h6>
<p>l l l Red/Green/Blue (RGB): Each slider sets the values of 0-255 for the color. Set the value using the sliders or type in the value directly in the input boxes. Color Preview: Box displaying the preview of the color (converted to RGB when relevant). Tint: l l l Source: Select an existing Color in the template. The tint or opacity will be applied to this color. Tint/Opacity: The slider sets the percentage of tint or opacity.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-934.html">PAGE 934</a></h6>
<p>l Options Group: l Rendering intent: Use the drop-down to specify how colors are converted that are out of range of a profile. For example, you may use tricks like reducing the saturation of the entire print so that a color that is out of range still appears a bit more vibrant than ones that are in range. Rendering intents use different methods to trick the eye into believing that the print can reproduce irreproducible colors.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-935.html">PAGE 935</a></h6>
<p>Includes Tab The Includes tab defines which style sheets and JavaScript files should be included in the Web context when generating output, and in which order; see "Includes dialog" on page 943. For more information about stylesheets, see "Styling templates with CSS files" on page 743. For more information about using JavaScript, see "Using JavaScript" on page 564. Edit Label Properties The Edit Label Properties defines how a Pie Chart Label displays its title and data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-936.html">PAGE 936</a></h6>
<p>standard layout. l Custom: To create a custom PDF report, you need two files: l l Template: A template design with the desired layout and variable data. This .OL-TEMPLATE file has to be made in the Designer. DataMapper: A data mapping configuration that provides the variable data. This .OL-datamapper file has to be made in the DataMapper module, using the standard XML template report as data sample.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-937.html">PAGE 937</a></h6>
<p>Custom tab On this tab custom properties can be defined. Click the Add icon and enter a name for the property and a value. Use the arrow icons to reorder the list of custom properties. Custom property lists can be exported to, and imported from, a .CSV file, using the Import and Export buttons. Find/Replace Dialog The Find/Replace dialog can replace text within the current template. The scope of the replacement depends on the currently selected tab in the Workspace.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-938.html">PAGE 938</a></h6>
<p>l Options l l l l l Case sensitive: Use a case sensitive search, which differentiates TEXT from text or TexT. Wrap search: Loop back from the end of the template or selection to its beginning, when the Search is at the end of the template or the selection. Whole word: Searches for the source string as a whole word. Incremental: With this option selected, each letter you type in the Find field causes the editor focus to move to the first complete occurrence of the text you are typing.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-939.html">PAGE 939</a></h6>
<p>The following buttons appear to the right of the list of fonts: l New: Click to open the Edit Font dialog to add a new font. l Edit: Click to open the Edit Font dialog to edit the currently selected font. l Remove: Click to delete the currently selected font entry. l Duplicate: Click to create a copy of the currently selected font entry. Edit Font The Edit Font dialog appears when clicking New or Edit from the Fonts Dialog. l l l Name: Enter the name that should be used to refer to the font.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-940.html">PAGE 940</a></h6>
<p>All settings in this dialog are in fact CSS properties. Cascading Style Sheets (CSS) were originally designed for use with web pages: HTML files. Since Designer templates are HTML files, they are styled with CSS. To learn how to use CSS in the Designer, see "Styling and formatting" on page 741 and "Styling templates with CSS files" on page 743. For information about specific properties and their options, see W3Schools CSS Reference.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-941.html">PAGE 941</a></h6>
<p>l l Clear: Use the drop-down or type the value to clear pre-existing alignments. Equivalent to the CSS clear property. Positioning: l l l l l l Position: Use the drop-down or type in the value for the type of positioning for the image. Equivalent to the CSS position property (see "Using the CSS position property" on page 760). Top: Set the vertical offset between this image and its parent's top position. Equivalent to the CSS top property.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-942.html">PAGE 942</a></h6>
<p>l Top, Left, Bottom, Right: Each group defines the following properties: l l l Width: Specify the thickness of the border. Equivalent to the CSS border-width property. Style: Specify the style of the border such as solid, dashed or dotted. Equivalent to the CSS border-styleproperty. Color: Specify the color of the border: select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 931).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-943.html">PAGE 943</a></h6>
<p>Names that represent files or folders on disk are case-insensitive, while all other names are case-sensitive. l l l Rename: Import the resource, giving its name a suffix to make it unique in the target folder. Note that when a section is renamed, the properties of its context are not copied over, except for Includes (Web contexts only; see "Includes" on page 546). Includes are transferred to the imported section. Overwrite: Replace the existing resource.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-944.html">PAGE 944</a></h6>
<p>Email clients do not read CSS files and some even remove a <style> tag when it is present in the email's header. Nevertheless, CSS files can be used with the Email context in the Designer. When generating output from the Email context, the Designer processes all CSS rules that apply to the content of the email to inline style properties, as if local formatting was applied. 1. From the File types dropdown, select Stylesheets, JavaScripts or all. 2.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-945.html">PAGE 945</a></h6>
<p>It is recommended to check at least one of the options: async or defer, or both. Page content will become visible more quickly, resulting in a better user experience. If you enable both options, async takes precedence on modern browsers, while older browsers that support defer but not async will fallback to defer. When neither of the options is checked, the script gets fetched and executed immediately, interrupting the page loading and rendering.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-946.html">PAGE 946</a></h6>
<p>Note The JSON Sample Data is not stored with the template. In order to reuse the data you should create a JSON file on disk and load it via the File option in this dialog. Types of JSON data You can add the following types of JSON data: l A JSON object or an array of JSON objects representing records. The data type is derived from the data: l Any value surrounded with quotes is converted to a field of type String. l Any numeric value containing a period is converted to a field of type Float.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-947.html">PAGE 947</a></h6>
<p>A single record with a detail table { "name":"Peter Parker", "email":"parkerp@localhostcom", "detail": [{"id":"inv123","ExtraData":"hello"}, {"id":"456","ExtraData":"world"}] } A JSON Record Data List A JSON Record Data List describes a list of data fields (as name/value pairs), a data table schema and nested data records (if any) for one or more data records. This example holds a single, simple record.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-948.html">PAGE 948</a></h6>
<p>General tab Most settings on the General tab correspond to properties of the AmSerialChart class in the amCharts library; see: AmSerialChart. l General Group: l l l l Rotate: Check to rotate the chart 90 degrees so that the bars are horizontal starting from the left. (Equivalent to the rotate property; see: rotate.) Stack Series: Check to stack the values in one bar, instead of having one bar per value. (Equivalent to the stackType property of the ValueAxis ; see: stackType.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-949.html">PAGE 949</a></h6>
<p>l Angle: The angle of the 3D part of the plot area. (Equivalent to the angle property; see: angle.) Value Axis tab Settings on the Value Axis tab are equivalent to properties of the ValueAxis class in the amCharts library; see: ValueAxis. l Title group: l l l l l Label: Enter a label for the value axis (the Y axis, or the X axis if the graph is rotated). (Equivalent to the title property; see: title.) Bold: Check this option if the title should be bold.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-950.html">PAGE 950</a></h6>
<p>l l Thickness: Enter a thickness for the grid lines. Default is 1. (Equivalent to the gridThickness property; see: gridThickness.) l Tick Length: Length of the tick marks. (Equivalent to the tickLength property; see: tickLength.) Axis group: l l l l Color: Select a color for the value axis: click the colored square to open the Color Picker dialog ("Color Picker" on page 931), or enter a valid hexademical color (HTML Hex Color) or a predefined CSS color (CSS color names).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-951.html">PAGE 951</a></h6>
<p>Category Axis tab Settings on the Category Axis tab correspond to properties of the CategoryAxis class in the amCharts library; see: CategoryAxis. l Title group: l l l l l Label: Enter a label for the category axis (the X axis, or the Y axis if the graph is rotated).(Equivalent to the title property; see: title.) Bold: Check if you want the title to be bold. (Equivalent to the titleBold property; see: titleBold.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-952.html">PAGE 952</a></h6>
<p>of a cell. (Equivalent to the gridPosition property; see: gridPosition.) Tip The position of the ticks (which is Middle by default) does not move with the grid. To change the tick position, add the following to the categoryAxis section on the Source tab: "tickPosition": "start" . l Tick Length: Length of the tick marks. (Equivalent to the tickLength property; see: tickLength.) Tip By default, one label per grid line will appear on the Category axis.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-953.html">PAGE 953</a></h6>
<p>property; see: axisAlpha.) l l Thickness: Enter the thickness of the axis. (Equivalent to the axisThickness property; see: axisThickness.) Auto Wrap: Specifies if axis labels (when horizontal) should be wrapped if they don't fit in the allocated space. (Equivalent to the autoWrap property; see: autoWrap.) Graphs Settings on the Graphs tab correspond to properties of the AmGraph class in the amCharts library; see: AmGraph. l Line: l Thickness: Sets the thickness of the lines in a Line chart.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-954.html">PAGE 954</a></h6>
<p>property; see: position.) l l l l l Horizontal Space: Horizontal space between legend items, in pixels. (Equivalent to the spacing property; see: spacing.) Vertical Space: Enter a numerical value (in pixels) to define the vertical space between legend items, and also between the legend border and the first and last legend item. (Equivalent to the verticalGap property; see: verticalGap.) Max Columns: Enter a numerical value to define the maximum number of columns in the legend.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-955.html">PAGE 955</a></h6>
<p>property; see: markerLabelGap.) l l l Border Width: Use the drop-down to define the thickness of the border added to the Markers. The default value (0) means the line will be a "hairline" (1 px). In case the Marker type is line, this style will be used for the line thickness. (Equivalent to the markerBorderThickness property; see: markerBorderThickness.) Border Color: Color of the Legend's border.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-956.html">PAGE 956</a></h6>
<p>l l l Data Field: Select this to use a data field from the record. The locale will be recordspecific in this case. Locale: Use the drop-down to select a specific locale. Only enabled when Explicit Locale is selected above. Data Field: Use the drop-down to select a field within the current data model that contains the locale. This field must be a string and contain the exact locale to be used, such as "en" or "fr-CA". It cannot be an alias such as "english" or "french".</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-957.html">PAGE 957</a></h6>
<p>Properties Tab l l Name: The name of the Media, displayed in all drop-downs where the Media is shown as well as in the Resources Pane. Size: This group is read-only and only used to display the size selected in the linked Print section's properties (see "Print section properties" on page 987). l Page Size: The named page size. l Width: The width of the page. l Height: The height of the page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-958.html">PAGE 958</a></h6>
<p>l Media Type: The type of paper, such as Continuous, Envelope, Labels, Stationery, etc. l Weight: The weight of the media in grammage (g/m2). l Front Coating: The pre-process coating applied to the front surface of the media, such as Glossy, High Gloss, Matte, Satin, etc. l Back Coating: The pre-process coating applied to the front surface of the media. l Texture: The texture of the media, such as Antique, Linen, Stipple or Vellum.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-959.html">PAGE 959</a></h6>
<p>l l Project wizards: Lists all "Project Wizards" on page 973. A Project Wizard generates a Connect solution consisting of a Workflow configuration as well as any templates, data mapping configurations, and Print Presets that are used in that configuration. Templates: Lists all types of templates that you can create with a wizard. See "Templates" on page 451.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-960.html">PAGE 960</a></h6>
<p>Package dialog The Package dialog saves templates, data mapping configurations and Print Presets as a package file. Package files can be sent to other Connect Designer users. l Configurations: Initially this list contains the Connect files that are currently open. l l Browse: This button opens the Select Files dialog that lets you add one or more templates (*.OL-template) data mapping configurations (*.OL-datamapper) and Print Presets (*.OL-jobpreset, *.OL-outputpreset) to the list.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-961.html">PAGE 961</a></h6>
<p>The Apply button lets you preview the template with the new settings. For information about text and how to style it see "Text and special characters" on page 735 and "Styling text and paragraphs" on page 753. Formats tab l General group: l l l l l l Line-height: Specify the height of each line in the element's text, in measure or percentage. Note that this is not spacing between lines, but rather the complete height of the line itself including the text.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-962.html">PAGE 962</a></h6>
<p>to the widows property. Widows and orphans are ignored if the page-breakinside property is set to avoid. l Orphans: Specifies how to handle orphans within the paragraph (lines appearing alone at the end of a page if the paragraph does not fit on the current one). Equivalent to the orphans property. Note For more information on page breaks, widows and orphans, see the W3 Paged Media reference.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-963.html">PAGE 963</a></h6>
<p>l Color: Specify the color of the border. select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 931). Alternatively you could type a name or value in the Color field directly. It must be a predefined CSS color name (CSS color names), a hexadecimal color code (HTML Hex Color), an RGB color value, for example rgb (216,255,170) or a CMYK color value, for example cmyk(15%, 0%, 33%, 0%).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-964.html">PAGE 964</a></h6>
<p>l Text Group: Determines how text is displayed in labels and legends. l l l l Font: Type in the font-face to use to display text. The font must be installed on the system and defaults to Verdana if the font is not found. (Equivalent to the fontFamily property; see: fontFamily.) Size: Type in the size of the font. Defaults to 11. (Equivalent to the fontSize property; see: fontSize.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-965.html">PAGE 965</a></h6>
<p>l l Color: Enter a color for the outline: a valid HTML hexadecimal color value (HTML Hex Color) or a predefined CSS color (CSS color names), or click the colored square to open the Color Picker dialog ("Color Picker" on page 931). (Equivalent to the outlineColor property; see: outlineColor.) Opacity: Enter the opacity of the outline. 100 is fully opaque, 0 is transparent. (Equivalent to the outlineAlpha property; see: outlineAlpha.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-966.html">PAGE 966</a></h6>
<p>line: l [[title]] : Refers to the field label. l [[percents]] : Contains the percentage of the Pie chart the value represents. l [[value]] : Contains the numerical value of the field. Any text: Adding text (such as a dollar sign or column, etc) will make it appear in each label. (Equivalent to the labelText property; see: labelText.) l l l Tick Group: Defines how ticks (line between the Pie chart and its labels) is shown. l l l Radius: The distance between the label and the slice, in pixels.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-967.html">PAGE 967</a></h6>
<p>property; see: enabled.) l Legend Group: Defines how the legends are shown. l l l l l l l Position: Use the drop-down to select where the legend is shown: at the Right, Left, Top or Bottom. (Equivalent to the position property; see: position.) Align: Use the drop-down to select how to align the text in the labels: Left, Middle or Right. (Equivalent to the align property; see: align.) Horizontal Space: Horizontal space between legend items, in pixels.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-968.html">PAGE 968</a></h6>
<p>l l l l l l Type: Use the drop-down to select in which shape the Markers are displayed; "none" hides the Markers completely. (Equivalent to the markerType property; see: markerType.) Size: Enter the size (in pixels) for the Markers to be displayed. (Equivalent to the markerSize property; see: markerSize.) Label Gap: Enter the distance (in pixels) between the legend marker and legend text. (Equivalent to the markerLabelGap property; see: markerLabelGap.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-969.html">PAGE 969</a></h6>
<p>the "Scripts pane" on page 1044 execute. It helps greatly in troubleshooting performance issues caused by scripting (see also: "Testing scripts" on page 862). When the dialog opens, the script profiler runs automatically, on 1000 instances of all the scripts by default (this can be changed through the "Scripting preferences" on page 851). Note The script profiler can take a while, so please be patient.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-970.html">PAGE 970</a></h6>
<p>Note Rasterization options are only available for Boxes (<div> elements); see "Boxes" on page 692. Note A business graphic in an Email section is rasterized by default and output as PNG image, because email clients usually don't support SVG images. SVG images in an Email section give an error in the Preflight window (see "Doing a Preflight" on page 864).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-971.html">PAGE 971</a></h6>
<p>Scripts and call stack The left side of the window displays all enabled scripts that apply to the current context, with the call stack on top. If the selector of a standard script or post pagination script has no matches in the current resource (Master Page or section) the script will be skipped. If an error is thrown, the rest of the current script is skipped and execution continues with the next script. In the call stack, frames are ordered from new to old, top to bottom.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-972.html">PAGE 972</a></h6>
<p>Tip When you click on an identifier (such as a variable name) in a script, the overview ruler at the right highlights all other occurrences of that identifier straightaway. Variables At the bottom right the Script Debugger shows a hierarchical overview of all variables in the scope chain and their state. This information is always relative to the current stack frame, which is the one that's selected on the left.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-973.html">PAGE 973</a></h6>
<p>Step-through buttons The buttons at the bottom of the Script Debugger let you step through the code. When you step through the code it always steps relative to the most recent stack frame. l l l l l l Into (F5): Step into the function on the current line, if possible. A common use case for this is to step into a results.each() call. Note that you can only step into functions that are defined in user scripts. For other statements this behaves like (Step) Over. Over (F6): Step over the current line.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-974.html">PAGE 974</a></h6>
<p>l l Print promotional jobs. This project generates a batch of basic personalized letters, in the format that was selected in the wizard: PDF, PCL or PostScript Level 3. (See: "Project Wizard: Print Promotional Jobs" on page 188.) The Workflow configuration uses the All In One plugin (see "Print processes with OL Connect tasks" on page 220). Print transactional jobs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-975.html">PAGE 975</a></h6>
<p>l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder. The Workspace folder is meant to be used when debugging the solution (see "Basic Email - Project Wizard" on the previous page). Send Templates and resources to Workflow: Check this option to send the necessary resource files to the active Workflow instance on the local machine.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-976.html">PAGE 976</a></h6>
<p>menu. For more detailed information about this project, and instructions on how to test and customize it, see "Project Wizard: COTG Timesheets" on page 180. The wizard contains the following options. l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-977.html">PAGE 977</a></h6>
<p>the same computer, making it impossible for the COTG app to submit form data to Workflow on the same computer. The COTG user guide explains how to change these restrictions; see COTG user guide. l Send Templates and resources to Workflow: Check this option to send the necessary resource files to the active Workflow instance on the local machine.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-978.html">PAGE 978</a></h6>
<p>For more detailed information about this project, and instructions on how to test and customize it, see "Project Wizard: Print Promotional Jobs" on page 188. The wizard contains the following options. l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-979.html">PAGE 979</a></h6>
<p>For more detailed information about this solution and instructions on how to test and customize it, see "Project Wizard: Print Transactional Jobs" on page 195. To start the Project Wizard, select File > New > Project Wizards > Print Transactional Jobs from the menu. It contains the following options. l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-980.html">PAGE 980</a></h6>
<p>l Workflow l l Project folder: Select a folder. In this folder, the Project Wizard will create two folders: Configurations and Workspace. The project's resource files are saved to the Configurations folder. The Workspace folder is meant to be used when debugging the solution (see "Submitting Data with Web Forms - Project Wizard" on the previous page). Send Templates and resources to Workflow: Check this option to send the necessary resource files to the active Workflow instance on the local machine.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-981.html">PAGE 981</a></h6>
<p>Without these files the Workflow configuration can be inspected, but it cannot be tested; in order to test the configuration, you'll have to send the resources manually (see "Sending files to Workflow" on page 457). Note In order for this option to work, Workflow and the Designer must be installed on the same machine. In addition, the PPMessenger service must be running. By default, this service is always started automatically from the moment Workflow has been installed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-982.html">PAGE 982</a></h6>
<p>Options For the options in Conditional Script wizards see "Conditional script dialog" on page 985. In other Script wizards, the following options are available. l Name: The name of the script, making it easier to identify it. l Selector/Find text: The Selector or Text to apply the result of the script to. l l l Selector: Uses CSS selectors to find the element to which the script applies Text: Uses text as a trigger for the script. The script applies to all instances of the text found in the template.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-983.html">PAGE 983</a></h6>
<p>l [+]: Adds a new line to the Wizard Results. Note that by default there is no line return between fields in the list. Adding <br> in the Suffix or Prefix field can establish a line return. l [-]: Removes the currently selected line in the Wizard Results list. l Arrow Up: Moves the currently selected line up one position. l Arrow Down: Moves the currently selected line down one position. l Refresh Types: Updates field types to match the types in the active data model.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-984.html">PAGE 984</a></h6>
<p>Expanded Script window When expanded, the Script window replaces all parts of the wizard below the Selector by a box in which the script can be typed. See "Writing your own scripts" on page 853. For an overview of keyboard shurtcuts that can be used in this script editor, see "Keyboard shortcuts" on page 1009. Chart Script dialog The Chart Script dialog specifies which variable data will be displayed in a chart and shows a preview of both the chart (on the right hand side) and the data (at the bottom).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-985.html">PAGE 985</a></h6>
<p>l Values: Select data fields with a numerical value. l l l Column: Removing the topmost check deselects all data fields. Labels: Click the label to enter a new label for a field. It depends on the Input Type where the labels appear: with Data Fields, the labels appear under the x-axis of the chart; with a Data Table, labels appear in the Legend. Color: Click on the color to open the Color Picker dialog ("Color Picker" on page 931) and select a different color.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-986.html">PAGE 986</a></h6>
<p>Conditional. If the current element has neither an ID nor a class, an ID will be automatically generated. See "Showing content conditionally" on page 810. The options in the Conditional Script wizard are: l Name: The name of the script, making it easier to identify it. l Selector: The Selector or Text to apply the result of the script to. l l l Selector: Uses CSS selectors to find the element to which the script applies. Text: Uses text as a trigger for the script.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-987.html">PAGE 987</a></h6>
<p>Email section properties For information about Email sections, see: "Email templates" on page 526. Properties tab The properties for an Email section are minimal and contain the following options: l l l Name: Enter the name of the Section in the Email Context. This has no effect on output. The Meta Information group lists all <meta> tags that will be added to the header of the email. See "Meta information" on page 535.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-988.html">PAGE 988</a></h6>
<p>These properties can be used in a Control Script; see the topic "Control Scripts" on page 885 and the page about the section object: "section" on page 1395. For an explanation of other settings on the Properties tab, see "Page settings: size, margins and bleed" on page 498. Includes Tab The Includes tab defines which style sheets and JavaScript files should be applied to the section when generating output, and in which order; see "Includes dialog" on page 943.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-989.html">PAGE 989</a></h6>
<p>Properties tab For information about the settings on the Properties tab, see "Setting the title, meta data and a shortcut icon" on page 552. Includes Tab The Includes tab defines which style sheets and JavaScript files should be included in the section when generating output, and in which order; see "Includes dialog" on page 943. For more information about stylesheets, see "Styling templates with CSS files" on page 743. For more information about using JavaScript, see "Using JavaScript" on page 564.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-990.html">PAGE 990</a></h6>
<p>A test template automatically appears in the app's Repository for 4 days from the moment it is sent. Once downloaded it remains accessible in the app's Library for 2 days. Note The dialog is only available on templates containing a Web context. It does not, however, verify whether any Capture OnTheGo form elements have been added to the page. The dialog contains the following options: l General group: l l l l l l l Server: Select the Capture OnTheGo server.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-991.html">PAGE 991</a></h6>
<p>Send (Test) Email The Send Email dialog is used to generate mail output and send it to each recipient in the Record Set. To open this dialog, select File > Send Email, on the menu. Note that the subject, recipients etc. must be specified before sending the email; see "Email header settings" on page 530. For more information about the process of sending out email and the possible settings, see "Generating Email output" on page 1438.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-992.html">PAGE 992</a></h6>
<p>embedded in the file. This HTML file is then added as an attachment to the outgoing email. l Outgoing mail settings: l Presets: Use the drop-down to select a preset. These presets are configured in the Email (SMTP) preferences; see "Email SMTP settings" on page 531. Note It is recommended to use an Email Service Provider to get access to tools that give you full control over your mailings, like open rates, click through rates etc. See "Using an ESP with PlanetPress Connect" on page 1442.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-993.html">PAGE 993</a></h6>
<p>Tip Actually, the path may not begin with 'C:\Users', as this is languagedependent. On a French system, for example, it would be 'C:\Utilisateurs'. Type %userprofile% in a Windows File Explorer and press Enter to open the actual current user's home directory. There are two ways to make it easier to find the file that you need: l The Show drop-down list lets you select the type of preset that you want to open.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-994.html">PAGE 994</a></h6>
<p>l Click Resources, Disk or Url, depending on where the image is located. l l l Resources lists the images that are present in the Images folder on the Resources pane. Disk lists image files that reside in a folder on a hard drive that is accessible from your computer. Click the Browse button to select a folder (or an image in a folder). As an alternative it is possible to enter the path manually. You can give a local path (e.g. C:\Images\Test.jpg) or use the "file" protocol.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-995.html">PAGE 995</a></h6>
<p>page 505). Note Master Pages, Media and Duplex printing options can also be set in a Control Script (see "Control Scripts" on page 885 and "Control Script API" on page 1351). This is especially useful when you need identical sections with different settings. General options The first option defines Duplex printing, which also enables or disables the settings for the Back side of each sheet.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-996.html">PAGE 996</a></h6>
<p>will be printed on it. As such it does not count in the Content Page Number and Content Page Count markers which can be inserted via the Insert menu (see "Page numbers " on page 499). l Media: Defines the media that is used. If the Media has Virtual Stationery defined, the selected image is shown as a background to each page that corresponds to the media's sheet position. l l l Edit Script: Click this button to create a script that defines which Media is used.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-997.html">PAGE 997</a></h6>
<p>l l l Duplicate: Click to create a duplicate of the currently selected rule in the Rule List using the Edit Rule dialog. The default name for the new rule is the name of the current one plus "-duplicated". See "New/Edit Rule dialog" below. Move Up: Move the currently selected rule in the Rule List up one position in the list. Move Down: Move the currently selected rule in the Rule List down one position in the list. l Save: Click to save all changes to the style sheet and close the dialog.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-998.html">PAGE 998</a></h6>
<p>colored square to create a new color or to manually enter a color value (a valid HTML color name or hexadecimal color code). This is equivalent to the CSS background-color property. l Spacing group: l l l l Letter Spacing: Set the space between characters in a text in measure or percentage. This is equivalent to the CSS letter-spacing property. Word Spacing: Set the space between each word in a text in measure or percentage. This is equivalent to the CSS word-spacing property.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-999.html">PAGE 999</a></h6>
<p>l l Display: Select how to display the element. This can also be used to hide an element completely using the none option. See CSS Display. Equivalent to the display property. Breaks group: l l l l l Before: Specifies whether a page break should occur before the element. Equivalent to the page-break-before property. Inside: Specifies whether to accept page breaks within the element. Equivalent to the page-break-inside property. After: Specifies whether a page break should occur after the element.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1000.html">PAGE 1000</a></h6>
<p>l l Same for all sides: Defines the border properties for all sides using the Top properties. Equivalent to theborderproperty. Top, Left, Bottom, Right: Each group defines the following properties: l l l Width: Specify the thickness of the border. Equivalent to the border-width property. Style: Specify the style of the border such as solid, dashed or dotted. Equivalent to the border-style property. Color: Specify the color of the border.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1001.html">PAGE 1001</a></h6>
<p>For more information about template translation, see "Translating templates" on page 907. l l New Strings: Lists the texts, found in elements that are tagged for translation, for which there is no matching translation entry. Orphaned Strings: Lists the translation entries that seem to be unused: currently there is no matching element in the content of the template for them.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1002.html">PAGE 1002</a></h6>
<p>All settings in this dialog are in fact CSS properties. Cascading Style Sheets (CSS) were originally designed for use with web pages: HTML files. Since Designer templates are HTML files, they are styled with CSS. To learn how to use CSS in the Designer, see "Styling and formatting" on page 741 and "Styling templates with CSS files" on page 743. For information about specific properties and their options, see W3Schools CSS Reference.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1003.html">PAGE 1003</a></h6>
<p>l Positioning: l l l l l l l Position: Use the drop-down or type in the value for the type of positioning for the table. Equivalent to the CSS position property. Top: Set the vertical offset between this table and its parent's top position. Equivalent to the CSS top property. Left: Set the horizontal offset between this table and its parent's left position. Equivalent to the CSS left property. Bottom: Set the vertical offset between this table and its parent's bottom position.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1004.html">PAGE 1004</a></h6>
<p>l l l All sides: Check to set all padding to use the Top value. Equivalent to the CSS padding property. Top, Left, Bottom, Right: Set padding for each side. Equivalent to the CSS padding-left, padding-top, padding-right and padding-bottom properties. Margin group: Defines margins (spacing outside the element) in measure or percentage: l l All sides: Check to set all margins to use the Top value. Equivalent to the CSS margin property. Top, Left, Bottom, Right: Set the margin for each side.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1005.html">PAGE 1005</a></h6>
<p>l General group: l l Color: Specify the color of the table background:select a named color (defined in the Colors Editor) from the drop-down, or click the colored square to open the Color Picker dialog ("Color Picker" on page 931). Alternatively you could type a name or value in the Color field directly.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1006.html">PAGE 1006</a></h6>
<p>Cell Tab l l l Width: Set the width of the table in measure or percentage. Equivalent to the CSS width property. Height: Set the height of the table in measure or percentage. Equivalent to the CSS height property. Vertical Align: Specify how text is vertically aligned in the cell: top, middle, bottom or baseline. With the baseline value all the table data share the same baseline. Often this has the same effect as the bottom value. However, if the fonts are in different sizes, baseline looks better.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1007.html">PAGE 1007</a></h6>
<p>l Underline: Sets the text-decoration to underline. l Strikethrough: Sets the text-decoration to line-through. l Subscript: Sets the vertical-align to super. l Superscript: Sets the vertical-align to sub. l Capitalize: Sets the text-transform to capitalize. l Uppercase: Sets the text-transform to uppercase. l Lowercase: Sets the text-transform to lowercase. l Small-caps: Sets the font-variant to small-caps. Spacing Tab For information about spacing see "Spacing" on page 783.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1008.html">PAGE 1008</a></h6>
<p>a hexadecimal color code (HTML Hex Color), an RGB color value, for example rgb (216,255,170) or a CMYK color value, for example cmyk(15%, 0%, 33%, 0%). Equivalent to the CSS border-color property. Background Tab For information about backgrounds see "Background color and/or image" on page 770.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1009.html">PAGE 1009</a></h6>
<p>l String: l l l Source: This is the text that will be presented to the translator, and that will be replaced with a translation when OL Connect generates output from the template. It is case-sensitive. When a new translation entry is created by tagging an HTML element for translation (see "Tagging elements for translation" on page 909), the text of that element gets copied to this field.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1010.html">PAGE 1010</a></h6>
<p>Although some of the keyboard shortcuts are the same, this isn't a complete list of Windows keyboard shortcuts. To find that, refer to the documentation of the Windows version that you are using. Menu items The following key combinations activate a function in the menu. Key combination Function Alt Put the focus on the menu. (Alt + the underlined letter in a menu name displays the corresponding menu.) The menu can then be browsed using the Enter key, arrow up and arrow down buttons.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1011.html">PAGE 1011</a></h6>
<p>Key combination Function Ctrl + O Open file Ctrl + P Print Ctrl + R Show/hide rulers Ctrl + S Save file Ctrl + V or: Shift + Insert Paste Ctrl + X or: Shift + Delete Cut Ctrl + W Close file Ctrl + Y or: Ctrl + Shift + Z Redo Ctrl + Z Undo Ctrl + Alt + ; Lock guides Ctrl + Shif + R Clear preview cache Ctrl + Shift + S Save all Ctrl + Shift + W Close all Ctrl + Shift + ; Snap to guides Ctrl + ; Show guides Ctrl + ' Show/hide virtual stationery Page 1011</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1012.html">PAGE 1012</a></h6>
<p>Key combination Function Ctrl + \ Highlight Master Page items Ctrl + F5 Revert Ctrl + F10 Save as Ctrl + F11 "Send COTG Test" on page 989 Ctrl + F12 "Send to Workflow dialog" on page 992 Ctrl + Shift + F12 Package Workspace The following key combinations activate a function in the Workspace.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1013.html">PAGE 1013</a></h6>
<p>Key combination Function Workspace) Ctrl + Shift + F6 Previous editor (when there is more than one file open in the Workspace) Shift + F10 or: Ctrl + Shift + F10 Open context menu Design and Preview tab In addition to the keyboard shortcuts for menu items and the Workspace, the following key combinations have a special function in the Design tab and Preview tab of the Workspace.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1014.html">PAGE 1014</a></h6>
<p>Key combination Function Tip You can also use the mouse's scroll wheel in combination with the Ctrl button to gradually zoom in or out.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1015.html">PAGE 1015</a></h6>
<p>Key combination Function Ctrl + I Indent (Tab) Ctrl + J l l Script Editor: Add a line break. Other editors: Incremental find; start typing a search string directly after pressing this key combination. Ctrl + K Find next Ctrl + L Go to line; a prompt opens to enter a line number.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1016.html">PAGE 1016</a></h6>
<p>Data Model pane You can use the following keys to browse records in the Data Model pane: l Page Up: next record l Page Down: previous record l Home: first record l End: last record. Menus The following menu items are shown in the Designer menu. For a list of keyboard shortcuts, see "Keyboard shortcuts" on page 1009. File Menu l l l l l l New...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1017.html">PAGE 1017</a></h6>
<p>l l l l l l Save: Saves the current data mapping configuration or template to its current location on disk. If the file has never been saved, the Save As dialog appears instead. Save All: Saves the open files. If a file has never been saved, the Save As dialog opens for it. Save As...: Saves the current file to a new location on disk. Save a Copy: Save a copy of the current template in the selected Connect version's format. See "Saving a copy / down-saving a template" on page 455.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1018.html">PAGE 1018</a></h6>
<p>l l l l l l l Job Creation Presets: Opens the"Job Creation Presets Wizard" on page 1159 dialog. Output Creation Presets: Opens the "Output Creation Presets Wizard" on page 1173 dialog. Proof Print: Opens the "Print options" on page 1174 dialog as a Proof Print dialog which limits the number of records output. The options themselves are identical to the regular Print Output dialog. Send Email: Opens the Send Email dialog; see "Send (Test) Email" on page 991 and "Generating Email output" on page 1438.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1019.html">PAGE 1019</a></h6>
<p>l Locale...: Opens the Locale Settings dialog. See "Locale" on page 782. l Color Settings...: Opens the Color Settings dialog. See "Colors" on page 774. Insert Menu l l Image: Inserts an image using a resource that is local to the template, a resource on disk or a URL. See "Images" on page 724. Text: l l Wrap in span: Wraps selected text in a <span> element. The ID or class of the span can be used as a selector for scripts and styles.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1020.html">PAGE 1020</a></h6>
<p>l l l l Dashes and Spaces: Use the list to insert special dashes, such as an em-dash, and spaces, such as non-breaking spaces or an en-space. (The HTML code inserted for the dash or space is visible on the Source tab of the workspace.) Arrows: Use the list to insert directional arrows (in one of four directions). Geometric Shapes: Use the list to insert a special geometric shape, such as circles, triangles and squares.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1021.html">PAGE 1021</a></h6>
<p>l l Address...: Opens a dialog to add an <address> element. l Preformatted...: Opens a dialog to add a <pre> element. Structural Elements: l Div...: Opens a dialog to add a <div> element; see "Boxes" on page 692 l Span...: Opens a dialog to add a <span> element; see "Boxes" on page 692 l Article...: Opens a dialog to add an <article> element l Section...: Opens a dialog to add a <section> element (the HTML element, not a section in a context). l Header...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1022.html">PAGE 1022</a></h6>
<p>l l l l l l l Number Field...: Opens a dialog to add a Number Field; see "Number" on page 719. Hidden Field...: Opens a dialog to add a Hidden Field; see "Hidden field" on page 719. Label...: Opens a dialog to add a Label; see "Label" on page 719. Checkbox Field...: Opens a dialog to add a Checkbox; see "Checkbox" on page 720. Radio Button...: Opens a dialog to add a Radio Button; see "Radio Button" on page 720. Select Field...: Opens a dialog to add a Select (drop-down); see "Select" on page 721.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1023.html">PAGE 1023</a></h6>
<p>l l l l l l l l l l Barcode Scanner...: Opens a dialog to add a Barcode Scanner element, see "Barcode Scanner" on page 706. User Account...: Opens a dialog to add a User Account element, see "User Account" on page 711. Device Info...: Opens a dialog to add a Device Info element, see "Device Info" on page 709. Repository ID: Opens a dialog to add a Repository ID element, see "Repository ID" on page 710. Document ID: Opens a dialog to add a Document ID element, see "Document ID" on page 709.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1024.html">PAGE 1024</a></h6>
<p>dialog (Format > Text) and checking the appropriate style. See "Styling text and paragraphs" on page 753. l l l l l l Color: When text is selected, sets the text color by applying the color attribute to the text. The color submenu lists all the colors in the Colors Editor. Text...: Opens the Text Formatting dialog to modify the current text selection. See "Styling text and paragraphs" on page 753. Align: When an element is selected, determines how its contents is aligned inside the element.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1025.html">PAGE 1025</a></h6>
<p>l l l l l Box...: Opens the "Box Formatting dialog" on page 926 to modify the box where the cursor is located. Image...: Opens the "Image Formatting dialog" on page 939 to modify the image that is currently selected. Table...: Opens the "Table Formatting dialog" on page 1001 to modify the table in which the cursor is located. If the cursor is within a table embedded within another, the innermost table's formatting is the one modified. Table Cell...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1026.html">PAGE 1026</a></h6>
<p>l l l l Includes: Opens the Includes dialog; see "Includes dialog" on page 943. This option is only available when editing a Web section in the Workspace. Preview HTML: Opens the currently selected section in the default system browser to preview it. This feature works in all contexts. Profile Scripts: Opens the "Profile Scripts dialog" on page 968 to test script performance (see "Testing scripts" on page 862). Preflight: Opens the Preflight dialog.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1027.html">PAGE 1027</a></h6>
<p>l l l l l Preview View: Shows the template as it will output with the current record, with the personalized content (see "Personalizing content" on page 786). Refresh: Reloads the view, including static external images and remote stylesheets, and re-runs the scripts (the latter in Preview Mode only). Show Edges: Shows or hides a colored border around elements on the page. Rulers: Shows or hides the rulers in the Workspace. Rulers only appear for Print contexts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1028.html">PAGE 1028</a></h6>
<p>l l l l Preflight Results: Shows the results of a Preflight; see "Doing a Preflight" on page 864. l Attributes: Shows the "Attributes pane" below. l Styles: Shows the "Styles pane" on page 1047. l Translations: Shows the "Translations pane" on page 1048. l Data Model: Shows the "Data Model pane" on page 1031. Reset Perspective: Resets all toolbars and panes to the initial configuration of the module.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1029.html">PAGE 1029</a></h6>
<p>General These attributes are common to all elements in the template and will always appear. l l ID: A unique identifier for the selected element. Used for CSS selections (see "Styling templates with CSS files" on page 743) as well as scripts (see "Writing your own scripts" on page 853) affecting single elements. Class: One or more classes that can be common to more than one elements. Used for CSS selections and scripts that can affect multiple elements.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1030.html">PAGE 1030</a></h6>
<p>l l l l l l Detail Table (table only): Defines which detail table the repeat of the table is based on. The number of detail lines in the table is the number of the time the repeating row (see below) is repeated. Title (table only): Defines the title of the table. This has no impact on the table's displays, only on accessibility of HTML pages and screen readers. Repeat (table row not in <tfoot> or <thead> only): Defines if the row is affected by the detail table calculation.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1031.html">PAGE 1031</a></h6>
<p>Note When no unit is added to a geometry value, the default unit will be added to the value; see "Print preferences" on page 848. Page These attributes appear when selecting the Page node in the Outline Pane. l Master Page: Which of the "Master Pages" on page 505 to use for the template. Data Model pane The Data Model Pane displays a Data Model used to help design the template, along with (optional) extracted data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1032.html">PAGE 1032</a></h6>
<p>l A Connect template (*.OL-template), data mapping configuration (*.OL-datamapper) or 'typed' JSON file (*.json; see the note below). The file's data model structure will be displayed in the Data Model pane without data. l : Export Data Model: Click to browse to a location to save the Data Model file. The available file types are: l l l A Data Model file (*.OL-datamodel). A JSON file (*.json): A JSON object or an array of JSON objects representing records. A 'typed' JSON file (*.json).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1033.html">PAGE 1033</a></h6>
<p>Browsing data When a Data Model is loaded in the Data Model Pane, it can be used to design templates by dragging fields directly into the template; see "Variable Data" on page 801. If data is present (from a data file or a data mapping configuration), it is possible to preview the resulting data in the template on the Preview tab (see Workspace).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1034.html">PAGE 1034</a></h6>
<p>l l Add Table: Click to add a new detail table at the current level (record or existing detail table). Enter the table name in the dialog and click OK to add it. Add Group: Click to create a new group at the current level (record or existing group). Enter the group name in the dialog and click OK to add it. Any selected fields will be added to the group. (See also: "Ordering and grouping fields in the Data Model" on page 288.) Note Rename, Delete and Set Type are only available for newly added fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1035.html">PAGE 1035</a></h6>
<p>Buttons l Export Log disk. : Click to open a Save As dialog where the log file (.log) can be saved on l Clear Log Viewer l Filters l : Click to remove all entries in the log viewer. : Displays the Log Filter. Activate on new events : Click to disable or enable the automatic display of this dialog when a new event is added to the pane. Field headers l Message: The contents of the message, indicating the actual error. l Component: Whether the entry is a warning or an error.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1036.html">PAGE 1036</a></h6>
<p>Moving and merging panes The PlanetPress Connect interface for both the Designer and DataMapper module is highly configurable. Each panel in the application can be moved, with the exception of the "The Data Viewer" on page 338 and"Workspace" on page 1049 which area always in a static location. All panels can be minimized or maximized. To move a panel: l l Click and hold the left mouse button on the panel title (tab) to move and keep the button pressed. Start moving the mouse to the new location.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1037.html">PAGE 1037</a></h6>
<p>To maximize a panel: l Click the Maximize button at the top-right corner of the panel. A maximized panel takes the full available size for the panels. All other panels are minimized. Outline pane The Outline pane displays the current structure of the template, including all HTML tags present in each page. l l l l l l The display is in a treeview, the root being the Page node. At the top of the pane, a Text Filter box appears.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1038.html">PAGE 1038</a></h6>
<p>Media Media resources define paper handling configurations for Print output (see "Generating Print output" on page 1410 and "Print options" on page 1174) including page size and paper type. See "Media" on page 508 for more information. Contextual menu l l l New Media: Click to create a new Media and open its properties ("Media Properties" on page 956). Delete: Click to delete the resource. This is the same as pressing the Delete key while the resource is selected.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1039.html">PAGE 1039</a></h6>
<p>Contexts Contexts hold the actual content of the template that is used to generate output. See "Contexts" on page 468 for more information. Contextual menu (Context folder or individual contexts) l New Print Context: Click to create a new Print Context with a single section. l New Web Page Context: Click to create a new Web Page Context with a single section. l l l New HTML Email Context: Click to create a new HTML Email context with a single section. Properties...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1040.html">PAGE 1040</a></h6>
<p>l Sheet Configuration... (Print Sections Only): Click to open the Sheet Configuration dialog; see "Master Pages" on page 505 and "Media" on page 508. l Copy: Click to copy the selected section (including its settings) to the clipboard. l Paste: Paste the copied section into the same Context. Images Images are graphical elements that can be added to the page for display, either statically or dynamically. See "Images" on page 724 for more information.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1041.html">PAGE 1041</a></h6>
<p>Contextual menu l l l l l l New Javascript: Click to create a new JavaScript resource. New Remote Javascript: Click to add a Remote JavaScript resource. See "Using JavaScript" on page 564 for more information. New Folder: Click to create a new folder to organize resources more easily. Rename: Click to open the resource's Rename. This is the same as pressing the F2 key while the resource is selected.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1042.html">PAGE 1042</a></h6>
<p>l New SCSS file: Click to add a new, empty Sass file to the Resources (extension: .scss). Sass is a CSS Preprocessor integrated in Connect. For more information about Sass, see: Sass website. Note When the name of Sass file begins with an underscore, it is considered a partial .scss file (e.g. _mySass.scss). Partial files are typically imported in a base .scss file. They may include Sass variables or other directives declared in the base file, and they cannot be compiled.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1043.html">PAGE 1043</a></h6>
<p>to the Stylesheets folder. The copy will have the same name as the remote style sheet, but its extension will be .css instead of .rcss. Any section that used the remote style sheet will from then on use the downloaded style sheet (see "Applying a style sheet to a section" on page 750). l Delete: Click to delete the resource. This is the same as pressing the Delete key while the resource is selected.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1044.html">PAGE 1044</a></h6>
<p>Contextual menu l New Translation: l l l l l l PO files...: Select a PO file to import it into the template. Remote PO file: Enter the URL Click to add a remote PO file. See "Using JavaScript" on page 564 for more information. New Folder: Click to create a new folder to organize resources more easily. Rename: Click to open the resource's Rename. This is the same as pressing the F2 key while the resource is selected.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1045.html">PAGE 1045</a></h6>
<p>Scripts can be exported and imported via the buttons or through drag & drop between the Scripts pane and any location on the computer. Note Scripts included on the Scripts pane are completely distinct from the JavaScript resources found in the "Resources pane" on page 1037 (see "Using JavaScript" on page 564). Think of scripts as server-side in the sense that they are executed through the Connect modules (Server and Content Creation especially).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1046.html">PAGE 1046</a></h6>
<p>l l l l l l l l l Post Pagination Script (Print context only): Adds a Post Pagination script, which runs on the Print context after the output has been paginated (see "Post Pagination Scripts" on page 900). Folder: Adds a folder in which scripts can be placed for easier management. See "Script folders" on page 860. Text Script: When you add variable data to a template, a script of this type is created by default. See "Variable Data" on page 801.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1047.html">PAGE 1047</a></h6>
<p>the insert location. See "Variable Data" on page 801. Contextual menu options l l l l l New: Click to create a new script or folder. See "Buttons" on page 1045 for a description of all options. Which script types are available depends on the current section and script folder. Duplicate: Click to create an exact copy of the script. Delete: Click to delete the selected script. This does not delete any element or text in the template itself. Rename: Click to open a dialog to rename the script.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1048.html">PAGE 1048</a></h6>
<p>Translations pane The Translation pane contains translation entries. They can be exported to a POT file, which can be opened in a translation tool (see "Translating templates" on page 907). Tip Hover over a translation entry to see which HTML elements in the template have the same text and are tagged for translation (see "Tagging elements for translation" on page 909). Buttons l l l l l Tag Element...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1049.html">PAGE 1049</a></h6>
<p>Contextual menu options l l Edit String: Opens the "Translation String Options dialog" on page 1008 for the clicked translation entry. Delete: Deletes the clicked translation entry and (optionally) removes the translation tag from matching elements. Workspace The Workspace pane is where everything comes together. It is the contents of the page, the WYSIWYG editor that shows what the output will look like. The Workspace contains three or, when a Web section is open,four tabs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1050.html">PAGE 1050</a></h6>
<p>l l Section Selector: Displays the currently active section. Clicking on another section switches to that section. Media Selector (Master Page editor only): Displays a list of Media resources. Clicking on a media will display its Virtual Stationery background while in Preview mode. l Zoom Level: Displays the current zoom level and drops-down to change the level. l Buttons l Zoom in: Zooms in by 25% l Zoom out: Zooms out by 25% l Actual Size: Zooms to 100%.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1051.html">PAGE 1051</a></h6>
<p>Source tab The source tab displays the HTML source of the section, including HTML Headers, CSS and HTML code. The source is displayed in a color-coded text editor, to quickly visualize the code. In this tab changes and adjustments can be made to the code. When editing a template in Source mode you should write HTML. For shortcuts that can be used in this editor, see "Text editors: Source tab, JavaScript, CSS, Script Editor" on page 1014 and "Emmet" on page 518.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1052.html">PAGE 1052</a></h6>
<p>x="103.19999694824219" offset-y="247.76666259765625">@Header1@ </div><!-- format:auto--> Live tab The Live tab shows the result of the template as rendered by the Gecko rendering engine. It is a good indication of how an HTML template would display in a visitor's browser, especially if they are using FireFox (which uses the Gecko engine). Toolbars This topic lists the buttons that are available in the top toolbar of the Designer module.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1053.html">PAGE 1053</a></h6>
<p>l l l Send COTG Test: Click to open the Send COTG Test dialog, to send the current Web Context to the Capture OnTheGo Application. See this how-to: Testing a COTG template. Get Job Data File on submit: Click to enable/disable. When enabled, the Job Data File will be returned to Connect Designer directly after a COTG Form has been submitted (see also: "Using COTG data in a template" on page 573). Add Dummy Data: Populate empty form fields with dummy data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1054.html">PAGE 1054</a></h6>
<p>Form Wizard l l Form Wizard: Click to open the Form Wizard to add a form to a Web Context. See "Forms" on page 713 and "Form Elements" on page 718. Validation Settings: Click to open the Validation settings dialog to change the validation settings on the currently selecting tools. See "Forms" on page 713. Table manipulation l l l Insert Standard Table...: Inserts a table with a specific number of columns and rows through the "Table" on page 731 Wizard. Insert Detail Table...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1055.html">PAGE 1055</a></h6>
<p>l Insert Column After: Inserts a column to the right of the current one. The column configuration, such as merged cells and cell styles, are duplicated, but contents is not. Objects l l l l l Insert Image...: Inserts an Image using a resource that is local to the template, at the current location of the pointer and opens its properties. See "Images" on page 724. Insert Barcode: Displays a list of available barcodes. Click on one to insert it on the page. See "Barcode" on page 634.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1056.html">PAGE 1056</a></h6>
<p>l Rotate Counter Clockwise: Rotates the currently selected box 90° counterclockwise. Rotate Clockwise: Rotates the currently selected box 90° counter-clockwise. l Align Objects l l l l l l Top: Aligns the top side of the selected objects with the top edge of the last selected object. Middle: Aligns the middle of the selected objects with the middle of the last selected object. Objects may move up or down.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1057.html">PAGE 1057</a></h6>
<p>Alignment l Align Left: Aligns the currently selected element to the left. l Align Center: Aligns the currently selected element to the center. l Align Right: Aligns the currently selected element to the right. l Justify: Aligns the currently selected element to stretch text lines to fill all available width. Text editing l Bold: Makes the currently selected text bold. l Italic: Makes the currently selected text italic. l Underline: Makes the currently selected text underline.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1058.html">PAGE 1058</a></h6>
<p>Miscellaneous l l l Insert Lorem Ipsum: Inserts a paragraph of generic lorem ipsum text, useful for placeholder or template design. Show Edges: Shows a colored border around elements on the page and the type of element that is highlighted. Welcome Screen: Click to re-open the Welcome Screen. Welcome Screen The Welcome Screen appears when first starting up PlanetPress Connect. It offers some useful shortcuts to resources and to recent documents and data mapping configurations.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1059.html">PAGE 1059</a></h6>
<p>l l License: Shows your current license's details. l Website: Opens the PlanetPress Connect website. More options l l Get Printer Configurations (PDC): Lists printer definition files available for download. The selected files will be downloaded to the current user's Connect\workspace\configurations\ folder and can be imported via the Print Wizard; see "Adding print output Models to the Print Wizard" on page 1423. Get Finishing Configurations (HCF): Lists HCF Files available for download.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1060.html">PAGE 1060</a></h6>
<p>options, but it cannot save your settings to file like the preset wizards allow. For more information about print preset files, see "Print Presets" on page 1415. The choices can be broken down as follows. Printer l Model: Use the drop-down to select the printer language / output type that will be generated. Connect comes with several bundled print output Models which cover a large range of industry standard print output types.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1061.html">PAGE 1061</a></h6>
<p>l Export printer definition from output preset: Use to extract a Printer Definition from a new or modified Printer Model. This option is only available when the Printer Model currently loaded differs from those previously saved or installed. For more information on how to add Printer Definitions to Connect, see "Adding print output Models to the Print Wizard" on page 1423.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1062.html">PAGE 1062</a></h6>
<p>l l l l Queue Name: The queue name that will accept the job on the LPD. Default is generally "auto". Job Owner Name: Optional entry for adding the name of the job owner. Job Name: The name of the output file. You can use ${template} as a variable for the name of the Designer Template used to generate the output. (See also: "Print output variables" on page 1426.) Windows Printer: Select to send the Print Job to a printer queue (note that this is an actual printer queue, not a Workflow Printer Queue).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1063.html">PAGE 1063</a></h6>
<p>properties" on page 987. l l l l l l l l l Imposition: Check to enable Cut & Stack Imposition, which is set in the "Imposition options" on page 1181 page. Add Inserter marks: Check to enable Inserter mark functionality, which is set in the "Inserter options" on page 1190 page. Runtime Parameters: select "Runtime Parameter Options" on page 1081 to store information which can be used at runtime for comparisons against conditions within Job Creation, or for use with external sorting programs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1064.html">PAGE 1064</a></h6>
<p>l l Copies: Enter the number of copies to print, of each record. Collate: When printing multiple copies you can check this checkbox to have the record copies printed together. For example in a three record job the records would print out as 1-1-2-2-3-3, rather than 12-3-1-2-3. Pure Color Thresholds This section is valid for PCL only. It applies to elements within the record that are shades of grey, rather than black or white.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1065.html">PAGE 1065</a></h6>
<p>Printer settings This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. The Printer Settings page provides options for cut-sheet printers. It maps media types to printer trays. It is available for PCL and PostScript printers that are configured for cut-sheet printing. Note Not all the settings will be available for all printers. Only those printers whose Printer Definition supports the extra information will have the Position, Weight, Type or Color options available.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1066.html">PAGE 1066</a></h6>
<p>l Add: Adds a new Media/Tray entry in the table. l Delete: Deletes the current Media/Tray selections from the table. l l / Move Up / Move Down: Move the selected Media/Tray entries up or down within the table. Import Tray Settings: Import the Media/Tray settings from a Connect Template. This entry will only be available for those printers that support the extra information.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1067.html">PAGE 1067</a></h6>
<p>Advanced Print Wizard and Output Creation Preset Wizard navigation options l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1068.html">PAGE 1068</a></h6>
<p>l l 1 up Perfect Binding: This binding does not contain any folding. The pages are lined up side by side and bound along one edge. Booklet Binding Edge: Use the drop-down to select the side on which to bind the booklet. Optional Cover Page selections are available to Saddle Binding only.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1069.html">PAGE 1069</a></h6>
<p>This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. l Cancel button: Cancels the Print Wizard, without creating any printout. Imposition options This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. Imposition refers to the printing of multiple pages on a single sheet. This is also known as N-Up printing.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1070.html">PAGE 1070</a></h6>
<p>l Sample Page group: Use to choose a paper size for the logical page(s) which would be printed upon the actual physical Imposition sheet. This helps in decision making regarding what paper sizes and orientations to use, with the Sample Page shown in blue on the white Imposition Sheet in the output preview (and validation) diagram. Note The logical page size can be set independently of any template open in the Designer, allowing for output presets to be created independently from the active template.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1071.html">PAGE 1071</a></h6>
<p>l l The Width and Height values are real-only and appear for display and design purposes only. Output diagram and validation. Use the settings here to control how the output diagram is to look and behave. It contains the following options: l l l l Display size entry: Chose between a pre-set viewing percentage, or manually enter whatever percentage you would like, or select Fit Page or Fit Width to have the diagram display the page(s) within the diagram window dimensions.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1072.html">PAGE 1072</a></h6>
<p>l Method selection: Set the position of the logical page(s) upon the Imposition Sheet. The choices are as follows: l l l l l l Center: Have the logical page(s) centered within the Imposition Sheet. Scale to fit: Scales the logical page(s) so that they fit the Imposition Sheet exactly. Offset: Have the logical page(s) offset within the Imposition Sheet. The offset values can be set in the Left and Top entry boxes, which only become available for this positional method.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1073.html">PAGE 1073</a></h6>
<p>illustrated by way of example. The following "Cut and stack" example has a job with 100 single page documents and repetition settings of 5 Horizontal and 2 Vertical, plus a Stack Depth of 5.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1074.html">PAGE 1074</a></h6>
<p>Each set of 5 Imposition Sheets is a discrete drill sorted nUp block that can be guillotined and stacked. The first 5 sheets encompass records 1-50, whilst the next 5 sheets encompass records 51-100.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1075.html">PAGE 1075</a></h6>
<p>The following example is the same job but with a Horizontal repetition setting of 6: As you can see, the outputs are very different.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1076.html">PAGE 1076</a></h6>
<p>Note If the Stack Depth is greater than the number of sheets in the entire job then you will get a single drill sorted block that can be guillotined and stacked to give the complete job in record order. l l Sides selection: Select how many sides of the Imposition Sheet are to be printed upon. Choice is between Simplex or Duplex. Method selection: In 2018.2 we introduced a new imposition page order for cut & stack impositioning that works with continuous feed devices: Stack by Column.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1077.html">PAGE 1077</a></h6>
<p>l l l l Off. Output is not reversed. Stack upside down: Essentially turns the stack upside down by reversing the output imposition page sides. The last sheet becomes the first, and in the case of duplex imposition, the back sides become the front sides. For presets created in a version prior to Connect 2018.2, a "Reverse Pages" selection will apply this Stack upside down setting. Inverse page order: This impositions the output in the exact opposite order from what has been selected.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1078.html">PAGE 1078</a></h6>
<p>l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. Cancel button: Cancels the Print Wizard, without creating any printout.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1079.html">PAGE 1079</a></h6>
<p>l l l l Collation level: Select whether the markings will be made at Document level, or Document Set level. Print marks on back: Check to place the Inserter Marks on the rear of the page. Selective Inserts: If selective inserts are supported by the chosen Mark Configuration you can select what markings to include and whether those markings are to included based upon some conditional setting.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1080.html">PAGE 1080</a></h6>
<p>through the wizard to return to the main selection page (the "Print options" on page 1174 page) and add or remove printing options from the print run. l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1081.html">PAGE 1081</a></h6>
<p>l l l Show Page: Use the up and down arrows or type a page number to display a specific page within the document. Zoom in/out: Click to zoom in or out by 25% Zoom Level: Use the drop-down to select a predefined level or enter a zooming percentage. Selective Insert Dialog The Selective Insert Dialog provides control over individual inserts. In this dialog the selected can be set to be either selected ("Yes") or not ("No"), or selected based upon some conditional criteria ("Conditional").</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1082.html">PAGE 1082</a></h6>
<p>Another example would be a list of document types for a job: the document could have a property with its document type (e.g., reminder, collection letter, etc.), and the runtime parameter could be a comma separated list of document types for the job. So a rule would then compare if document type occurs in the list of document types. Finishing rules scenarios Similar to filtering, a finishing condition could use runtime parameters to compare against.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1083.html">PAGE 1083</a></h6>
<p>l l l l l Add: Click to open a new Runtime Parameter. This launches the Add/Edit Runtime Parameter dialog. Edit: Click to edit the currently selected entry. This launches the Add/Edit Runtime Parameter dialog. Double clicking on an entry in the table has the same effect as this button. Delete: Click to delete the currently selected entry or entries. Duplicate: Click to create a duplicated copy of the entry.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1084.html">PAGE 1084</a></h6>
<p>Finishing options This page appears as part of the Advanced Print Wizard and the "Job Creation Presets Wizard" on page 1159. Use the Finishing Options page to force the use of specific printer finishing options, rather than using any finishing options that might have been set in the template's Print Context and Print Section options. These settings are only applied when producing print output. They do not modify the original finishing options in either the Section or the Template.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1085.html">PAGE 1085</a></h6>
<p>l Binding group: l l l l l Style: What type of Binding to request on the printer. This includes Stapled, Glued, Stitched, Ring, Comb, Coil, amongst other options.. Side: Sets the side of the paper that the Binding is to occur. This includes both the top and the bottom of the paper, Location: Sets where the binding is to occur, if applicable. The selections available here will be dependent upon the selection made in the Binding Style.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1086.html">PAGE 1086</a></h6>
<p>through the wizard to return to the main selection page (the "Print options" on page 1174 page) and add or remove printing options from the print run. l l Print button: Click to produce print output according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. Cancel button: Cancels the Print Wizard, without creating any printout.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1087.html">PAGE 1087</a></h6>
<p>options for sorting are either Ascending or Descending order. l Size Grouping section: Check the checkbox to enable size grouping, which separates Documents into different groups, based upon their relative sizes. For example, selecting Document Set Grouping for the Grouping Level, Documents for the Item to group, Group by Page Count and then creating a page range from 1-5 and another page range 6 to Largest, will create two Document Set groups.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1088.html">PAGE 1088</a></h6>
<p>l l Meta data property edit box: Select a name for the meta data field that is created. This meta data field can then be used in other Print Wizard/Preset pages, such as in the Job Output Mask Dialog. Size Ranges: Add (or remove ) entries to this list to create new groups based upon the number of pages in the level selected above. All groups must be contiguous from 1-to-Largest and they must not contain any gaps. l l l Range Name: Enter a name identifying the range.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1089.html">PAGE 1089</a></h6>
<p>Note Meta data properties have a length limitation of 255 characters. The meta data entries can be added to any of these levels, as indicated by the tabs on top: Job, Job Segment, Document, Document Set, and Page Tags. Note It is important to note that if Impositioning is used then the only meta data that will be available to the job thereafter will be the meta data at Job Segment level.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1090.html">PAGE 1090</a></h6>
<p>Once loaded in the table, the meta data fields Tag Names can be modified as desired. As can the source they point to, in the case of runtime parameters and data fields. l l Delete: Click to delete the currently selected meta data entry. / Move Up / Move Down: Click to move the currently selected tag(s) one position up or down. Separation options This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1091.html">PAGE 1091</a></h6>
<p>l Slip Sheets group: l l l l Add slip sheet: Use the drop-down to select whether to add a slip sheet before or after a specific separation, or whether to use none. Every: Use the drop-down to select at which separation to add a slip sheet, at the Job, Job Segment, Document or Document Set level. Media Size: Use the drop-down to select the media size of the slip sheet. If a custom Media Size was chosen: l Width: enter slip sheet page width. l Height: enter slip sheet page height.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1092.html">PAGE 1092</a></h6>
<p>different types of Additional Content that can be added at print time: Text; Images; Barcodes and OMR Marks. They can be used to add either static content or variable content. The Additional Content option is particularly useful when you might need to drive custom processes on production machines using either Barcodes or OMR Marks, or if you need to add some last minute additions to the print job via text and/or images.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1093.html">PAGE 1093</a></h6>
<p>l Type: Displays an icon showing what type the Additional Content entry is. l Description: Displays the Description" that was entered in the Additional Content dialog. Note The entered text Description might stretch over a couple of lines, so it is possible that not all of the Description will be displayed here. l Left: Displays the Additional Content Left Positional value. l Bottom: Displays the Additional Content Bottom Positional value.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1094.html">PAGE 1094</a></h6>
<p>Additional Text Settings The Additional Text Settings dialog displays the property of Text added in the "Page breakdown" on page 1195 page. l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1095.html">PAGE 1095</a></h6>
<p>Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l Style: Choose between "Regular", "Italic", "Bold" or "Bold Italic". l Font Size: Enter the font size in points (pt). l Color: Select what color the Text will be. Text: Enter the actual Text to appear on the page in the selected location. The Text can be spread over multiple lines, but no additional formatting can be added within this edit box.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1096.html">PAGE 1096</a></h6>
<p>included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the image. Layer: Whether this image will appear behind the text (the text will print over the image) or in front of the text (the text behind will be blanked out by the image, as transparent images are not supported).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1097.html">PAGE 1097</a></h6>
<p>and specific limitations can be applied used a combination of the following options: l l l l Max Width: Enter the absolute maximum width the image can be scaled to, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Max Height: Enter the absolute maximum height the image can be scaled to, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Scale: What scale to apply to the image. The maximum scale is 10.0 to 1. Decimal values are allowed for this field.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1098.html">PAGE 1098</a></h6>
<p>l "PDF417 Settings" on page 1232 l "QR Code Settings" on page 1235 l "Royal Mail 4 State (CBC) Settings" on page 1242 l "Royal Mail 4 State (CBC) Settings" on page 1242 l "Royal Mail 4 State Mailmark C Settings" on page 1244 l "Royal Mail 4 State Mailmark L Settings" on page 1247 l "UPC-A Settings" on page 1250 l "UPC-E Settings" on page 1253 l "US Postal Service IMb Settings" on page 1256 l "US Postal Service IMpb Settings" on page 1259 Codabar Settings Codabar barcodes support the foll</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1099.html">PAGE 1099</a></h6>
<p>l Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page. Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1100.html">PAGE 1100</a></h6>
<p>Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l l l Font size: Enter a font size for the human readable text. Display start/stop symbols checkbox: Adds the stop/start symbols to the Barcode text. Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1101.html">PAGE 1101</a></h6>
<p>the print run and the barcode. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries. This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1102.html">PAGE 1102</a></h6>
<p>l Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1103.html">PAGE 1103</a></h6>
<p>Code 39 Settings Code 39 is a discrete, self-checking barcode that is also known as "Alpha39", "Code 3 of 9" (often abbreviated to "3 of 9"), "Code 3/9", "Type 39", "USS Code 39" and "USD-3". Code 39 data should contain no more than 20 digits from within the following range: Numeric digits: (0-9), upper-case letters (A-Z), seven special characters (- . space $ / + %) and the start/stop asterisk (*) character.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1104.html">PAGE 1104</a></h6>
<p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1105.html">PAGE 1105</a></h6>
<p>l Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l Font size: Enter a font size for the human readable text. Process Tilde: Check this option to process tilde characters in the data as special characters. Note: with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1106.html">PAGE 1106</a></h6>
<p>following requirements: l l l The barcode data must start with a leading FNC1 character. Either ~1 or ~d232. The GS1 Application Identifiers (AI) must be used for all data. The function code ~1 must be used as field separator for variable length AI elements. Only ASCII characters should be used.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1107.html">PAGE 1107</a></h6>
<p>l l Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Data Matrix Properties group: l l Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1108.html">PAGE 1108</a></h6>
<p>l l ~6 = Macro6 l ~7 = ECI expressions Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields. l Condition: Enter the condition which determines whether or not the Barcode will be added to the document at print time.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1109.html">PAGE 1109</a></h6>
<p>This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1110.html">PAGE 1110</a></h6>
<p>l n13 defines a numeric field with exactly 13 digits. l n13+cd defines a numeric field with exactly 13 digits plus a check digit. l an1-9 defines an alpha-numeric field with 1 to 9 characters. Elements can be combined using the '+' symbol. l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1111.html">PAGE 1111</a></h6>
<p>l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition. EAN-13 Settings EAN-13 barcodes are composed entirely of numerical data. The first 12 digits representing country/economic area, manufacturer and product codes + 1 following checksum digit. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1112.html">PAGE 1112</a></h6>
<p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1113.html">PAGE 1113</a></h6>
<p>Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l l Font size: Enter a font size for the human readable text. Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1114.html">PAGE 1114</a></h6>
<p>included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page. Output once per sheet: This option relates to Imposition printing (see Imposition), also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1115.html">PAGE 1115</a></h6>
<p>l l l l Add: Calculate and add a checksum character to Barcode, regardless of current value. Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1116.html">PAGE 1116</a></h6>
<p>odd number of digits, then a leading zero must be added to the beginning of the data. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1117.html">PAGE 1117</a></h6>
<p>higher value will generally make the Barcode bigger. l Bar width ratio: Set the Barcode bar width. l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1118.html">PAGE 1118</a></h6>
<p>files and actual data bytes. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1119.html">PAGE 1119</a></h6>
<p>l l Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. PDF417 Properties group: l l Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. Row height: Defines the height of the bars for a single row, measured in pixels, points or metric. l Width to height ratio: Select the ratio of column width to row height.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1120.html">PAGE 1120</a></h6>
<p>Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields. l Condition: Enter the condition which determines whether or not the Barcode will be added to the document at print time. For details on how to create a conditional, see "How to Set Conditionals" on page 1265. l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1121.html">PAGE 1121</a></h6>
<p>sheet rather than once per document page. Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1122.html">PAGE 1122</a></h6>
<p>Note The Encoding and Version fields work together to determine how many characters are encoded within a length field. The following table shows the number of bits in a length field, based upon the selections made: Encoding l l l Ver. 1-9 Ver. 10-23 Ver.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1123.html">PAGE 1123</a></h6>
<p>l Use FNC1: Check to enable Application Identifiers. These are often used to encode links to websites, or to encode production/batch details. l Position: Select between the two methods for encoding FNC1 characters within QR Codes: l l First Position - uses the GS1 QR Code standard. Second Position - uses the AIM QR Code standard. If this option is chosen then the appropriate Application Indicator will also need to be set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1124.html">PAGE 1124</a></h6>
<p>Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1125.html">PAGE 1125</a></h6>
<p>UPC A Properties group: l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. l Checksum: Use the drop-down to select how to deal with the Barcode checksum: l Ignore: Ignore checksum calculations. l l l l l l Auto: Add a checksum character to the Barcode if the initial value does not validate. This is the default value.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1126.html">PAGE 1126</a></h6>
<p>Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields. l Condition: Enter the condition which determines whether or not the Barcode will be added to the document at print time. For details on how to create a conditional, see "How to Set Conditionals" on page 1265. l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1127.html">PAGE 1127</a></h6>
<p>also known as N-Up printing. Select this box to have the Barcode printed once per sheet rather than once per document page. Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1128.html">PAGE 1128</a></h6>
<p>Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l l Font size: Enter a font size for the human readable text. Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1129.html">PAGE 1129</a></h6>
<p>This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l l Orientation: Use the drop-down to select the orientation of the OMR Mark added to the page. Page Side: Select whether the OMR Mark will print on the front or back of page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1130.html">PAGE 1130</a></h6>
<p>l Line Thickness: Sets the thickness of each OMR mark line. l Line Length: Sets the lenght of each OMR mark line. l Line Spacing: Determines how the spacing between each OMR mark line will be set. The associated control beneath the combination box will be enabled, based upon this selection. l l l l Line Per Inch: If Line Spacing is set to Lines Per Inch this option will be enabled. It defines how many lines will print per inch.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1131.html">PAGE 1131</a></h6>
<p>Note The Match Number iterates per group and is used to identify missing groups l l l Start: Start number l Stop: Stop number Condition: Enter the condition which determines whether or not the OMR Mark will be added to the document at print time. For details on how to create a conditional, see the "How to Set Conditionals" on page 1265 page. OMR Marks Tab: l #: OMR Mark number (display only). l Type: Type of OMR Mark (display only). l l Value: OMR Mark Value.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1132.html">PAGE 1132</a></h6>
<p>in the sequence number of the page. For example, if the bit for the mark is set to 2 and the sequence number for the page is 5 then it will not print since the value 5 consists of the bits 1 and 4. Use the drop down box to select the entry. l Match: This represents a mark that is printed when the specified bit is set in the match number of the group. For example, if the bit for the mark is set to 2 and the match number for the group is 3 then it will print since 3 consists of the bits 1 and 2.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1133.html">PAGE 1133</a></h6>
<p>Tip You can also double click a Conditional entry within the table to edit it. How to Set Conditionals l Condition: Enter the condition which determines whether or not this element will be added to the document at print time. Use JavaScript conditional expressions to construct your conditional. You may use JavaScript logical operators ( ==, !=, <, >, &&, ||, etc), literal values ("text', 3.14, etc), mathematical operators (/, *, +, -, etc) and data fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1134.html">PAGE 1134</a></h6>
<p>l PDF Creation Group l l Type: Use the drop-down list to specify what PDF format will be generated. The options are: l Standard PDF (PDF) l Archive format PDF (PDF/A-1b) l E-invoice format PDF (PDF/A-3b) l Graphics format PDF (PDF/X-4 ) l Variable data printing format PDF (PDF/VT). Font Creation selection: The choices are: l Simple fonts when possible (smallest size). This is the default option. This option uses Simple fonts in cases where the fonts do not use too many characters.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1135.html">PAGE 1135</a></h6>
<p>making for the most portable of PDF outputs. Customers using Asian fonts should generally use the CID font option. Note Any pre Connect 2018.2 Output Presets will use the Simple Fonts default, unless updated in Connect 2018.2. l Embed standard fonts: Click to embed the 14 standard system fonts within the PDF output. This increases the output filesize but makes the PDF output truly portable.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1136.html">PAGE 1136</a></h6>
<p>Note Encrypted PDF files are not supported in PDF pass-through mode. l Meta data Group: Add optional Metadata to the PDF output. The fields that can be configured are the Title, Author, Description and Keywords. These metadata entries are those that are displayed in the Adobe Reader Document Properties dialog. The values for all the fields can be either static or dynamic (such as values obtained from datamapping) or a combination of both. l l l l l Title: Add the document name(s).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1137.html">PAGE 1137</a></h6>
<p>l Name: The user-defined name of the Keystore\Signature. l Alias: The user-defined alias for the signature. The table allows the following options: l l l l Add Keystore: opens the "Keystore" on page 1270 dialog for adding a Digital signature Keystore. Digital signatures require a Keystore, so initially only the Add Keystore option will be available. Add Signature button only becomes active once a Keystore has been added.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1138.html">PAGE 1138</a></h6>
<p>key. The keystores currently supported by Connect are: l JKS (Java Key Store) format. l JCEKS (Java Cryptography Extension Key Store) format. l PKCS#12 l PKCS#11 Note JKS and JCEKS represent file based keystores in a Java proprietary format. The Java keytool command line application can be used to create and manage keystores in this format. Type PKCS#12 also represents a file based keystore, but in the PKCS#12 format. Type PKCS#11 represents a keystore on a hardware device.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1139.html">PAGE 1139</a></h6>
<p>l PKCS#11 properties group: l l Module Name: Select which secure hardware device (USB tokens, smart cards, and Hardware Security Modules) to connect to through PKCS#11. These hardware devices must first be setup in the "Hardware for Digital Signing preferences" on page 843 Preferences page, before they become available as an option in this dialog. Slot list index: Select which hardware slot to use. Note Slots are logical partitions in the hardware device.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1140.html">PAGE 1140</a></h6>
<p>PDF Signature The PDF Signature dialog appears when either adding or editing a Signature on the "PDF Options" on page 1266 page. Note PlanetPress Connect currently supports only a single Digital Signature per PDF output file. l l l Name: Enter a name that describes the signature entry. Keystore name: Use the drop-down to select which keystore the signature is pulled from. These keystores are set in the "Keystore" on page 1270 dialog, called from the "PDF Options" on page 1266 page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1141.html">PAGE 1141</a></h6>
<p>l l Account: Account name specific to the TSA server chosen. l Password: Password specific to the TSA server chosen. l Repeat Password: Repeat of password. Visible Signature group: Check to add a visible signature to the PDF file. The signature is added to the first page of each output file. Note When creating PDF/VT-1 or PDF/X-4 output, the visible signature should be located outside the visible page area (trimbox/bleedbox). The Weaver engine logs a warning message if this is not the case.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1142.html">PAGE 1142</a></h6>
<p>options" on page 1174 page have been completed or not. l Cancel button: Cancels the Print Wizard, without creating any printout. PPML Options This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. The PPML Options page is shown only when a PPML Print output type is selected in the Print Options dialog. It is used for tray selection. PPML Tray Options Use the drop-down list to specify what output Tray Options to use, if any.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1143.html">PAGE 1143</a></h6>
<p>repopulate the table with those entries (had they been deleted). If the existing entries had not been deleted, then the newly imported Media names will be identical to the entries already in the table, and thus their names will need to be changed. l l Import from template file: Import Media settings from some other Connect Template file. Mapped PPD Entries: This allows selection of a printer manufacturer's printer specific PostScript Printer Definition (PPD) file.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1144.html">PAGE 1144</a></h6>
<p>Import from template file: Import Media settings from some other Connect Template file. Double clicking the left mouse button on a Media table entry will launch the Dynamic Tray Mapping Editor Dialog to allow you to modify that Media's properties. l l l Details: This is a read only table that displays the Details of whatever Media has been selected in the Media box.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1145.html">PAGE 1145</a></h6>
<p>*OrderDependency: 50 AnySetup *PageRegion ... *CloseUI: *PageRegion l InputSlot: *OpenUI *InputSlot: PickOne *OrderDependency: 20 AnySetup *InputSlot ... *CloseUI: *InputSlot We can see that one has an Order Dependency of 50 and the other 20. If PageRegion was selected prior to InputSlot in the Add Printer Options Dialog, then they would appear like this in the Print Wizard: To sort them into the correct dependance order, use the Sort by Order dependency button.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1146.html">PAGE 1146</a></h6>
<p>Options. This can be seen in the following example, which shows multiple conflicting Folding Options have been chosen: The breadth and diversity of PPD files as well as individual printer capabilities mean that the Print Wizard cannot meaningfully validate the selections made, and thus does not attempt to. So you must be careful when making selections. We recommend that you always test each individual selection made, to confirm that they are valid and that they do what you expected of them.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1147.html">PAGE 1147</a></h6>
<p>This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. l Cancel button: Cancels the Print Wizard, without creating any printout. Printer settings This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. The Printer Settings page provides options for cut-sheet printers. It maps media types to printer trays.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1148.html">PAGE 1148</a></h6>
<p>l Media/Tray Table buttons: l Add: Adds a new Media/Tray entry in the table. l Delete: Deletes the current Media/Tray selections from the table. l l / Move Up / Move Down: Move the selected Media/Tray entries up or down within the table. Import Tray Settings: Import the Media/Tray settings from a Connect Template. This entry will only be available for those printers that support the extra information.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1149.html">PAGE 1149</a></h6>
<p>Default output destination selection: Select the default output bin from those bins available to this Printer Definition. Advanced Print Wizard and Output Creation Preset Wizard navigation options l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1150.html">PAGE 1150</a></h6>
<p>Dynamic PPD Options within Connect - An example. Note As of OL Connect 2019.1 JobPatchFile sections in PPDs are automatically added to the output, if the PPD includes them. The Dynamic PPD mode Options page can be broken up as follows: PPD Info group This shows information about the selected PostScript Printer Definition. The information box contains general printer details (such as the model name) whilst the PPD file name field displays the name of the actual PPD file that is loaded.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1151.html">PAGE 1151</a></h6>
<p>If your Template already has Finishing and Media/Trays entries set, then those options will appear pre-populated in the Rules table along with their Triggers, to allow you to assign specific options as Printer Option entries. Additional Rules (and Triggers) can be added (or deleted) and all Rules can be edited, and/or moved up or down within the table after being added. Within a group of Rules, the Rules are processed sequentially, from top to bottom.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1152.html">PAGE 1152</a></h6>
<p>l JCL (Job Control Language) Rules: This option only appears if the PPD contains a "*JCL keywords" section. Certain printers require Printer Job Language (a type of JCL) commands to function properly, or to allow certain features. If such entries are included in the PPD, then rules can be added to use them via the Add button. NOTE: JCL is a generic way to refer to languages like PCL's Printer Job Language. l l l Prolog Rules: This adds options to the Prolog section of a PostScript document.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1153.html">PAGE 1153</a></h6>
<p>Note You should also choose an Option to switch off the Finishing selection, to cater for subset Finishing. l l Plex rules: This fixed group allows you to set rules for sheet plexing. The choices are Duplex, Simplex or Tumble Duplex. You should add Printer Options for each of these Plexing Rules. Custom rules: The Custom group does not appear by default, but can be added at any point via the Add button. The Rules Options.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1154.html">PAGE 1154</a></h6>
<p>You should add Printer Options for each of the Rules added.See the "Printer Options" on page 1156 section for how to do this. l l l l Media/Trays : If the Rule is being added to a Media/Trays selection, then the Dynamic Tray Mapping Editor Dialog will be launched. This dialog allows the description of standard Media options, such as paper Weight and Color. You should add Printer Options for each of the Rules added.See the "Printer Options" on page 1156 section for how to do this.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1155.html">PAGE 1155</a></h6>
<p>l l l Media/Trays : If the Rule is being edited is a Media/Trays selection, then the Dynamic Tray Mapping Editor Dialog will be launched. Finishing : If the Rule is being edited is a Finishing selection, then the Dynamic Finishing Editor Dialog will be launched. Plex : Plex Rules cannot be edited. Custom / Prolog / Setup : If the Rule being edited is any of these, then the Custom Group Editor Dialog will be launched. Rules can also be edited via double mouse clicking on the rule.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1156.html">PAGE 1156</a></h6>
<p>l Condition Tab: displays the logical condition that needs to be fulfilled before the Custom Rule is to be applied. Printer Options This section allows for the selection and ordering of Printer Options to be associated with the active Rule. The Print Options are all those contained in the PPD. If no Rule is active, the Printer Options section will not be available. The Printer Options table displays : l l l Name column: This column contains the names of the Printer Options, as taken from the PPD file.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1157.html">PAGE 1157</a></h6>
<p>l l PageRegion: *OpenUI *PageRegion: PickOne *OrderDependency: 50 AnySetup *PageRegion ... *CloseUI: *PageRegion InputSlot: *OpenUI *InputSlot: PickOne *OrderDependency: 20 AnySetup *InputSlot ... *CloseUI: *InputSlot We can see that one has an Order Dependency of 50 and the other 20.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1158.html">PAGE 1158</a></h6>
<p>This can be seen in the following example, which shows multiple conflicting Folding Options have been chosen: The breadth and diversity of PPD files as well as individual printer capabilities mean that the Print Wizard cannot meaningfully validate the selections made, and thus does not attempt to. So you must be careful when making selections. We recommend that you always test each individual selection made, to confirm that they are valid and that they do what you expected of them.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1159.html">PAGE 1159</a></h6>
<p>This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. l Cancel button: Cancels the Print Wizard, without creating any printout. Job Creation Presets Wizard The File>Print Presets>Job Creation Settings ... dialog displays a list of available presets and a summary of their settings. This dialog can be used to create new Presets or to edit and update existing Presets.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1160.html">PAGE 1160</a></h6>
<p>l l Data Mapping Configuration: Use the drop-down to select which data mapping configuration this job creation preset will be based on. The data mapping configuration's model is used for field names in sorting, etc. Configuration Name: Use the drop-down to select the presets saved in the default location Click the Gear icon for more options: l l l Click the Reload option to look for new presets. Click the Import Configuration... option to import one or more Job Presets using a Browse dialog.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1161.html">PAGE 1161</a></h6>
<p>l l l l l Include Metadata (only available for PDF output): Check to add meta data to the output. This can be done at Job, Job Segment, Document, Document Set and Page level. See "Meta Data options" on page 1169. Override Finishing Options: Check to configure custom "Finishing options" on page 1171, such as binding. Next: Click to go to the next page of the Job Creation Wizard, "Data filtering options" on page 1163.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1162.html">PAGE 1162</a></h6>
<p>Available Fields box in the same fashion. Once a field is added to the Available Fields box, its Sorting Option can be selected by clicking in the "Sorting Option" column, and selecting the appropriate option. The options for sorting are either Ascending or Descending order. l Size Grouping section: Check the checkbox to enable size grouping, which separates Documents into different groups, based upon their relative sizes.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1163.html">PAGE 1163</a></h6>
<p>l l l Size grouping after normal grouping checkbox: Check this option to firstly group using the selections made above and then secondly group upon page break grouping. This creates two different levels of grouping, applied in order. Meta data property edit box: Select a name for the meta data field that is created. This meta data field can then be used in other Print Wizard/Preset pages, such as in the Job Output Mask Dialog.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1164.html">PAGE 1164</a></h6>
<p>Conditions are evaluated on each record, and can be based upon such diverse data as the data fields used in records or the physical printing options for a record. The rule(s) apply at a Group level. There may be one rule or many rules at the same level, and there may be groups within groups, providing the ability to create quite complex nested logical structures. Group A group consists of one or more rules with a logic operator. Four logic choices are available at the Group level.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1165.html">PAGE 1165</a></h6>
<p>l Data Rule: This rule operates upon Data entries. Select the Data Field, then select the logical test and the associated test value(s). The options available will depend upon the Data Field type (they are "type aware"), but all have at least "is equal to" and "is not equal to" to another entry as an option.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1166.html">PAGE 1166</a></h6>
<p>l l l l Binding Rule: This rule operates upon the binding that applies to the record. The options are based on the Style, Side, Location or Angle of the binding. The logical operators that apply are dependent upon the type of Binding the test is being applied to. Duplex Rule: This rule operates upon the record Duplex settings. This is a binary choice between Duplex or non-Duplex. Size Rule: This rule operates upon the size of the selected group.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1167.html">PAGE 1167</a></h6>
<p>l l / Move up / down: Click to move the currently selected row up or down within the list. Use external sort: Sort the records using some external sorting software. A CSV file is exported, then sorted by the external application and the resultant sorted CSV file is returned and integrated, with all the records now being sorted according to the new order within the CSV file. Warning External Sort commands must return a non-zero error code if an error occurs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1168.html">PAGE 1168</a></h6>
<p>l l l l l l l ${output} file. Timeout: Enter the number of seconds to wait for an external sort command to complete before abandoning the external sort. Separator: Enter the field separator used in the CSV file, such as a comma (,), pipe (|), semicolon (;), etc. Quote Character: Enter the quoting character that wraps around any field that contains the separator. Escape Character: Enter the character use to escape the Quote character if it appears in the field value.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1169.html">PAGE 1169</a></h6>
<p>l l l l l Processing returns data checkbox: Select this if the sort processing will be returning data. This activates the whole optional Processing returns data subsection. First row of return data has field names checkbox: select to have field names placed on the first line of the returning datafile. Return Fields: Lists the fields available in the selected data mapping configuration that can be used to sort the records.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1170.html">PAGE 1170</a></h6>
<p>The meta data entries can be added to any of these levels, as indicated by the tabs on top: Job, Job Segment, Document, Document Set, and Page Tags. Note It is important to note that if Impositioning is used then the only meta data that will be available to the job thereafter will be the meta data at Job Segment level. When using Impositioning everything within the Segment is Impositioned, so all meta data below the Job Segment level is lost.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1171.html">PAGE 1171</a></h6>
<p>l / Move Up / Move Down: Click to move the currently selected tag(s) one position up or down. Finishing options This page appears as part of the Advanced Print Wizard and the "Job Creation Presets Wizard" on page 1159. Use the Finishing Options page to force the use of specific printer finishing options, rather than using any finishing options that might have been set in the template's Print Context and Print Section options. These settings are only applied when producing print output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1172.html">PAGE 1172</a></h6>
<p>l l Edit ... : Brings up the Rule Editor Dialog, which can be used to construct the rule (s) that determines whether this conditional Finishing option is to be applied or not. Binding group: l l l l l Style: What type of Binding to request on the printer. This includes Stapled, Glued, Stitched, Ring, Comb, Coil, amongst other options.. Side: Sets the side of the paper that the Binding is to occur.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1173.html">PAGE 1173</a></h6>
<p>l l l Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard. Up until the Print button is pressed, one can reverse all the way through the wizard to return to the main selection page (the "Print options" on the facing page page) and add or remove printing options from the print run. Print button: Click to produce print output according to the current settings.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1174.html">PAGE 1174</a></h6>
<p>If Output Presets of the same name already exist in the Output Presets list, then a choice as to whether to overwrite the existing Preset(s) or not will be provided. l Properties: Displays a summary of the settings for this Output Creation Preset. l l l l l l Output Type: Displays the print technology used, as defined in the "Print options" below. Inserter: Indicates whether Inserter Marks have been added in the "Inserter options" on page 1190 dialog.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1175.html">PAGE 1175</a></h6>
<p>The options that don't appear in the Output Creation Preset Wizard (as noted below), do appear in the Job Creation Preset Wizard. Only the Advanced Print Wizard contains all the options, but it cannot save your settings to file like the preset wizards allow. For more information about print preset files, see "Print Presets" on page 1415. The choices can be broken down as follows. Printer l Model: Use the drop-down to select the printer language / output type that will be generated.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1176.html">PAGE 1176</a></h6>
<p>l Edit available printers: Add extra Printer Definitions from the selection that come installed with Connect. Export printer definition from output preset: Use to extract a Printer l Definition from a new or modified Printer Model. This option is only available when the Printer Model currently loaded differs from those previously saved or installed. For more information on how to add Printer Definitions to Connect, see "Adding print output Models to the Print Wizard" on page 1423.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1177.html">PAGE 1177</a></h6>
<p>l l l l l Local Printer: The IP or host name of the printer or machine where the LPD is installed and will receive Queue Name: The queue name that will accept the job on the LPD. Default is generally "auto". Job Owner Name: Optional entry for adding the name of the job owner. Job Name: The name of the output file. You can use ${template} as a variable for the name of the Designer Template used to generate the output. (See also: "Print output variables" on page 1426.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1178.html">PAGE 1178</a></h6>
<p>Production Options l l l l l l l l l l Booklet Imposition: Check to tell the printer to generate a booklet for the print output. Booklet options are set in the "Booklet Options" on page 1180 page. This option is unselected by default unless selected in the Designer "Print section properties" on page 987. Imposition: Check to enable Cut & Stack Imposition, which is set in the "Imposition options" on page 1181 page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1179.html">PAGE 1179</a></h6>
<p>Copies (Not available in Output Creation Preset Wizard.) l l Copies: Enter the number of copies to print, of each record. Collate: When printing multiple copies you can check this checkbox to have the record copies printed together. For example in a three record job the records would print out as 1-1-2-2-3-3, rather than 12-3-1-2-3. Pure Color Thresholds This section is valid for PCL only. It applies to elements within the record that are shades of grey, rather than black or white.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1180.html">PAGE 1180</a></h6>
<p>This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. l Cancel button: Cancels the Print Wizard, without creating any printout. Booklet Options This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. The Booklet Options page defines how to generate booklets in the output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1181.html">PAGE 1181</a></h6>
<p>l Front Cover selections: l l l Blank: Select to add no data to the front cover. First page on outside and second page on inside: Select to use the first 2 pages as the inside and outside of the front cover. Back Cover selections: l l Blank: Select to add no data to the back cover. Last two pages on inside and outside: Select to use the final 2 pages as the inside and outside of the back cover.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1182.html">PAGE 1182</a></h6>
<p>handy dynamic diagram that displays a representation of the current imposition selections in real time. Whenever selections are changed, this display changes to reflect the selections made. You can even select how many pages are to be represented, whilst page numbers appear on the pages in the diagram and change dynamically, like everything else.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1183.html">PAGE 1183</a></h6>
<p>As a general rule, it makes little sense to modify the Sample Page size within the Print Wizard (as the template media size will already have been selected), but it does make sense when creating Print Output Presets for other templates. If no template is loaded or if the template does not have a Print section, then the Sample Page defaults to A4 portrait. l l l l Orientation: Select orientation (aspect ratio) of the logical template page (Landscape or Portrait).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1184.html">PAGE 1184</a></h6>
<p>l Output diagram: A real-time display that reflects the selections made in the Imposition Options page. The blue page(s) are the individual logical page(s), upon a white background that represents the physical Imposition Sheet. If the settings are invalid, the display will appear as red, such as in the following diagram: In this example the error is that the logical pages are too large to fit upon the Imposition Sheet that has been selected.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1185.html">PAGE 1185</a></h6>
<p>l Layout group: Select how the logical page(s) are to be laid out on the Imposition Sheet. l Horizontal selection: Set how many logical pages are to be placed on one horizontal line within the Imposition Sheet. Note If the logic page was set to Rotate in the Position selections, then the Horizontal selection might appear as vertical, and the Vertical selection might appear as horizontal, on the real time output diagram.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1186.html">PAGE 1186</a></h6>
<p>Each set of 5 Imposition Sheets is a discrete drill sorted nUp block that can be guillotined and stacked. The first 5 sheets encompass records 1-50, whilst the next 5 sheets encompass records 51-100.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1187.html">PAGE 1187</a></h6>
<p>The following example is the same job but with a Horizontal repetition setting of 6: As you can see, the outputs are very different.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1188.html">PAGE 1188</a></h6>
<p>Note If the Stack Depth is greater than the number of sheets in the entire job then you will get a single drill sorted block that can be guillotined and stacked to give the complete job in record order. l l Sides selection: Select how many sides of the Imposition Sheet are to be printed upon. Choice is between Simplex or Duplex. Method selection: In 2018.2 we introduced a new imposition page order for cut & stack impositioning that works with continuous feed devices: Stack by Column.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1189.html">PAGE 1189</a></h6>
<p>l l l l Off. Output is not reversed. Stack upside down: Essentially turns the stack upside down by reversing the output imposition page sides. The last sheet becomes the first, and in the case of duplex imposition, the back sides become the front sides. For presets created in a version prior to Connect 2018.2, a "Reverse Pages" selection will apply this Stack upside down setting. Inverse page order: This impositions the output in the exact opposite order from what has been selected.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1190.html">PAGE 1190</a></h6>
<p>l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. Cancel button: Cancels the Print Wizard, without creating any printout.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1191.html">PAGE 1191</a></h6>
<p>l l l l Collation level: Select whether the markings will be made at Document level, or Document Set level. Print marks on back: Check to place the Inserter Marks on the rear of the page. Selective Inserts: If selective inserts are supported by the chosen Mark Configuration you can select what markings to include and whether those markings are to included based upon some conditional setting.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1192.html">PAGE 1192</a></h6>
<p>through the wizard to return to the main selection page (the "Print options" on page 1174 page) and add or remove printing options from the print run. l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1193.html">PAGE 1193</a></h6>
<p>l Show Page: Use the up and down arrows or type a page number to display a specific page within the document. Zoom in/out: Click to zoom in or out by 25% l l Zoom Level: Use the drop-down to select a predefined level or enter a zooming percentage. Selective Insert Dialog The Selective Insert Dialog provides control over individual inserts. In this dialog the selected can be set to be either selected ("Yes") or not ("No"), or selected based upon some conditional criteria ("Conditional").</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1194.html">PAGE 1194</a></h6>
<p>l l l Separation: Use the drop-down to select when a job separation occurs, which is either None (no separation) or at the Job, Job Segment, Document or Document Set level. Slip Sheets group: l l l l Use the drop-down box to chose what the separation option is to be. The selection is either Sheets, Documents, Document Sets or Job Segments. The default separation option is Sheets, which was the only option available for splitting prior to Connect 2019.1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1195.html">PAGE 1195</a></h6>
<p>through the wizard to return to the main selection page (the "Print options" on page 1174 page) and add or remove printing options from the print run. l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1196.html">PAGE 1196</a></h6>
<p>l l l l Edit: Click to edit the currently selected entry. This will launch the appropriate edit box, for the selected entry type. Double clicking on an entry in the table has the same effect as this button. Delete: Click to delete the currently selected entry or entries. Duplicate: Click to create a duplicated copy of the entry. This creates a new entry that is exactly the same as the original. / Move Up / Move Down: Click to move the selected entry (or entries) up or down within the table.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1197.html">PAGE 1197</a></h6>
<p>Advanced Print Wizard and Output Creation Preset Wizard navigation options l l l l Preview button (active in Advanced Print Wizard only): Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1198.html">PAGE 1198</a></h6>
<p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Text, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Text, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1199.html">PAGE 1199</a></h6>
<p>Use the Add button for selection options. For details on how to create a conditional, see the "How to Set Conditionals" on page 1265 page. Additional Image Settings The Additional Image dialog displays the properties of the image added in the "Page breakdown" on page 1195 page. l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1200.html">PAGE 1200</a></h6>
<p>l l Bottom: Enter the distance between the bottom margin of the page and the image, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Filename: Use the browse button to launch a Browse box to select an image file. This is a mandatory field. Note Transparent images are not supported. l l Preview group: This displays a preview of the selected Image. Scaling group: Scaling the image expands the image but keeps the aspect ratio.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1201.html">PAGE 1201</a></h6>
<p>l "Australia Post Settings" on the facing page l "Codabar Settings" on page 1204 l "Code 128 Settings" on page 1210 l "Code 128 Settings" on page 1210 l "Data Matrix settings" on page 1213 l "EAN-13 Settings" on page 1219 l "EAN-13 Settings" on page 1219 l "GS1-128 Settings" on page 1222 l "Interleaved 2 of 5 Settings" on page 1225 l "Japan Post Settings" on page 1227 l "Japan Post Settings" on page 1227 l "PDF417 Settings" on page 1232 l "QR Code Settings" on page 1235 l "Royal M</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1202.html">PAGE 1202</a></h6>
<p>Australia Post Settings Australia Post 4 State barcodes are specific to Australian postal addresses. Every address in Australia has a numeric Delivery Point IDs (DPID) associated with it. Addresses must first be matched against an official Postal Address File (PAF), to obtain the unique DPID, and the DPIDs must be available to the job as "Meta Data options" on page 1169.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1203.html">PAGE 1203</a></h6>
<p>l Australia Post 4 State Properties group: l l Track height: The height of the small vertical centre bars, in metric (mm/cm). Value must be between 1 mm and 1.6 mm. Full bar height: Height of the tallest vertical bars, in metric (mm/cm). Value must be between 4.2 mm and 5.8 mm. The ascender and descender bar heights are automatically calculated based upon the Full and Track bar heights. l l l l Module width: Thickness of each bar in the Barcode, in metric (mm/cm). Value must be between 0.4 mm and 0.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1204.html">PAGE 1204</a></h6>
<p>Codabar Settings Codabar barcodes support the following data: 0-9 - $ : / . + plus the optional specification of start/stop characters. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1205.html">PAGE 1205</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Codabar Properties group: l l l l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1206.html">PAGE 1206</a></h6>
<p>l l Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1207.html">PAGE 1207</a></h6>
<p>Code 39 Settings Code 39 is a discrete, self-checking barcode that is also known as "Alpha39", "Code 3 of 9" (often abbreviated to "3 of 9"), "Code 3/9", "Type 39", "USS Code 39" and "USD-3". Code 39 data should contain no more than 20 digits from within the following range: Numeric digits: (0-9), upper-case letters (A-Z), seven special characters (- . space $ / + %) and the start/stop asterisk (*) character.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1208.html">PAGE 1208</a></h6>
<p>sheet rather than once per document page. Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1209.html">PAGE 1209</a></h6>
<p>l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode. Font name: Use the drop-down to select the font with which to display the human readable text. Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l Font size: Enter a font size for the human readable text.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1210.html">PAGE 1210</a></h6>
<p>Code 128 Settings Code 128 is a high-density barcode, used for alphanumeric or numeric-only barcodes. It supports all 128 ASCII characters. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1211.html">PAGE 1211</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. l Code 128 Properties group: l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1212.html">PAGE 1212</a></h6>
<p>l Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields. l Condition: Enter the condition which determines whether or not the Barcode will be added to the document at print time.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1213.html">PAGE 1213</a></h6>
<p>Data Matrix settings A Data Matrix barcode is a high-density, two-dimensional (2D) matrix barcode which supports encoded text, numbers, files and digital data. Note In order to create a GS1 compliant Data Matrix barcode, the barcode data must meet the following requirements: l l l The barcode data must start with a leading FNC1 character. Either ~1 or ~d232. The GS1 Application Identifiers (AI) must be used for all data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1214.html">PAGE 1214</a></h6>
<p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1215.html">PAGE 1215</a></h6>
<p>Note The following tilde codes are supported in GS1 DataMatrix barcodes: l l ~1 = FNC1 character (for GS1 DataMatrix barcodes) l ~2 = Structure Append l ~3 = Reader programming l ~5 = Macro5 l ~6 = Macro6 l ~7 = ECI expressions Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1216.html">PAGE 1216</a></h6>
<p>EAN-8 Settings An EAN-8 barcodes are composed entirely of numerical data. It is comprised of 7 data digits containing the country/economic area code and an item reference code, with 1 following checksum digit. Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not. It is checked by default for all new entries.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1217.html">PAGE 1217</a></h6>
<p>l EAN-8 Properties: l l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. The EAN-8 barcode employs a module width between 0.27mm and 0.66mm. l l l l l l l l Checksum: Use the drop-down to select how to deal with the Barcode checksum: Ignore: Ignore checksum calculations.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1218.html">PAGE 1218</a></h6>
<p>l Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields. l Condition: Enter the condition which determines whether or not the Barcode will be added to the document at print time.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1219.html">PAGE 1219</a></h6>
<p>EAN-13 Settings EAN-13 barcodes are composed entirely of numerical data. The first 12 digits representing country/economic area, manufacturer and product codes + 1 following checksum digit. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1220.html">PAGE 1220</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. EAN 13 Properties group: l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1221.html">PAGE 1221</a></h6>
<p>(@) character) are not supported in Connect. l l l Font size: Enter a font size for the human readable text. Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1222.html">PAGE 1222</a></h6>
<p>GS1-128 Settings GS1-128 is also known as "EAN 128", "EAN/UCC 128" and "UCC 128". This barcode type not only encodes data, but also provides a mechanism for defining the meaning (or format) of that data. It supports alphanumeric data and some predefined Function Codes. See the Wikipedia GS1-128 entry for more information. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1223.html">PAGE 1223</a></h6>
<p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1224.html">PAGE 1224</a></h6>
<p>Note Vertically-oriented fonts (fonts whose typeface name begin with the at (@) character) are not supported in Connect. l l Font size: Enter a font size for the human readable text. Process Tilde: Check this option to process tilde characters in the data as special characters. Note: with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~. l Text: Enter the text used to generate the Barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1225.html">PAGE 1225</a></h6>
<p>Interleaved 2 of 5 Settings Interleaved 2 of 5 barcodes are also known as "ITF" and "2/5 Interleaved". It is a numeric only barcode whose data must contain an even number of digits, as the barcode uses sequences of two digits interleaved with each other to create a single symbol. If the numeric data contains an odd number of digits, then a leading zero must be added to the beginning of the data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1226.html">PAGE 1226</a></h6>
<p>l Interleaved 2 of 5 Properties group: l l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values. Module Width: Specifies the width of the narrow bars. Changing this value to a higher value will generally make the Barcode bigger. Bar width ratio: Set the Barcode bar width. l l l Print human readable text: Check to add a textual version of the Barcode data. Placement: Use the drop-down to select whether to place the human readable text above or below the Barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1227.html">PAGE 1227</a></h6>
<p>Japan Post Settings Japan Post 4 State Barcodes (also known as Kasutama barcodes, or Japanese Postal Barcode) are used by Japan Post for automated mail sorting. These barcodes contain the address of the receiver encoded as a seven-digit postal code plus optional address data of up to 13 alphanumeric characters. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1228.html">PAGE 1228</a></h6>
<p>Note If Imposition options such as auto-positioning and scaling were selected, these options won't apply to the Additional Content added to the physical NUp sheet. l l l l l l l Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Japan Post Properties group: l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1229.html">PAGE 1229</a></h6>
<p>KIX Code (Dutch Post) Settings KIX code barcodes (also known as Klantenindex, or Dutch KIX 4-State), are used by Royal Dutch TPG Post (Netherlands) for Postal code and automatic mail sorting. They contain the address of the receiver, encoded in alphanumeric format (0-9, A-Z). Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1230.html">PAGE 1230</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. KIX Code Properties group: l l Track height: The height of the small vertical centre bars, in metric (mm/cm).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1231.html">PAGE 1231</a></h6>
<p>l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1232.html">PAGE 1232</a></h6>
<p>PDF417 Settings PDF417 is a two-dimensional, multi-row Barcode. It is used for encoding large amounts of data, with hundreds or even thousands of characters. It encodes alphabetic text, numbers, binary files and actual data bytes. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1233.html">PAGE 1233</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. PDF417 Properties group: l l Module Width: Specifies the width of the narrow bars.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1234.html">PAGE 1234</a></h6>
<p>Note that with this option checked, any tilde that needs to be included in the output must be escaped by adding another tilde: ~~. l Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1235.html">PAGE 1235</a></h6>
<p>QR Code Settings QR Code (Quick Response Code) is a 2D Barcode format that supports alphanumeric, numeric, byte/binary, and Kanji (Japanese-Chinese character) data. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1236.html">PAGE 1236</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1237.html">PAGE 1237</a></h6>
<p>are encoded within a length field. The following table shows the number of bits in a length field, based upon the selections made: Encoding l l l Ver. 1-9 Ver. 10-23 Ver. 27-40 Numeric 10 12 14 Alphanumeric 9 11 13 Byte 8 16 16 Kanji 8 10 12 Error Correction Level: Part of the robustness of QR codes is their ability to sustain “damage” and continue to function even when a part of the QR code image is obscured, defaced or removed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1238.html">PAGE 1238</a></h6>
<p>l Position: Select between the two methods for encoding FNC1 characters within QR Codes: l l First Position - uses the GS1 QR Code standard. Second Position - uses the AIM QR Code standard. If this option is chosen then the appropriate Application Indicator will also need to be set. l l Application ID: Enter the appropriate QR-Code Application Indicator in accordance with the specific industry or application specifications (as provided by AIM International).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1239.html">PAGE 1239</a></h6>
<p>Royal Mail 2D Mailmark Settings Royal Mail 2D Mailmark Barcodes are a variant of 2 dimensional Datamatrix barcodes. They are used by the British Royal Mail postal service. They contain the address of the receiver, encoded in alpha-numeric format (0-9, A-Z). Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1240.html">PAGE 1240</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Royal Mail 2D Properties group: l l Module Width: The size of each column and row within the barcode. Value must be between 0.5 mm and 0.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1241.html">PAGE 1241</a></h6>
<p>to Set Conditionals" on page 1265. l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1242.html">PAGE 1242</a></h6>
<p>Royal Mail 4 State (CBC) Settings Royal Mail 4-State Customer Bar Code (CBC) is also known as the Royal Mail 4-State Customer Code (RM4SCC or RoyalMail4SCC). It is used by the British Royal Mail postal service. The barcode contains an address, encoded in alpha-numeric format (0-9, A-Z). Use the following options to configure the output Barcode settings: l General group: l l l Include in output checkbox: This determines whether of not this Additional Content entry should be included in the output or not.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1243.html">PAGE 1243</a></h6>
<p>l Royal Mail Properties group: l l Track height: The height of the small vertical centre bars, in metric (mm/cm). Value must be between1.02 mm and 1.52 mm. Full bar height: Height of the tallest vertical bars, in metric (mm/cm). Value must be between4.22 mm and 5.84 mm. The ascender and descender bar heights are automatically calculated based upon the Full and Track bar heights. l l l l Module width: Thickness of each bar in the Barcode, in metric (mm/cm). Value must be between0.38 mm and 0.63 mm.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1244.html">PAGE 1244</a></h6>
<p>Royal Mail 4 State Mailmark C Settings Royal Mail 4-State Mailmark C is used by the British Royal Mail postal service. The barcode contains an address, encoded in alpha-numeric format (0-9, A-Z).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1245.html">PAGE 1245</a></h6>
<p>This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1246.html">PAGE 1246</a></h6>
<p>l l Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1247.html">PAGE 1247</a></h6>
<p>Royal Mail 4 State Mailmark L Settings Royal Mail 4-State Mailmark L is used by the British Royal Mail postal service. The barcode contains an address, encoded in alpha-numeric format (0-9, A-Z).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1248.html">PAGE 1248</a></h6>
<p>This option allow for "libraries" of Additional Content to be created in Presets, libraries from which you can pick and choose what entries you wish to have included, at time of printing. l l Description edit box: An edit box for adding an optional Description to the Additional Content entry. Position group: l l Orientation: Use the drop-down to select the orientation of the Barcode added to the page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1249.html">PAGE 1249</a></h6>
<p>l l Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1250.html">PAGE 1250</a></h6>
<p>UPC-A Settings The Universal Product Code (UPC-A) Barcode is widely used for tracking trade items in stores and at the point-of-sale. It consists of 12 numerical digits which are uniquely assigned to each trade item. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1251.html">PAGE 1251</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. UPC A Properties group: l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1252.html">PAGE 1252</a></h6>
<p>l l Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1253.html">PAGE 1253</a></h6>
<p>UPC-E Settings The Universal Product Code (UPC-E) Barcode is widely used for tracking trade items in stores and at the point-of-sale. It consists of 6 numerical digits which are uniquely assigned to each trade item. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1254.html">PAGE 1254</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. UPC A Properties group: l l Height: Enter the Barcode height in either metric (cm/mm), inch (in) or point (pt) values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1255.html">PAGE 1255</a></h6>
<p>l l Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1256.html">PAGE 1256</a></h6>
<p>US Postal Service IMb Settings US Postal Service Intelligent Mail Barcodes (IMb) are used by the United States postal service. They contain the address of the receiver, encoded in numeric format (0-9). Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1257.html">PAGE 1257</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. USPS IMB Properties group: l l l l Track height: The height of the small vertical centre tracking bars, in inches (in).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1258.html">PAGE 1258</a></h6>
<p>l l Process Tilde: This selection is not applicable to this barcode type. Text: Enter the text used to generate the Barcode. l Add button: Click to display a list of variable data that could be used for generating the Barcode. This includes metadata fields which must previously have been added in the Metadata options, likely at the Document Tags level (see Metadata Options), as well as some information fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1259.html">PAGE 1259</a></h6>
<p>US Postal Service IMpb Settings US Postal Service Intelligent Mail Package Barcodes (IMpb) are used by the United States postal service for parcel deliveries. They contain parcel destination information along with other information about the delivery. Note To create dynamic barcodes, Metadata options must first have been set (see "Meta Data options" on page 1169). Metadata fields are required to create the association between the dynamic data used in the print run and the barcode.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1260.html">PAGE 1260</a></h6>
<p>these options won't apply to the Additional Content added to the physical NUp sheet. l l l l l l l l l Bottom: Enter the distance between the bottom margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. USPS IMPB Properties group: l l Left: Enter the distance between the left margin of the page and the Barcode, in either metric (cm/mm), inch (in) or point (pt) values. Barcode height: The height of the bars in the barcode, in inches (in).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1261.html">PAGE 1261</a></h6>
<p>l Add button: Click to display a list of metadata fields, information fields to add, or common expressions to the condition. Additional OMR Mark Settings The Add OMR dialog displays the properties of an OMR Mark that was added in the "Page breakdown" on page 1195 page. These OMR marks differ from High Capacity Feeder (HCF) generated inserter marks. Those marks are specific to the inserter machine they were created for, whereas these additional OMR marks are completely independent and customizable.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1262.html">PAGE 1262</a></h6>
<p>Up sheet. l l l Left: Enter the distance between the left margin of the page and the OMR Mark, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Bottom: Enter the distance between the bottom margin of the page and the OMR Mark, in either metric (cm/mm), inch (in), pixel (px) or point (pt) values. Options Tab: l Collation Level: Choices are: l l l l Document: Treats each document as a group and the group and match marks will be set based upon the start and end of a document.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1263.html">PAGE 1263</a></h6>
<p>follows: 2, 3, 4, 5, 6, 7, 8, 9, 10, 2, 3, 4 ... Note The Sequence Number iterates per page within a group and is used to identify missing pages in a group. l l Start: The starting point for the range l Stop: The end point of the range l Start number: The number to start from (from within the selected range). Match Number Range group: Allows selection of Start and Stop points for the wrapping match number for a group.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1264.html">PAGE 1264</a></h6>
<p>l l l l On: This represents a mark that is always printed. Off: This represents a mark that is never printed; i.e. it pads the marks out with an empty position. Group Start: This represents a mark that is printed on the first page of a group. Group End: This represents a mark that is printed on the last page of a group. Note In a single page group both Group Start and End marks will print if defined since the page is both the start and end of the group.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1265.html">PAGE 1265</a></h6>
<p>total number of other printed marks on the page is even in order to keep the overall count odd. Use the drop down box to select the entry. l Conditional: Enter the condition which determines whether or not this OMR Mark will be added to the document at print time.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1266.html">PAGE 1266</a></h6>
<p>PDF Options This page appears as part of the Advanced Print Wizard and the Output Creation Preset Wizard. The PDF Options page is shown only when a PDF Print output type is selected in the Print Options dialog. It is used to select PDF specific options. Note Ideally, PDF should not be used for generating Mixplex output. You should instead use a print format that supports Duplex/Simplex switching. PDF is not suitable for this as it has no device control.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1267.html">PAGE 1267</a></h6>
<p>Note A Simple font can be a Type1 font, a TrueType font or a Type3 font. One of the main characteristics of a Simple font is that its glyphs are selected using a single byte character code, limiting the number of glyphs to a maximum of 256. For more information on Simple fonts, see Abode's documentation regarding Portable Document Format files. l Always create CID fonts (best compatibility). This option always uses composite fonts (CID fonts), regardless of the number of glyphs in the font.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1268.html">PAGE 1268</a></h6>
<p>l Pass-through PDF resources: Click to have PDF resources used as-is, without any additional processing. This guarantees the fidelity of any PDF graphics used within the template will be retained in the output. This option is only available for standard PDF output. Note Connect tries to write content in the best way possible, depending on the chosen output format and optimization settings. Selecting PDF pass-through means the output will be less optimized, which typically produces somewhat larger files.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1269.html">PAGE 1269</a></h6>
<p>encrypted information which is unique to the signer and which can be password protected and verifiable. Note PlanetPress Connect currently supports only a single Digital Signature per PDF output file. The Digital signature table contains the Digital signature Keystore and associated Signature. It has the following columns: l Name: The user-defined name of the Keystore\Signature. l Alias: The user-defined alias for the signature.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1270.html">PAGE 1270</a></h6>
<p>l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. Cancel button: Cancels the Print Wizard, without creating any printout.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1271.html">PAGE 1271</a></h6>
<p>l Keystore properties group: l l l l Type: Use the drop-down to select the appropriate type of keystore format. Password: If the keystore is password protected, type in the password that secures the keystore. Repeat Password: Re-type in the password that secures the keystore. Once this is done the two Password entry boxes will no longer have the red cross icon (indicating incomplete or unselected) flag beside them.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1272.html">PAGE 1272</a></h6>
<p>other, or neither. l Properties file group: l File: Load optional keystore properties file. Properties files could be used for storing the password, or similar. PDF Signature The PDF Signature dialog appears when either adding or editing a Signature on the "PDF Options" on page 1266 page. Note PlanetPress Connect currently supports only a single Digital Signature per PDF output file. l l l Name: Enter a name that describes the signature entry.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1273.html">PAGE 1273</a></h6>
<p>l Timestamp: Check to enable time stamping authentication. Note Not available for signatures set to use Adobe.PPKLite Handler. l l Timestamp Server URL: Select the Time Stamp Authority (TSA) URL address. One example of a TSA is https://freetsa.org. l Account: Account name specific to the TSA server chosen. l Password: Password specific to the TSA server chosen. l Repeat Password: Repeat of password. Visible Signature group: Check to add a visible signature to the PDF file.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1274.html">PAGE 1274</a></h6>
<p>Advanced Print Wizard navigation options l l l l Preview button: Click to launch a Proof Preview window, which displays how the printed output would look based upon the currently chosen selections. Back and Next buttons: Used to navigate back and forth through all the selected options within the Wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1275.html">PAGE 1275</a></h6>
<p>l Media: Lists the Media name, as defined in the template. l Tray: Use the drop-down to select in which Tray to send any page using the media. l l l l l Position: Enter a MediaPosition option on the printer to define the media to use. This entry will only be available for those printers that support the extra information. Weight: Enter a weight for the paper. This entry will only be available for those printers that support the extra information.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1276.html">PAGE 1276</a></h6>
<p>l Rules: Defaults to true, but can be altered at will. Double clicking in the field brings up the Rule Editor, which can be used to construct the rule(s) that determines whether this bin is to be used or not. The options (both button and right mouse click context menu) available to the table are: l Add: Adds a new bin selection choice to the table. l Delete: Deletes the current selection(s) from the table. l l / Move Up / Move Down: Move the selected entries up or down within the table. Edit ...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1277.html">PAGE 1277</a></h6>
<p>Note This Print Wizard page is intended for use only by those operators who are very familiar with their PostScript printer's capabilities and the options available to them in the printer's associated PPD file. A video example of how to set Dynamic PPD Options can be found here: Setting Dynamic PPD Options within Connect - An example. Note As of OL Connect 2019.1 JobPatchFile sections in PPDs are automatically added to the output, if the PPD includes them.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1278.html">PAGE 1278</a></h6>
<p>In such a scenario, selecting this checkbox will have those printers print in Landscape mode. Rules This group displays the print options for the template along with their associated triggers, as well at the more general Simplex/Duplex options. If your Template already has Finishing and Media/Trays entries set, then those options will appear pre-populated in the Rules table along with their Triggers, to allow you to assign specific options as Printer Option entries.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1279.html">PAGE 1279</a></h6>
<p>It is possible to create a set of Rules in which none of the Rules ever evaluate to true, and thus no Rule will be applied. This could be done on purpose, to allow the printer's default settings to apply. The types of Rules are as follows: l JCL (Job Control Language) Rules: This option only appears if the PPD contains a "*JCL keywords" section. Certain printers require Printer Job Language (a type of JCL) commands to function properly, or to allow certain features.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1280.html">PAGE 1280</a></h6>
<p>Once the Finishing Rules are entered you will need to assign specific Printer Options (from those contained in the PPD) to each of the individual Finishing Rules. Note You should also choose an Option to switch off the Finishing selection, to cater for subset Finishing. l l Plex rules: This fixed group allows you to set rules for sheet plexing. The choices are Duplex, Simplex or Tumble Duplex. You should add Printer Options for each of these Plexing Rules.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1281.html">PAGE 1281</a></h6>
<p>section for how to do this. l l l l l Setup : If the Rule is being added to a Setup selection, then the Dynamic Custom Element Editor Dialog will be launched. You should add Printer Options for each of the Rules added.See the "Printer Options" on page 1283 section for how to do this. Media/Trays : If the Rule is being added to a Media/Trays selection, then the Dynamic Tray Mapping Editor Dialog will be launched.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1282.html">PAGE 1282</a></h6>
<p>l Edit: This allows you to edit the current Rule, dynamically. What options are available is dependant upon what rule is currently selected. The options are as follows: l l l Media/Trays : If the Rule is being edited is a Media/Trays selection, then the Dynamic Tray Mapping Editor Dialog will be launched. Finishing : If the Rule is being edited is a Finishing selection, then the Dynamic Finishing Editor Dialog will be launched. Plex : Plex Rules cannot be edited.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1283.html">PAGE 1283</a></h6>
<p>The table is read only and the details cannot be adjusted or edited from within the table. Rules need to be edited from within the Rules table directly, through either the Edit button or by double mouse clicking on the Rule. l Condition Tab: displays the logical condition that needs to be fulfilled before the Custom Rule is to be applied. Printer Options This section allows for the selection and ordering of Printer Options to be associated with the active Rule.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1284.html">PAGE 1284</a></h6>
<p>l Sort by Order dependency: This sorts the Printer Options by the order of their dependencies. Not all Printer Options have dependencies, but for those that do, the order is important. For example, consider these following PPD file Printer Option extracts: l l PageRegion: *OpenUI *PageRegion: PickOne *OrderDependency: 50 AnySetup *PageRegion ... *CloseUI: *PageRegion InputSlot: *OpenUI *InputSlot: PickOne *OrderDependency: 20 AnySetup *InputSlot ...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1285.html">PAGE 1285</a></h6>
<p>Warning Nothing prevents the selection of conflicting and contradictory Print Options. This can be seen in the following example, which shows multiple conflicting Folding Options have been chosen: The breadth and diversity of PPD files as well as individual printer capabilities mean that the Print Wizard cannot meaningfully validate the selections made, and thus does not attempt to. So you must be careful when making selections.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1286.html">PAGE 1286</a></h6>
<p>l l Print button (Advanced Print Wizard only) or Finish button (Output Creation Preset Wizard only): Click to produce print output/finalize the Preset according to the current settings. This can be done at any point within the Wizard, whether or not all the options selected in the "Print options" on page 1174 page have been completed or not. Cancel button: Cancels the Print Wizard, without creating any printout.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1287.html">PAGE 1287</a></h6>
<p>Note In a Print context, the scripts in the Scripts pane run once for each section and once for each Master Page (see "Master Pages" on page 505). Control Script API Control Scripts are a special kind of Designer Scripts. They don't touch the content of the sections themselves, but they change the way a template is outputted, for example by selecting or omitting sections from the output. For more information about Control Scripts and their use, see "Control Scripts" on page 885.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1288.html">PAGE 1288</a></h6>
<p>Objects Object Description "results" on page 1389 This object is used to manipulate the content of the template. It contains the HTML element or set of HTML elements that match the selector of the script, specified in the script editor. This object is not available in Control Scripts, because that type of script doesn't have a selector (see "Control Scripts" on page 885). "record" on page 1290 The record in the main data set that is currently being merged.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1289.html">PAGE 1289</a></h6>
<p>Object Description key-value pairs (a JSON string). Note: The contentitem object is not available in PrintShopMail Connect, due to the absence of a Connect database. Global functions Function Description "fatalError (message)" on page 1329 Triggers a fatal error that aborts content creation. "loadhtml()" on page 1338 Loads HTML data from an HTML (snippet). The returned HTML can be placed into a variable or into a set of HTML elements. "loadjson()" on page 1342 Loads JSON data from a URL.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1290.html">PAGE 1290</a></h6>
<p>logger This is a global ScriptLogger object that allows logging messages such as error, warning or informational messages. The messages will appear in the Messages pane (see "Preflight Results and Messages" on page 1034 and "Designer User Interface" on page 915). Methods These are the methods of the logger object.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1291.html">PAGE 1291</a></h6>
<p>Field Type Description followed by a numeric index for a record inside that detail table. For example, to access the value of the field prod_id in the first record of a detail table called detail, use: record.tables["detail"][0].fields["prod_id"]. Examples The following Standard Script evaluates the data field Country in the current record. If the value is 'CANADA' it will show the results, otherwise it will hide them.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1292.html">PAGE 1292</a></h6>
<p>Note that indexes start counting at 0, so tables["detail"][0] refers to the first record in the detail table. results The results object (type: QueryResults) is the result of the query for HTML elements that match the selector of the script. The selector of a script can be specified in the Script Editor and is visible in the second column of the Scripts pane, next to the name of the script. If, for example, a script would have the selector p.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1293.html">PAGE 1293</a></h6>
<p>Function Description "Examples" on page 1296 Adds elements to a set of HTML elements. "Examples" on page 1297 Adds the specified class to each element in a set of HTML elements. Has no effect if the class is already present. "Examples" on page 1298 Inserts content after each element in a set of HTML elements.. "Examples" on page 1300 Inserts content at the end of each element in a set of HTML elements.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1294.html">PAGE 1294</a></h6>
<p>Function Description "Example" on page 1311 Returns a subset of the current result set. "Example" on page 1312 Performs a search for a text in the children of each element in a set of HTML elements, and returns a new result set with elements that surround the occurrences. "get(index)" on page 1313 Returns the element found at the supplied index in a set of HTML elements. "Example" on page 1313 Returns true if the first element in this result set has the specified class.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1295.html">PAGE 1295</a></h6>
<p>Function Description "Example" on page 1318 Returns the parents of the elements in a set of HTML elements. "Examples" on page 1319 Inserts content at the beginning of an HTML element or of each element in a set of HTML elements. "Examples" on page 1321 Removes an HTML element or a set of HTML elements from the document. "Examples" on page 1323 Removes the specified attribute from each element in this result set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1296.html">PAGE 1296</a></h6>
<p>Function Description page 1326 borders. add() The add() function allows you to add elements to a set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349). add(content) Returns the union of this result or result set and other content. content A query result. This can be an HTML string or a result set. Examples Add one result set to another This script adds one query result to another and sets the background color to yellow.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1297.html">PAGE 1297</a></h6>
<p>Selector Matched element Matched element after script execution #chapters <p id="chapters">{{chapters}}</p> <h1>Chapter 1</h1> <p>Lorem ipsum...</p> <h1>Chapter 2</h1> <p>Lorem ipsum...</p> <h1>Chapter 3</h1> <p>Lorem ipsum...</p> <h1>Chapter 4</h1> <p>Lorem ipsum...</p> addClass() Adds the specified class(es) to each element in a set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1298.html">PAGE 1298</a></h6>
<p>Selector Matched element Matched element after script execution p <p>Hello world</p> <p class="foo bar">Hello world</p> after() Insert content after each element in the set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349). See also: " Examples" on page 1304.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1299.html">PAGE 1299</a></h6>
<p>Matched element Matched element after script execution <p id="salesrep">Peter Parker</p> <p id="salesrep" style="color: red;">Peter Parker</p> <p>Lorem ipsum</p> Note: the way the functions after() and css() are used in this script is called 'chaining'. Chaining is optional; the same could be achieved by storing the result of the query in a variable: var salesrep = query("#salesrep"); salesrep.after("<p>Lorem ipsum</p>"); salesrep.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1300.html">PAGE 1300</a></h6>
<p>Matched element Matched element after script execution <p id="salesrep">Peter Parker</p> <p id="salesrep">Peter Parker</p> <span>Lorem Ipsum</span> append() Insert content at the end of each element in the set of each element in a set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349). See also: "Examples" on page 1319.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1301.html">PAGE 1301</a></h6>
<p>This script appends a string to the results (the HTML elements that match the selector of the script). The string is added to the end of the matched element(s) and wrapped in a Span element. results.append("Peter Parker"); Selector Matched element Matched element after script execution .</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1302.html">PAGE 1302</a></h6>
<p>Selector Matched element Matched element after script execution #box <div id="box"> <h1>Personal information</h1> </div> <div id="box"> <h1>Personal information</h1> <p>Peter Parker</p> </div> This script looks for an element with the ID box and appends a paragraph to it. query("#box").</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1303.html">PAGE 1303</a></h6>
<p>attr() Returns the value of the specified attribute of the first element in a result set, or sets the value of the specified attribute of each element in a result set. attr(attributeName) : String Returns the value of the specified attribute of the first element in a result set. attributeName String; the name of the attribute. Examples This script - with the selector img - stores the source of the first image in a variable. var src = results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1304.html">PAGE 1304</a></h6>
<p>The following script sets the background color of a specific table cell in an email to red if the value of the field TOTAL has a negative value in the current record. if(record.fields.TOTAL<0) { query("#total").attr("bgcolor","red"); } before() Insert content before each element in the set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349). See also: "Examples" on page 1298.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1305.html">PAGE 1305</a></h6>
<p>Matched element Matched element after script execution <p id="salesrep">Peter Parker</p> <p>Lorem ipsum</p> <p id="salesrep">Peter Parker</p> The following script looks for an element with the ID salesrep, inserts a paragraph before that element and colors that element red. query("#salesrep").before("<p>Lorem ipsum</p>").</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1306.html">PAGE 1306</a></h6>
<p>Matched element Matched element after script execution <p>ipsum dolor sit amet, consectetur adipiscing elit.</p> <span>Lorem Ipsum</span> <p id="salesrep">Peter Parker</p> children() Returns the immediate children (inner HTML) of the elements in a result set. Examples This script retrieves the inner HTML of an element selected from a snippet. var snippet = loadhtml('snippets/snippet.html','#foobar').children (); results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1307.html">PAGE 1307</a></h6>
<p>The following script clones an existing table row to match the number of rows in a detail table. Afterwards it iterates over the rows to populate the fields. // Create the number of rows based on the records in the detail table // We start at 1 so the boilerplate row is used too and there is no need to delete that row for(var r = 1; r < record.tables['detail'].length; r++) { results.parent().append(results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1308.html">PAGE 1308</a></h6>
<p>} // Hide our boilerplate row (note that this doesn't really delete the row). results.hide(); closest() For each element in a set, this function gets the first parent element that matches a selector, by testing the element itself and traversing up through its ancestors in the DOM tree. (In HTML, a parent is an element that contains another element.) To get a child element or all child elements, use children() (see "Examples" on page 1306).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1309.html">PAGE 1309</a></h6>
<p>css() Gets the value of a style property for the first element in the set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349), or sets one or more CSS properties for every element in the set. css(styleName) : String Returns the value of the specified CSS property. propertyName String; the name of the CSS property.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1310.html">PAGE 1310</a></h6>
<p>query("#callout p").css('color' , 'red'); The following script does the same, but it only sets the text color to red if in the current record the value of the field 'accounttype' is 'PRO'. if(record.fields.accounttype == "PRO") { query("#callout p").css("color","red"); } This script sets the text color of the results to a hexadecimal color code. results.css('color' , '#669900'); This script loads a snippet into a variable.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1311.html">PAGE 1311</a></h6>
<p>Example This script empties all Span elements found in the template. results.empty(); Selector Paragraph before script execution Paragraph after script execution span <p>Lorem ipsum <span>dolor sit</span> amet, consectetuer adipiscing elit.</p> <p>Lorem ipsum <span></span> amet, consectetuer adipiscing elit.</p> filter() filter(callback) Returns a subset of a set. All elements for which the callback function returns true will be included in the result.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1312.html">PAGE 1312</a></h6>
<p>results.filter(function(index) { return index % 3 === 2; }).css( "background-color", "red" ); filter(selector) Returns a subset of a set. All elements matching the selector will be included in the result. The difference between results.filter(selector) and query(selector, results) is that query() searches throughout the entire results while filter() only takes the top-level elements into account. selector A String containing a CSS selector. See https://www.w3schools.com/cssref/css_selectors.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1313.html">PAGE 1313</a></h6>
<p>decoration','underline'); results.replaceWith(mysnippet); get(index) Returns the element found at the supplied index in a set of HTML elements. index Place of the element in the result set. The index starts counting at zero. Example This Post Pagination Script copies the page numbers of level 1 and 2 headings in all Print sections to the corresponding entry in a table of contents. var $numbers = query('.number'); merge.context.query("h1, h2").each(function( index ) { var pageNo = this.info().</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1314.html">PAGE 1314</a></h6>
<p>if (results.hasClass('green')) { results.css('color', 'green'); } height() Gets or sets the outer height, including padding and borders, of the first element in the results (see "results" on page 1389), i.e. the set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349). height(): Number Returns the outer height of this element, including padding and borders, excluding margins. To include margins, call height(true).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1315.html">PAGE 1315</a></h6>
<p>w = w + 20; results.height( h, true); results.width( w, true); hide() Hides the elements in a set. This doesn't remove the elements; to make them visible again, use the function "show()" on page 1324. These functions are used by the Conditional Script Wizard, as you can see when you open a Conditional Script and click the Expand button; see "Showing content conditionally" on page 810.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1316.html">PAGE 1316</a></h6>
<p>var promoTxt = loadhtml('snippets/promo-en.html', '#' + record.fields['YOGA']); results.html(promoTxt); The following script loads a snippet. Then it looks for a placeholder (@var2@) in the text of that snippet and replaces every found placeholder by the text '<i>OL Connect 1</i>'. It uses html() so the HTML formatting (<i> and </i>) will indeed be interpreted as HTML. Finally, it places the snippet in the template. var mysnippet = loadhtml('snippets/snippet.html'); mysnippet.find('@var1@').</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1317.html">PAGE 1317</a></h6>
<p>while ( ! query("#mybox").overflows()) { //do something } The following script selects three boxes that all have the class box (selector: .box). It loops over them, inserting as many products from an array as possible into the box. In fact, it inserts one too many and removes the last one before moving on to the next box. var products = ["Appetizer","Beans","Beef","Lettuce","Sprouts","Coconut","Juice"," Soup","Coriander","Cheese","Pasta","Sugar","Vinegar","Bread"]; var i = 0; results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1318.html">PAGE 1318</a></h6>
<p>toc += '</ul>'; results.after(toc); The first line creates a variable for the table of contents, which will be a list (a <ul> element with the ID toc). The start tag of the list is added to the variable. The next line does a query for all level 1 headings (<h1> elements) with the class title in the current section. With each() the script loops through them. For each of the headings it adds a line item to the list, with the text (this.text()) and the page reference of the respective heading.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1319.html">PAGE 1319</a></h6>
<p>prepend() Insert content at the beginning of each element in the set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349). See also: "Examples" on page 1300. prepend(content) Insert content as the first element to each element in the set of HTML elements that match the selector of the script or of another query in the template (see "query()" on page 1349). Append creates a new result set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1320.html">PAGE 1320</a></h6>
<p>Selector Matched element Matched element after script execution <p class="name">Peter Parker</p> </div> Parker</p> </div> This script inserts content in multiple <div> elements at the same time. results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1321.html">PAGE 1321</a></h6>
<p>Matched element Matched element after script execution <div id="box"> <p>Peter Parker</p> </div> <div id="box"> <h1>Personal information</h1> <p>Peter Parker</p> </div> This script uses the function query() to find a box, prepends a heading and sets the text color of the entire box to red. query("#box").prepend("<h1>Personal information</h1>").</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1322.html">PAGE 1322</a></h6>
<p>results.remove(); Selector Paragraph before script execution Paragraph after script execution span <p>Lorem ipsum <span>dolor sit</span> amet, consectetuer adipiscing elit.</p> <p>Lorem ipsum amet, consectetuer adipiscing elit.</p> The selector of the following sample script is tbody. Before this script runs, the table body consists of a single placeholder row with three cells. After running the script, it contains thirty rows.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1323.html">PAGE 1323</a></h6>
<p>removeAttr() Removes the specified HTML attribute from an element or from each element in a set of elements. To add or change an attribute, use attr() (see "Examples" on page 1303). removeAttr(attributeName) attributeName String; the name of the attribute. Examples This script looks up an email field in a form (which is an <input> with the ID #email1) and removes its readonly attribute. query("#email1").removeAttr('readonly'); removeClass() Removes the specified class from each element in this result set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1324.html">PAGE 1324</a></h6>
<p>replaceWith(content) Replaces each element in a set of HTML elements. Returns the result set. content A query result. This can be an HTML string or a result set. Examples Replace elements with a snippet The following script loads a snippet and then replaces the elements matched by the script's selector with the snippet. var snippet = loadhtml('snippets/mysnippet.html'); results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1325.html">PAGE 1325</a></h6>
<p>if (record.fields["Country"] == "CANADA") { results.show(); } else { results.hide(); } tagName() Returns the HTML tag name of one element in a set of HTML elements, in uppercase (e.g. H1, P, ARTICLE). Example This Post Pagination Script finds level 1 and 2 headings in all Print sections and stores their page number, text and HTML tag name. merge.context.query("h1, h2").each(function() { var pageNo = this.info().pageNo; var text = this.text(); var level = this.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1326.html">PAGE 1326</a></h6>
<p>Example This script loads a snippet, then looks for placeholders using find(), and replaces them using text(value). var mysnippet = loadhtml('snippets/snippet.html'); mysnippet.find('@var1@').text('OL Connect 1'); mysnippet.find('@var2@').html('<i>OL Connect 2</i>').css('textdecoration','underline'); results.replaceWith(mysnippet); width() Gets or sets the outer width, including padding and borders, of the first element in the results (see "results" on page 1389), i.e.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1327.html">PAGE 1327</a></h6>
<p>results.height( h ); results.width( w ); The following script does the same, but in this case, margins are included. ar h = results.height(true); v var w = results.width(true); h = h + 20; w = w + 20; results.height( h, true); results.width( w, true); each() A generic iterator function, to iterate over the elements in the result set. each(callback) Iterates over the elements in a set, such as the enumerable properties of an object, in arbitrary order.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1328.html">PAGE 1328</a></h6>
<p>this.html(test); }); Selector Matched element Matched element after script execution p <p></p> <p></p> <p></p> <p>3</p> <p>1</p> <p>7</p> The next script gets the row index (of the current element in the set) and puts it in a paragraph. results.each(function(index){ this.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1329.html">PAGE 1329</a></h6>
<p>Selector Matched element Matched element after script execution p <p datatranslate="first"></p> <p datatranslate="last"></p> <p datatranslate="email"></p> <p>primero</p> <p>último</p> <p>dirección de correo electrónico</p> fatalError(message) The fatalError() function triggers a fatal error that aborts content creation. message A string.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1330.html">PAGE 1330</a></h6>
<p>for(variable in object) { ... } Iterates over the enumerable properties of an object, in arbitrary order. For each distinct property, statements can be executed. Examples This script iterates over field names in the current record and adds them to a paragraph. for(var i in record.fields){ results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1331.html">PAGE 1331</a></h6>
<p>Selector Matched element Matched element after script execution #countries <h1 id="countries">Countries</h1> <h1 id="countries">Countries</h1> <p>The Netherlands</p> <p>Canada</p> <p>Australia</p> This script iterates over rows in a detail table and adds the contents of the 'ItemID2' field to an option. The <option> tag defines an option in a select list in an HTML form. for(var i in record.tables['detail']) { var str = record.tables['detail'][i].fields["ItemID2"]; results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1332.html">PAGE 1332</a></h6>
<p>Function l l l Description integerUngrouped () number() numberUngrouped () l date() l dateLong() l dateMedium() l dateShort() l dateTime() l dateTimeLong() l dateTimeMedium() l dateTimeShort() l timeLong() l timeMedium() l timeShort() l lowerCase() l upperCase() l properCase() The date(), dateTime() and time() functions allow you to format a date and/or time in different ways. See "Creating a Date object from a string" on page 1336.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1333.html">PAGE 1333</a></h6>
<p>l dateTimeLong() l dateTimeMedium() l dateTimeShort() l time() l timeLong() l timeMedium() l timeShort() Note The locale also influences the output of the different Date functions; see "Locale" on page 782. Tip To format a date from a date field in the record set, you can enter a custom pattern via the Text Script Wizard; see "Using the Text Script Wizard" on page 803, "Formatting variable data" on page 807 and "Date and time patterns" on page 1337).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1334.html">PAGE 1334</a></h6>
<p>dateMedium(value) Formats a date as medium string representation, for example 01/04/16. value A Date object. A Date can contain a date and time. dateShort(value) Formats a date as short string representation, for example 1-Apr-2016. value A Date object. A Date can contain a date and time. dateTime(value, pattern) Formats a date and time object using a custom pattern. value A Date object. A Date can contain a date and time. pattern String.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1335.html">PAGE 1335</a></h6>
<p>dateTimeShort(value) Formats a date and time as short string representation, for example 01/04/16 12:00 AM. value A Date object. A Date can contain a date and time. time(value, pattern) Formats a time using a custom pattern. value A Date object. A Date can contain a date and time. pattern String. The custom pattern may consist of pattern letters, separating symbols and quoted text, for example: "'at' HH:mm:ss z"; see "Date and time patterns" on page 1337.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1336.html">PAGE 1336</a></h6>
<p>Examples The following script passes the value of a field in the record set to the date() function. This will only work if the type of the field has been set to Date in the data mapping configuration and if the field contains a valid date. var myDate = formatter.date(records.fields.DATE, "MM/dd/yyyy"); The custom pattern that the script provides, outputs the month and day in two digits each and the year in four digits: 05/21/2016.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1337.html">PAGE 1337</a></h6>
<p>Another way to put a string in a Date is to use the Date.parse function; see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_ Objects/Date/parse. The date variable can be used as the value in the date, dateTime or time functions of the formatter. var myDate = formatter.date(date, "MM/dd/yyyy"); Date and time patterns Dates and times in a template originating from a date field in a record set can be displayed using a custom pattern.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1338.html">PAGE 1338</a></h6>
<p>M Month in year Month July; Jul; 07 w Week in year Number 27 W Week in month Number 2 D Day in year Number 189 d Day in month Number 10 F Day of week in month Number 2 E Day name in week Text Tuesday; Tue u Day number of week (1 = Monday, ...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1339.html">PAGE 1339</a></h6>
<p>An optional selector allows you to retrieve only the content of matching elements. Note l The specified HTML file is expected to be UTF-8 encoded. l Loadhtml() is cached per batch run (based on the URL) in print/email. Tip To load a JavaScript file (.js) or a style sheet (.css) you can use loadtext(). See "loadtext()" on page 1343. Tip External content is not loaded while editing a script. To test a script that loads external content, you can do a preflight; see "Doing a Preflight" on page 864.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1340.html">PAGE 1340</a></h6>
<p>Tip To quickly get the location of an HTML snippet in the template resources, right-click the snippet in the Resources pane and select Copy Resource Location. The path to a remote HTML snippet can be copied from the snippet's properties: right-click the snippet in the Resources pane and select Properties. Examples This script loads a local HTML snippet (from the Resources panel) directly into the matched elements results.loadhtml("snippets/snippet.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1341.html">PAGE 1341</a></h6>
<p>results.append("<p style='font-weight: bold;'>" + subject + "</p>"); loadhtml(location, selector) Retrieves specific content from the specified HTML file. location String containing a path that can be absolute or relative to the section/context. Use snippets/<snippet-name> to retrieve the content from an HTML file residing in the Snippets folder on the Resources panel. In order to retrieve files from outside the template the file protocol is supported as well as the http/https protocols.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1342.html">PAGE 1342</a></h6>
<p>This script loads the children of the selected element. var snippet = loadhtml ('file:///C:/Users/PParker/Documents/Example.html','foobar').childr en(); results.replaceWith(snippet); The next script loads a remote snippet (see "Remote snippets" on page 738), looks for an H1 heading and uses that text. var post = loadhtml('snippets/post.rhtml'); var h1 = query('h1', post).text(); results.text(h1); Another example is given in the following how-to: Using a selector to load part of a snippet.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1343.html">PAGE 1343</a></h6>
<p>String; the supplied location should be either a URL or a relative file path. The file protocol is supported as well as the http/https protocols. The complete syntax of a fully qualified URL with the "file" protocol is: file://<host>/<path>. If the host is "localhost", it can be omitted, resulting in file:///<path>, for example: file:///c:/somefolder/somejson.json. Examples This sample script retrieves JSON data from a snippet. var localJSON = loadjson('snippets/jsonsnippet.json'); if(localJSON.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1344.html">PAGE 1344</a></h6>
<p>Tip To load an HTML fragment, you can use use loadhtml() (see Skin/Formats/CrossReferencePrintFormat("loadhtml()Loads HTML content from the specified HTML file. The file may be located inside the template (see Skin/Formats/CrossReferencePrintFormat("Snippets" on page 1)) or hosted on a Content Management System or on another location outside the template.An optional selector allows you to retrieve only the content of matching elements.The specified HTML file is expected to be UTF-8 encoded.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1345.html">PAGE 1345</a></h6>
<p>a path that can be absolute or relative to the section/context. Use snippets/<snippet-name> to retrieve the content from an HTML file residing in the Snippets folder on the Resources panel. In order to retrieve files from outside the template the file protocol is supported as well as the http/https protocols. The complete syntax of a fully qualified URL with the "file" protocol is: file://<host>/<path>.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1346.html">PAGE 1346</a></h6>
<p>http/https protocols. The complete syntax of a fully qualified URL with the "file" protocol is: file://<host>/<path>. If the host is "localhost", it can be omitted, resulting in file:///<path>, for example: file:///c:/somefolder/somecontent.js. Examples This script loads a JavaScript file (from the Resources pane) directly into a <script> element. var js = loadtext("js/my-script.js"); results.append(query("<script>").</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1347.html">PAGE 1347</a></h6>
<p>currency(value, pattern) Formats a number as an amount of money using a custom pattern. Which currency symbol and which thousands separator are used depends on the Locale; see "Locale" on page 782. For available patterns, see "Number patterns" below. value A number. This can be a value from a field that contains a SmallInteger, BigInteger, Float, SmallCurrency or LargeCurrency. pattern A custom pattern that may consist of symbols; see "Number patterns" below.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1348.html">PAGE 1348</a></h6>
<p>In the Script Editor, the pattern can be passed to a function of the formatter; see "formatter" on page 1331. The custom pattern may consist of pattern characters (see below), a prefix and a suffix. Note that strings need to be converted to a number before they can be formatted this way. The repetition of pattern letters determines the exact presentation. For example, the pattern "00000" limits the number to 5 digits and adds leading zeros to any numbers that are not 5 digits long.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1349.html">PAGE 1349</a></h6>
<p>symbol. If present in a pattern, the monetary decimal separator is used instead of the decimal separator. ' Prefix or suffix Text Used to quote special characters in a prefix or suffix, for example, "'#'#" formats 123 to "#123". To create a single quote itself, use two in a row: "# o''clock". Source: http://docs.oracle.com/javase/7/docs/api/java/text/DecimalFormat.html.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1350.html">PAGE 1350</a></h6>
<p>Examples Look for an element with a certain ID This scripts applies a style rule to the queried elements. query("#test1").css("color", "yellow"); Matched element Matched element after script execution <p id="test1">foo</p> <p id="test1" style="color: yellow;">foo</p> Look for an element in a snippet The following script loads a snippet. Then it looks up an element in a snippet and sets its text. Finally, it replaces the elements matched by the script's selector by the snippet.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1351.html">PAGE 1351</a></h6>
<p>Since the results object also is the result of a query (for elements that match the selector of the script), it can be passed as context. For example in a script with the selector “table”. var rows = query("tr", results); query(html) Creates a new HTML element on the fly from the provided string of raw HTML, and returns the new element. html A String containing a HTML element. Tags that can contain other elements should be paired with a closing tag.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1352.html">PAGE 1352</a></h6>
<p>(see "What Control Scripts are" on page 885). For example, the query() function can't be used in a Control Script because it requires access to the DOM which a Control Script doesn't have. Object Usage channel (see "Channel" on page 1382) The channel for which output is generated. This is registered in the merge object: merge.channel.Note that the channel doesn't change when the output consists of different contexts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1353.html">PAGE 1353</a></h6>
<p>Object Usage "template" on page 1379 The template object contains all contexts and sections. It is accessed through the merge object: merge.template. automation This object (of the type: Automation) encapsulates the properties of the PlanetPress Workflow process that triggered the current operation. Note This object is only available in a Web context. Note The automation object available in DataMapper scripts is not of the same type. It has different properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1354.html">PAGE 1354</a></h6>
<p>To access ProcessName, OriginalFilename or TaskIndex (defined in Workflow): automation.properties.OriginalFilename; Example Assume that a Workflow process can be triggered when an XML file appears in a certain folder. The XML file contains data that you want to show on a web page. Add a Set Job Infos and Variables Task to the Workflow process (see Set Job Infos and Variables in the Workflow Online Help) .</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1355.html">PAGE 1355</a></h6>
<p>Field Type Description context: merge.template.contexts.PRINT.sections ['Section X']. type "ContextType" on page 1383 The context type: PRINT, EMAIL or WEB. Function Description "query (selector)" on page 1388 Runs a query across all sections in the Print context. This function is only available in Post Pagination Scripts, which are only applied to the Print context. See "Post Pagination Scripts" on page 900.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1356.html">PAGE 1356</a></h6>
<p>Functions and fields Field Type "Examples" on page 1378 "Setting the margins of a Print section" on page 1403 Description Sets the initial HTML of the body element. Margins Allows to set the header and footer of a Master Page, using a Measurement string, for example: "2in" (this sets a margin to two inches). html(value) Replaces the contents of the <body> of a section or Master Page by the supplied value. This function is only available in Control Scripts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1357.html">PAGE 1357</a></h6>
<p>Fields Field Type Description bottom left right top String These fields allow to set the bottom, left, right and top of a Print section, using a Measurement string, for example: "2in" (this sets a margin to two inches). footer header String These fields allow to set the header and footer of a Master Page, using a Measurement string. Examples Setting the margins of a Print section var sectionA = merge.template.contexts.PRINT.sections["Section A"]; sectionA.margins.top = "2in"; sectionA.margins.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1358.html">PAGE 1358</a></h6>
<p>Fields Field Type Description stationery Stationery The Stationery's object's front and back fields are used to set the front and the back of a Media; see "front, back" below. front, back The front and back fields of the Stationery object are used to set the front and the back of a Media (see "media" on the previous page). Both front and back have the following fields. Field Type Description enabled boolean When enabled, the stationery will be included in the output (Print sections only).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1359.html">PAGE 1359</a></h6>
<p>Field Type Description left Measurement The horizontal offset from the left of the page, used to position the stationery (only when absolute positioning is selected). This value can be negative. merge In Control Scripts, the root level instance of the object merge is the entry point from where you can query and change the way contexts are merged. It gives access to the template with all its contexts and sections.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1360.html">PAGE 1360</a></h6>
<p>Field Type on page 1395 Description Note! In Control Scripts, merge.section is only available when the output channel is WEB. To make sure that it is defined, use the following statement: if (merge.channel == Channel.WEB && merge.context.type == ContextType.WEB) { ... }. To retrieve any section in a Control Script, use: merge.template.contexts.ContextType.Section['Section name']; (for example: merge.template.contexts.PRINT.sections["Section EN"]).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1361.html">PAGE 1361</a></h6>
<p>The location should be a URL relative to the template root or an absolute file-based URL (without protocol), e.g. "C:/myfile.pdf". pageNumber (optional) The desired page. Counting starts at 1. If no page number is given, information about the first page will be retrieved. The returned object is of the type ImageInfo. It has the following fields: Field Type Description height float The height of the current page (in points). page Number Current page number (counting from 1) within the resource.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1362.html">PAGE 1362</a></h6>
<p>Permissions Allows to verify if a PDF is password-protected or has restrictions for printing. This is part of the information about an image that is returned by the resource() function; see "resource()" on page 1360). Note If a PDF that does not allow content copying, Connect cannot handle the PDF at all and we cannot determine the permissions. In that case hasPassword will be true (even if the password is not set) and printingAllowedwill be unknown.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1363.html">PAGE 1363</a></h6>
<p>A section can also be retrieved via merge.context.sections['section name']. Remember, however, that when several contexts need to be merged (for example, when the Print context is attached to an email), the script needs to check if the current context is of the type that contains the desired section (for example: if (merge.context.type == ContextType.PRINT) {}). When sections in different contexts have the same name, it is safer to use merge.template.contexts.ContextType.sections["section name"].</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1364.html">PAGE 1364</a></h6>
<p>Field Type Description sections are enabled by default. headers String DEPRECATED. Use the addHeader() function instead. Email sections only. Used to set custom email headers. margins Margins Print sections only. Used to set the print margins of a section. You can set the bottom, left, right and top margin using a Measurement string; for example, "2in" sets a margin to two inches. minPages Number Minimum number of pages in the section. The default is 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1365.html">PAGE 1365</a></h6>
<p>Field Type Description part String Name for the part. part is used to specify where a new part starts and the title for the part. This is used to split Email attachments. The Email output can, for example, attach 3 PDFs generated from the Print context. The part name will be used as the file name for the attachment. See "Parts: splitting and renaming email attachments" on page 890. password String Print sections only.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1366.html">PAGE 1366</a></h6>
<p>Functions Note For cloned sections, functions are not available. Function Description "Examples" on page 1376 Clone this section. See "Dynamically adding sections (cloning)" on page 895. addAfter() Add a cloned section after this section. addBefore() Add a cloned section before this section. addHeader (key, value) Email sections only. Used to set custom email headers. The function expects a key and a value (both of type string).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1367.html">PAGE 1367</a></h6>
<p>var printSections = merge.template.contexts.PRINT.sections; printSections['Section EN'].enabled = false; printSections['Section FR'].enabled = false; if(record.fields.Language === 'FR'){ printSections['Section FR'].enabled = true; } else { printSections['Section EN'].enabled = true; } Selecting different sections for Print output and Email PDF attachment This script selects a different Print section for output, depending on the output channel (Email or Print). var printSections = merge.template.contexts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1368.html">PAGE 1368</a></h6>
<p>if (channel == Channel.EMAIL) { // only when generating Email output if (merge.context.type == ContextType.PRINT) { merge.context.sections['Section 1'].enabled = false; merge.context.sections['Section 2'].enabled = false; merge.context.sections['Section 3'].enabled = true; merge.context.sections['Section 3'].part = "PDFAttach1"; merge.context.sections['Section 4'].enabled = true; merge.context.sections['Section 4'].restartPageNumber = false; merge.context.sections['Section 5'].enabled = false; merge.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1369.html">PAGE 1369</a></h6>
<p>Using abolute positioning var activeSection = merge.template.contexts.PRINT.sections['Section 1']; activeSection.background.source = BackgroundResource.RESOURCE_PDF; activeSection.background.position = MediaPosition.ABSOLUTE; activeSection.background.left = "10mm"; activeSection.background.top = "10mm"; activeSection.background.url = "images/somepage.pdf"; Scaling to Media size var activeSection = merge.template.contexts.PRINT.sections['Section 1']; activeSection.background.source = BackgroundResource.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1370.html">PAGE 1370</a></h6>
<p>resources as its background. It explicitly enables the clone and then adds it to the Print context. var printSections = merge.template.contexts.PRINT.sections; merge.template.contexts.PRINT.sections["Policy"].enabled = false; if(record.fields.policy_a == 1) { addPolicy('a'); } if(record.fields.policy_b == 1) { addPolicy('b'); } function addPolicy(policy){ var resourceUrl = 'images/policy-' + policy + '.pdf'; var clone = printSections["Policy"].clone(); clone.name = "policy_" + policy; clone.background.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1371.html">PAGE 1371</a></h6>
<p>Field Type Description left Measurement The left offset of the PDF background (only when absolute positioning is selected). positio n "MediaPosition" on page 1384 Set the position of the PDF background (Absolute, centered, fit to media). rotation Number Set the rotation of the PDF background to 0, 90, 180 or -90 degrees. scale Number Set the size of the PDF background as a percentage of the original image.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1372.html">PAGE 1372</a></h6>
<p>Field Type Description images/background.pdf. l l A URL (either file:, http:, or https:). The complete syntax for an external file is: file://<host>/<path>. If the host is "localhost", it can be omitted, resulting in file:///<path>, for example: file:///c:/resources/images/image. jpg. An absolute Windows-style path. A relative path and a URL are expected to be URL encoded. For example, a space needs to be encoded as %20.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1373.html">PAGE 1373</a></h6>
<p>Tip For more examples, see "Control Script: Setting a Print section's background" on page 893. sheetConfig Sheet configuration settings are the Master Page, Media and Duplex printing options of first/middle/last/single or all sheets in a Print section. The sheetConfig object holds these options and can be used to set (or rather, override) them via a Control Script (see "Control Scripts" on page 885 and "Control Script API" on page 1351).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1374.html">PAGE 1374</a></h6>
<p>Field Type Description (see "Example s" on page 1376 ) allow content on sheets in different positions; for example: var section1 = merge.template.contexts.PRINT.sections [0]; section1.sheetConfig.positions.all.me dia = "Media 1"; For an overview of the available settings in each position see "Examples" on page 1376. tumble Boolean (Only with duplex printing.) When tumble is set to true, pages are printed like in a calendar. (On Portrait output, this would be equivalent to short-edge duplex.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1375.html">PAGE 1375</a></h6>
<p>l all: All sheets in the section. Note Settings for all sheets may conflict with settings for a particular position. In such cases, the setting that was specified last overrides the other. Each of these positions has the following fields. Field Type Description allowContent AllowContent Used to specify on which sides of a sheet (in a certain position) content is allowed. Possible values: l l l l AllowContent.ALL_SIDES AllowContent.FRONT_ONLY (only with duplex printing) AllowContent.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1376.html">PAGE 1376</a></h6>
<p>Note To remove a Media or Master Page via script, give it the value undefined, or null, or an empty string (""); see the examples below. Examples This script retrieves a Print section and modifies a number of settings for all of its sheets. let section = merge.template.contexts.PRINT.sections["Section 1"]; section.sheetConfig.positions.all.allowContent = AllowContent.ALL_ SIDES; section.sheetConfig.positions.all.media = "MyMedia"; section.sheetConfig.positions.all.masterFront = "Master page 1"; section.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1377.html">PAGE 1377</a></h6>
<p>The following script clones an existing table row to match the number of rows in a detail table. Afterwards it iterates over the rows to populate the fields. // Create the number of rows based on the records in the detail table // We start at 1 so the boilerplate row is used too and there is no need to delete that row for(var r = 1; r < record.tables['detail'].length; r++) { results.parent().append(results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1378.html">PAGE 1378</a></h6>
<p>} // Hide our boilerplate row (note that this doesn't really delete the row). results.hide(); html(value) Replaces the contents of the <body> of a section or Master Page by the supplied value. This function is only available in Control Scripts. See also: "section" on page 1395 and "masterpage" on page 1355. value A String that may contain HTML tags. Examples The following script loads a snippet based on the value of a field, and then replaces the content of a Print section with the snippet using html().</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1379.html">PAGE 1379</a></h6>
<p>template The template object represents the template with all its contexts and sections. It is used frequently in Control Scripts (see "Control Scripts" on page 885 and "Control Script API" on page 1351). It is retrieved via the merge object: merge.template (see "merge" on page 1405). Which contexts are available in the template can be queried using merge.template.contexts. To get access to a specific context, you have to specify the ContextType (see "ContextType" on page 1383).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1380.html">PAGE 1380</a></h6>
<p>var printSections = merge.template.contexts.PRINT.sections; printSections['Section EN'].enabled = false; printSections['Section FR'].enabled = false; if(record.fields.Language === 'FR'){ printSections['Section FR'].enabled = true; } else { printSections['Section EN'].enabled = true; } properties The properties object inside the template object (see "template" on the previous page) contains all default properties of the template file as well as any custom properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1381.html">PAGE 1381</a></h6>
<p>Field Type Description keywords String Semicolon-separated list of keywords modified Date Date and time on which the document was last saved Example This script stores a default property (author) and a custom property in variables. var author = merge.template.properties.author; var myProperty = merge.template.customProperties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1382.html">PAGE 1382</a></h6>
<p>// Enable the section background and specify that the PDF should be read // from a resource file rather than using a PDF DataMapper background merge.template.contexts.PRINT.sections['Policy'].background.source = BackgroundResource.RESOURCE_PDF; // Specify the path var resourceUrl = 'images/policy-' + record.fields.policy + '.pdf'; merge.template.contexts.PRINT.sections['Policy'].background.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1383.html">PAGE 1383</a></h6>
<p>Example The following Control Script selects different sections for Print output and for Email with the Print context attached to it. var printSections = merge.template.contexts.PRINT.sections; if(merge.channel === Channel.EMAIL){ printSections['Section 1'].enabled = false; printSections['Section 2'].enabled = true; } if(merge.channel === Channel.PRINT){ printSections['Section 1'].enabled = true; printSections['Section 2'].enabled = false; } ContextType ContextType is an enumeration for the context types.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1384.html">PAGE 1384</a></h6>
<p>var printSections = merge.template.contexts.PRINT.sections; printSections['Section EN'].enabled = false; printSections['Section FR'].enabled = false; if(record.fields.Language === 'FR'){ printSections['Section FR'].enabled = true; } else { printSections['Section EN'].enabled = true; } MediaPosition In a Control Script, the position is an enumeration for the position of background resources for a Print section. It is retrieved and set via background.position.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1385.html">PAGE 1385</a></h6>
<p>var activeSection = merge.template.contexts.PRINT.sections['Section 1']; activeSection.background.source = BackgroundResource.RESOURCE_PDF; activeSection.background.position = MediaPosition.FIT_TO_MEDIA; activeSection.background.url = "images/somepage.pdf"; Post Pagination Script API The table below lists the functions and objects that are only available in Post Pagination Scripts. Click through to the object to find a description and sample scripts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1386.html">PAGE 1386</a></h6>
<p>Object or function Usage page 1395). merge.pagination Used to get the total page count, sheet count and start/end page numbers for all sections in the Print context after pagination. See "Pagination" on page 1406. "PaginationInfo" on page 1388 This object contains essential information about one element in order to create a table of contents (see "Creating a Table Of Contents" on page 902). results."info()" on page 1393 A call to results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1387.html">PAGE 1387</a></h6>
<p>Field Type Description properties Properties Key-value pairs containing custom properties. context In a Control Script, the context object represents one context in the template. Which contexts are available in the template can be queried using merge.template.contexts. The context being merged can be queried using merge.context. Field Type Description sections Array Array of sections (see "section" on page 1395) inside a particular context defined in the template. Note: When using merge.context.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1388.html">PAGE 1388</a></h6>
<p>Example This script checks if the output channel is EMAIL and if the context to be merged is the Print context (which happens if the Print context is attached to an email). If this is the case, it includes and excludes certain Print sections from the output. if (channel == Channel.EMAIL) { if (merge.context.type == ContextType.PRINT) { merge.context.sections['Section 1'].enabled = false; merge.context.sections['Section 2'].enabled = false; merge.context.sections['Section 3'].</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1389.html">PAGE 1389</a></h6>
<p>In other words, page numbering continues from the start of the first section to the end of the last section in the group. (See "Configuring page numbers" on page 501 and "Control Script: Page numbering" on page 888.) The PaginationInfo object (as well as the info() function) is only available in Post Pagination Scripts (see "Post Pagination Scripts" on page 900).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1390.html">PAGE 1390</a></h6>
<p>If, for example, a script would have the selector p.onlyCanada, the script would apply to all paragraphs that have the class onlyCanada. (Classes can be defined in the Attributes pane at the right: select the element in the content and type the class(es) in the Class field.) The script could then use the results object to hide or show those paragraphs, depending on the value of the data field Country in the current record: if (record.fields["Country"] == "CANADA") { results.show(); } else { results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1391.html">PAGE 1391</a></h6>
<p>Function Description page 1298 "Examples" on page 1300 Inserts content at the end of each element in a set of HTML elements. "Examples" on page 1303 Change the given attribute of the element or set of HTML elements with the given value. " Examples" on page 1304 Inserts content before an element or before each element in a set of HTML elements. "Examples" on page 1306 Returns the immediate children of an HTML element.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1392.html">PAGE 1392</a></h6>
<p>Function Description page 1313 HTML elements. "Example" on page 1313 Returns true if the first element in this result set has the specified class. "height()" on page 1314 Gets or sets the outer height of an element, including padding and borders. "hide()" on page 1315 Hides the HTML element or set of HTML elements.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1393.html">PAGE 1393</a></h6>
<p>Function Description page 1321 document. "Examples" on page 1323 Removes the specified attribute from each element in this result set. "Examples" on page 1323 Removes the specified class from an element or from each element in a set of HTML elements. Has no effect if the class is not present. "Replace elements with a snippet" on page 1324 Replaces an HTML element or a set of HTML elements (with a snippet, for example). Returns the result set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1394.html">PAGE 1394</a></h6>
<p>This function can only be used in a Post Pagination Script ; see "Post Pagination Script API" on page 1385. For an example see: "Creating a Table Of Contents" on page 902. overflows() The overflows() method returns a boolean value indicating whether an HTML element overflows its box boundaries. This function could for instance be used in a design where content needs to flow separately from the main text flow, or where a new, full-page, multi-column box should be inserted when the current one overflows.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1395.html">PAGE 1395</a></h6>
<p>The following script selects three boxes that all have the class box (selector: .box). It loops over them, inserting as many products from an array as possible into the box. In fact, it inserts one too many and removes the last one before moving on to the next box. var products = ["Appetizer","Beans","Beef","Lettuce","Sprouts","Coconut","Juice"," Soup","Coriander","Cheese","Pasta","Sugar","Vinegar","Bread"]; var i = 0; results.each( function() { // Add elements to the box until it overflows. while ( ! this.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1396.html">PAGE 1396</a></h6>
<p>Fields Field Type Description "background" on page 1370 Background Print sections only. Used to set a PDF background on a Print section. See "Control Script: Setting a Print section's background" on page 893 and "BackgroundResource" on page 1381. enabled Boolean Enables or disables this section for output (see "Examples" on page 1399).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1397.html">PAGE 1397</a></h6>
<p>Field Type Description margins Margins Print sections only. Used to set the print margins of a section. You can set the bottom, left, right and top margin using a Measurement string; for example, "2in" sets a margin to two inches. minPages Number Minimum number of pages in the section. The default is 1. name String Used to get or set the name of the section. Note that section names must be unique and that sections cannot have an integer as its name.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1398.html">PAGE 1398</a></h6>
<p>Field Type Description password String Print sections only. Used to set the user password and owner password for a PDF attachment to the same value. See "Control Script: Securing PDF attachments" on page 898.* restartPageNumber Boolean Print sections only. Enables or disables a restart of the page numbering. When generating Print output this can be used to let page numbering continue over multiple sections.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1399.html">PAGE 1399</a></h6>
<p>Function Description "Examples" on page 1376 Clone this section. See "Dynamically adding sections (cloning)" on page 895. addAfter() Add a cloned section after this section. addBefore() Add a cloned section before this section. addHeader (key, value) Email sections only. Used to set custom email headers. The function expects a key and a value (both of type string). For examples, see "Adding custom ESP handling instructions" on page 1444.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1400.html">PAGE 1400</a></h6>
<p>Selecting different sections for Print output and Email PDF attachment This script selects a different Print section for output, depending on the output channel (Email or Print). var printSections = merge.template.contexts.PRINT.sections; if(merge.channel === Channel.EMAIL){ printSections['Section 1'].enabled = false; printSections['Section 2'].enabled = true; } if(merge.channel === Channel.PRINT){ printSections['Section 1'].enabled = true; printSections['Section 2'].</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1401.html">PAGE 1401</a></h6>
<p>merge.context.sections['Section 6'].enabled = true; merge.context.sections['Section 6'].part = "PDFAttach2"; } else if (merge.context.type == ContextType.WEB) { merge.context.sections['default Section'].enabled = false; // disable whatever is the default section merge.context.sections['Section A'].enabled = true; merge.context.sections['Section A'].part = "WebPartA"; merge.context.sections['Section B'].enabled = true; merge.context.sections['Section B'].</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1402.html">PAGE 1402</a></h6>
<p>Scaling to Media size var activeSection = merge.template.contexts.PRINT.sections['Section 1']; activeSection.background.source = BackgroundResource.RESOURCE_PDF; activeSection.background.position = MediaPosition.FIT_TO_MEDIA; activeSection.background.url = "images/somepage.pdf"; See also: "BackgroundResource" on page 1381, "MediaPosition" on page 1384 and "Control Script: Setting a Print section's background" on page 893.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1403.html">PAGE 1403</a></h6>
<p>function addPolicy(policy){ var resourceUrl = 'images/policy-' + policy + '.pdf'; var clone = printSections["Policy"].clone(); clone.name = "policy_" + policy; clone.background.url = resourceUrl; clone.enabled = true; printSections["Policy"].addAfter(clone); } margins The margins object is used to set a Print section or Master Page's margins in a Control Script (see "Control Scripts" on page 885 and "Control Script API" on page 1351).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1404.html">PAGE 1404</a></h6>
<p>Setting the header and footer of a Master Page var masterA = merge.template.masterpages["Master page A"]; masterA.margins.header = "2in"; masterA.margins.footer = "2in"; paginate() This method of the section object (see "section" on page 1395) triggers pagination of the current section. The pagination process re-establishes page boundaries, updates page numbers and page counts, and reapplies Master Pages.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1405.html">PAGE 1405</a></h6>
<p>Field Type Description pageCount Number The total number of pages in this section. pageEnd Number The index (1-based) of the last page in this section. pageStart Number The index (1-based) of the first page in this section. sheetCount Number The total number of sheets in this section. sheetEnd Number The index (1-based) of the last sheet in this section. sheetStart Number The index (1-based) of the first sheet in this section.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1406.html">PAGE 1406</a></h6>
<p>Field Type Description merged. pagination "Pagination" below Contains the total page count and sheet count of all sections in the Print context after pagination. "section" on page 1395 Section In Standard Scripts, this object defines the section that is being merged. Note! In Control Scripts, merge.section is only available when the output channel is WEB. To make sure that it is defined, use the following statement: if (merge.channel == Channel.WEB && merge.context.type == ContextType.WEB) { ... }.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1407.html">PAGE 1407</a></h6>
<p>For information about where an element is located and the counts of pages and sheets in a page bundle - a group of sections in which the page numbering continues - use "info()" on page 1393. For the total page count, sheet count and start/end page numbers of a single section, use the section object's "Pagination" on page 1404 (see also: "section" on page 1395). Field Type Description pageCount Number The total number of pages in all Print sections together.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1408.html">PAGE 1408</a></h6>
<p>Generating output When merged with a record set, the templates made in the Designer can generate three types of output: Print , Email and Web. You can print and email from the Designer, but if you want to do this in an automated process, or if you want to produce web pages that are not attached to an email, you need to build Workflow processes with OL Connect tasks. For more information, see: "Workflow processes in OL Connect projects" on page 213.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1409.html">PAGE 1409</a></h6>
<p>Fax output It is possible to generate Fax output from PlanetPress Connect through a Print output job creating PDF/VT output, with some additional Workflow steps. See "Generating Fax output" on page 1435 for details. Email output The Email context outputs HTML email with embedded formatting to an email client through the use of an email server. The HTML generated by this context is meant to be compatible with as many clients and as many devices as possible.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1410.html">PAGE 1410</a></h6>
<p>To learn how to attach other files, see "Email attachments" on page 537. Web output The Web context outputs an HTML web page that contains the HTML text and all the resources necessary to display it. Web output can be generated in two different ways: it can be attached to an Email template when generating Email output (see above), or it can be generated using Workflow; see "Generating Web output" on page 1448.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1411.html">PAGE 1411</a></h6>
<p>Note Proof Print generates output directly from the Designer, without using the Print Service. A Proof Print run won't impact upon production printing l File > Print... allows the following printing options: l l l Using the Default output settings. For more details, see "Print Using Standard Print Output Settings" on page 1413 Using the same settings that were last used to produce printed output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1412.html">PAGE 1412</a></h6>
<p>documents and splitting the print jobs into smaller print jobs, as well as the more standard selection of printing options, such as binding, OMR markings and the like. See "Print Presets" on page 1415 for more details. Generating Print output from Workflow If you want to generate Print output via an automated process, this means that you have to design a Print process in the Workflow configuration tool.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1413.html">PAGE 1413</a></h6>
<p>l l l l Duplex printing. Duplex printing has to be enabled for a Print section, in order to print that section on both sides of the paper. The same applies to Mixplex printing. See "Enabling double-sided printing (Duplex, Mixplex)" on page 495. Finishing. The Print context , as well as each of the Print sections, can have its own Finishing settings. In printing, Finishing is the way pages are bound together after they are printed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1414.html">PAGE 1414</a></h6>
<p>the Last Used printer settings or by using previously created Printing Presets. To learn how to create Printing Presets please see Job Creation Presets and Output Creation Presets. l Configuration Selection Group: l l l Output Creation: Leave the selection at the Default or use the drop-down to select an existing Output Creation Preset. Use the Gear button to edit the currently selected Preset or to reload the list of Presets from the system.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1415.html">PAGE 1415</a></h6>
<p>l l Copies: Enter the number of output copies you want. Collate: When printing multiple copies you can check this checkbox to have the record copies printed together. For example in a three record job the records would print out as 1-1-2-2-3-3, rather than 1-2-3-1-2-3. Wizard navigation buttons l Advanced button: Click to open the "Print Using Advanced Printer Wizard " on page 1422where you can manually change the printing options.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1416.html">PAGE 1416</a></h6>
<p>process. l l A Job Creation Preset is used by the Connect Server after a template and data have been merged. Based on the settings in a Job Creation Preset the server can filter, sort, and group the print content items, add meta data and make finishing settings. The resulting print job is then handed to the Weaver engine for output creation (see also: "Connect: a peek under the hood" on page 161). This engine generates the final print output file, or files.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1417.html">PAGE 1417</a></h6>
<p>Job Creation Presets A Job Creation Preset is a file that contains settings for creating a print job. It is used after a template has been merged with data, but before the actual print output file is produced. Merging a template with data results in a set of print content items. Based on the settings in a Job Creation Preset, the Connect server can take a number of actions on a set of print content items. The actions are described below. Select File > Print Presets > Job Creation Settings...</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1418.html">PAGE 1418</a></h6>
<p>The remaining items can be sorted, either by the Connect Server, based on data fields, or by some external sorting software (see "Sorting options" on page 1166). Tip External sorting benefits considerably from runtime parameters, defined in the Job Creation Preset (see "Runtime Parameter Options" on page 1081). Grouping While creating a print job, the Connect Server can group Print content items into Jobs, Job Segments and Document Sets (see "Grouping options" on page 1161).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1419.html">PAGE 1419</a></h6>
<p>Override finishing options The Print context and Print sections can have their own finishing options (see "Print settings in the Print context and sections" on page 484.) A template could be setup with a glue binding, for example. When the printer doesn't support the chosen finishing options you could override the finishing options, and use staple binding, for instance.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1420.html">PAGE 1420</a></h6>
<p>Printer model and output type An Output Creation Preset specifies the type of printer the output should be suitable for, and determines where that output should then be sent: to a folder, LPR queue or Windows printer (see "Print options" on page 1174). Printer definitions A printer model and its capabilities for Connect are defined in a printer model definition file (.OL-printerdef). Connect comes with a number of such files.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1421.html">PAGE 1421</a></h6>
<p>Imposition An Output Creation Preset can tell a printer to print multiple pages on a single sheet (Simplex, or Duplex). This is called Imposition, also known as N-Up printing. The two Imposition types are Cut & Stack and Stack by Column (see "Imposition options" on page 1181). With each Imposition type there is a wide range of options to control the exact layout of the output: the number of pages that go on one sheet, their order, the way they are stacked, the stack depth, the margins, markings, etc.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1422.html">PAGE 1422</a></h6>
<p>possible when you use Imposition. With Booklet Imposition, however, the output can be separated on all levels. Additional content Via an Output Creation Preset, content - Text, Images, Barcodes and OMR Marks - can be added to the output at the time of output creation. The additional content can be either static or variable (see "Page breakdown" on page 1195).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1423.html">PAGE 1423</a></h6>
<p>The Wizard can be used to generate once-off print runs (either entirely from scratch, or based upon selected pre-existing Presets). Note: These print runs cannot be saved as presets and can only be replicated in the following print run, using the Last Used option. The output settings are determined by selections made throughout the Wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1424.html">PAGE 1424</a></h6>
<p>have been customized specifically for your printer(s). 2. Select Create Definition from PPD to add a customizable PostScript Printer Model using the printer manufacturer provided PostScript Printer Definition (PPD) file. This launches the PPD Import Wizard. In the Wizard, do the following. l l Select the printer's PPD file. Once selected details about that specific printer will load in the information box, for confirmation. NOTE: The PPD information extraction and processing can take some seconds.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1425.html">PAGE 1425</a></h6>
<p>Print Wizard, then click OK. Splitting printing into more than one file By default, when Connect saves the print output spool file to a directory, it creates one spool file that contains all the generated documents (one document per data record). It is, however, possible to output one spool file per document, or to create groups of documents and store those in separate spool files.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1426.html">PAGE 1426</a></h6>
<p>province. Here's how to do that: 1. First, define meta data at the intended separation level. This is done in the Job Creation Preset (see "Include meta data" on page 1418). 2. Then, in the Output Creation Preset, use those meta data in the Job Output Mask (see "Output options" on page 1176). They are inserted into the file name as variables. For example: ${segment.metadata.State} refers to a meta data tag State defined on the job segment level.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1427.html">PAGE 1427</a></h6>
<p>This is done by setting a Job Info variable in the Workflow configuration see Job Info variables in the Workflow Online Help) and then referencing it in the "Print options" on page 1174 fields via the variable @automation.JobInfoX@ (where "X" is the number of the Job Info variable). If the output is to be separated into multiple files, some Output content variables can also be used as Output file variables, depending on the level of separation (see "Content variables" on page 1430).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1428.html">PAGE 1428</a></h6>
<p>${template.base} expands to My-Invoices-EN . ${template.name} Returns the name of the template file without the path. Example If the template file is C:\Data\My-Invoices-EN.OL-template, then ${template.name} expands to My-Invoices-EN.OL-template. Note that ${template.name} still includes the extension of the template file (.OL-template in the example above). ${template.nr} An automatic sequence number belonging to the current output file.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1429.html">PAGE 1429</a></h6>
<p>Example When printing to PDF, ${file} could expand to merged.5852941188491153960_0001.pdf. ${file.base} Expands to a unique, internally generated file name, without a trailing dot or extension. ${file.ext} The extension that corresponds to the chosen output format, for example pdf or ps. Note that ${file.ext} does not include a leading dot. ${file.nr} An automatic sequence number belonging to the current output file.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1430.html">PAGE 1430</a></h6>
<p>${job.base} or ${job.name} Returns the name of the applied Job Creation Preset without any extension. Expands to Untitled if no Job Creation Preset was used. ${job.nr} An automatic sequence number belonging to the current output file. It is automatically incremented for each new output file that gets created. Note, that multiple output files are created, for example, when output separation has been selected for output creation. It is possible to format the number using a pattern and locale.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1431.html">PAGE 1431</a></h6>
<p>System ${system.time} Displays the current system data and/or time. Can be formatted using the "Formatting date and number values " on page 1434, as seen below. Page ${page.back} True when the page is on the back of the sheet. ${page.front} Boolean indicating whether the page is on the front of the sheet. ${page.height} The page's height (in points). ${page.landscape} True when the page's orientation is landscape. ${page.portrait} True when the page's orientation is portrait. ${page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1432.html">PAGE 1432</a></h6>
<p>${sheet.height} The sheet's height (in points). ${sheet.pageDevice} Array specifying the sheet's Type (e.g. Plain), Weight (e.g. 83), Color (e.g. yellow), Width (in points), Height (in points) and Tumble (e.g. false). ${sheet.nr} or ${sheet.sequence.document} Sheet number within the document. ${sheet.sectionName} Name of the Template Section that the Sheet belongs to. ${sheet.sequence.set} Sheet number within the document set. ${sheet.sequence.segment} Sheet number within the job segment.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1433.html">PAGE 1433</a></h6>
<p>${document.count.sheets} Total number of sheets in the document. ${document.nr} or ${document.sequence.set} Document number within the document set. ${document.sequence.segment} Document number within the job segment. ${document.sequence.job} Document number within the job. Set ${set.metadata. propertyname} or ${set.metadata ['propertyname']} Value of a meta data property of the Document Set.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1434.html">PAGE 1434</a></h6>
<p>propertyname} or ${segment.metadata ['propertyname']} The propertyname must have been defined as a Tag Name on the Job Segement Tags tab of the "Meta Data options" on page 1169 page in the Advanced Print Wizard or Job Creation Preset. Note: this is only available if Separation based on Job Segment or Split At Exactly n Sheets has been selected on the "Separation options" on page 1193 page in the Advanced Print Wizard or Output Creation Preset. ${segment.count.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1435.html">PAGE 1435</a></h6>
<p>${ expression,pattern,locale } Apply pattern with the specified country locale ${expression,,locale} Apply a default format with the specified country locale ${system.time, "dd MMMM yyyy", fr} ${system.time,,fr} > 19 décembre 2017 19 décembre 2017 12:30:55 It is possible to enclose the values of the pattern and locale in single or double quotes. This is required for including whitespace in a pattern, or when the ${expression} would otherwise be ambiguous.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1436.html">PAGE 1436</a></h6>
<p>l l FaxNumber: The phone number where the fax will be sent. Often part of the data. FaxInfo: The description of the fax in both the PlanetPressFax dialog box and the fax log file. Output Preset Configuration The following settings must be used in the Output Preset: l In the Print Options, a PDF type should be selected, such as Generic PDF.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1437.html">PAGE 1437</a></h6>
<p>Job Creation Preset configuration For email output, the following meta data fields must be added to the "Meta Data options" on page 1169 page in the Job Creation Preset: l l l l l ImageSendTo: Add to have PlanetPress Image use the specified field as the E-mail address to which to send the PDF file. ImageSendCc: Add to have PlanetPress Image use the specified field as the E-mail address to which to send the PDF file as a carbon copy (CC).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1438.html">PAGE 1438</a></h6>
<p>l The four regular Connect tasks to generate print output: l Execute Data Mapping l Create Print Content l Create Job using the above Job Creation Preset l Create Output using the above Output Creation Preset. The task's Output Management must be set to be Through Workflow. For more information, see "Print processes with OL Connect tasks" on page 220. l The PlanetPress Image connector task set to Passthrough (the first "Document" on the list).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1439.html">PAGE 1439</a></h6>
<p>For more information see "Email attachments" on page 537. Before generating Email output l l l Decide on the use of an Email Service Provider; see "Using an ESP with PlanetPress Connect" on page 1442. Make sure that a data set is loaded, that any necessary files, such as images and attachments, are in place, and that the correct settings are selected (see below). You may want to rasterize certain elements, to ensure that most email clients would actually see the output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1440.html">PAGE 1440</a></h6>
<p>record is skipped automatically when generating email output. Note When you send a test email, the Email To Script will not be used; instead, the email will be sent to the address that you specify in the Send Test Email dialog. l l l l l The sender(s), recipient(s) and the subject can be set using Script Wizards; see "Email header settings" on page 530. Default SMTP settings can be set in the preferences; see "Email header settings" on page 530.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1441.html">PAGE 1441</a></h6>
<p>configuration. The output is not limited to the number of records shown in the Data Model pane (which is one of the settings in the DataMapper). 3. On the File menu, click Send Email or Send Test Email. In the dialog that appears you can, among other things, attach the Print context or the Web context to the email. See "Send (Test) Email" on page 991 for a description of all the options. Finally, click OK.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1442.html">PAGE 1442</a></h6>
<p>Note If the input data is JSON, a data mapping configuration isn't needed. 2. Create a process in PlanetPress Workflow. See: "Email processes with OL Connect tasks" on page 218. Aborting content creation You may want the content creation process to be aborted in certain situations; for example, when a template script fails to load remote content. To abort the content creation process, you may raise a fatal error from within a script in the template; see "fatalError(message)" on page 1329.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1443.html">PAGE 1443</a></h6>
<p>l l l l ESPs ensure a high deliverability, as most ESPs are whitelisted or approved by ISPs (Internet Service Providers) as legitimate email delivery service. So they help you to avoid having mail detected as spam. ESPs provide comprehensive tracking options to measure open rates and they log which links were clicked and by who. Typically this information is available via an online dashboard. Most ESPs provide Bounce Management options.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1444.html">PAGE 1444</a></h6>
<p>Sending an email with an ESP To send an email or test email with the use of an ESP, start generating the email as usual (see "Generating Email output" on page 1438). In the Send (Test) Email dialog, pay attention to the following settings: l l In the Outgoing mail settings area, select the preset for your ESP in the Presets dropdown. In the Password box, type the password provided by the ESP. Note The ESP might also have a test function you can use. Check the options of your ESP.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1445.html">PAGE 1445</a></h6>
<p>Documentation: https://sendgrid.com/docs/API_Reference/SMTP_API/using_the_smtp_ api.html. (Use the SMTP API; the Connect Server sends SMTP email). Add a name meta tag with the value X-SMTPAPI and set its content to the required JSON string (for example: "' category': ['invoices']"). You can make this setting in the Email section properties (see "Meta information" on page 535). Alternatively you could write a Control Script, for example: var headerObj = { "category": ["invoices"] }; merge.context.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1446.html">PAGE 1446</a></h6>
<p>MailGun Dashboard: https://mailgun.com/cp/stats Documentation: https://documentation.mailgun.com/api-sending.html#sending Add a name meta tag with the value X-Mailgun-Tag and set its content (for example: invoices). You can make this setting in the Email section properties (see "Meta information" on page 535). Alternatively you could write a Control Script, for example: merge.context.sections["Content"].</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1447.html">PAGE 1447</a></h6>
<p>MailJet Dashboard: https://app.mailjet.com/dashboard Documentation: https://app.mailjet.com/docs/emails_headers To assign a campaign, set a meta tag of the type name with the value X-Mailjet-Campaign and set its content to the name of the campaign (for example: invoices). You can make this setting in the Email section properties (see "Meta information" on page 535). Alternatively you could write a Control Script, for example: merge.context.sections["Content"].</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1448.html">PAGE 1448</a></h6>
<p>verified via the respective campaign stats page in the Mailjet dashboard. There is no need to pre-create the campaign: adding it to the email header via a Control Script autogenerates the campaign. To view the campaign, login to Mailjet and choose: Campaigns > All. Generating Web output The Web context outputs one HTML web page. In addition to the HTML text it contains either the resources or references to the resources necessary to display it.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1449.html">PAGE 1449</a></h6>
<p>If you have an open data mapping configuration and open another data file, the current data mapping configuration will try to retrieve data from the file or database using its own Data Model and extraction logic. Note When generating output with just an open data mapping configuration, the template is merged with the complete sample data file that is part of the data mapping configuration.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1450.html">PAGE 1450</a></h6>
<p>l l Which Web section is the 'default'; see "Setting a default Web page for output" on page 551. When generating Web output, if there are multiple Web sections, only one of them can be merged with each record. The title, shortcut icon and meta tags appearing in the web page's header. See "Setting the title, meta data and a shortcut icon" on page 552 Attaching Web output to an Email template To attach the Web context to Email output: 1. Open a template with a Web context and an Email context. 2.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1451.html">PAGE 1451</a></h6>
<p>Generating Web output from Workflow Generating Web output from Workflow requires you to send a template with a Web context to Workflow; see "Sending files to Workflow" on page 457. Next, you will have to create a process in Workflow that serves one or more web pages; see "Web processes with OL Connect tasks" on page 222.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1452.html">PAGE 1452</a></h6>
<p>Optimizing a template This topic describes some ways to optimize a template in order to speed up the output process. However, the template itself is not the only factor to be taken into account. The server configuration and hardware configuration have an influence on the output speed as well. For advice on server configuration and hardware configuration, see "Performance considerations" on page 34. Scripts In the process of output generation, the execution of scripts may take up more time than necessary.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1453.html">PAGE 1453</a></h6>
<p>Images l l Make sure to use optimized graphic resources. For instance, avoid using images with transparency where no transparency is needed. When a template that contains lots of images is merged with a large record set, the many file requests may slow down the process of output generation. One solution is to combine the images into a single image file (an 'image sprite') and display the part that holds the image. This reduces the number of file requests and can improve the output speed significantly.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1454.html">PAGE 1454</a></h6>
<p>l Dynamically added images are loaded in a script. To retrieve one page from a PDF file in a script, add the page parameter to the file path and set that as the source of the image. Here is an example (assuming that the page number is stored in a variable pageNumber): var imageStr = ""; var imagePath = "file:///C:/image-collection.pdf?page=" + pageNumber; imageStr += '<img src="' + imagePath + '">'; results.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1455.html">PAGE 1455</a></h6>
<p>2019.1 to first update their OL Connect License. A dialog box appears as part of the Connect upgrade process requesting you to do this. It is heavily recommended that you first update the OL Update Client, as version 1.2.40 of the Update Client can update your OL License to the required version, then install Connect 2019.2. For further details on how to upgrade the Update Client and update your Connect License see the Update Client 1.2.40 Upgrade Guide.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1456.html">PAGE 1456</a></h6>
<p>Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 2019.2 and PlanetPress Workflow 2019.2, as well as some important installation information. Installing PlanetPress Connect 2019.2 and PlanetPress Workflow 2019.2 l l l PlanetPress Connect is released as a 64 Bit version only (with the exception of the Workflow, Fax, Search and Imaging modules).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1457.html">PAGE 1457</a></h6>
<p>OL Connect 2019.2 Enhancements Windows Server 2019 now officially supported As of PlanetPress Connect 2019.2, Connect is now officially supported under Windows Server 2019. (SHARED-69995) Performance Scheduling settings simplified and improved Not only have the Performance Scheduling options been greatly simplified in Connect 2019.2, but the installer now dynamically sets the values such that fresh installations should perform a whole lot better out of the box.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1458.html">PAGE 1458</a></h6>
<p>We have also introduced Performance setting presets. Each preset caters for a different use case scenario. This vastly simplifies optimizing systems for the included scenarios. Out of the box, OL Connect dynamically matches the setup of the engines with the hardware it is running on, typically giving better performance after a fresh installation. Only users who have a mixed workload with parallel running tasks will need to go beyond choosing a preset.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1459.html">PAGE 1459</a></h6>
<p>Saving Connect files for different versions You can now save Connect templates and Datamapper configuration files in previous Connect version formats. (SHARED-71187) Improved PDF Signing We have overhauled OL Connect’s functionality for digitally signing PDFs. Amongst other improvements, Connect now supports signing certificates on secure devices such as USB tokens, and HSM’s. This enables applying digital signatures for use cases where regulations require secure storage of the certificate.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1460.html">PAGE 1460</a></h6>
<p>The PDF signing improvements include: l Support hardware security devices (USB tokens, smart cards, and Hardware Security Modules) for digitally signing a PDF. The settings for this can be found in the Preferences dialog. l Storing PDF signing passwords encrypted in output preset files. l More reliable handling of time stamp server requests and responses. l Can now add a timestamp to all types of digital signatures. l Support for invisible signatures.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1461.html">PAGE 1461</a></h6>
<p>l Improved default performance, for most users, courtesy of simplified and improved performance settings, and better initial assignment of Engines by the Connect installer. Installer Improvements l l l Issues with license importations have been fixed. (SHARED-67735) The Microsoft Access Database Engine has been updated to version 2016 (ACE 16.0) as the previously used engine (2010) is scheduled for end-of-life in 2020.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1462.html">PAGE 1462</a></h6>
<p>Barcode Improvements l Added support for the Royal Mail Mailmark 4-State C and Mailmark 4-State L barcodes. (SHARED-63467/69719) l Several barcode names have been changed to better match how they are referred to in industry.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1463.html">PAGE 1463</a></h6>
<p>Connect 2019.2 Designer Improvements Import resources from other Connect jobs Introduced an option to import resources (such as scripts and snippets) and data models from other Connect template files. This makes sharing existing Connect resources much easier.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1464.html">PAGE 1464</a></h6>
<p>Simplified use of dynamic background images A new scripting wizard has been introduced, simplifying creation of documents with dynamic background images. These images could be stored in the template, on a local folder on disk or remotely on a web server. (SHARED-67948/71096) Improved white-space behaviour Designer adds an empty paragraph to each HTML editor, to allow easy (keyboard) editing.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1465.html">PAGE 1465</a></h6>
<p>Scripting Improvements l l l l l When a master page editor is active in the Designer, the Post Pagination folder in the Designer Scripts panel is now decorated with an icon and a tooltip to clarify that post pagination scripts are not active in a master page editor. (SHARED-68543) Scripts can now differentiate between master pages and sections through an attribute selector. (SHARED-69811) Matches from cross-section queries are now highlighted when the mouse is hovering over a post pagination script.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1466.html">PAGE 1466</a></h6>
<p>l Pressing Ctrl+F in the script debugger now starts an "Incremental Find" operation. (SHARED-70147) l l Fixed an issue whereby custom expressions were not always refreshed when stepping through the code. (SHARED-71276) Some cosmetic improvements made in the scripts overview within script debugger. (SHARED-72034) General Designer Improvements l l l l l l To prevent issues it is no longer possible to replace absolute positioned direct child elements with inline elements in the body of Master Pages.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1467.html">PAGE 1467</a></h6>
<p>l The Send to Workflow and Package dialogs will now only automatically add the latest job and output preset files when there is a template open with a print context. And only if those preset files where created or modified in the current session of the designer. (SHARED-71361) l l Saving a SASS partial file now auto compiles root level .scss files. (SHARED-72224) Modern, Roman and Script fonts are no longer available in the Designer Font ComboBox since these fonts are no longer supported.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1468.html">PAGE 1468</a></h6>
<p>Connect 2019.2 DataMapping Improvements Added option to "Stop data mapping" New “Stop data mapping” option added to the Action Step to stop data processing at the specific record where the selected condition is met. As the data mapping operation then no longer needs to examine any further records, skipping those records can considerably improve performance. (SHARED-70320) General DataMapper Improvements l l Improved field selection for PDF split fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1469.html">PAGE 1469</a></h6>
<p>l Added a toolbar button to send the currently opened DataMapper configuration to Workflow server. (SHARED-70561) l Improved Tab navigation in DataMapper workflow view. (SHARED-70738) l You can now rename DataMapper fields directly. (SHARED-70940) l Boundary Script changes now activate the 'Save' button in DataMapper. (SHARED-72471) Connect 2019.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1470.html">PAGE 1470</a></h6>
<p>Page 1470</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1471.html">PAGE 1471</a></h6>
<p>They can also be used as Meta Data fields, or in External Sorting. The fields can be alphanumeric, numeric, Boolean, or even dates. You will also be able to pass runtime parameters to the Connect Workflow Job Creation and All In One plugins.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1472.html">PAGE 1472</a></h6>
<p>Add customized PostScript commands to Dynamic PPD PostScript output Added support for customized PostScript commands in Dynamic PPD PostScript printer output. The commands can include metadata values, so dynamic runtime information can be incorporated within the commands. (SHARED-72170) Added bin selection to PCL output Added support for bin selection in certain PCL printer definitions that support bins.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1473.html">PAGE 1473</a></h6>
<p>Print Output Improvements l l When using a PDF file with a specific combination of page elements as background in the template ("use PDF from datamapper input as section background") and creating PostScript output, it was possible that some page elements could get positioned incorrectly. This has been fixed. (SHARED-68080) Fixed potential PDF/A or PDF/X compliance issue when outputting multiple channels or both variants simultaneously (as some custom OL Enhance workflows do).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1474.html">PAGE 1474</a></h6>
<p>l PPML: Tray options now available for PPML print output. (SHARED-69314) l Reduced memory usage requirements for large impositioned jobs. (SHARED-71177) l l Modern, Roman and Script fonts have been removed from the additional content font combo boxes since these fonts are no longer supported. (SHARED-72464) Ensured that PDF pass through is not active when the output PDF type is not standard PDF.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1475.html">PAGE 1475</a></h6>
<p>Email Output Improvements New Workflow Email plugins Several new email related Workflow plugins have been created to improve the email sending performance by simplifying the integration with Email Service Providers (ESP). See "New email plugins" on page 1477 section for further details. General Email improvements l l Improved the scripting API for email headers. Connect now supports multiple headers with the same key.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1476.html">PAGE 1476</a></h6>
<p>General Output Improvements l Improved error handling when loading a template during output generation. (SHARED67730) l l TrueType "OS/2" tables in embedded fonts are now passed through as-is, and the output engine will no longer abort if it does not recognize them (for example, a newer version of the format). (SHARED-69378) Fixed a problem with simulating font style (generating styled fonts).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1477.html">PAGE 1477</a></h6>
<p>Workflow 2019.2 Improvements New email plugins Several new email related Workflow plugins have been created to improve the email sending performance by simplifying integration with external Email Service Providers (ESP). The original Create Email Content renders email messages and sends these over SMTP in a single run. This limits use to the slower SMTP protocol, which becomes a bottleneck when larger batches are processed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1478.html">PAGE 1478</a></h6>
<p>With Connect 2019.2 we also introduce connectors for the Email Service Providers SendGrid and MailJet, to facilitate fast bulk processing. (SHARED-71120/71123) These new connector plugins can be used to send pre-rendered email content (created by the new Render Email Content plugin) to either SendGrid or MailJet for bulk processing. The plugins will be made available via http://help.objectiflune.com.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1479.html">PAGE 1479</a></h6>
<p>These stand alone plugins will be available from http://help.objectiflune.com/en/#ppc-plugins. New PDF to Bitmap plugin A new PDF to Bitmap plugin provides functionality for converting page(s) of a PDF to either JPG or PNG image format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1480.html">PAGE 1480</a></h6>
<p>Workflow display improvements Process branches and conditions can now be collapsed and expanded to allow a better overall view. (SHARED-63520) CTRL-A now available The CTRL-A (i.e. Select All) keyboard shortcut has been implemented in all edit/memo controls in Workflow, making it easier to select the entire contents of a field.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1481.html">PAGE 1481</a></h6>
<p>Passing runtime parameters to Connect plugins It is now possible to pass runtime parameters to the All In One plugin's Job Creation panel as well as to the Job Creation plugin itself.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1482.html">PAGE 1482</a></h6>
<p>General Workflow Improvements l l Create Email Content now supports adding both the sender name and sender email address by expressing the email/name combination as "My Name <myemail@myhost.com>" in the Sender Address field. (SHARED-69901) Improved error reporting, as the actual error information is now included as part of the Error process. Whenever an error occurs in a plugin in Debug mode, the error message now appears in the Debug Information panel of the UI under the error.errorlog variable.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1483.html">PAGE 1483</a></h6>
<p>Known Issues As of PlanetPress Connect 2018.1 the Known Issues have moved from the Release Notes to the Connect online Help. They can be found here. Previous Releases License Update Required for Upgrade to Connect 2019.1 From OL Connect 2019.1 onwards, only customers with a current OL Care subscription will be able to update Connect. Every Connect license will now contain an end date that represents the last day of OL Care coverage for each customer.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1484.html">PAGE 1484</a></h6>
<p>For further details on how to upgrade the Update Client and update your Connect License see the Update Client 1.2.40 Upgrade Guide. If issues arise, or if you need to renew your OL Care subscription, please contact your local Customer Care group. Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 2019.1 and PlanetPress Workflow 2019.2, as well as some important installation information. Installing PlanetPress Connect 2019.2 and PlanetPress Workflow 2019.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1485.html">PAGE 1485</a></h6>
<p>Reduced Memory Version (not recommended for production) It is possible to install OL Connect on a machine with a minimum of 2 GB of RAM. The Connect Designer will automatically detect whether it has been installed on a machine with less than 4 GB of RAM and default to only using one internal Weaver and one internal merge engine on that system. The Server will also run using internal engines.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1486.html">PAGE 1486</a></h6>
<p>OL Connect 2019.1 Enhancements Script Debugger Connect 2019.1 introduces a new Script Debugger. This provides options to step through code (i.e. execute the code line by line) and to add breakpoints to pause execution at strategic points, as well as displaying the current state of variables, both local and global. (SHARED-66671) The Script Debugger simulates an output run for all sections in the current context, including section clones.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1487.html">PAGE 1487</a></h6>
<p>These Project Wizards create building blocks to kick-start your projects as well as providing samples that explain Connect concepts and capabilities. A Project Wizard generates a pre-configured Workflow configuration and associated Connect Templates, Data Mapper configuration, Job Presets and Output Presets. The Project Wizard creates a folder containing all the resources along with a workspace folder that is ready to be modified, tested and deployed. Connect 2019.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1488.html">PAGE 1488</a></h6>
<p>l Capture OnTheGo Timesheets, a set of Workflow processes to deploy and serve COTG Timesheet forms. Additional processes capture the submitted data and illustrate how this information can be stored in JSON, XML and PDF formats. The PDF is generated by merging the data with a Connect template. These new projects are also available from the Welcome screen.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1489.html">PAGE 1489</a></h6>
<p>Improved Data Model view l Grouping/Ungrouping items PlanetPress Connect 2019.1 introduces the ability to add and modify logical Groups within the Data Model view. This enhancement doesn't impact on the database structure itself, but it does allow you to manipulate the way the data is presented within Connect . Groups are a purely logical construct and can be nested within other groups, and expanded or contracted as desired.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1490.html">PAGE 1490</a></h6>
<p>l Filtering the view Data Model pane now allows filtering the displayed database items via a new Filter box. This narrows the list of displayed items to just those tables, groups or fields whose name contains the typed string.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1491.html">PAGE 1491</a></h6>
<p>New Translation feature A multilingual Connect template can handle content and static text elements in more than one language. Traditionally this was done through creating a separate Template or Section for each of the language variants. A new Translation feature in Connect 2019.1 simplifies this process and introduces options to export translation strings in a standardized file format.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1492.html">PAGE 1492</a></h6>
<p>Installer Improvements l l l You can now modify your installation choices, when upgrading Connect from an earlier version. (SHARED-67956) The Database Connection Check now displays a progress monitor, which is useful when attempting to connect to remote databases. (SHARED-23309) Now able to connect to a non-Connect-installed instance of MySQL with an encrypted connection using SSL for main Connect application database interactions.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1493.html">PAGE 1493</a></h6>
<p>Connect 2019.1 Designer Updates Scripting Improvements l l l Regular JavaScript resources can now have Defer and Async properties set, as was already the case for remote JavaScript resources. (SHARED-67235) Scripts created by the Make Conditional option previously just used the ID and class of an element by default for the selector, but this can now be changed as desired from within the Edit Script dialog.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1494.html">PAGE 1494</a></h6>
<p>Barcode Improvements l l Added support for the Japan Post barcode. (SHARED-59708 / 59711) Most barcodes except the 4 state barcodes (Australia Post, Japan Post, Kix and Royal Mail 4 State) and One Code now have an option to enable\disable Tilde Processing. (SHARED-68565) When this option is disabled, notations like "~d009" will no longer add a tab character to the barcode value. Rather the literal value "~d009" will be encoded.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1495.html">PAGE 1495</a></h6>
<p>General Designer Improvements and Fixes l l l l Added ability to copy the location of snippets and images, so the locations can be pasted into scripts to simplify using those resources in scripts. (SHARED-33976) We've added filter options to the Package and Send To Worklow dialogs, to make it easier to locate the correct presets. (SHARED-68033) The Package and Send To Worklow dialogs now automatically add the last modified Output Creation and Job Creation configurations to the package.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1496.html">PAGE 1496</a></h6>
<p>l l Added a Shared Content Editing option to the View menu with which you can disable/enable the editing of Shared Content in the template. (SHARED-60983) Default section clone names weren't always made unique when creating multiple clones. This could lead to lost clones, when naming conflicts arose. This issue has now been fixed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1497.html">PAGE 1497</a></h6>
<p>Connect 2019.1 DataMapping Updates Stepping Improvements In complex Data Mapping configurations, the Steps pane can contain hundreds of steps. This made the interface sluggish when the navigating from step to step. Accordingly, the interface has been modified to redraw much more quickly than it used to. Visually speaking, the dotted lines that used to connect each Step have been reworked to now use full lines that are drawn directly onto the display.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1498.html">PAGE 1498</a></h6>
<p>The results are displayed next to the Find box, and one can click on the Next / Previous match buttons to immediately jump to the next/previous step within the list of matches. XML Performance Improvements The XML Viewer has been completely overhauled resulting in a much more responsive interface. It is now possible to scroll through extremely large records (i.e. thousands of elements) as easily as one would a text file. But the changes are not limited to the interface.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1499.html">PAGE 1499</a></h6>
<p>XML boundaries XML boundaries now can be split on variable element names. This solution adds the ability to specify an XPATH statement as the boundary, instead of a fixed element name. The XPATH statement supports dynamic values, allowing the boundaries to adjust dynamically to values passed by Workflow. (SHARED-65739) General DataMapping Improvements l l l l Improved compatibility with third-party PDF files.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1500.html">PAGE 1500</a></h6>
<p>l Enhanced print job summary in Server logs. A summary of print jobs will now be displayed in the Server logs when either printing to the Server from Designer, using an All-In-One plug-in from Workflow, or by submitting a request to the All-In-One Process. (SHARED-66793) l l l Improved page breaking. This might impact upon some existing templates. (SHARED-68453) Extended the range of allowable Media weights. Media weight now ranges from 25 to 1000 gsm.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1501.html">PAGE 1501</a></h6>
<p>l PDF output l l Added support for e-Invoice PDF (PDF/A-3b) output. (SHARED-68209) Redesigned the Digital Signatures section of the PDF output options to use a tree display which better reflects the structure of digital signatures. (SHARED-68364) l Added support for internal hyperlinks within a PDF document. (SHARED-52674) l XMP data now output in Canonical format for PDF/VT output. (SHARED-68483) l It's now possible to control the metadata in PDF output.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1502.html">PAGE 1502</a></h6>
<p>General Output Improvements l l l The PDF Preview function and PDF attachments created for Email messages now have the same producer name as standard Connect PDF output. (SHARED-56002) Improved memory footprint of the output engine. (SHARED-67225) Several improvements have been made to the output engine to ensure that output creation terminates even in exceptional circumstances. For example when handling faulty input files or in tight memory situations.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1503.html">PAGE 1503</a></h6>
<p>Print Wizard and Preset Wizard Improvements Dynamic Print Control Improvements Improvements have been made to the creation of Dynamic Print Controls. l l l l When working with PPD files to dynamically drive PostScript printers, some printers have fragments called JobPatchFile in their PPD, which are required for the printer to function properly. These are now supported and automatically added to the output if the PPD includes such.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1504.html">PAGE 1504</a></h6>
<p>Import multiple Presets You can now import more than one preset at a time in the Job Preset and Output Preset wizards, as well as in the Print dialog. (SHARED-66727) Improved Data Filtering Options The Data Filtering page in the Print Wizard has been totally revamped. It has been enhanced with extra features, and the user interface overhauled. The user interface is now much more consistent with other rule builders available within the Print Wizard.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1505.html">PAGE 1505</a></h6>
<p>General Print Wizard Improvements l l l l The Additional Content dialog now uses the selected Designer language's decimal and thousand separators in entry boxes. (SHARED-60881) Sample size preferences for standard and booklet imposition setups are now saved to the output preset.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1506.html">PAGE 1506</a></h6>
<p>Workflow 2019.1 Updates PDF/A-3 e-Invoices A number of national standards now rely on PDF/A-3 as a standard for e-Invoicing. Workflow can now add invoice information and set Conformance levels for both the German (ZUGFeRD) and French (Factur-X) PDF/A-3 outputs via the new PDF/A-3 plug-in. More e-Invoice standards will be added in future releases. (SHARED-69195) NodeJS NodeJS now accepts raw content types. It is possible to send a raw JSON, XML, HTML, CSV, CSS, JS, TXT and XHTML body.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1507.html">PAGE 1507</a></h6>
<p>Capture/Send emails with SSL support You may now retrieve emails from and send emails through secure online mail servers like Office365 or GMail. Different encryption methods can be specified, with the default (TLS v1.2) working out of the box with Office365 and Gmail. The new Secure Email Input task allows capturing POP3 or IMAP emails with SSL The new Secure Email Output task support. This means Workflow can now process provides an option for sending emails with SSL support.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1508.html">PAGE 1508</a></h6>
<p>General Workflow Improvements l You can now specify the color of the highlight for any task to allow color coding of tasks or sections to make them stand out better. (SHARED-61963) This enables you to define personalised color schemes. For instance Scripts could always be highlighted in red, or each Send To Folder task could have a different color, based upon its destination folder. l l Connect resources which have been used are now logged when a Connect plugin finishes.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1509.html">PAGE 1509</a></h6>
<p>l l New Workflow specific configuration Preference option introduced to Connect Designer to cater for instances where the Workflow is running on a different machine with a different Windows codepage. (SHARED-69053) New option added to the Workflow preferences to determine whether the current Workflow Configuration should be automatically re-opened when the Workflow application is next started. (SHARED-65133) Known Issues As of PlanetPress Connect 2018.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1510.html">PAGE 1510</a></h6>
<p>They can be found here. Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 2018.2.1 and PlanetPress Workflow 2019.2, as well as some important installation information. Installing PlanetPress Connect and PlanetPress Workflow l l l PlanetPress Connect is released as a 64 Bit version only, although the PlanetPress Workflow, Fax, Search and Imaging modules are 32 Bit..</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1511.html">PAGE 1511</a></h6>
<p>Upgrading from PlanetPress Connect 1.7 It is highly recommended that you update the Objectif Lune Update Client before upgrading PlanetPress Connect from version 1.7 to version 2019.2. If you do not update the Update Client, an unexpected error might occur whilst updating Connect. This error does not prevent the successful upgrade of Connect to 2019.2, even though it appears as if it might have.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1512.html">PAGE 1512</a></h6>
<p>l l l l Backwards compatibility issues with Workflow/REST API processes that incorporate Connect DataMapper configurations connecting to databases. (SHARED-67683) External sort metadata fields were not being catered for properly in the metadata validation code in the Output Preset and Print Wizards. (SHARED-67687) Fixed a problem affecting scripted Section configurations containing different scripted values for different records. The merge engine would sometimes use previously applied scripted values.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1513.html">PAGE 1513</a></h6>
<p>Connect 2019.2 Enhancements Sassy CSS PlanetPress Connect 2018.2 introduces Sass CSS preprocessor functionality to the Designer. (SHARED-64625) Sass (Syntactically Awesome Style Sheets) is an extension of CSS that enables you to use things like variables, nested rules, inline imports and more. Maintenance of CSS styles for templates requiring many different style rules can become a tedious undertaking. Stylesheets files keep getting larger and more complex and thus harder to maintain.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1514.html">PAGE 1514</a></h6>
<p>Commingling Commingling (creating a job from content sets that were created with different templates) has now been added to PlanetPress Connect as a standard feature, just as it is for PReS Connect. (SHARED-64963) New ERP Template Wizards ERP templates have been added to the Template Wizards. (SHARED-52963) The new wizard allows you to create seven different transactional print documents, all with a uniform style. They all include a datamodel with appropriate scripting embedded.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1515.html">PAGE 1515</a></h6>
<p>In Connect 2018.2 new scripting commands have been added to dynamically set Sheet Configuration options from within a Control Script. This allows you to set the Duplex mode dynamically, or do things such as applying a different Master Pages based upon the data, or omitting empty sides from the last sheet, or single sheets. The following Control Script sample enables Duplex mode for "Section 1": let section = merge.template.contexts.PRINT.sections["Section 1"]; section.sheetConfig.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1516.html">PAGE 1516</a></h6>
<p>REST API Improvements REST API calls that take resource IDs, whether on the URL or in a JSON payload, have been improved in two ways. 1. The existence of the resource represented by the ID is now verified. If it doesn't exist, a HTTP status code of either 403 or 404 is returned. Previously the result was undefined and varied depending upon the call made.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1517.html">PAGE 1517</a></h6>
<p>One change is the introduction of an option to set the Overall Logging Level. By default the logging level is set at the midpoint of Info, but it can be set higher to include more logging (All, Trace, Debug) or lower to reduce the logging (Warning, Error). NOTE: Higher logging settings will have an impact upon Connect production speeds, as well as leading to substantially larger log files. We have also introduced Advanced Logging preferences.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1518.html">PAGE 1518</a></h6>
<p>l l The logging format default has changed from dd MMM yyyy (31 May 2018) to yyyy-MM-dd (2018-05-31) to make it easier to sort log files when using tools to merge and view multiple log files together. (SHARED-64233) Connect will now log a warning message in the event that there are insufficient engines currently available for a specific job, leading to the scheduler having to wait.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1519.html">PAGE 1519</a></h6>
<p>Connect 2019.2 Designer Updates JSON support added to the Data Model Panel The Designer now allows you to add JSON sample data straight into the Data Model for debugging purposes. (SHARED-61655) This can be done via a new File menu option Or from the Data Model Panel itself, using the new JSON Sample Data button. Invoking this option launches a wizard which allows you to either select a JSON file or paste JSON data copied from a Workflow variable.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1520.html">PAGE 1520</a></h6>
<p>Minimum Pages option added to Print Sections Connect 2019.2 introduces a new section property for controlling the minimum number of pages for a Print Section. This can be used to generate pages with only absolute positioned content, simplifying workflows where the number of pages are known up front and you want to draw boxes (absolute positioned divs) on specific pages. (SHARED-10236) The property can be set when the new Template is being created. Or through the Print Section properties.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1521.html">PAGE 1521</a></h6>
<p>Color Output option added to Print Contexts For certain full color print jobs, it is important to be able to set black text on top of color areas to overprint. This is of particular importance for small text, because mis-registration problems are more visible with small text. To support this a new Color Output option has been added to the Print Context. (SHARED-62265) The default encoding for the color black has also changed from RGB to CMYK.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1522.html">PAGE 1522</a></h6>
<p>Send To Workflow Improved The Send To Workflow option has been simplified and streamlined, and a new Package option has been added. (SHARED-60392) Paste as Plain Text option added Option added to paste content copied from an external editor as plain text. This ensures any unwanted formatting and invisible elements are removed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1523.html">PAGE 1523</a></h6>
<p>Scripting Improvements l An overview ruler has been added to the Script Editor. The ruler shows annotations concerning the entire script. These annotations are shown relative to their position in the script and do not move as the user scrolls the script source. Script errors are highlighted by a red icon, and warnings in yellow. The topmost icon will display red if any errors exist in the script at all.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1524.html">PAGE 1524</a></h6>
<p>l l l Scripts in Print Context jobs can now attach arbitrary properties to content items generated by Content Creation. The properties are retained in the database, allowing the information to be utilized in Workflow for further processing along with the base record information when retrieved by the Retrieve Items action. (SHARED-65239) Introduced "width" and "height" script functions with the same behaviour as jQuery's "outerWidth" and "outerHeight".</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1525.html">PAGE 1525</a></h6>
<p>Business Graphics Improvements l l Color picker options added throughout the Chart Properties dialog. (SHARED-62564) The "Values (y)" table in both the Insert Graph Wizard and the Graph Script dialog can now be filtered to show only numeric fields. This will then limit the display to only Integer, Float and Currency fields in the Data Model.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1526.html">PAGE 1526</a></h6>
<p>General Designer Improvements l l Download Remote Resources (CSS stylesheets, JavaScript files, JSON and HTML snippets) to your template through a new context menu in the Resources view. This allows you to keep a link to a centralized file but quickly download a copy to your template without having to separately copy and paste.(SHARED-58949) New Media now defaults to the same paper size as the current Print Section.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1527.html">PAGE 1527</a></h6>
<p>l l Media Properties dialog behaviour improved. When any of the media in the Resources tree properties are changed, the "Page Setup" button gets activated and Designer prompts to save the media properties changes. (SHARED-62353) Disabled irrelevant menu items in the View menu when a Snippet editor is active.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1528.html">PAGE 1528</a></h6>
<p>Connect 2019.2 DataMapping Updates Ignore Blank Lines Option added to the DataMapper Settings to ignore any blank lines in the data. (SHARED-57790) Dynamic SQL Queries Custom SQL queries now support the use of dynamic elements which can be built using JavaScript syntax. This allows an SQL query to use information passed on by Workflow to dynamically customize the query. (SHARED-34301) For instance, a custom query could contain the following code: =SELECT {automation.variables.FieldList} FROM {automation.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1529.html">PAGE 1529</a></h6>
<p>Set Data Fields as Not Required Individual data model fields can now be set as required or not required. By default all data base fields are initially set to being required. This new option provides the ability to set individual fields as not required. Non-required fields are indicated in the Data Model panel by a green asterisk ('*') symbol after the field type. (SHARED-60067) Landscape PDF Input Rotated PDF pages are now fully supported in PDF input files.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1530.html">PAGE 1530</a></h6>
<p>This would get converted dynamically to something like ./address[@state="California"] based on the value of JobInfo(9). General DataMapping Improvements: l Can now set default values to ExtraData fields, in the same way as other fields. (SHARED61348) l Improvements in the way engines communicate in a multithreaded environment which should see a reduction in the number of times an engine fails to register with the server.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1531.html">PAGE 1531</a></h6>
<p>Connect 2019.2 Server Enhancements Engine Setup The settings for the number of Connect Server engines to launch has been removed from the "Scheduling" settings page, which controls how the engines are actually used. They have been moved into a new "Engine Setup" page that controls how many engines of each type are to be launched. This also simplifies the Scheduling preferences page. Automatic Engine Restarts To safeguard server availability restarting the Connect engines periodically is recommended.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1532.html">PAGE 1532</a></h6>
<p>and the engines can now be set to use a different port from the primary connection port. This prevents the engines from being starved from connections to the Connect Server if the external connections are not closed fast enough. These settings are located on the new “Connections” page of the Connect Server Configuration. The “Security” preferences page for the Connect Server connection is now a sub page of this new page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1533.html">PAGE 1533</a></h6>
<p>Note: When running really large jobs, it often pays to increase Weaver memory allocation, even if only for the duration of the production job(s). Font handling l Additional Content Text improvements When adding text as Additional Content in Output Presets, TrueType Collections (TTC) font files were not supported. TTC fonts allow a single file to hold multiple fonts types. Since TTC fonts can be important for Asian language fonts, we have now added support for these.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1534.html">PAGE 1534</a></h6>
<p>To accommodate such, we have provided an alternative font creation method which always creates CID fonts with identity encoding. This results in larger output files, but provides better compatibility with PDF viewers. When generating PDF for non-Western languages, this new option may be the recommended choice. l Asian language PDF output made smaller through improved glyph handling. (SHARED63549) l Further improvements made in handling simulated style fonts for OTF fonts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1535.html">PAGE 1535</a></h6>
<p>Email Output Improvements l l Meta information added to the Email Section Properties This allows viewpoint meta information to be added and configured in the email. This meta information will not be visible to the receiver, but can have an effect on how the email is represented in the email client. (SHARED-64761) Email Script dialog improvements The email Script dialogs have been streamlined and simplified.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1536.html">PAGE 1536</a></h6>
<p>the specified conformance level. This has been fixed. (SHARED-61714) l In PDF/A-1b, PDF/X4 and PDF/VT output the document title in the PDF metadata is now derived from the template name, rather than the full path of the output file name. (SHARED61168) General Output Improvements l l l l l Output engine now warns instead of crashing if it encounters text with a non-invertible transformation matrix (such as a zero point size).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1537.html">PAGE 1537</a></h6>
<p>Print Wizard and Preset Wizard Improvements Size grouping The ability to group documents by their size has been extended. In addition to grouping documents, you can now also group document sets and job segments by the number of pages. And instead of just using the page count, it is also now possible to use the sheet count for the size of the documents, sets, or segments. This makes size grouping useful for jobs that might contain both simplex and duplex content.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1538.html">PAGE 1538</a></h6>
<p>Tip In Output Creation, you could create an output file per job segment, and use ${segment.metadata.ItemSize} in the output file mask to automatically name these files appropriately.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1539.html">PAGE 1539</a></h6>
<p>Impositioning We have made a number of improvements to Impositioning, both by improving usability and by adding new features. These changes led to a redesign of the layout of the imposition wizard page, with some options being moved and others renamed. The major improvements are as follows. Visual warning The page layout diagram now displays in red when the selected imposition options do not fit the selected sheet.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1540.html">PAGE 1540</a></h6>
<p>have added a sample page setting that will be used for both the preview and the validation of the settings. This sample page now defaults to the size and orientation of the first section of a template, instead of its first media. Stack by Column Alongside the existing cut and stack impositioning order, we have introduced an imposition order that is more suited for continuous feed printing when the imposition has multiple rows.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1541.html">PAGE 1541</a></h6>
<p>done properly, this causes the roll output by the printer to have the first page on the outside of the roll, allowing the roll to start with the first page. Our existing option to reverse the order of impositioning is reversing the order of the resulting imposition sheets by starting with the last side of the last sheet, and then going backwards. This effectively turns the stack up side down. It also means that, in case of duplex impositioning, all back sides become front sides and vice versa.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1542.html">PAGE 1542</a></h6>
<p>Workflow 2019.2 Updates New HTTP Server Input - NodeJS An alternative HTTP server option now ships with PlanetPress Connect Workflow: NodeJS Sever Input. (SHARED-62247) The new implementation is backward-compatible with the existing HTTP Server Input (except for PlanetPress Capture requests), but also introduces several new capabilities. These include: l The ability to serve static resources from several folders. l Redirect requests to other servers using a Proxy list.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1543.html">PAGE 1543</a></h6>
<p>Process Grouping Support has been added for nested Process grouping in the Workflow Configuration Components. (SHARED-65457) Groups can be added to existing groups, moved from one group to another or ungrouped within another group. In addition, multiple startup processes can now be defined. (SHARED-65454) This allows you to create startup processes that are specific to certain projects (or groups, or subgroups) and to specify the order in which the processes should run at launch time.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1544.html">PAGE 1544</a></h6>
<p>l All-in-One can now accept a Job Preset configuration. The settings for this are contained in the new Job Creation tab. (SHARED-33510) Create Job Improvements l New option has been added to show only those Documents which are included in the job. (SHARED-53893) l All Content Set IDs are now stored in the metadata returned by the Create Job task.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1545.html">PAGE 1545</a></h6>
<p>DataMapper Validation Option added to Execute Data Mapping to validate the records without actually extracting them. This provides an elegant option for determining potential data errors prior to actually running the job. (SHARED-57946) When running with this option, the Data Mapping task returns a summary of the data mapping job as well as a list of records that would generate an error, if any.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1546.html">PAGE 1546</a></h6>
<p>l l Improved error handling when invalid JSON data is passed to a Create Content task in Workflow. (SHARED-63584) Retrieve items with Record ID list now trims white space from end of Record. (SHARED63603) l l When a Retrieve Items query returns multiple job sets, all the Job Set IDs are now stored in the Workflow Metadata at the Job level. (SHARED-64730) Improved Create Web Content task support for anchors.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1547.html">PAGE 1547</a></h6>
<p>l Fixed potential security threats in HTTP Service static resources serving. (SHARED-61144) l Timeout in Connect Send Get Job Data plugin now works as expected. (SHARED-61308) l GetKeySets() command made backwards compatible. Command now retrieves all keys when parameter list is left empty or if the select all character ‘*’ is used. (SHARED-64160) Known Issues As of PlanetPress Connect 2018.1 the Known Issues have moved from the Release Notes to the Connect online Help. They can be found here.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1548.html">PAGE 1548</a></h6>
<p>The license allows regular printing via the Print Wizard but runs Email and Web output in demo mode. For more information, please contact your local OL Customer Care or Sales team. Templates Used in Workflow For improved performance we recommend re-saving Workflow templates set up in the previous versions to run with PlanetPress Connect2018.1\Workflow 2018.1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1549.html">PAGE 1549</a></h6>
<p>Upgrading from PlanetPress Connect 1.7 It is highly recommended that you update the Objectif Lune Update Client before upgrading PlanetPress Connect from version 1.7 to version 2018.1. If you do not update the Update Client, an unexpected error might occur whilst updating Connect. This error does not prevent the successful upgrade of Connect to 2018.1, even though it appears as if it might have.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1550.html">PAGE 1550</a></h6>
<p>Connect 2018.1.6 Enhancements/Fixes Improved Weaver Engine memory usage Weaver Engine memory usage has been considerably improved. These changes have resulted in the Weaver Engines not only requiring fewer system resources but have also improved stability and reduced the need for periodic restarts. (SHARED-65330) Improved font handling l l Improved font style simulation, for when the full font family is not available.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1551.html">PAGE 1551</a></h6>
<p>Connect 2018.1.4 Enhancements/Fixes PDF/A-1b compliance broken with Polish text An issue was discovered with Polish text in PDF/A-1b compliant output, whereby the output was missing "CIDSet" font descriptor entries for TrueType-based CID fonts. This error has now been fixed. (SHARED-64536/64816) Issues with text extraction from PDF output Problems were encountered in extracting non-latin and multilingual text from PDF output. These problems have now been addressed. (SHARED-64936) Connect 2018.1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1552.html">PAGE 1552</a></h6>
<p>OutOfMemory Errors in PostScript Output When creating PostScript output or using the REST API to run a custom Enhance configuration containing one or more PostScript output channels, "OutOfMemoryError: Metaspace" errors could be encountered. This was due to JavaScript source code in the PostScript printer definition being compiled too often. This issue has now been fixed. (SHARED-64350) Issue with background image URL paths Fixed issues with URL path encoding.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1553.html">PAGE 1553</a></h6>
<p>However, it was subsequently found that this could cause issues with previously created templates using the function on PDF files. Consequently, this change was reverted in 2018.1.1. (SHARED-64201) Workflow - Updated GetKeySets() implementation now made backwards compatible The Workflow function to retrieve key values GetKeySets() was updated in Workflow 2018.1 to use the more formerly correct asterisk '*' parameter for retrieving all key sets.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1554.html">PAGE 1554</a></h6>
<p>This allows: l l The use of printer features that are not yet supported through the Connect user interface, such as: l switching between color and greyscale printing l selecting output bins Direct control of supported PostScript functionality, such as: l Duplex/Simplex l Print Media selection l Finishing options (e.g.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1555.html">PAGE 1555</a></h6>
<p>NOTE: Case sensitivity/insensitivity has not been added as an option in this first cut of the Dynamic Print Control rules editor. This will be added in a subsequent version.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1556.html">PAGE 1556</a></h6>
<p>Improved Business Graphics Business Graphics have been greatly enhanced and now display a preview of the data and graph as part of the Pie, Line and Bar chart wizards. The updated wizards simplify data selection and allows you to set and preview graph options dynamically, prior to inserting the graph object.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1557.html">PAGE 1557</a></h6>
<p>Refer to the amChart documentation for more information on the numerous configuration options available. NOTE: As a consequence of changes in both the user interface and the underlying technology, Business Graphics made with a version prior to PlanetPress Connect 2018.1 may not display correctly when opened in version 2018.1. See the Business Graphics: Backwards Compatibility section on this page for full details.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1558.html">PAGE 1558</a></h6>
<p>Windows Server 2016 now officially supported As of PlanetPress Connect 2018.1, Connect is now officially supported under Windows Server 2016. NOTE: The Objectif Lune Inc. Update Client application might be blocked by enhanced security settings in Windows Server 2016. To fix this, add http://updates.ca.objectiflune.com to the list of trusted web sites on that machine, or lower the internet access rules. Improved Previews The Preview now smooths text, images and line art when rasterizing a page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1559.html">PAGE 1559</a></h6>
<p>New Preferences options: l l Scheduling preferences for Merge and Weaver engines now include a preference for specifying the memory (RAM) to be used per engine. (SHARED-44547) Merge and Weaver engine scheduling preferences now include an option for scheduling an engine restart if the total amount of memory (RAM) used by the engine exceeds the specified entry. This is in addition to the time limit setting.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1560.html">PAGE 1560</a></h6>
<p>l Log file settings can now be adjusted within the Designer and Server Configuration preference windows. The settings are global to all Connect applications. Settings include log file rollover options (time or size based), and the format of the log messages generated. (SHARED-60043) Installer Improvements: l l l Prerequisites now installed silently when installing Connect using silent installer. (SHARED-59286) Messaging improved for when the Connect installer cannot safely commence uninstallation.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1561.html">PAGE 1561</a></h6>
<p>l l When using the REST API to execute a +PReS Enhance configuration that logged to a custom log file, the log file could not be deleted at the end of the execution. Repeating the execution of the +PReS Enhance configuration also caused unreadable NUL characters to appear in the log file and log messages were appended to it. This has been fixed and the custom log file now closes at the completion of the Enhance configuration execution. (SHARED-59656) Logging infrastructure has been updated.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1562.html">PAGE 1562</a></h6>
<p>Connect 2018.1 Designer Enhancements/Fixes Updated internal browser component The browser component (Mozilla Gecko) used in the WYSIWYG editor of the Designer has been updated. This allows you to use new CSS properties like flexbox. Connect 2018.1 now uses Mozilla Gecko 38 as its HTML rendering engine. (SHARED-42286) NOTE: The update to the Mozilla Gecko engine could lead to increased output file sizes for some PCL jobs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1563.html">PAGE 1563</a></h6>
<p>You can also select whether the Print Context should be added as a PDF attachment or not, using the "Attach Print context as PDF" check-box. Rotate and Scale Background Images Section Background images can now be rotated or scaled, either via the Section Properties dialog or via a control script. (SHARED-60244/60855) Align multiple objects You can now select and align several absolute positioned objects at once with the new Align Objects context menu.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1564.html">PAGE 1564</a></h6>
<p>Preflight improvements Double-clicking a script warning or error in the Preflight report will now open the offending script within a script editor. (SHARED-60273) Improved language support Disable certain CTRL + ALT + <?> shortcuts in source editors, including source tab, HTML snippet editors and CSS editors.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1565.html">PAGE 1565</a></h6>
<p>Scripting improvements: l l Option added to allow Case Sensitivity to be set on or off for any conditional string comparison scripts. (SHARED-56535) Improved support in Text Script Wizards for the custom formatting of Date, Currency, and Numeric fields. (SHARED-60261) The above example shows a custom pattern for a currency value, containing a subpattern for negative values. How the result would appear is shown in the Example field.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1566.html">PAGE 1566</a></h6>
<p>l l l l Improved Email Context script selection. All the Email Context scripts are now bundled together in their own sub-menu. (SHARED-56602) Improvements made to the default data field selection logic when adding new Text Scripts. (SHARED-57286) Double clicking a script in the Script Panel with the script editor open will now prompt you to save your changes. (SHARED-47908) Any open Script Editor will now close when another template is opened.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1567.html">PAGE 1567</a></h6>
<p>General Designer improvements: l l l Style rule changes can now be saved and applied instantly from within the Edit Rule dialog, via a new Apply button. (SHARED-58595) A new Send to Workflow icon has been added to Designer. It has been added as a new option in the icon toolbar and also to the File menu option. (SHARED-59322) You can now copy/paste or drag/drop images files from the file system or Images folder to the Stylesheets folder.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1568.html">PAGE 1568</a></h6>
<p>l l l l l l l l l The New Email and New Print template wizards now open using the last used Template settings. Selections such as page size, page margins and the like will be retained. (SHARED-33982) Improved element insertion rules, to make context menus and dialogs more accurate. For example, the option to add Absolute elements in emails has been removed, as the email format does not support this functionality. (SHARED-60947/61117) Improved support for remote images (http-based URLs).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1569.html">PAGE 1569</a></h6>
<p>Connect 2018.1 DataMapping Enhancements/Fixes Standalone DataMapper Engine The DataMapper Engine has been stripped into a separate stand-alone server. This is to make it more efficient and configurable as well as more adaptable in the future. The new DataMapper Engine options can be set via the Connect Server Configuration tool. (SHARED-59696) Improved date field support for Excel datafiles Formatting for date fields in Excel data files has been improved.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1570.html">PAGE 1570</a></h6>
<p>Ignore CR/LF in Text records New option added to allow ignore end-of-line CR/LF characters in Text datafiles. This prevents empty trailing records being added to the dataset. (SHARED-62139) Create unique GUID in scripts New DataMapper Script function createGUID() added to the Boundaries and Steps scripts. This function returns a unique GUID. (SHARED-61246) New "No Data" warning A visual warning has been added to the DataMapper when an open table contains no data.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1571.html">PAGE 1571</a></h6>
<p>l l It is now possible to add a CSV input file containing just a single column. (SHARED59814) Improved DataMapping performance for XML files containing large numbers of end-of-line CR/LF characters.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1572.html">PAGE 1572</a></h6>
<p>Connect 2018.1 Output Enhancements/Fixes Redesigned Additional Content page in the Print Wizard The Additional Content page in the Print Wizard has been re-designed to present all the Additional Content entries in a single table, simplifying Additional Content management. (SHARED-56444) Improved Tray Mapping in Printer Wizard Media attributes can now be imported directly into the output config tray mapping from either the currently open template or from a saved template file.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1573.html">PAGE 1573</a></h6>
<p>New Conditional option During Output Creation, it is now possible to determine the template section to which a sheet belongs to using the new sheet.sectionName property. This property has been made available as a conditional option in the Printer Wizard. (SHARED-61275) NOTE: The introduction of this property introduces a slight risk of compatibility issues, but only for cases where an existing custom printer definition or Enhance configuration already has a user-defined property with the exact same name.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1574.html">PAGE 1574</a></h6>
<p>Print Output Improvements: l l l l Transparency support for PDF output. (SHARED-61492) Soft mask improvement in PDF. The soft mask is now set by the CTM ("Current Transformation Matrix") when the soft mask is created. (SHARED-58893) Improvements made to generic PCL output for some printers. (SHARED-60019) Booklet Impositioning for mix-plex jobs has been improved, reducing the likelihood of empty pages.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1575.html">PAGE 1575</a></h6>
<p>Workflow 2018.1 Enhancements/Fixes Improved Performance The performance of the Execute Data Mapping and Retrieve Items tasks have been improved when setting the options to "Output Records to Metadata". (SHARED-56678) NOTE: The performance update to Retrieve Item is currently only implemented for Data Records. The other entity types will be added in a subsequent release. Retrieve Items by their IDs Option added to the Retrieve Items task to support retrieving items via their associated entity IDs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1576.html">PAGE 1576</a></h6>
<p>New option in Create Web Content task An option to "Do not alter HTML" was added to the Create Web Content task. When selected the task shall not add the BASE element to the HTML as it usually does, nor shall it modify the local anchors with JavaScript code. (SHARED-62521) New option in FTP Input task An option to "Search in subfolders" has been added to the FTP Input task.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1577.html">PAGE 1577</a></h6>
<p>New Workflow Preferences: l l You can now set the default Workflow scripting language. This defaults to VB Script for backwards comparability. (SHARED-60000) Improved PHP like Array options are now available for the HTTP Service plug-in. (SHARED-50770) Number of email attachments now available The number of email attachments is now available to the Email Input task.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1578.html">PAGE 1578</a></h6>
<p>GUID variable introduced A new %U system variable has been introduced to support full GUID values. This new variable is an addition to the pre-existing %u ( a unique 15-char string). The new %U system variable is available in the same locations that the %u system variable is, including in the context menus.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1579.html">PAGE 1579</a></h6>
<p>l Options for setting the logging refresh speed have been added. (SHARED-60029) Workflow Data Repository Manager improvements: l Improved Data Repository Key Set editor. (SHARED-59137/60165) l Improved speed when writing to a Data Repository. (SHARED-51564) l l l Instead of throwing an error the lookup() function now returns NODATA when an invalid group and/or key is passed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1580.html">PAGE 1580</a></h6>
<p>l Fixed issue whereby Workflow would stop processing PostScript and PDF jobs on some Windows 10 Fall Creators Update machines. (SHARED-62516) Known Issues As of PlanetPress Connect 2018.1 the Known Issues have moved from the Release Notes to the Connect online Help. They can be found here. Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 1.8 and PlanetPress Workflow 8.8, as well as some important installation information.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1581.html">PAGE 1581</a></h6>
<p>Upgrading from PlanetPress Connect 1.1 In order to upgrade from Connect Version 1.1 to Version 1.8 via the Update Manager, it is necessary to install a newer version of the Objectif Lune Update Client. The next time you run your current Update Client it will show that there is an update available for itself. Simply click on the download button in the dialog to install the new version of the Update Client. Note that it is no problem in running the update while the Client itself is still open.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1582.html">PAGE 1582</a></h6>
<p>Updating stand-alone Workflow Messenger installations If Workflow Messenger was installed stand alone with no other Workflow components installed, the Update Client will be unable to find the Messenger component and thus it will not automatically update to the Workflow 8.8 version. To get around this, download and run the Workflow 8.8 installer manually. Print Only Version A Print Only license is available with version 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1583.html">PAGE 1583</a></h6>
<p>Connect 1.8 General Enhancements and Fixes Native support for Microsoft Excel spreadsheet files The Connect DataMapper can now handle Microsoft Excel files natively. The CSV data type has been enhanced to automatically recognize *.XLS and *.XLSX files and use them directly without any additional steps. Both the CSV Wizard and the Add Data options now allow you to pick these file types.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1584.html">PAGE 1584</a></h6>
<p>Dynamically set Media Background Images Support has been added for dynamically setting the path of media backgrounds at run time (aka Virtual Stationery). This is achieved via the Control Script API. The path can be set to an image in the Images folder but also to a file on disk (the http:// and https:// protocols are not currently supported). This greatly simplifies template management in situations where a design is shared between different brands.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1585.html">PAGE 1585</a></h6>
<p>Installer improvements l Improved error capture, handling and messaging. (SHARED-40209) l Significantly improved logging of Server Service installation. (SHARED-50796) Korean Language Support PlanetPress Connect 1.8 is now available in Korean, in addition to the other languages already supported. Korean is not yet available in PlanetPress Workflow, however. (SHARED-40161) Context Sensitive Help Context Sensitive Help has been added to PlanetPress Connect.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1586.html">PAGE 1586</a></h6>
<p>Anchored positioned boxes losing style attributes Absolute positioned (Anchored) elements would lose some style attributes under certain circumstances. These issues would only occur when the absolute positioned element had multiple style attributes that ended with the text "top" or "left". Such as is the case with "padding-top" and "top". If both those attributes were set, then only one of the attributes would be retained. (SHARED-57361) l l Customers upgrading from 1.6.1 to 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1587.html">PAGE 1587</a></h6>
<p>Connect 1.8 Performance Related Enhancements and Fixes Faster Performance Tweaking in Server Configuration When tweaking performance it can be hard to figure out the right settings for the number of Merge engines, Weaver engines, dividing speed units, etc. Having to restart the Connect Server to apply the changes every time a setting was changed also made tweaking performance harder than it should have been.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1588.html">PAGE 1588</a></h6>
<p>Connect 1.8 Designer Enhancements and Fixes Automatically Fit Text to Container (Copy Fit) The Designer can now automatically scale text content to fit the boundaries of a box (inline or absolute positioned <div> ). Scaling text to fit a container is a very popular feature when creating personalized post cards and the like. The option is found in the Content tab of the Box properties dialog and can be set to scale all text or a specific element in that box by entering a CSS selector.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1589.html">PAGE 1589</a></h6>
<p>Toggle Comments On/Off via Shortcut Keys Toggle comments off or on in HTML, CSS and JavaScript editors via a keyboard combination. Use Ctrl + / to comment out a single line and Ctrl + Shift + / to comment out multiple lines. (SHARED-56440) Refresh View button added You can now refresh the contents of both Design and Preview views via the new Refresh button or new Refresh selection in the Menu.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1590.html">PAGE 1590</a></h6>
<p>Specify Page Range for Preflight You can now optionally perform Preflights on a range of records. (SHARED-35076) Select and adjust multiple Box elements simultaneously Multiple Box elements can now be selected at the same time. Once selected you can either move or resize the selected boxes as a group. You can move them either via the mouse, or by nudging them around a single pixel at a time with the arrow keys. When nudging, the boxes will not snap to guides.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1591.html">PAGE 1591</a></h6>
<p>Set Template Locale Previously Connect always assigned the System Locale to new templates. A new option has been added to the preferences to allow the selection of a specific locale. This selection will then apply to all new templates thereafter. It applies to Date and Time fields plus numeric and currency data fields.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1592.html">PAGE 1592</a></h6>
<p>General Designer improvements l l l l l l GS1 Datamatrix barcode now supported. (SHARED-55999) Section, Media, and Master resources can now be duplicated by copy-pasting. (SHARED-52261) Reopening a template will put the focus on the section that was active when the template was closed. (SHARED-53199) Keyboard shortcuts to increase (Ctrl + Shift + >) or decrease (Ctrl + Shift + <) text size now work as expected. (SHARED-11660) "Problem" view renamed more accurately as "Preflight Result".</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1593.html">PAGE 1593</a></h6>
<p>Connect 1.8 DataMapping Enhancements and Fixes Extracting Variables without using JavaScript Variables are frequently used in data mapping configurations as counters or as a way to concatenate values before extracting the final result to a data model field. Until Connect 1.8, the only way to extract those variables would be to create a Javascript-mode field and to use the appropriate API syntax (e.g. automation.jobinfo.jobinfo1, or sourceRecord.properties.MyVariable).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1594.html">PAGE 1594</a></h6>
<p>"Extract all from here" feature added In TXT mode, we’ve often had the request to be able to extract everything after a specific location, regardless of the record length. This would be useful, for instance, when extracting the body of an email which is never fixed-length. Until PlanetPress Connect 1.8, the customary way of proceeding would be to use a Loop step that stores all lines in a variable and an Extract step after the loop to store that variable into a field.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1595.html">PAGE 1595</a></h6>
<p>Improvements made for Transactional Style Datafiles. l l l The DataMapper and Output have both been enhanced to better cater for extremely large data records (where thousands of details might be associated with a single record). (SHARED-51691). The Designer has been updated to allow a limit to the maximum number of records to display in preview. Tooltip now displays a warning if detail table exceeds the preview limit.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1596.html">PAGE 1596</a></h6>
<p>Connect 1.8 Output Enhancements and Fixes Dynamic Finishing Print Output Finishing has been improved considerably, and is now much more powerful and flexible. In Templates, you could already set finishing for documents and sections. Job Creation would allow you to specify a different kind of Finishing for your documents and Templates. This has been extended to allow Finishing settings on all levels of Job Creation: Document Sets, Job Segments and Jobs.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1597.html">PAGE 1597</a></h6>
<p>The reason we call this feature dynamic finishing, is that it includes a brand new rules editor to allow you to choose when to apply a finishing setting: Page 1597</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1598.html">PAGE 1598</a></h6>
<p>PDF Pass-through Connect’s output creation (Weaver engine) tries to write content the best way possible, depending on the chosen output format and optimization settings. However, there are cases when this might not be desired, such as when the graphics have already been optimized for the device and you do not want the software to change them. It is now possible to instruct output creation to include PDF resources in the output file as-is.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1599.html">PAGE 1599</a></h6>
<p>whether this will be an issue on your specific printer(s) or not. This issue will also be addressed in a later release. Overprint for Spot Colours Overprinting certain content on top of other content is sometimes required. (SHARED-56743) For example: l l To deal with special print applications, such as applying special (invisible) inks that are intended to go on top of coloured areas, for instance printing UV ink or applying varnish to a certain area.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1600.html">PAGE 1600</a></h6>
<p>Print Output l l Mixplex support added An option has been introduced to omit empty back sides for the Single and Last sheet positions when Duplex is enabled, resulting in mixplex output. This helps in reducing costs in printing environments where page count or click-charging is applied. (SHARED46965\55459) Improved logging of output generation.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1601.html">PAGE 1601</a></h6>
<p>Capture OnTheGo (COTG) Enhancements and Fixes New and improved COTG library A new jQuery plugin variant of the COTG.js library introduces events and options for COTG widgets. These concepts greatly simplify event based programming. For example: it allows your code to set a date for a date field and retrieve the geolocation automatically on the drawing of a signature. The COTG jQuery plugin is the successor of the cotg-1.x.js JavaScript library found in COTG forms based on the COTG Starter templates (v1.x).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1602.html">PAGE 1602</a></h6>
<p>Workflow 8.8 Enhancements and Fixes Deleting documents from the COTG repository Many COTG customers create documents for which they don’t want to set an expiry date (or a lifespan). They therefore set an expiry date far into the future to make sure the document remains in the repository. However, once the document has been filled they would like to remove it from the repository as soon as possible so it doesn’t clutter the view of the repository.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1603.html">PAGE 1603</a></h6>
<p>The Connect Server has its own File Store which it uses for transient files. This File Store is managed by the Cleanup service who takes care of removing obsolete files when those files are not marked as permanent. This greatly reduces the amount of administration required to manage the files. We figured that since there is already a File Store and REST API calls to connect to it, why not turn that into an accessible feature for customer implementations? With Connect 1.8, the Workflow 8.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1604.html">PAGE 1604</a></h6>
<p>Generating all contents using JSON instead of data records A number of customer workflows involve generating new versions of documents based on the original one created by Connect. For instance, a Delivery Note might come back with adjusted quantities on certain line items. Or a web-based status page might need to get updated with additional data. However in many cases, the original data must still be left untouched (for reprints, for instance).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1605.html">PAGE 1605</a></h6>
<p>Converting XML to JSON and JSON to XML XML is already one of the most popular data formats used with Connect. In many implementations, most notably web-based ones, XML is used to transfer or update information back and forth between Connect and Workflow. However, using XML means the DataMapper must be involved each time the data changes, which impacts performance, especially when all you want is to update a Status web page.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1606.html">PAGE 1606</a></h6>
<p>Full Timestamp entries added to Data Repository Added full timestamps to the Repository to allow for more precise information on each key set. The DateC and DateM keys now both contain a full time stamp in the form of: YYYY-MMDDThh:mm:ss.sZ. Please consult the online Help for a full description of the Timestamp. (SHARED-52160) General Workflow fixes and enhancements l Additional Tooltips added to interface. (SHARED-54981) l Improved support for multiple IDs in Retrieve items task.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1607.html">PAGE 1607</a></h6>
<p>Known Issues Issues with Microsoft Edge browser The Microsoft Edge browser fails to display web pages when the Workflow's CORS option (in the HTTP Server Input 2 section) is set to "*". This issue will be resolved in a future release.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1608.html">PAGE 1608</a></h6>
<p>GoDaddy Certificates When installing Connect offline, dialogs allow installing the GoDaddy certificates. Most users should use the default settings and click Next. In some cases, however, this may not work correctly. For this reason those users should activate Place all certificates in the following store and then select the Trusted Root Certification Authorities as the target certificate store. MySQL Compatibility After installing Connect 1.8 a downgrade to a Connect version earlier than Connect 1.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1609.html">PAGE 1609</a></h6>
<p>l Generic PS LEVEL2 (DSC compliant) l Generic PS LEVEL2 (DSC) External Resources in Connect There are certain limitations on how external resources can be used in Connect. For example if you want to link a file (e.g., CSS, image, JavaScript etc.) from a location on the network but you do not want to have a copy of the file saved with the template you need to do the following: 1. The resource must be located where it can be accessed by all Servers/Slaves run as users.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1610.html">PAGE 1610</a></h6>
<p>Colour Model in Stylesheets The colour model of colours defined in a stylesheet can sometimes change after editing the stylesheet. This is a known issue and will be addressed in a subsequent release.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1611.html">PAGE 1611</a></h6>
<p>Print Limitations when the Output Server is located on a different machine The following limitation may occur when using the Print options from a Designer located on a different machine to the Output Server: l l l The file path for the prompt and directory output modes is evaluated on both the client AND server side. When printing to a network share it must be available to BOTH the Designer and Server for the job to terminate successfully.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1612.html">PAGE 1612</a></h6>
<p>Once you have done this, PlanetPress Connect 1.7.1 will become available for download. From Connect Version 1.2 onwards, the newer version of the Update Client was included with the Connect installation. Updating stand-alone Workflow Messenger installations If Workflow Messenger were installed stand alone, with no other Workflow components installed, the Update Client will be unable to find the Messenger component and thus it will not automatically update to the Workflow 8.7 version.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1613.html">PAGE 1613</a></h6>
<p>Connect 1.7.1 General Enhancements and Fixes Template Reports added to Connect Generate a report in PDF format containing the most important information about your template. The report lists contexts, sections, master pages, scripts, the data model, graphic files, and any other resources used, along with their properties. This report can be added as part of your project documentation.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1614.html">PAGE 1614</a></h6>
<p>Document Properties Document Properties can now be added to both Templates and DataMapper Configurations. This allows you to specify properties such as the document author, the customer name and other important references. You can also add custom key/value pairs. The respective properties can be retrieved in scripting and are thus available as content in your documents. The information is also included in the Template Report feature.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1615.html">PAGE 1615</a></h6>
<p>"Enhance with Connect" option added for PDF files in Windows Explorer A Windows Explorer context menu entry "Enhance with Connect" has been added for PDF files. When a user selects this context menu entry, PlanetPress Connect Designer opens with a prefabricated template, that uses the selected PDF file as the background. (SHARED15350/47156) Support added for Remote HTML and JSON Snippets In PlanetPress Connect 1.7.1 we introduce the concept of remote snippet resources.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1616.html">PAGE 1616</a></h6>
<p>Handling Nested Detail Data Simplifying the handling nested detail data has been on our agenda for some time. As part of our research into this we have looked at an approach that repeats table rows for nested detail data. This doesn’t create HTML tables in HTML tables but rather clones a base row specified for each level. Consider the following image: At this stage there is no user interface to configure this type of dynamic table but in a separate Technical article.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1617.html">PAGE 1617</a></h6>
<p>Installer improvements l l The PlanetPress Connect 1.7.0 installation did not work on machines running Windows 10 build 1703 (i.e. the "Creators Update", released March 2017). This has been fixed for PlanetPress Connect 1.7.1. (SHARED-56800) The silent installation process has been enhanced, and now supports the following: l l l l l l Setting the repository. This can be configured via the "product.repository" entry in "install.properties".</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1618.html">PAGE 1618</a></h6>
<p>Connect 1.7.1 Designer Enhancements and Fixes Edit and Save CSS, HTML, JavaScript and JSON files within the Designer Ever needed to quickly edit an external CSS, HTML, JavaScript or JSON file? The PlanetPress Connect 1.7.1 Designer now allows you to open and save these file types via the File menu. (SHARED-42094) Data Model Panel Enhancements Various enhancements have been made to the Data Model panel.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1619.html">PAGE 1619</a></h6>
<p>Improved Customization of the Designer interface Customize your interface by selecting your own colours for object edges, margins, guidelines, etc.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1620.html">PAGE 1620</a></h6>
<p>Guideline behaviour improved Along with visible/invisible settings, Guidelines can now be locked in place or set to snap to objects, using the new Guides option in the View menu. (SHARED-47159). Warning now displayed when opening templates created in an older version When PlanetPress Connect opens an older template file it is automatically migrated to the template structure of the current version.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1621.html">PAGE 1621</a></h6>
<p>These Warnings can be switched on again at any time thereafter, via the "Reset All Warning Dialogs" button in the General Preferences dialog. (SHARED-16962) Option to automatically Delete a dynamic table when the table is empty An option has been added to allow you to automatically delete a dynamic table when the data table is empty. To do so, select the entire table, and then tick the "Hide when empty" checkbox in the Attributes panel.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1622.html">PAGE 1622</a></h6>
<p>Replace elements with data-insert-location when inserting HTML elements When inserting an element from an Insert dialog, Connect now checks the data-insertplaceholder attribute. The value of the attribute is then used to set the default value for the Insert Location option within the Insert dialog. If the attribute is not found, things behave as in previous versions. This ticket also introduces the Replace option for the Insert Location drop down.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1623.html">PAGE 1623</a></h6>
<p>Scripting improvements l Context menu added to the Edit Script dialog. (SHARED-45381) . l l l l Find and Replace functionality has been added to Script editors. (SHARED-48424) New menu option to rename Scripts or Folders has been added to the Context Menu within the Script panel. (SHARED-48607) Support added for copy and paste of folders and scripts within the Scripts panel.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1624.html">PAGE 1624</a></h6>
<p>General Designer improvements l l l l l l l Duplicate and Delete line(s) using shortcuts in the Stylesheet, JavaScript and HTML editors. Use Ctrl+D to duplicate and Ctrl+Shift+D to delete the currently selected lines. (SHARED-46928) Entering geometry values without stating a specific unit type will now automatically assign the default unit type to the entry. (SHARED-50656) When deleting an element (such as a Barcode or a Chart) on a page, a check will now be made for associated scripts.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1625.html">PAGE 1625</a></h6>
<p>Capture OnTheGo (COTG) improvements l l l l l Two new form inputs have been introduced to facilitate the retrieval of the document ID and the store ID. (SHARED-53987/54054) Improvements made to updating the COTG library within existing templates. The user will now be prompted as to whether they wish to switch to the new version or not.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1626.html">PAGE 1626</a></h6>
<p>Connect 1.7.1 DataMapping Enhancements and Fixes DataMapper can now fetch or update data from remote sources New in PlanetPress Connect 1.7.1 is the ability to create an XMLHTTPRequest object (aka XHR) in DataMapper scripts in order to issue REST/AJAX calls to external servers. This feature allows the datamapping process to complement the extraction process with external data, including data that could be provided by a HTTP process in Workflow.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1627.html">PAGE 1627</a></h6>
<p>This yields two immediate and major benefits: l l Data Extraction is much faster since you are only extracting the records you actually want The database will not be cluttered with useless records (potentially numbering in the thousands) that you were not going to use anyway. As a consequence, the automated clean-up process will have much less work to perform when the time comes to delete obsolete entries from the database. This should result in a lighter workload and better overall performance.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1628.html">PAGE 1628</a></h6>
<p>the record will still be stored in the database, with un-extracted fields being assigned whatever default value (if any) you defined for them. So if your goal is to completely prevent unwanted records from being stored in the database, you should make sure to implement your filtering conditions early in the data mapping process.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1629.html">PAGE 1629</a></h6>
<p>General DataMapper Enhancements and Fixes l l l l l XML Wizard: option added to extract Attributes and to set boundaries on Attribute changes. (SHARED-42251) Improved support for UNC paths to image files. (SHARED-44316) The Extradata fields are now available in the DataMapper to more easily allow setting of field default values. The display of the Extradata fields can be toggled on or off directly from the Data Model panel. (SHARED-51426) New data.findRegExp() function added.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1630.html">PAGE 1630</a></h6>
<p>This means that, apart from straightforward cases where we are grouping with or without sorting, it is also possible to create combinations where some fields do alter the sort order and others have no effect. Please note that grouping without sorting also means that any documents that have the same value for the same grouping field (i.e., customer number in the example above), but which are not consecutive in the input data, will not end up in the same group.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1631.html">PAGE 1631</a></h6>
<p>Additionally, some settings on the Imposition Options page affect the way that booklets are created. These settings are now editable, so settings such as the gap between pages can now also be set for booklets.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1632.html">PAGE 1632</a></h6>
<p>Additional Postal Services Barcodes added to Output Creation Barcodes for postal services are excellent candidates for adding during the Output Creation steps, rather than during Content Creation. Reasons for this include: l l l They often cannot be added during Content Creation because they depend on document size (or weight) and on a sort order that is determined during Job Creation. They need to go in a fixed position, dependent upon the envelope window, rather than document design.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1633.html">PAGE 1633</a></h6>
<p>The new barcodes include: l Australia Post 4 State l KIX Code (Dutch postal service - Post.NL) l Royal Mail (UK) l Royal Mail 2D (UK) l USPS IMB (US) l USPS IMPB (US) Some of these barcodes have specific requirements in order for them to be usable. The respective postal services provide specifications and sometimes also the tools for generating the content of these barcodes. The checksums needed for Australia Post 4 State and IMPB are calculated automatically.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1634.html">PAGE 1634</a></h6>
<p>Job Output Mask improvements, to simplify working with output file names We have improved the way that output file names can be specified. A new dialog box has been added to the Print Wizard, to simplify the creation of Job Output Masks. While it is still possible to directly type a file name with placeholders in the Output File Mask box, it is now also possible to use the dialog to pick the metadata fields and other variables that can be used to create dynamic file names.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1635.html">PAGE 1635</a></h6>
<p>For the Output Preset to know what metadata is available, you can select a Job Preset when creating or modifying an Output Preset: In the Advanced mode of the Print Wizard this new dialog works a bit different, because the metadata can be directly edited in the same wizard instead of having to refer to a Job Preset. Tray Mapping for Multiple Templates For printing to a cutsheet printer, the Output Preset allows mapping of media defined in a template to trays and media known by the printer.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1636.html">PAGE 1636</a></h6>
<p>such a way that no conflicting tray mappings can occur within a job, as Job Presets allow filtering by media type. Print Output l Improvements made to the Print Wizard These include: l Improved usability in Inserter dialog. (SHARED-38279) l Data Filtering dialog usability improved.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1637.html">PAGE 1637</a></h6>
<p>Workflow 8.7 Enhancements and Fixes Custom Task descriptions The Comments section of each Workflow Task can now be used as the task's description in the Workflow Configuration tool, allowing users to better document the process without having to resort to numerous Comment Tasks. (SHARED-39120) Workflow processes can sometimes become rather complex and thus they require some documentation in order to allow subsequent users to know why they were implemented in one fashion or another.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1638.html">PAGE 1638</a></h6>
<p>reason (reprints, produce additional jobs, etc.), you will have to perform the data mapping configuration from scratch. So make sure you only tick the box for true one-off jobs. (SHARED48956/56420) Retrieve Items task now has a JSON Output option The Retrieve Items task can now output the results of its query as a JSON string instead of storing them within the metadata. This allows easy handling of the results either through Workflow Scripting or directly in the Designer.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1639.html">PAGE 1639</a></h6>
<p>Note The "Test SMTP Settings" does not work when using TLS. This limitation will be addressed in a later release. General Workflow fixes and enhancements l l l l l l l l l l Improved datamapping speed when outputting records in metadata. (SHARED-38455) Improved performance when creating metadata after Content Creation. (SHARED47150) Processing a Secure PDF as passthrough through CreatePDF will retain the Security options.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1640.html">PAGE 1640</a></h6>
<p>Known Issues Issues with Microsoft Edge browser The Microsoft Edge browser fails to display web pages when the Workflow's CORS option (in the HTTP Server Input 2 section) is set to "*". This issue will be resolved in a future release.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1641.html">PAGE 1641</a></h6>
<p>MySQL Compatibility After installing Connect 1.7.1 a downgrade to a Connect version earlier than Connect 1.3 or to a MySQL version earlier than 5.6.25 is not seamlessly possible. This is because the database model used in Connect 1.3 and later (MySQL 5.6) is different to that used in earlier versions. If you need to switch to an older version of Connect / MySQL, it is first necessary to remove the Connect MySQL Database folder from "%ProgramData%\Connect\MySQL\data" before installing the older version.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1642.html">PAGE 1642</a></h6>
<p>do not want to have a copy of the file saved with the template you need to do the following: 1. The resource must be located where it can be accessed by all Servers/Slaves run as users. Failure to do this will cause the image to appear as a Red X in the output for all documents which were merged by engines which could not access the file. The job will terminate normally and the error will be logged. 2. The file must be referenced via a UNC path e.g.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1643.html">PAGE 1643</a></h6>
<p>Online Help Links Point to Introductory Page Context sensitivity for the online help is not yet enabled in Connect. All links and F1 calls point to the introductory page, where you can Search on keywords to bring up Help pages relating to the topic. Context sensitivity will be introduced in a subsequent release of Connect.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1644.html">PAGE 1644</a></h6>
<p>model. Fields of other types will not be updated in the database and no error will be raised. This will be fixed in a later release. Print Limitations when the Output Server is located on a different machine The following limitation may occur when using the Print options from a Designer located on a different machine to the Output Server: l l l The file path for the prompt and directory output modes is evaluated on both the client AND server side.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1645.html">PAGE 1645</a></h6>
<p>l Note that both PlanetPress and PlanetPress Connect Workflow come with a 30 day trial licenses by default. Updating from PlanetPress Connect 1.1 In order to upgrade from Connect Version 1.1 to Version 1.6.1 via the Update Manager it is necessary to install a new version of the Objectif Lune Update Client. The next time you run your current Update Client it will show that there is an update available for itself.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1646.html">PAGE 1646</a></h6>
<p>Reduced Memory Version Note This is not recommended for production. It is now possible to install PlanetPress Connect on a machine with a minimum of 2 GB of RAM. The PlanetPress Connect Designer will automatically detect whether it has been installed on a machine with less than 4 GB of RAM and default to only using one internal Weaver and one internal merge engine on that system. The Server will also run using internal engines.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1647.html">PAGE 1647</a></h6>
<p>OL Connect Send OL Connect Send is an application of two components. The first is a Windows printer driver and the second is a set of Workflow plug-ins. In its most basic form, OL Connect Send allows the transmission of print files over the Internet from any Windows Desktop application. OL Connect Send flavors OL Connect Send comes in three flavors. These are: l l l Free of charge: No license required; any user; any domain; no usage limits; no web interaction.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1648.html">PAGE 1648</a></h6>
<p>l Supply Chain: Inbound document processing, such as capturing inbound invoices or POs for publication in an ECM. Print to EDI for outbound documents such as invoices. For further information on Connect Send, please refer to the OL Connect Send website and standalone User Guide.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1649.html">PAGE 1649</a></h6>
<p>Connect 1.6.1 General Enhancements and Fixes Performance improvements l Changes to the handling of transparency in PDF backgrounds has not only cured some job failures, but has also led to substantial improvements to both output speeds and filesizes. (49680) l Improved processing speed for multiple large detail table documents. (47252/48537) l Improvements made to the clean-up processes, improving overall production speed. l Some memory leaks plugged, improving overall production speed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1650.html">PAGE 1650</a></h6>
<p>Connect 1.6.1 Designer Enhancements and Fixes General Designer improvements l Interface improvements such as inclusion of icons for different types of files (js and CSS). l Provided option to configure the script timeout period. (48639) l Minor issues with non-English language translations fixed. l l l l l l Display issues that were sometimes encountered when changing section background images have been fixed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1651.html">PAGE 1651</a></h6>
<p>Connect 1.6.1 DataMapping Enhancements and Fixes l Support for Regular Expressions added to database searches. (51694) l Improved Datamapping process reliability. l Improved data record reliability when handling large jobs (those in excess of 50,000 records). l Improved PDF extraction avoids character duplication. l Improved marking of data fields in extraction steps. l l l l l New option added to support multibyte (variable length) encoded data such as Big5, GBK, UTF-8 and Shift-JIS.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1652.html">PAGE 1652</a></h6>
<p>Email Output l l l Fixed issue with the email Subject field not being encoded properly when using characters other than Latin characters. (48781) To improve privacy certain Meta tags that were embedded in the output email HTML have been removed. These include "email-reply-to", "email-from", "sender-name" and "sender-address". (49864) The Date field was not always included in the email header. This has been fixed and the Date field should now be present in all email headers.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1653.html">PAGE 1653</a></h6>
<p>Connect Workflow 8.6 Enhancements and Fixes General improvements l l l l l l l l A multitude of changes and enhancements made to support new OL Connect Send functionality within Workflow. Support for password protection added to "Create PDF" task. (48380) Generic Data Repository field length extended beyond previous limit of 32 characters. (47734) Added new "Create PDF Preview" task for lightning fast creation of single record PDF. (49497) Minor issues with some language translations fixed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1654.html">PAGE 1654</a></h6>
<p>l l Fixed potential out-of-memory error with very large Workflow configuration files. (51621) Fixed crashes encountered when large numbers of data selection calls were issued in highly threaded processes. (50569) HTTP and SMTP Server improvements l Support added for cross-origin HTTP (CORS HTTP) requests, to facilitate the development and testing of web templates. (47014) l Added option to specify SMTP port number in "Create Email Content" task.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1655.html">PAGE 1655</a></h6>
<p>Known Issues Installing OL Connect Send on a machine with Connect installed. When OL Connect Send Plug-Ins are installed (either standalone or via a Workflow installation) on the same machine as Connect, an interference between OL Connect Send's internal Database and that of Connect may occur, which will block a browser popup on that same machine. This issue can be fixed by applying a startup wait to the Connect Server Service.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1656.html">PAGE 1656</a></h6>
<p>1. Go to the .ini files for the Designer and Server Config: l l C:\Program Files\Objectif Lune\OL Connect\Connect Designer\Designer.ini C:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.ini 2. Change the language parameter to the required one under Duser.language=en | es | de | fr | it | ja | pt | tw | zh Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1657.html">PAGE 1657</a></h6>
<p>To add additional printer models click on the settings entry box. button next to the Model selection Note that the descriptions of some of the printers were updated in version 1.2 meaning that if you had version 1.n installed, you may find that the same printer style appears twice in the list, but with slightly different descriptions.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1658.html">PAGE 1658</a></h6>
<p>Using Capture After Installing Workflow 8 If PlanetPress Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, Capture can no longer be used within Workflow 7. The plugins are now registered uniquely to Workflow 8 and the messenger for Workflow 7 is taken offline. It is only possible to use Capture from PlanetPress Connect Workflow 8 thereafter.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1659.html">PAGE 1659</a></h6>
<p>Merge\Weaver Engines when Printing The print operation in the Designer will automatically detect whether the Merge\Weaver engines are available and display a message for the user to retry or cancel if not. Once the Merge\Weaver engine becomes available and the user presses retry the print operation will proceed as normal.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1660.html">PAGE 1660</a></h6>
<p>l When printing via the Server from a remote Designer, the output file remains on the Server machine. This is remedied by selecting “Output Local” in the Output Creation configuration. Overview This document provides an overview of the new features and enhancements in PlanetPress Connect 1.5 and PlanetPress Workflow 8.5. Installing PlanetPress Connect 1.5 and PlanetPress Workflow 8.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1661.html">PAGE 1661</a></h6>
<p>Print Only Version A Print Only license is available with version 1.5 of PlanetPress Connect which allows legacy PlanetPress Suite 7 customers on OL Care to upgrade to Connect for a minimal fee. The license allows regular printing via the Print Wizard but runs Email and Web output in demo mode. For more information, please contact your local OL Customer Care or Sales team.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1662.html">PAGE 1662</a></h6>
<p>Simplified creation of templates based on existing PDFs l l l Option added to allow the creation of a new print document based on an existing PDF. (SHARED-19220) Improved support for adding PDF files as Section backgrounds. Files can now be referenced from disk or imported into Template. (SHARED-42496) Added support for drag and dropping Data Fields directly onto the page as absolutely positioned textboxes.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1663.html">PAGE 1663</a></h6>
<p>l l Barcode improvements made in Preview mode. Support added for resizing and dragging of absolute positioned barcode objects, as well as resizing of inline barcode objects. (SHARED-43641) Barcodes can now have transparent backgrounds. (SHARED-43659) Scripting improvements l l l l l New closest() command added to the Scripting API, to locate closest matching element above it in the Document Object Model (DOM) tree. (SHARED-41789) Script editing improved.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1664.html">PAGE 1664</a></h6>
<p>l l l l New scripting options have been added to the COTG.js library to register custom functions for save and restore. (SHARED-40670) Colour picker support has been added to the COTG Starter Template wizards. (SHARED-33561) Improved speed/size of COTG Camera objects. Rather than embedding images in output PDFs, Connect now supports embedding data URLs in COTG templates. (SHARED38575) Documents from the Library now automatically deleted upon successful submission.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1665.html">PAGE 1665</a></h6>
<p>Connect 1.5 DataMapping Enhancements and Fixes l l l l l Multiple Conditions step can now evaluate several conditions and branch out accordingly. (SHARED-14329/44435) Performance improvements made when extracting text from PDFs and spool files. (SHARED-43056) Improved default formatting when extracting Date, Float or Currency data fields. (SHARED-43415) An extra field is now appended to every Document record and to every Detail table inside that record.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1666.html">PAGE 1666</a></h6>
<p>l l l l l l l New HCF file added that supports “top down wrap around sequence marks”. (SHARED42326) Use PostScript Media name values in the PostScript DSC comments, to improve subsequent searches. (SHARED-42826) Option added to allow storing of job resources on PostScript printer’s own storage medium. (SHARED-43467) OMR marks improved, with support added for Match Numbers (Match Code, MC).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1667.html">PAGE 1667</a></h6>
<p>Connect 1.5 General Enhancements and Fixes Installer improvements l l Improvements made to installation robustness. The installer now copes better when encountered permissions issues during installation. (SHARED-43732/43737) The Update Client has been updated to 1.1.9 and has been included in both the Connect 1.5 and Workflow 8.5 installations.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1668.html">PAGE 1668</a></h6>
<p>Connect 8.5 Workflow Enhancements and Fixes l l l l l l l l l l Support for PHP-like arrays for COTG or web-based form submissions. (SHARED-41706) New Workflow system variable (%r) added to allow a process to determine which if it is currently running in service or debug mode. (SHARED-43411) Create Output and the Connect All In One tasks can now be added as Output tasks without waiting for the operation's result. (SHARED-43413) The Folder Capture task can now monitor multiple folders.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1669.html">PAGE 1669</a></h6>
<p>Known Issues Installation Paths with Multi-Byte Characters When installing the Chinese (Traditional or Simplified) or Japanese versions of Connect, if the user specifies an alternative installation path containing multi-byte/wide-char characters it can break some of the links to the Connect-related shortcuts in the Start Menu and cause an error to appear at the end of the installer. The workaround for the moment is to use the default installation path. The problem will be addressed in a later release.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1670.html">PAGE 1670</a></h6>
<p>model used in Connect 1.3 and later (MySQL 5.6) is different to that used in earlier versions. If you need to switch to an older version of Connect / MySQL, it is first necessary to remove the Connect MySQL Database folder from "%ProgramData%\Connect\MySQL\data" before installing the older version. PostScript Print Presets The print presets for PostScript were changed from Version 1.1 onwards meaning that some presets created in Version 1.0 or 1.0.1 may no longer work.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1671.html">PAGE 1671</a></h6>
<p>documents which were merged by engines which could not access the file. The job will terminate normally and the error will be logged. 2. The file must be referenced via a UNC path e.g., file:////w2k8r2envan/z%20images/Picture/Supported/JPG/AB004763.jpg l l UNC paths are required because the services will be unable to access mapped network drives (Windows security feature).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1672.html">PAGE 1672</a></h6>
<p>Context sensitivity will be introduced in a subsequent release of Connect.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1673.html">PAGE 1673</a></h6>
<p>VIPP Output Some templates set up with landscape orientation are being produced as portrait in VIPP. It can also sometimes be the case that text and images can be slightly displaced. These are known issues and will be addressed in a later release of Connect.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1674.html">PAGE 1674</a></h6>
<p>the download button in the dialog to install the new version of the Update Client. Note that it is no problem to run the update while the Client is open. It will automatically update itself. Once you have done this, PlanetPress Connect 1.4.n will become available for download. From Connect Version 1.2.0 onwards, the newer version of the Update Client was included with the Connect installation. Print Only Version A Print Only license is available with version 1.4.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1675.html">PAGE 1675</a></h6>
<p>Connect 1.4.2 Enhancements and Fixes Designer l l A blank page is no longer added to beginning of templates that use scripting to add pages from PDF files. This problem only appeared when saving to a new file from within Preview mode, or when generating output from Preview mode. (SHARED-44564) Image elements (<img>) referencing a PDF image would multiply when switching back and forth between Live and Preview modes, in both email and web contexts. This has now been fixed.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1676.html">PAGE 1676</a></h6>
<p>The language can be selected during the installation of Connect or via the Language Setting options in the Preferences dialog (note that Connect needs to be restarted in order to apply the selected language). At present only the Connect user interface has been translated. Error messages and warnings will be translated for a later release.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1677.html">PAGE 1677</a></h6>
<p>Welcome Screen Extended l l The Printer Definition Configs and HCF files available on the OL Connect website are now grouped by manufacturer, to simplify selection. Connect 1.4.1 also introduces Responsive Email Templates. Virtualisation l Connect is now supported on the Microsoft Hyper-V and Hyper-V/Azure environments as well as the VMWare Workstation, Server, Player and ESX infrastructure environments. Modifying Connect Installations l Connect 1.4.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1678.html">PAGE 1678</a></h6>
<p>Email Context l Email context sections can be enabled or disabled based upon data value. (SHARED33656) l Email port number can now be specified as part of the host name. (SHARED-38008) l New template wizard for Slate templates by Litmus. (SHARED-36843) Print Context l l Ability added to mirror margins on back pages of Duplex jobs, via Facing Pages selection added in Sheet Configuration dialog. (SHARED-40505) Can now suppress Master Page on duplex back pages, if there are no contents.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1679.html">PAGE 1679</a></h6>
<p>l l l Option to generate JSON string from data model fields to pass data record information to client side script. (SHARED-39337) CSS Class name completion suggests CSS classes based upon the current section. (SHARED-36870) CSS Style inspector allows full control over styles. (SHARED-22929) Connect 1.4.1 DataMapping Enhancements and Fixes l l l All fields can now be renamed through the Data Model view. (SHARED-40116) SQL Server data mapping can now use Windows Authentication credentials.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1680.html">PAGE 1680</a></h6>
<p>Connect 8.4.1 Workflow Enhancements and Fixes l l l l l Major performance improvements when updating data records. (SHARED-38897) Stand-alone Update Data Record task allows data records to be updated in the database without having to create content. (SHARED-38867) Update Records operations performed in batches, allowing for unlimited number of records. (SHARED-38948) All-In-One task can now return the output file to the Workflow, to allow customising output destination(s).</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1681.html">PAGE 1681</a></h6>
<p>Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up. GoDaddy Certificates When installing Connect offline, dialogs allow installing the GoDaddy certificates. Most users should use the default settings and click Next. In some cases, however, this may not work correctly.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1682.html">PAGE 1682</a></h6>
<p>Note that the descriptions of some of the printers were updated in version 1.2 meaning that if you had version 1.n installed, you may find that the same printer style appears twice in the list, but with slightly different descriptions. For example the following printer types are actually identical: l Generic PS LEVEL2 (DSC compliant) l Generic PS LEVEL2 (DSC) External Resources in Connect There are certain limitations on how external resources can be used in Connect.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1683.html">PAGE 1683</a></h6>
<p>Capturing Spool Files After Installing Workflow 8 If PlanetPress Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, the PlanetPress Suite 7 option to capture spool files from printer queues will no longer function. The solution is to use PlanetPress Connect Workflow 8 to capture spool files from printer queues. Colour Model in Stylesheets The colour model of colours defined in a stylesheet can sometimes change after editing the stylesheet.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1684.html">PAGE 1684</a></h6>
<p>l If the server is offline and you are not using Proof Print l On some occasions before the Print Wizard opens REST Calls for Remote Services The Server will now accept REST calls for all remote services and will make commands wait indefinitely until the required engines become available. The Server will log when it is waiting for an engine and when it becomes available. Note that there is no way to cancel any commands other than stopping the Server.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1685.html">PAGE 1685</a></h6>
<p>Knowledge Base You can find extra information in Connect Knowledge Bases which complement the information contained in this manual.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1686.html">PAGE 1686</a></h6>
<p>Legal Notices and Acknowledgements PlanetPress Connect, Copyright © 2019, Objectif Lune Incorporated. All rights reserved. The license agreements for the associated open source third party components can be found in the following installation folder: C:\Program Files\Objectif Lune\OL Connect\Legal Notices This application uses the following third party components: l l l l l l l l l Adobe PDF Library which is either a registered trademark or trademark of Adobe Systems Incorporated in the United Stat</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1687.html">PAGE 1687</a></h6>
<p>l l l l l l l l l l l l HyperSQL, Copyright © 2001-2010, The HSQL Development Group. All rights reserved. IcoMoon. Connect uses unmodified icons from IcoMoon (https://icomoon.io/#iconsicomoon) which have been made available under the Creative Commons By 4.0 license (https://creativecommons.org/licenses/by/4.0). ICU4J 4.4.2 Copyright © 1995-2013 International Business Machines Corporation and others. All rights reserved.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1688.html">PAGE 1688</a></h6>
<p>l l l l l l l l l l Logback which is distributed under the terms of the Eclipse Public License (EPL) Version 1.0. The source code for Logback can be obtained from the following location: https://logback.qos.ch/download.html Mchange Commons Java which is licensed under the terms of the Lesser General Public License (LGPL) Version 2.1. The source code can be obtained from the following location: https://mvnrepository.com/artifact/com.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1689.html">PAGE 1689</a></h6>
<p>l l l l Web Services Description Language for Java which is distributed under the terms of the Common Public License v 1.0. The source code for this can be obtained from the following location: http://wsdl4j.cvs.sourceforge.net/viewvc/wsdl4j/ XULRunner which is distributed under the terms of the Mozilla Public License Version 2.0. The source code for this can be obtained from the following location: http://ftp.mozilla.org/pub/mozilla.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1690.html">PAGE 1690</a></h6>
<p>l Apache Commons Pool l Apache Commons Text l Apache Commons Validator l Apache Derby l Apache Felix and dependencies l Apache Geronimo l Apache HttpClient Mime l Apache POI l Apache ServiceMix l Apache Xerces2 Java Parser l Apache XML Graphics l Apache XML Beans l Barcode4j l Google Collections l Google GSON l Hibernate Validator l Jackson JSON processor l Jetty l Liquibase l LMAX Disruptor l Objenesis l OpenCSV l OPS4J Pax Web l org.json.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1691.html">PAGE 1691</a></h6>
<p>Eclipse Technology: This Software includes unmodified Eclipse redistributables, which are available at www.eclipse.org. The Eclipse redistributables are distributed under the terms of the Eclipse Public License - v 1.0 that can be found at https://www.eclipse.org/legal/epl-v10.html. Java SE framework and platform: This application uses the Java SE framework and platform which is distributed under the terms of the Oracle Binary Code License Agreement for the Java SE Platform Products and Java FX.</p>
</li>
<li>
<h6><a class="text-decoration-none text-link fw-bold" href="/manual/objectif-lune/planetpress-connect/2019-2-english/page-1692.html">PAGE 1692</a></h6>
<p>Objectif Lune Inc.disclaims all warranties as to this software, whether expressed or implied, including without limitation any implied warranties of merchantability, fitness for a particular purpose, functionality, data integrity or protection. PlanetPress, PReS and PrintShop Mail are registered trademarks of Objectif Lune Inc.</p>
</li>
</ul>
</nav>
</div>
</section>
</section>
</main>
<footer class="page-footer">
<div class="container flex-column py-3 py-sm-4">
<div class="row mb-1 mb-sm-2 mb-md-5">
<a href="/" class="brand offset-sm-0 col-sm-4 col-md-3 col-lg-2 offset-2 col-8 text-center text-md-start"><img class="logo-small" src="/assets/img/brand-large.png" alt="Manualshelf"/></a>
</div>
<div class="row">
<dl class="text-center text-sm-start col-sm-3">
<dt class="fw-bold">Who We Are</dt>
<dd><a class="text-decoration-none" href="/about">About Us</a></dd>
<dd><a class="text-decoration-none" href="/company">Company</a></dd>
<dd><a class="text-decoration-none" href="/careers">Careers</a></dd>
<dd><a class="text-decoration-none" href="/terms">Terms & Privacy</a></dd>
</dl>
<dl class="text-center text-sm-start col-sm-3">
<dt class="fw-bold">Resources</dt>
<dd><a class="text-decoration-none" href="/brands">List of Manufacturers</a></dd>
<dd><a class="text-decoration-none" href="/">Support</a></dd>
<dd><a class="text-decoration-none" href="/press">For the Press</a></dd>
<dd><a class="text-decoration-none" href="/press#assets">Media assets</a></dd>
<dd><a class="text-decoration-none" href="/faq">FAQ</a></dd>
</dl>
<dl class="text-center text-sm-start col-sm-3">
<dt class="fw-bold">Get in touch</dt>
<dd><a class="text-decoration-none" href="#">Blog</a></dd>
<dd><a class="text-decoration-none" href="#">Email</a></dd>
<dd><a class="text-decoration-none" href="/dmca">DMCA</a></dd>
</dl>
</div>
<div class="row">
<div class="text-center text-sm-start col-sm-4 pe-sm-0">
<a href="https://www.facebook.com/pages/ManualShelf/1488826334681423" class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-facebook-f"></i></a>
<a href="https://www.twitter.com/ManualShelf" class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-twitter"></i></a>
<a href="https://plus.google.com/+ManualShelf" class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none me-2"><i class="fab fa-google-plus-g"></i></a>
<a href="http://www.pinterest.com/ManualShelf" class="fs-5 text-center d-inline-block social rounded-2 align-middle text-decoration-none"><i class="fab fa-pinterest-p"></i></a>
</div>
<div class="col col-sm-8 d-flex flex-column align-items-center flex-sm-row flex-wrap flex-sm-nowrap justify-content-center justify-content-sm-end">
<div class="copy w-auto d-flex align-items-center justify-content-center justify-content-sm-end mt-2 mt-sm-0 me-2">ManualShelf © 2013-2024</div>
<select class="form-select form-select-sm w-auto mt-2 mt-sm-0">
<option value="usa">USA</option>
</select>
<div>
</div>
</div>
<!-- /22287960372/pixel -->
<div id='pixel'>
<script>
googletag.cmd.push(function() { googletag.display('pixel'); });
</script>
</div>
</footer>
<!-- JavaScript -->
<script src="/assets/js/jquery-3.3.1.min.js"></script>
<script src="/assets/js/bootstrap.bundle.min.js"></script>
<script src="/assets/js/jquery.autocomplete.min.js"></script>
<!-- Support code -->
<script type="text/javascript">
$.extend({
redirectPost: function(location, args) {
var form = '';
$.each(args, function(key, value) {
form += '<input type="hidden" name="' + key + '" value="' + value + '">';
});
form = '<form id="s1" action="' + location + '" method="POST">' + form + '</form>';
$(document.body).append(form);
$("#s1").submit();
}
});
$(document).ready(function(){
$("#query").autocomplete({
minChars: 3,
groupBy: 'type',
paramName: 'q',
dataType: 'json',
serviceUrl: '/autocomplete',
noCache: true,
showNoSuggestionNotice: true,
noSuggestionNotice: 'Zarro results found',
onSelect: function (suggestion) {
$.redirectPost(suggestion.data.url, {highlight: encodeURIComponent(JSON.stringify(suggestion.data.hls))});
}
});
var toc = $('.toc-selector');
if (toc.length) {
var slideParams = { duration: 800, easing: 'linear' };
toc.click(function() {
$(this).toggleClass('open');
var section = $('.toc-content');
var isCollapsed = section.attr('data-collapsed') === 'true';
if (isCollapsed) {
section.slideDown(slideParams)
section.attr('data-collapsed', 'false')
} else {
section.slideUp(slideParams);
section.attr('data-collapsed', 'true')
}
});
}
});
var lastSmall = $(window).width() < 576;
$(window).resize(function() {
var newSmall = $(window).width() < 576;
if (lastSmall != newSmall) {
lastSmall = newSmall;
window.location.href = window.location.href;
}
});
</script>
</body>
</html>
