OL Connect Release Notes 2025.1.1

License Update Required for Upgrade to OL Connect 2025.x

From OL Connect 2019.1 onwards, only customers with a current OL Care subscription will be able to update OL Connect.

Every OL Connect license now contains an end date that represents the last day of OL Care coverage for each customer. Upgrades and updates of OL Connect will be freely available up until that end date, but will not be available thereafter, unless the OL Care period is extended.

This licensing model requires anyone upgrading from OL Connect versions earlier than 2019.1 to first update their OL Connect License. A dialog box appears as part of the OL Connect upgrade process requesting that you do this.

It is recommended that you first update the OL Update Manager, as newer versions of the Update Manager can update your OL License to the required version.

For further details on how to upgrade the OL Update Manager to the latest version and update your OL Connect License see the Update Manager 1.9 - Upgrade Guide.

If issues arise, or if you need to renew your OL Care subscription, please contact your local Customer Care group.

Backup before Upgrading

It is recommended that you always backup your existing OL Connect preferences before upgrading to a new version. This will enable you to revert back to the previous version, in a worst case scenario in which the new version introduces issues with your existing production processes. Whilst the probability of such a worst case scenario is remote, it cannot hurt to take some simple precautions, just in case.

For instructions on how to do so, please see Backup existing OL Connect version.

Overview

This document provides an overview of the new features and enhancements in OL Connect 2025.1 and Workflow 2025.1, as well as some important installation information.

Installing OL Connect 2025.1 and Workflow 2025.1

• OL Connect is released as a 64 bit version only (with the exception of the Workflow, Fax, Search and Imaging modules).
• Full details on installing and licensing OL Connect and Workflow can be found in the online helps.
  OL Connect: Installation and activation.
  OL Connect Workflow: Workflow Installation.
• Note that both OL Connect and Workflow come with a 30 day trial license by default.
• It is recommended that you install and use OL Connect Designer and Server under the same user account.

OL Connect and Workflow installers require Administrator rights

Please note that the OL Connect and Workflow installations can only be run by users who have Administrator rights.

OL Connect templates used in Workflow

For improved performance we recommend re-saving any OL Connect templates used in Workflow to the current version of OL Connect templates.

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 OL 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.

OL Connect 2025.1.1 Improvements

 

During the OL Connect 2025.1.0 partner preview the following issues were discovered:

• An issue was discovered where if PDF security options were used in the Output Preset, some links within the output PDF would not work. This has been fixed in the 2025.1.1 release. (94542)

• An issue was discovered with PlanetPress Suite documents containing PNG images with transparency. These would show some slight differences in output. This has been fixed in the 2025.1.1 release. (95096)

OL Connect Improvements

Windows Server 2025

OL Connect and OL Connect Workflow are now officially supported on Windows Server 2025. (95106)

OL Connect general improvements

• Added ability to force using the default port in the database connection Preferences. This allows you to connect by Instance name when using a Microsoft SQL Server as your back-end database. (92236)
  
  

• Support added for turning Windows authentication on and off for Microsoft SQL Server back-end database connections. (92247)
  
  

• Improved stability for better detection of licensing problems. (92497)

• Fixed an issue where in certain scenarios no data would initially be available in the Designer after opening a data mapping config, unless you also refreshed (synchronized) the data model. (92652)

• Installer now does an extra validation to prevent the Connect server from being configured to run as one of the built-in Windows service accounts, which is unsupported by Connect. (92923)

• Fixed an issue with the custom database preferences set by the installer not using the proper delimiter. (93730)

• Improved Context Sensitive Help for a number of dialogs. (93847\93859)

• Several improvements made to interface localisation. (93996)

• The Logging Preference rollover policy was not being applied to the licence logs. This has now been fixed. (94012)

• Resolved issue with Preferences being incorrectly updated or even deleted when upgrading Connect. (94242)

Architectural Software Updates

• Removed Microsoft VBScript dependencies from OL Connect. (93724)

• Replaced older Eclipse j2v8 with Javet. (93864)

Security improvements

• Third party libraries updated to more recent versions. (94136/94221)

OL Connect REST API improvements

