Release Notes for QXI
Release Notes for Current Version
QXI Server Version: 1.8.6Date: March 2015QAD Enterprise Applications Compatibility: eB SP4 through current releaseSupported 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.4Supported Java Version: Java 1.6 or higherQAD QXtend Documentation: QAD QXtend User Guide (70-3190-1.8.6) and QAD QXtend Installation Guide (78-0952-1.8.6) New and Changed Features
1 A new parameter Number of Records per Page has been added to queue configuration to specify how many QDocs can be displayed on one page.
2 Some Inbound programs/scripts have been modified to support the QAD 2015 EE Cloud version, which uses QAD Reference Architecture (QRA). For example, UIAPI client scripts use a different startup program in the QAD 2015 EE Cloud version.
3 QXtend Inbound Usage Report now has a date range filter, which allows you to view the usage records for a specific period.
4 Two new parameters, QRA Source Directory and Extra Propath Entries have been added to QXtend Installer.
5 QXtend can now detect browser type and is able to give a warning message if the browser is not Internet Explorer.
6 A new configuration element includeUniqueIdInQdoc has been added to the qxtendconfig.xml to specify whether a unique ID should be put in the session context of every QDoc response. The unique ID is the QXtend ID associated with each QDoc in qdocRequests, qdocResponses, and qdocSummary log files. The uniqueID in QDoc responses helps you to quickly locate the QDoc in log files.
7 The following QDocs are merged into QXtend:
• SAQ-related QDocs for 2015 EE
• New EOB QDocs for EE
Fixes
Fix Description | Internal ID | Issue Affected Versions |
Previously, there was a compilation error when compiling QGen program in ICT-enabled environment. This issue has been fixed. | QXT-1767 | 1.8.2+ |
Previously, when a QDoc had scopeTransaction set to true and an application error occurred, in some situations, it would take about two minutes to get a response QDoc. This issue has been fixed. | QXT-1748 | 1.7+ |
Previously, when maxUses of a UPAI connection pool was reached by an agent, and a QDoc with scopeTransaction set to true had an application error, it took two minutes for a response to be returned. This issue has been fixed. | QXT-1742 | 1.7+ |
The QDocs with brackets in their names have been replaced or renamed to avoid issues in using these QDocs. | QXT-1706 | 1.8.5 |
Previously, QDoc processing failed with StringIndexOutOfBoundsException if the field type format contained a right bracket. The issue has been fixed. | QXT-1702 | 1.7+ |
Previously, the byte order mark (BOM) in a QDoc request that was processed by queue caused a SOAPFault. This issue now has been fixed. When the BOM filter on the Axis Servlet is turned on, the filter removes the BOM in the QDoc request. | QXT-1698 | 1.7+ |
The issue that modifying a SIAPI QDoc in Inbound blanked out the methodName of the QDoc has been fixed. | QXT-1690 | 1.7+ |
The syncPassword and newPassword fields in session context that are used by QAD Mobile Field Service are obfuscated as asterisks in the response QDoc, qdocRequests.log, and qdocResponses.log. Previously, the passwords were shown in clear text. | QXT-1683 | 1.7+ |
Fixed the reisrc01.p program to bypass the Issue Data Input Selection list and remapped the recordRepetitiveLaborTransaction API for the existing version eB_2. | QXT-1682 | 1.8.5 |
The message text of the email alerts that QXtend generated can be shown as message body, instead of as attachments, in MS Outlook. | QXT-1671 | 1.7+ |
When generating WSDL of QXI APIs, the minOccurs value of a table element in a generated schema is the same as in the original schema instead of being always 0. | QXT-1669 | 1.7+ |
maintainItemMaster SIAPI now validates the pt_part field and reports an error when the part number contains more than 18 characters. | QXT-1667 | 1.7+ |
When the request QDoc XML is invalid, the system now returns “FailureException002 - Error processing xml document.” | QXT-1665 | 1.7+ |
Previously, if Internet Explorer 11 was used, the left side menu frame could not be displayed correctly after creating or deleting Email Alerts related items. This issue has been fixed. | QXT-1641 | 1.8.5 |
Known Issues
• When installing QXtend 1.8.6 against QAD SE, the installer stops at a default configuration error. Follow the instructions in article AA-93907 in QAD Knowledge Base to complete the installation.
• When QXtend 1.8.6 works with QAD 2015 EE in the Cloud environment and LDAP users have been synchronized into EE, for FinAPI QDoc processing, only LDAP user ID can be used as username in connection pool or request QDocs. Domain\userID or user e-mail cannot be used.
• When QXtend 1.8.6 works with QAD 2014 EE and QAD 2015 EE, if no username/password is set in the connection pool and no username/password or session ID is provided in the QDoc, the QDoc cannot be processed, but the system still returns success. This issue happens with SIAPI QDocs.
QDoc Disclaimer
Some of the QDocs pre-delivered with QXtend Inbound only cover the basic flows of the corresponding program. It could happen that a QDoc is missing certain flows or fields. QXtend provides QGen, the tool to customize QDocs.