Version 4.2.1  |  Version 4.2  |  Version 4.1  |   Version 4.0.3  |   Version 4.0.2  |   Version 4.0.1  |   Version 4.0  |   Version 3.1  |  


Loftware Universal Connector 4.2.1

Release Notes: August 2018

Universal Connector 4.2.1 is a Loftware Connector maintenance release. The features and fixes provided by version 4.2 are listed below to assist users who are upgrading from a release prior to 4.2.

What are the new features of this release?

  • Added support for Web Services Integrations.
  • Added support for non-clustered Windows Server 2016.
  • Added the ability for the Connector Console to automatically update when printer lists are modified on any configured Loftware Print Servers.
  • Added the ability to treat non-group values for the _FORMAT attribute as labels.
  • Added the ability to test with large XML files.
  • Added the ability to register a listener without a filter.
  • Added additional feedback when errors are encountered while running “Discover All LPS Servers”.
  • JRE 1.8 is now packaged with Loftware Connector products, which results in providing separate installation packages for 32- and 64-bit Operating Systems.

What fixes are available in this release?

  • Corrected issues with Repair functionality incorrectly reporting on status of XDK java classes and failing to install the Console service.
  • Corrected a defect that prevented labels with fixed text fields only from printing via the Connector.
  • Corrected issues running service.bat if both JAVA_HOME and JRE_HOME are set.
  • Method type of “literal” is now disallowed when configuring a Default Data Lookup filter.
  • Corrected an error with Format Substitution not working after a Default Data Lookup in a filter chain.
  • Corrected issues with a failed import rendering the Connector useless.Corrected an issue in which high volumes of jobs across a large number of scan folders can result in jobs being stacked in the Processing folder.
  • Corrected a loadjava call by surrounding the JDBC_URL with double quotes.

What issues are known about this release?

  • When using the Web Services integration, if an XML job-file has a UTF-8 byte order mark (BOM) ahead of the XML declaration, the job sent to LWWS via SoapUI, or through code, will cause the following error to occur: org.xml.sax.SAXParseException; Content is not allowed in prolog 
    • This does not occur when passing the XML with BOM data as a ByteArrayInputStream. This error can be avoided using either of the following workarounds:
      • Strip the BOM from the head of the XML, by using the String replace method, and replacing '\uFEFF' with an empty character
      • Pass the XML as a stream of bytes via ByteArrayInputStream


Loftware Universal Connector 4.2

Release Notes: July 2017

What are the new features of this release?

  • Added support for non-clustered Microsoft Windows Server 2016

  • Added the ability for the Connector Console to automatically update when printer lists are modified on any

    configured Loftware Print Servers

  •  Added the ability to treat non-group values for the _FORMAT attribute as labels

  • Added the ability to test with large XML files

  • Added the ability to register a listener without a filter

  • Added additional feedback when errors are encountered while running “Discover All LPS Servers”

  • JRE 1.8 is now packaged with Loftware Connector Products, which results in providing separate installation

    packages for 32 and 64-bit Operating Systems

What fixes are available in this release?

  • Corrected issues with Repair functionality incorrectly reporting on status of XDK java classes and failing to install

    the Console service

  • Corrected a defect that prevented labels with fixed text fields only from printing via the Connector.

  • Corrected issues running service.bat if both JAVA_HOME and JRE_HOME are set

  • Method type of “literal” is now disallowed when configuring a Default Data Lookup filter

  • Corrected an error with Format Substitution not working after a Default Data Lookup in a filter chain

  • We no longer automatically remove an existing INV_SYNC_PRINT_REQUEST during install

  • Corrected issues with a failed import rendering the Connector useless

  • Corrected a loadjava call by surrounding the JDBC_URL with double quotes


Loftware Universal Connector 4.1

Release Notes: December 2014

Note: The Loftware Universal Connector version 4.1 requires the Loftware Print Server Premier Edition version 10.0.1 or higher.

What are the new features of this release?

  • Added support for non-clustered Windows Server 2012 R2
  • Added the ability to Import and Export Business Rules and configuration to the local client. This allows for easy migration between different Connector instances
  • Enhanced flexibility for Business Rules that allows labels to be printed unless a certain condition occurs (“Execute Unless”). This expands the existing “Execute When” logic, which allows a label to be printed when specified conditions are met
  • Added support for field truncation via the API
  • Added the ability to fail a print job on a database error
  • Added Network Proxy Support for load balanced environments
  • Improved JDBC Driver Handling, providing easy connectivity to additional external data sources
  • Support for Oracle 12c and Java 1.8
  • Changed “Filter” terminology to “Rules”

What fixes are available in this release?

  • Improved Business Rules load times
  • Fixed issue where the Connector was holding onto an invalid socket connection
  • Fixed issue where DELINKODBC was getting removed from dropped XML
  • Additional error handling and logging improvements

What issues are known about this release?

  • High volumes of jobs across a large number of scan folders can result in jobs being stacked in the Processing folder.
  • LPS commands within incoming XML files must be in all UPPERCASE.
  • Label Groups cannot be deleted if they are currently associated with a Rule Chain or another label.
  • Loftware recommends you disable console persistence across restarts.
  • When triggering a filter that queries either an SQL Server 2005 or 2008 R2 database, an AccessControlException is thrown, indicating that "...listen, resolve permissions have not been granted to user LOFTWARE". This can occur when a JDBC URL string has a named instance, and the optional port address is left off. To fix this issue, either fully qualify the connection with the port information, or remove the named instance.