• If a jobOutputFolder parameter is specified for an All-In-One print operation, the pre-output test print will now use the value of the parameter specified instead of the default value. (94353)
• The Rasterize File REST API endpoint now supports the conversion of XPS files. (94597)
• Document set properties are now included in the JSON Job Statistics structure returned from the Job Statistics REST API endpoint, when a level mode of documentSetOnly or documentSetAll is specified. (94716)

• Creating too many REST API calls could cause a Stack Overflow, which would require restarting the Server to resolve. This has been fixed. (94723)

• Improved security by removing hard coded default credentials from some PowerShell commands used in the REST API Cookbook. (94881)

• Rate limiting has been added to REST API authentication to reduce the risk of malicious parties attempting a brute force attack. (94883)

OL Connect 2025.1 Designer Improvements

Improved support for editing non-Connect resources

Double-clicking a resource file in the resources panel for which the Designer does not have a built-in editor now pops up a dialog, which allows you to open that resource file in the default application associated with that file type, directly from within Designer. (90440)

For example, double-clicking an image resource in the Resources. If the Designer doesn’t have a built-in viewer for the file type, a prompt will appear, allowing you to open it in the default application. This allows you to not only view the image but also make edits that are saved directly to the file in the template.

Section Cloning Wizard improvements

• Cloned sections no longer require unique names. (93973)

• The Section Cloning Wizard now lets you set section clone names based on a data field, such as an insurance policy name. This makes it easier during the design phase to quickly find and view a specific section in Preview mode, helping you validate the content presentation or check the results of certain business rules. (94772)

• The Section Cloning Wizard now inserts expressions that work with the detail record context, reducing the need to rewrite or remember the correct syntax.

  Note: Only supported in the wizard, not in raw scripts.

Copy Data Model

Options added to the context menu of the Data Model view allowing you to copy the model of the current template/data mapping configuration.



These copy a JSON representation of the data model to the clipboard. This makes it easier to generate sample data using AI tools like ChatGPT and Microsoft Copilot. Simply copy the model, then paste it into the AI and request one or more sample records. (94114)

Learn more about streamlining template design with AI: https://olresourcecenter.uplandsoftware.com/blog/streamlining-template-design-with-ai/

Insert image through insertion point

The Image Insert dialog now includes an Insertion Point option, which inserts the new image at a specific position. (92004)



In previous versions, images were always added as inline elements, requiring manual steps to move them to the correct location or place them in an absolute position. This now vastly simplifies that process.

General Designer improvements

• The ability to create additional copies of records in the DataMapper is a powerful feature that was introduced in a previous version. However, until now, the results could only be viewed by generating output. We have now made the copies visible and browse-able within the Data Model so you can preview them directly in the Designer.

• Clicking on an absolute positioned image element will now trigger the box selection mode directly. (90602)
• When a Data Model field is drag and dropped outside the page margins an absolute positioned box is created. If you resized that box to be smaller than the contents within, the text would overflow outside the box. This is no longer the case. The box now behaves similar to a regular absolute positioned box that can be inserted from the toolbar. (91170)
• Fixed an error in the Data Model for the last record, when the number of records to be displayed is limited. (91302)
• Fixed issue with buttons disappearing after Expand All selected in Data Model. (91576)
• Remote content is no longer cached while editing a template in the Designer. (91620)

• The JSON sample data has been simplified and improved. (91788)

• Support added for "Alt+arrow up" and "Alt+arrow down" keyboard shortcuts to both script source and JSON sample data editors. (92463)
• Added support for zooming in and zooming out using the CTRL + '+' and CTRL + '-' keys in the script source and JSON sample data editors. (92479)
• Fixed an issue with the display of filtered results in the Data Model view. (92965)
• If the main editor is read-only we have made sure you can still scroll in the Attributes panel and view and copy-paste values. (93118)
• You can now browse through copied data in the Data Model view. (93204)
• You can now define the encoding used in external files imported in to the DataMapper or Template. (93372)
• When importing from Word we now substitute the font “Aptos” (a proprietary cloud font that cannot be used by a browser) with the more general “Calibri”. (93417)
• Fixed a cosmetic issue where the Data Model view would keep showing a “Copies” label even after closing the DataMapper config editor. (93652)
• Prevented excess error logging by the barcode library. These would appear in the Designer messages panel and could cause confusion. (93685)

