QAD QXtend Release Notes > Release Notes for QXI > Release Notes for Version 1.7
Release Notes for Version 1.7
QXI Server Version: 1.7
Date: September 2010
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 (78-0915A) and Installation Guide: QAD QXtend (78-0922A)
New Features
1 When you generate a WSDL for a single API, both the resultant compressed .zip file and its contained WSDL .xsd file now use the same name as the API name rather than the generic QdocWebService file name as in earlier versions. A sample empty QDoc is now available for each API in WSDL generation.
2 You can now use the script to start, stop, and restart connection pools, as well as query the connection pool status. Previously, you could only manage connection pools through Connection Pool Manager.
3 You can now use the script to start, stop, and restart queues, as well as query the connection pool status. Previously, you could only manage queues through Queue Manager.
4 Queue Manager enhancements:
You can now select and resubmit failed QDocs directly using a new Resubmit button in Queue Administration. Previously, you could only resubmit failed QDocs in the Edit QDoc Request screen.
When configuring queue settings, you can now use a new Pause on Queue Error option to specify whether Queue Manager pauses the queue or proceeds to the next QDoc when encountering errors.
You can now use a new Max Retry Limit option to specify the maximum number of times Queue Manager will try to send a request QDoc when there is a SOAP error; for example, web service is not available.
A new Req Date column is now available in Queue Manager to display the date and time of QDoc requests.
5 When a program, such as an add-on application, has already logged into QAD Enterprise Applications, it now can include a valid QAD Enterprise Applications session ID in the QDoc to pass authentication checks, instead of providing a username and a password. This applies to QAD EE and QDoc 1.1 for UI API. Previously, only SIAPI allowed a session ID to be included in QDocs.
6 QXtend licensing now can handle license expiration for certain senders.
7 SI API AppServer can now be configured as State Free. To support this, the State Free check box has been added to the SIAPI connection pool configuration settings.
8 QXI now supports System QDocs. System QDocs are mandatory QDocs required by QAD applications like QAD Workflow Alerts and QXtend Excelerator. They are automatically included for the receiver, not visible from the UI, and cannot be removed by end users.
Fix Description
Internal ID
Issue Affected Versions
In the Windows environment, the subscriber response page can now be displayed correctly if the subscriber is using HTTP version 1.1.
QGen can now generate two or more different APIs without relogin.
Previously, the WEB-INF/conf/licence.xml file could get corrupted somehow and be set to 0 bytes, which eventually caused Tomcat to crash. This has been solved.
Previously, for a non-US language user, QXtend returned SUCCESS even if there was an error returned from QAD Enterprise Application. Now the error can be returned by QXtend in this case.
A QDoc sent to a SI API now contains the full response if the relation fields between a parent and child table differ in terms of upper and lower case.
QXtend can now be shut down properly when Tomcat is shut down.
Known Issues
1 When scopetransaction is set to false and a QDoc contains multiple requests for native APIs, if an error occurs in one request, subsequent requests are not processed.
2 Some error messages like “URL: is not a valid URL” can be found in the qxosi_AS AppServer log, but they do not affect anything and can be safely ignored.