QAD QAD QXtend 1.8.7 > Release Notes > QAD QXtend Release Notes > Release Notes for QXI
  
Release Notes for QXI
Release Notes for Current Version
QXI Server Version: 1.8.7
Date: March 2016
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, 11.1, 11.2, 11.3, 11.4,11.6
Supported Java Version: Java 1.6 or higher
QAD QXtend Documentation: QAD QXtend User Guide (70-3190-1.8.7) and QAD QXtend Installation Guide (78-0952-1.8.7)
New and Changed Features
1 A new attribute preprocessChunkSize has been added to qxtendconfig.xml to allow Inbound to pass large QDocs to the preprocessor in smaller chunks. This is mainly useful in an AIX environment to solve the issue that a large QDoc cannot be passed to the preprocessor in one chunk.
2 All of the QDocs and BO/profiles for QAD Financials have been replaced with the Financials schema of 2016 EE, which uses Int64 ID fields. They are not compatible with previous EE versions. If QXtend 1.8.7 is used against previous EE versions, the QDocs and BO/profiles for QAD Financials should be replaced with the Financials schema of the specific EE version.
3 A new session context parameter hideFields has been introduced. When a field list is defined for hideFields, the values of these fields display as asterisks in qdocRequests.log, qdocResponses.log, and QDoc responses.
4 The following QDocs are merged into QXtend:
SAQ QDocs for QAD 2016 EE
More EOB QDocs for QAD EE
Now all EOB QDocs for QAD EE are available.
Fixes
 
Fix Description
Internal ID
Issue Affected Versions
The Installer now deploys the correct version of QRA library depending on the Progress version when QRA Library is absent from QAD ERP.
QXT-1580
1.7+
Inbound now returns the correct error when an SI API QDoc has no username/password or sessionID and there is no username/password defined in the connection pool. Previously, in this situation with QAD 2014 EE and QAD 2015 EE, Inbound returned success without processing the QDoc.
QXT-1768
1.8.6
Previously, if the Queue Manager was configured for Inbound, error messages were found in Install Log when starting Inbound. Now this issue has been fixed.
QXT-1779
1.8+
When QXtend 1.8.6 was installed against QAD SE, the default configuration failed. This issue has been fixed.
QXT-1784
1.8.6
Previously, in some situations Inbound would report ConcurrentModificationException error when processing SIAPI QDocs. This issue has been solved.
QXT-1785
1.7+
Previously, in some situations when MFG/PRO error message was long, QXtend Inbound could not return the error message properly. This issue has been solved.
QXT-1824
1.7+
Now the Queue Manager does not stop processing when there are pending QDocs. Previously, it could get stuck and required a restart.
QXT-1830
1.7+
When loading data from Excelerator, the corresponding log entry in qdocSummary log no longer has a line break after the first field.
QXT-1850
1.8+
When posting UIAPI QDocs, Inbound now takes the domain time zone instead of the QXtend server time zone.
QXT-1851
1.7+
QXtend Inbound no longer throws AdapterException003 when processing QDocs.
QXT-1853
1.7
Inbound now can catch the null appServer connection and throw a meaningful error QdocException 94 for SIAPI QDocs.
QXT-1871
1.7+
The Session ID from the connection pool cache is used in place of a blank Session ID in the QDoc request. Previously, if the Session ID in the request was blank, then the User and Password from the connection pool were used and a new session was created every time.
QXT-1882
1.7.1+
A queue can always continue processing after restarting. Previously, the queue could get stuck if it was started while processing multiple requests.
QXT-1893
1.7+