QAD QAD QXtend 1.8.7 > Release Notes > QAD QXtend Release Notes > Release Notes for QXO
  
Release Notes for QXO
Release Notes for Current Version
QXO Server Version: 1.8.7
Date: March 2016
QAD Enterprise Applications Compatibility: eB SP4 through current release
Supported Progress Releases: OpenEdge 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 You can now add additional session context to a subscriber message by configuring the AdditionalContext.xml file in <qxoserver>/conf folder.
2 The Archive Service has been enhanced to improve the performance of archiving. You can configure Archive Service to check all records for archiving or only the newly added records since the last run. A few indexes also have been added to qxodb tables to improve archive performance.
3 The default value of tlPartialUpdate is now always set to true when Financials data is published via Outbound.
4 The following database triggers have been added for QADEE and are available in the event type list:
• Triggers used by BPM EOB processes – qc_mstr, vep_mstr, and vepd_det
• Triggers for ql_mstr, a new table since 2015 EE
• Triggers that were missing previously for top-level tables of business objects except the tables that are managed by the Financials module
Fixes
 
 
Fix Description
Internal ID
Issue Affected Versions
The Tables button on a business object can be used to remove data objects. Previously, removing data objects using this button could cause an error.
QXT-1758
1.7+
Outbound now always validates a business object after save. Previously, in some situations, the BO was set to invalid and you had to use the Validate button to validate the BO. In some other situations, the BO could not be changed to invalid.
QXT-1766
1.7+
In Subscriber Message Viewer, deleting a filter condition no longer affects a subscriber message. Previously, it would delete selected subscriber messages as well.
QXT-1774
1.7+
Subscriber messages now always have correct operations if the profile structure has changed since the latest message was published.
QXT-1777
1.7.1+
Added a new index to est_event_msg table to improve the performance of Outbound archive service.
QXT-1811
1.7+
When Outbound received a response from a web service subscriber and the HTTP header status of the response does not start with “20,” Outbound can still display the full response in Viewer. Previously, it could only show an exception such as “HTTP/1.1 500 Internal Server Error.”
QXT-1812
1.7+
A new index has been created for est_extract_row to solve the event service performance issue when there are many est_extract_row records.
QXT-1814
1.7+
The BPM subscriber can now be configured by Configuration Service.
QXT-1820
1.8+
The Message Sender no longer sends the same message twice when the first delivery was successful. Previously, this could happen when the sender had multiple agents.
QXT-1823
1.7+
If subscriber is set to Allow Superseded, a message can now supersede the previous pending messages of the same record. Previously, only the last message would be delivered later but it did not supersede the previous messages.
QXT-1829
1.7+
Previously, when a profile was registered to many subscribers, a token in the subscriber message was sometimes incorrect. This issue has been solved.
QXT-1868
1.7+
If a subscriber has Require Acknowledgement set to true, when a subscriber message is in WAITACK status, the second message of the same record will not be sent out and cannot be seen in Subscriber Messages Viewer. Previously, the second message would be sent out, which defeated the purpose of Require Acknowledgement.
QXT-1899
1.8.2+
Known Issues
1 The Validate Progress step in QXtend installer does not do the validation as expected. If an unsupported Progress version (any version lower than 11.1) is used for Outbound, Validate Progress still shows success but the installation will fail in a later step.
2 When raising an event, Outbound adapter code does not clear the error-status if domains are not defined in Source Application configuration. Some QAD ERP programs can erroneously report this as an error: “ERROR: Find First/Last failed for table erm_app_domain.(565).”