• Inserting a barcode on a Master page will now only insert a script if the active section does not have Handlebars enabled. If the section has Handlebars enabled a Handlebars expression will be used in the barcode box. (93862)

• Any changes made in the Source tab to the inner HTML of an (empty) article for shared content are now assumed to be unintentional and will be ignored. (93978)

• Fixed an error that was encountered when switching a cloned section between Preview and Source modes. 93994)

• When dragging a data field to a cloned section that uses a detail table as the context for Handlebars, the expression is adjusted accordingly. (94001)

• When you create a package to be sent to Workflow or saved on disk and you try to add a resource with a name that is already in the package you will now get a dialog asking if you want to overwrite the file in the package with the new one. Prior to this change you could have two files with the same name but when the package file was saved an error would occur. (94095)

• Fixed some issues with nested tables that include Handlebars expressions. (94361/94362)

• Fixed an issue where master page objects where positioned incorrectly on the section page when the top and left bleed were set to different values. (94398)

• Fixed an issue with Dynamic Image Scripts when the Folder on disk location option was used with an empty path. Previously this caused the base path to use the path of the Designer application. Now it will use an empty path as the base path.
  Additionally a validator was added to that Path field to disallow relative paths and accept only absolute paths.
  This validator was also added to the Dynamic Background Script. 94549)

• Improved text font size changes implemented through Format dialogs. (94550)

• When the Duplex checkbox in the Sheet configuration dialog gets checked we now set the Allow content on fields to All sides. If it gets unchecked, we set it to Front Only. (94551)

• Applying text alignment within a Positioned box no longer wraps content in a new inline <div> element. (94554)

• Fixed an issue with the script debugger that may occur if a run is aborted and Handlebars are not used. (94566)

• Improved support for Handlebars expressions in src or href attributes. We URL-encode the expression result by default, but this can now be disabled using a triple-stash. (94595)

• When selecting an Absolutely positioned table through the 'breadcrumbs' section and then choosing the Table… option, none of the fields within the Table Properties dialog were set. This has now been fixed. (94645)

• Improved the importation of new tabular data into Templates already linked to a data file. (94720)

• Fixed an error that may occur when applying styles like bold and italic to text in a positioned box. (94811)

• Fixed an issue introduced in 2024.2 that prevented page-break-before or page-break-after styles from having any effect when applied to an element inside a table. (95132)

• Fixed an issue where references to empty Handlebars partials would produce an error instead of the reference being replaced with an empty string. (95262)

OL Connect 2025.1 DataMapper Improvements

Improved handling of control characters in DataMapper configuration fields

• Improved stability of configuration scripts containing special characters. (90417)
• Prompt when saving configuration files with invalid characters. (93412)

General DataMapper Improvements

• Added support for Unicode surrogate pairs to ensure proper extraction of extended Unicode characters in text data file processing. (57312)
• Improved JavaDoc handling in the post-processor script engine of DataMapper. (90673)
• In XML data mapping configurations, extraction fields based on Location now have their XPath property validated to make sure they are not empty. (91393)
• Improved action to rename multiple fields in DataMapper extraction step. (91525)

• Improvement of jsonpath default selection when adding repeat step to JSON data. (91585)

• We now check whether font files referenced by user Fontmap files actually exist. (91802)
• Improved use of the selected field in the appropriate view of the Extraction step. When selecting any field from the Field List dropdown, the Data Model now highlights the corresponding field and scrolls it into view if it isn’t already. 92262)
• The actions skip to next record and stop datamapping are now available in the DataMapper script engine as functions. This reduces the need for additional Condition and/or Action steps. (92289)
• An error will now be shown when the Sheet field is empty in an Excel input data settings. (92388)
• The lowest version that the DataMapper configuration can now be saved as is version 1.8. (92443)
• Fixed an issue where printing using a JSON based DataMapper configuration with a data file that used an encoding other than UTF-8 would generate an error. (92622)
• Improved property management for automation.properties.OriginalFilename, which is based on the filename stored in the OL Connect database. (93092)
• Improved the efficiency of text searching and implemented infinite loop detection in the PDF skip to the next occurrence step. (93146)

