QAD 2017 Enterprise Edition > QAD 2016 EE Combined Release Notes > QAD Enterprise Applications 2017 Combined Release Notes > QAD QXtend 1.8.8
  
QAD QXtend 1.8.8
QXtend Inbound
QXI Server Version: 1.8.8
Date: September 2017
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.8) and QAD QXtend Installation Guide (78-0952-1.8.8)
Fixes
 
Fix Description
Internal ID
Issue Affected Versions
Previously, the QXtend installer wrote the event file with the QDoc version as a suffix during upgrade, which caused a problem. Now the installer does not change the QDoc event files during upgrade.
QXT-1833
1.8+
For an MFS-QXtend integration, the data in the response QDoc sometimes was inconsistent with the API dataset sent to QXtend. The issue has been fixed.
QXT-1913
1.8+
Previously, when setting the maxuses value of UI connection pool in connectionManagerConfig.xml to 1 and suppressResponseDetail to false, the response QDoc got the error “No response from MessageServlet for HTTPPost to get API User data”. This issue has been fixed.
QXT-1915
1.8+
Previously, a “File not found” or “Could not read request file” error could occur during processing queue. Now this issue has been fixed.
QXT-1916
1.8+
Previously, if there was an error during Inbound upgrade in a YAB environment, Inbound configurations would be missing after the issue was solved and upgrade was rerun. This issue has been fixed.
QXT-1923
1.8.7
Previously, the perpetual Excelerator license was removed during QXtend upgrade. In this case, you had to enter the license after upgrade. Now the license is kept during upgrade.
QXT-1929
1.8+
For 2015 EE or later versions, when a UI API agent was reused with a different set of credentials or domain, it failed to log out of the session. As the orphaned sessions were built up, the login process slowed down as the login procedure tried to clean up the orphaned sessions. Now this issue has been fixed.
QXT-1936
1.8.6+
A memory leak in QXtend Inbound Alert Configuration Manager (responsible for sending out alert emails) has been fixed.
QXT-1941
1.8+
Note: For QDoc fixes, see the Product Changes area on QAD’s Online Support Center:
http://support.qad.com/product_changes/
QXtend Outbound
QXO Server Version: 1.8.8
Date: September 2017
QAD Enterprise Applications Compatibility: eB SP4 through current release
Supported Progress Releases: OpenEdge 11.1, 11.2, 11.3, 11.4, 11.6, 11.7
Supported Java Version: Java 1.6 or higher
QAD QXtend Documentation: QAD QXtend User Guide (70-3190-1.8.8) and QAD QXtend Installation Guide (78-0952-1.8.8)
New and Changed Features
The performance of filters in QXO Subscriber Messages Viewer has been improved when the filter conditions include delivery status and/or profile name.
Fixes
 
 
Fix Description
Internal ID
Issue Affected Versions
MaintainItemMaster(SIAPI) QDoc now creates item records without error in the destination domain when configured items are created in the source domain.
QXT-1906
1.8+
Now subscriber messages can still be delivered to File Directory Service subscribers (Include SOAP Envelope is set to false) even when the profile of this message has been deleted.
QXT-1917
1.8+
Direct data publish in operational code now works in a QRA-enabled environment.
QXT-1918
1.8.7
Previously, qxo-services-stop did not stop all Windows processes related to Outbound services when QXtend was installed on a Windows server. Now this issue has been fixed.
QXT-1924
1.8.7
Fixed the issue that QXtend configuration service could not load the profiles of Financial business objects.
QXT-1925
1.8+
Previously, when QXtend was installed on a Windows server, starting QXO services from the web opened command prompt windows. This issue has been fixed.
QXT-1928
1.8.7
Previously, when a subscriber was set to allow superseded and there were pending messages, Message Sender kept looping without sending a message under certain conditions. Now this issue has been fixed.
QXT-1932
1.8.7
Previously, deadlock happened between Message Publisher and Message Sender under certain conditions when the subscriber had Allow Superseded set to true. This issue has been fixed.
QXT-1837
1.8.7
The sequence number in the Events database that assigns unique numbers to generated events is limited up to 32 bits.
QXT-1947
1.8+