In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com




Release Notes for Version 1.7
QXO Server Version: 1.7
Date: September 2010
QAD Enterprise Applications Compatibility: eB SP4 through current release
Important: Due to time zone enhancements in QAD 2010.1 EE, earlier versions of QXtend may experience incorrect behavior in the Outbound Event Service. To avoid this problem, always use QXtend 1.7+ with QAD 2010.1 EE or later releases of QAD Enterprise Applications.
Supported Progress Releases: OpenEdge 10.1C, 10.2A, 10.2B
Note: If QAD QXtend is installed on an HP-UX IA64 machine with Progress OE10.2A01 or OE10.2A02, a Progress hotfix needs to be applied to avoid issues with QXO services. Please check the Platform Guide and make sure the hotfix is applied.
QAD QXtend Documentation: User Guide: QAD QXtend (78-0915A) and Installation Guide: QAD QXtend (78-0922A)
New Features
1
QXO now supports QAD Workflow Alerts by publishing alert data to the new product. QAD Workflow Alerts is a business management tool that helps you manage your business by exception—keep a close tab on your key business processes and receive real-time alerts of any outstanding events that often need corrective actions. For details on QAD Workflow Alerts, see User Guide: QAD Workflow Alerts.
QXO now has a new QAD Workflow profile type that lets you select which components of a business object are sent to QAD Workflow Alerts. When you define a profile of type QAD workflow, you can also specify the source application to monitor and alert on and choose whether to have the alert system keep track of alert messages that have been delivered for a specific business event instance using the new Module and Maintain State fields, respectively.
When defining subscribers, you can now select a new QAD Workflow communication method to have the system send messages through the QAD Workflow Alerts Event Publishing Web service.
In the subscriber profile configuration, a new Unmodified option is now available for the Operations field so that you can have the system send alerts on records even if their status is unmodified or unchanged.
2
Subscriber enhancements:
You can now configure the subscriber to be suspended on one or more of the following errors: sending error, SOAP error, and application error. Message Sender does not send messages to suspended subscribers, and suspended subscribers can be resumed later through the UI or a batch process script. Previously, the subscriber was not suspended when errors occurred.
You can now specify the response parser the subscriber uses to parse QDoc information when Communication Method is Web Service. Previously, the response parser setting belonged to the profile type.
For the file directory service, you can now designate the file extension of QDocs for filedrop subscribers when configuring subscriber parameters; for example, you can specify .req as the QDoc file extension so that QDocs can be directly dropped into a queue to be processed by Queue Manager. In earlier releases, QDocs could only be generated as .xml files for filedrop subscribers.
You can now specify whether to set the suppressResponseDetail attribute of QDoc requests to true or false for a subscriber profile.
3
Source Application enhancements:
You can now configure the source application to be suspended on one or both of the following errors: database connection error and calculation error.
All QXO services should only process events or messages of active source applications and will ignore events or messages of suspended source applications.
Users can manually resume or suspend QXO source applications through QXO Dashboard or batch process scripts.
When a QXO source application is resumed, QXO services should automatically reprocess the extracted event data and raw message with the ERR status.
4
Changes to QXO Viewers:
The Events Viewer has a new check box column and a new delete button. You can now delete application event messages with status ERR in the Application Event Viewer.
The Raw Message Viewer has a new business object column, a check box column, and a new delete button. You can now delete extracted raw data with status ERR in the Raw Messages Viewer.
The Subscriber Messages Viewer now has a new Identifier column that helps you identify subscriber messages. Identical message identifiers indicate that the same subscriber message has been processed multiple times.
5
Changes to Dashboard:
Subscribers have been moved from under Services to under Overview.
Shut down QXO services in the dashboard now also stops the archive service.
6
QXO can now automatically detect business events in DDP published data and save them as inactivated if the events are not in the QXO database.
7
The delivery schedule functionality has been enhanced with a new Delay sending type that lets you postpone publishing subscriber messages by a specified amount of time after message creation.
8
The sess-control.sh script has been rewritten to support the capability of starting and stopping the archive and e-mail services.
9
You can now delete subscriber messages in Message Monitor.
10
QXtend provides the ability to easily call the direct data publishing API from core QAD Enterprise Applications without any new programs, specific setup, or configuration.
QXtend Outbound Control (36.16.19) in QAD EA now allows you to specify an Appserver configuration name—maintained in AppServer Maintenance (36.19.1)—and the name of the source application configured in QXO for the QAD EA instance. If the default configuration is used during installation, then the configuration will be automatically created.
A new program has been created that can be used by any application that is a part of the QAD EE baseline to publish business events to QXtend Outbound using the Direct Data Publishing API.
Fixes
 
Fix Description
Internal ID
Issue Affected Versions
For a file drop subscriber, if the file cannot be successfully written, subscriber message status now is set to SENDERR rather than DLV.
QXT-639
1.1+
Known Issues
1
To avoid potential issues, QXO triggers for the sct_det and spt_det tables are not deployed for QAD EE.