QAD QXtend Release Notes > Release Notes for QXO > Release Notes for Version 1.8
Release Notes for Version 1.8
QXO Server Version: 1.8
Date: March 2012
QAD Enterprise Applications Compatibility: eB SP4 through current release
Supported Progress Releases: OpenEdge 10.2B
QAD QXtend Documentation: User Guide: QAD QXtend (70-3190-1.8) and Installation Guide: QAD QXtend (78-0952-1.8)
New and Changed Features
1 New Profile Type and Communication Method for QAD BPM
This release of QXO introduces a new profile and a new communication method both named Workflow BPM to be used for configuring QAD Business Process Management (BPM) as the subscriber. The QAD BPM subscriber sets up the communication channel between QXO and QAD BPM and publishes business events and data to the QAD BPM server.
When you define the subscriber for QAD BPM, the system validates QXtend profile definitions against business object definitions in QAD BPM.
2 Database Connection ID
In the source application database configuration screen, the field Logical Name has been renamed ID to avoid confusion. This field is used by QXO as the ID of the database connection rather than the actual database logical name.
3 E-Mail Alerts on Source Application Suspensions
Once configured, QXO now sends out e-mail alerts to registered recipients when a source application is suspended on database connection error or calculation error.
4 QXO Session ID Count Limit Increased
The session ID of QXO Services can now exceed 999 and use the 5-digit numeric format if it is greater than 999 and less than 99999. Previously, QXO Services could not start after the count reached 999.
5 QXO Log File Name Renamed
QXO qxtendserver.log has been renamed outbound-ui.log to avoid confusion over the content of the log file.
6 Reprocess Button in the Application Event Viewer
In the application event viewer, there is a new Reprocess button that lets you reprocess events with processing errors.
7 Support for Socket-level Authentication for External Web Service Subscribers
When configuring external Web Service subscribers that use XML syntax other than QDoc 1.0 and 1.1, you can now set the username and password for socket-level authentication.
Fix Description
Internal ID
Issue Affected Versions
Force Publish now works well when there are two or more source applications. Previously, when two or more source applications were connected with different databases, QXO would connect to the first available database for all the source applications.
Password is now displayed as asterisks (******) rather than in plain text in the response QDoc, the QDoc log, and the message alert.
When a source application is resumed, the Event Service for the source application does not terminate any more.
Previously, when QXO first connected to a source application with no domains and then connected to another source application with domains, inner joins in data objects did not work and failed BO validation. Now this issue has been fixed.
The following issue with Query Service that previously occurred in some environments has been fixed: Error “No data returned by the query” preceded by another error “Procedure: ‘attachDataSources com.qad.qxtend.qxo.BusinessObjectManager’ (Line:823) Invalid handle. Not initialized or points to a deleted object. (3135).”
Data watch configuration settings can now be migrated/converted from QXO versions earlier than 1.6 to version 1.6 and later.
QXO no longer sends out an e-mail alert if the associated subscriber message has already been removed.
If a source application database is disconnected, especially one that is not used to trigger events, QXO now checks if this database can be connected before further processing the event. Previously, a disconnected source application database might leave events partially processed, preventing future updates to the same record.
When a file drop subscriber is migrated from a QXtend version earlier than 1.7, the default file extension is automatically set to xml. Previously, the migration incorrectly caused the file extension to be removed.
Known Issues
1 If a business object is already in use but you migrate one from the test environment to your production environment that contains some updates, the system will first remove the existing BO and replace it with the new one, and all links to existing transactions will be lost.