Loftware Universal Connector 4.0.3

Release Notes: December 2013

Note: The Loftware Universal Connector version 4.0.3 requires the Loftware Print Server Premier Edition version 10.0.1 or higher.

What are the new features of this release?

  • Support for IE versions 9, 10, and 11.
  • Support for Non-Clustered Windows Server 2012
  • Support for Windows 8
  • Support for customizable "Job Listener" to identify and intercept specific print jobs that have been processed through a filter, before they are allowed to continue to LPS for printing.

What fixes are available in this release?

  • Java Connector API has been updated to accept a label name in any upper or lower case.
  • XML parser has been updated to not require a CR at the end of jobs in stacked XML files.

What issues are known about this release?

  • High volumes of jobs across a large number of scan folders can result in jobs being stacked in the Processing folder.
  • LPS commands within incoming XML files must be in all UPPERCASE.
  • Label Groups cannot be deleted if they are currently associated with a Filter Chain or another label.
  • Loftware recommends you disable console persistence across restarts.


Loftware Universal Connector 4.0.2

Release Notes: February 2012

Note: The Loftware Universal Connector 4.0 requires Loftware Printer Server Premier Edition version 10.0.

What are the fixes available in this release?

  • When the Connector is installed on a Windows operating systems, dropping a UTF-8 XML files containing high ASCII characters to the scan directory no longer produces errors. Previously you may have received an "Invalid byte" error followed by a parser exception.
  • A minor update to the installer window.
  • If you made changes to advance filters while either the Console or UCFDA were in service mode, the changes were not updated without restarting the Universal Connector. You no longer need to restart the Universal Connector for the advance filter changes to occur.
  • A correction was made to the 4.0 Release Notes. The new feature description: Added ability to turn off XSLT transforms using the SkipXSLTransforms property in the LPSConnector.property file.

Was changed to: Added ability to turn off XSLT transforms by adding the element <tns:runXSL>false</tns:runXSL> within the parent <tns:ScanDirectory> element, in the jcfda_config.xml file.


Loftware Universal Connector 4.0.1

Release Notes: December 2011

Note: The Loftware Universal Connector 4.0 requires Loftware Printer Server Premier Edition version 10.0.

What are the fixes available in this release?

  • The Loftware Universal Connector now allows the setting of Java Options. A user can now add to the JAVA_OPTS variable within the .cmd script files; these files will also inherit external JAVA_OPTS values by default.
  • Instance Expansion Rules are now functioning correctly and are providing error messages. Job XML assembly now reacts properly to XML transformers used by UCFDA


Loftware Universal Connector 4.0

Release Notes: November 2011

Note: The Loftware Universal Connector 4.0 requires Loftware Printer Server Premier Edition version 10.0.

What are the new features of this release?

  • Updated the look and feel of the Connector Console user interface.
  • Added support for Windows Server 2008 and Server 2008 R2.
  • Added support for JDBC compliant databases.
  • Introduction of an installation Wizard for the Loftware Universal Connector.
  • Allow Filter triggers in the console to be based on incoming xml data .
  • Added the ability to turn on or off individual filters without deleting them from the Filter Manager in the console.
  • Added ability to turn off XSLT transforms by adding the element <tns:runXSL>false</tns:runXSL> within the parent <tns:ScanDirectory> element, in the jcfda_config.xml file.
  • The XML created by the Connector Instance Expansion filter can be modified so that labels can besent to multiple printers.
  • Add Save As Capability to Connector Filters.
  • Allow over-writing data values on Print Attribute Substitution.

What fixes are available in this release?

  • The Default Servers check box on the LPS Servers page now remains selected when Show/Hide Printers is selected.
  • Print Attribute Substitution Filter is able to modify the literal _QUANTITY if _QUANTITY exists and a value has been assigned.
  • Replace forward slashes (/) in printer model names to a space.
  • When in the Modify Filter view, clicking the browser Back button no longer produces an error.
  • Settings in the Connector Console do not update to the File Drop Service until the service restarts.
  • LPSTemplate.setData(string,string) now truncates data if the data string being passed is too long.

What issues are known about this release?

The Loftware Universal Connector Setup program will not recognize and upgrade previous versions of the Loftware Java Connector on Windows systems.

  • On servers with just the Loftware Java Connector installed, the setup program will perform a first-time install of the Loftware Universal Connector version 4.0.
  • On servers with both the Loftware Java Connector and the Loftware Connector Console installed, the setup program will recognize and upgrade the Loftware Connector Console. To add the Loftware Universal Connector, you will need to follow these instructions on Windows systems:
    1. After completing an upgrade of the Loftware Connector Console, navigate to the <Connector Install>\Connector\_Loftware Universal Connector_installation folder.
    2. Run the Change Loftware Universal Connector Installation.exe program. The Configure Loftware Universal Connector wizard opens in Maintenance Mode.
    3. Select Add Features, and click Next. A confirmation screen appears.
    4. Click Next, and select Loftware Universal Connector.
    5. Click Next, and then click Done to close the wizard and finalize the maintenance.


Loftware Connector for Java 3.1

Release Notes: 2008

New Features and Enhancements

File Drop capability

  • Enables the receipt and processing of label print request files from any application
  • Supported file types: XML, PAS, CSV and XSLT
  • Supported on Windows and Unix platforms

New Job Status capability

  • Job status information based on job name or filename is available via a JAVA API.