QAD QXtend Release Notes > Release Notes for QXI > Release Notes for Version 1.7.1
Release Notes for Version 1.7.1
QXI Server Version: 1.7.1
Date: March 2011
QAD Enterprise Applications Compatibility: eB SP4 through current release
Supported Progress Releases: Progress 9.1E, OpenEdge 10.0B, 10.1A, 10.1B, 10.1C, 10.2A, 10.2B
QAD QXtend Documentation: User Guide: QAD QXtend (70-3093A) and Installation Guide: QAD QXtend (78-0934A)
New Features
1 When processing QDocs through SIAPI connection pool, QXtend Inbound can now reuse the QAD Enterprise Applications session ID created during the authentication of previous QDocs (when the user name/password combination is the same), which improves the system performance.
2 A new App Server Direct Connect option is now available in SI API connection pool configuration settings that lets you directly connect to the App Server without having to connect to the nameserver first.
Fix Description
Internal ID
Issue Affected Versions
When a receiver is not licensed and there is no domain in the request, the system now displays an error. Previously, the system bypassed the license check and still processed the QDoc in such situations.
After deploying a new API, you no longer need to restart QXtend Inbound before the system can process QDocs of this API.
Fixed: If a SIAPI schema is loaded and dumped through Generate WSDL multiple times in different QXtend systems, the schema index name can exceed 32 characters and may cause QDoc processing to fail.
Fixed: The locale.dat file in the adapter for eB2.1 SP4 to SP9 is out-of-date, which forces MFG/PRO client sessions into the mdy date format.
For a connection pool with a reasonably large timeout, an agent can be reused by a new request before the previous request has been completed using the agent. Previously, at some point during the processing of the new request, the agent would be reset by the original request, causing a FailureException in the new request. This has now been addressed.
QXtend Inbound can now work with the EDI eCommerce module.
recordBackflush QDoc has been corrected.
New QAD EE APIs for Work Order Operation Scrap and Work Order Operation Backflush are now available.
QXTS-20, QXTS-21
Previously, when suppressResponseDetail was set to False in QDoc, and telnet connection was slow, sometimes a wrong document ID (from previous transaction) might be returned in the response QDoc. This has been solved now by always resetting the responseData cache after processing.
Known Issues
1 Starting the QXtend Installer UI in X-Windows while using X-Windows clients (such as xterm) can make installer UI menu items difficult to select. This is a known environment-related issue with the Java X-Windows component. To work around it, use the Up and Down keys to make a selection.
2 When installing QXtend 1.7.1 against QAD 2011 EE, some programs required by QXtend Excelerator are not deployed. Please contact QAD Support for a patch that you should install.