Connector for SAP 2.0.2 - Release Notes Nov 2011
Note: The Loftware Connector for SAP v2.0.2 requires Loftware Printer Server Premier Edition version 10.0.
Bug Fixes
- Fixed potential performance issue when editing ODBC settings
- Fixed field name change when concatenating strings
- Improved LWEntUp handling of ODBC errors which could cause performance problems with large quantities of labels
Connector for SAP 2.0.1
Note: The Loftware Connector for SAP v2.0.1 requires Loftware Printer Server Premier Edition version 10.0.
Updated to support LPS 10.0 Premier Edition.
Connector for SAP 2.0
Note: The Loftware Connector for SAP Applications requires the Loftware Print Server version 9.8.
New Features
- The Loftware Connector for SAP Applications Version 2.0 is now Certified for SAP NetWeaver™
- Added support for Microsoft Windows Server 2008, 2008 R2 (32-bit and 64-bit)
- Updated the style of the Configuration and Diagnostics User Interface and added new capabilities
- Added support for label fields with a pipe (‘|’) character
- Automated the installation process
- Added asynchronous status updates to the SAP spooler through BC-XOM
Bug Fixes
- Improved the performance and device handling of Loftware Enterprise Update
- Enhanced the synchronization process between Loftware Enterprise Update and the Provda database
- Fixed issues on systems with Microsoft .NET 2.0 SP1 installed
- Changed the Date/Time format in logs to be consistent with other Loftware Products
- Added support for label formats with script data sources
- Increased server performance when label formats change
- Improved the handling of printer errors during heavy-printing load
- Improved the handling of network issues between the Loftware Connector for SAP Applications and SAP
Connector for SAP 1.5.2.15
Bug Fixes
Resolved incomplete device synchronization in Provda.mdb triggered by a device Add, Change or Delete. Loftware Connector for SAP now works with the Loftware Print Server version 9.6.
Connector for SAP 1.5.2.13
Job Status Capability
‘Invalid Printer’ status message is now returned to SAP.