QAD QAD QXtend 1.8.8 > Release Notes > QAD QXtend Release Notes > Release Notes for QXO
  
Release Notes for QXO
Release Notes for Current Version
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+