• Database ID allocation has been improved to reduce database traffic and also avoid potential ID allocation conflicts. (93459)

• Fixed the exception message when loading empty XLSX files from the DataMapper wizard with the ‘First row contains field names’ option enabled. (93774)

• Fixed mistaken error message that appeared after setting ODBC boundaries in the DataMapper. (93827)

• An issue was discovered when using certain AFP files through the DataMapper, whereby Type 1 CID fonts were not being extracted properly. This has been fixed in this release. (94701)

• Improved performance for tabular input when using an "on script" trigger for boundaries. (94885)

OL Connect 2025.1 Output Improvements

LPR print Improvements

• Multiple simultaneous LPR connections could cause failures, and then those failed jobs could mistakenly removed.
  We now move files to a printservice folder and add an LPR job to an internal task queue. This reduces the possibility of failures due to multiple simultaneous connections. And if the LPR fails the job will now be moved to the printservice/error folder. (86245)

• LPR Queue Timeout and Retry Attempts are now configurable in the Print Options page. (94461)
  
  
  

Controlling the Title value in PostScript output

Added capability to control the %%Title value in PostScript output.

The %%Title field is often used by printers to display as the job name in the printer controller. With this change OL Connect users no longer need to rely on automation tools (such as Connect Workflow) to modify the field. (94073)

Prompt for Printer Properties in all Connect versions

For OL Connect Desktop users, the "Prompt for Printer Properties" feature allows users to submit print jobs through the printer driver and modify finishing options (such as orientation, simple or duplex, color, & etc.) within Connect Designer.

This functionality has now been extended to OL Connect Professional and Enterprise editions, enabling users to handle ad-hoc jobs more efficiently directly within Connect Designer. (94294)

Print Wizard\Preset enhancements

• External sort metadata is now catered for in the Job Output Mask in the Print Options page of the Output Preset and Print Wizards along with the job output mask dialog. (92784)
  
  

• Increased the number of fields that can be supported in job creation grouping. (93589)

• Fixed an issue that was preventing dynamic PPD based output presets from being loaded into the Output and Print Wizards. (94250)

• Fixed display issue when switching between PDF and non-PDF printer models in the Print Options Page of the Output and Print Wizards while the output type is set to windows printer. (94670)

General Output Improvements

• Fixed an issue with loading images when the user profile location contains characters outside the US-ASCII range. (93453)
• Fixed an issue with batched pagination that could cause the output to contain blank content if the output for a single record consisted of more than 15 pages; one of the top-level elements spans multiple pages; and that element happens to intersect a page range boundary for batched pagination (every 15 pages by default). (94516)
• Improved behavior when the user running OL Connect has Unicode characters within their name. (94657)

Email Output Improvements

• Fixed an issue where the “Do not inline styles” option would still inline CSS style rules on elements. (94637)

  Note: This might affect existing jobs. Particularly if you were inadvertently using the "Do not inline styles" option, but actually wanted the "Apply CSS properties to elements" behavior.

Print Output Improvements

• Fixed an issue that could cause missing pages in output if a single record produces more than 15 pages of content and a post pagination script calls merge.section.paginate. (93714)

• Prevent entry of characters in the Job, Output and Print Wizards that are not valid according to the XML 1.0 specification. (94000)

• Fixed an issue where (in certain edge cases) repagination from a post pagination script could produce overlapping master pages. (94025)

• Additional Content now supports text patterns with hexadecimal and Unicode escaped characters. For example: ${"\x41"} (94465)

• Fixed an issue that could occur in some edge cases when “Omit Master Page Back in case of an empty back page” was turned on. (94478)

• Fixed masking of high byte in character codes when a TrueType (3,0) cmap table is being used. (94630)

• An issue was identified with gray color in PCL output, where specific gray values were inverted. Light gray appeared as dark gray and vice versa. This problem has now been resolved. (94658)

• Fixed a StackOverflowException which was being encountered during the creation of AFP output when processing a PDF input file that included a significant number of form elements (more than 32,000). (94949)

• Addressed an issue where filestore uploads from output engines running on a server extension would sporadically fail when there were large numbers of output files being uploaded. (95225)

Known Issues

The Known Issues can be found here, Known Issues.