QAD QXtend Release Notes > Release Notes for QXI > Release Notes for Version 1.7.2
  
Release Notes for Version 1.7.2
QXI Server Version: 1.7.2
Date: September 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-3190A) and Installation Guide: QAD QXtend (78-0952A)
New Features
1 Detailed QDoc Reference Information
You can now view detailed reference information about all QAD-supplied standard QDocs in an Excel spreadsheet accessible from the Configuration Manager. To access the spreadsheet, under the Configuration tab, click the QDoc Spreadsheet link beneath Help in the lower part of the tree view pane. The QDoc spreadsheet elaborates on all standard QDocs for all QAD Enterprise Application versions, allowing you to compare one version of a QDoc against another for differences. You can also sort and filter data in the spreadsheet to easily view the QDoc information you want.
2 Versioning of QGen Master Data (.dat) Files
During QXtend installation, only standard QGen master data (.dat) files that support the current QAD Enterprise Applications release are deployed. If a .dat file does not match the screen (usually because of screen customization), you can use QGen to remap the screen and save the customized .dat file without overwriting the standard one.
When you install QXtend, the installer now copies the QGen .dat files for the current release of QAD Enterprise Applications to this location:
<QXtend Adapter>/tools/datFiles/standard/
When you modify the .dat files and do not specify a directory when saving them, customized .dat files are always saved to the <QXtend Adapter>/tools/datFiles/ directory, leaving the standard .dat files intact.
When you load .dat files without specifying a directory, the system first looks for the files under <QXtend Adapter>/tools/datFiles/. If the files cannot be found under this directory, the system then loads the standard .dat files under <QXtend Adapter>/tools/datFiles/standard/.
3 Senders Licensing Information
A new License|Senders menu is now available under the License tab that allows you to view the current licensing information of all senders along with their license expiration dates, if any. Currently, only QAD Initial Data Load, which represents the license for QAD QXtend Excelerator, has an expiration date.
Fixes
 
Fix Description
Internal ID
Issue Affected Versions
In previous releases, when a password was supplied in the request QDoc, it was also contained in the response QDoc and the e-mail alert as a part of the context information. This has been fixed and passwords no longer appear in response files and e-mail alerts.
QXTS-39
1.4+
If a queue is set to automatically add a SOAP envelope, the Queue Manager now includes the <requestor> tag in the SOAP envelope only when the Require Authentication option is selected for the receiver and Requestor ID is not blank in the Queue settings. Previously, the Queue Manager included an empty <requestor> tag line without attributes in the SOAP envelope when requestor ID was not supplied, which caused every request to fail with the “invalid User/Password” error.
QXTS-40
1.7+
The Sales Order Shipment QDoc has been fixed so that it does not skip updating the line iteration
QXTS-43
1.7+
Previously, when ODBC security was activated, if a record in QAD Enterprise Applications was locked by another user, QXI returned a message indicating the record was locked but could not identify the user locking it. This has been fixed and the system now displays the user locking the record in the message.
QXTS-57
1.1+
The system has been modified to set the session idle time to 0 (zero) after processing each QDoc. Previously, the session idle time was not reset and when a session times out, an error message “User not authorized to access this function” was displayed.
QXTS-63
1.6+
Performance of native APIs has been improved through an authentication cache.
QXT-979
QXT-947
1.7+
When QXtend 1.7 and 1.7.1 are installed against earlier versions of QAD Enterprise Applications, some adapter files for Excelerator are missing, which causes the error “MenuSecurityService.p not found.” These missing adapter files are now included.
QXTS-925
1.7+
License code for Excelerator (Initial Data Load) can now be successfully loaded into QXtend on AIX machines.
QXTS-1001
1.7+
Previously, installing QXtend on HP machines using PA-RISC chips might fail when unzipping packages for QXtend adapters or the QXO qxevents database. Now this has been resolved.
QXTS-1015
1.6+
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.
Fixes
 
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.
QXT-808
1.7
After deploying a new API, you no longer need to restart QXtend Inbound before the system can process QDocs of this API.
QXT-812
1.4+
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.
QXT-848
1.6.2+
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.
QXT-855
1.7
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.
QXT-857
1.4+
QXtend Inbound can now work with the EDI eCommerce module.
QXTS-16
1.5.1+
recordBackflush QDoc has been corrected.
QXTS-2
 
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.
QXTS-31
1.4+
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.
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 conn-control.sh 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 queue-control.sh 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.
Fixes
 
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.
QXT-549
1.6.3
QGen can now generate two or more different APIs without relogin.
QXT-665
1.6.2+
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.
QXT-676
1.5+
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.
QXT-691
1.6.3
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.
QXT-718
1.4+
QXtend can now be shut down properly when Tomcat is shut down.
QXT-724
1.6.2+
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.