QAD QXtend Release Notes > Release Notes for QXI > Release Notes for Version 1.6
Release Notes for Version 1.6
QXI Server Version: 1.6
Date: April 2009
QAD Enterprise Applications Compatibility: eB SP4 through current release
QAD QXtend Documentation: Technical Reference: QAD QXtend (78-0691C) and Installation Guide: QAD QXtend (78-0692B)
Important: If you are using QAD 2009 EE or SE, use Qxtend version 1.6.
Application Changes
1 It is now possible to create more than one connection pool for the same receiving application. This allows one receiver to have connection pools to the Service Interface AppServer, Financial AppServer and the UI adapter.
2 Significant enhancements have been made to the QAD QXtend installer. For details see Installer.
1 QDoc schemas have been added for the Commodity Code Maintenance (1.4.19, ppcommt.p) API. In addition, this program now can be mapped successfully using the QAD QXtend QGen utility.
2 The QXtend service interface adapter now validates dates entered in QDocs. If an invalid date is entered, QXI now issues an exception instead of parsing it into a wrong date, as in previous versions.
3 The system now correctly validates the operation tag value. If the operation is invalid, the system issues an exception.
4 If scopeTransaction is used and a transaction is rolled back, the system returns an exception message.
5 The current version supports the 1.1 syntax for Sales Order Shipments (7.9.15). In previous versions, a missing mapping element prevented QGen from mapping this program successfully.
6 The current version of Technical Reference: QAD QXtend incorporates errata that were issued for the 1.5.1 release documentation. The errata sheet is accessible from
Known Issues
1 Certain double-byte characters do not work with the SI API adapter. If you are affected by this issue, contact QAD Support for a patch that you should install.
2 In an AIX environment, if you use the 1.0 syntax specification with your QDocs, the post-processing program may return an error even though processing was successful. You can avoid this situation by using the QDoc 1.1 specification instead.
3 When installing QAD QXtend using the console mode and a local repository, if the file you specify is not found, no warning is returned; instead, a message displays stating that there is nothing to install on the host.
4 In a QDoc containing multiple requests for native APIs, if an error occurs in one request, subsequent requests are not processed.