|
Fix Description
|
Internal ID
|
Issue Affected Versions
|
|
In previous releases, when a password was supplied in the request QDoc, it was also contained in the response QDoc and the e-mail alert as a part of the context information. This has been fixed and passwords no longer appear in response files and e-mail alerts.
|
QXTS-39
|
1.4+
|
|
If a queue is set to automatically add a SOAP envelope, the Queue Manager now includes the <requestor> tag in the SOAP envelope only when the Require Authentication option is selected for the receiver and Requestor ID is not blank in the Queue settings. Previously, the Queue Manager included an empty <requestor> tag line without attributes in the SOAP envelope when requestor ID was not supplied, which caused every request to fail with the “invalid User/Password” error.
|
QXTS-40
|
1.7+
|
|
The Sales Order Shipment QDoc has been fixed so that it does not skip updating the line iteration
|
QXTS-43
|
1.7+
|
|
Previously, when ODBC security was activated, if a record in QAD Enterprise Applications was locked by another user, QXI returned a message indicating the record was locked but could not identify the user locking it. This has been fixed and the system now displays the user locking the record in the message.
|
QXTS-57
|
1.1+
|
|
The system has been modified to set the session idle time to 0 (zero) after processing each QDoc. Previously, the session idle time was not reset and when a session times out, an error message “User not authorized to access this function” was displayed.
|
QXTS-63
|
1.6+
|
|
Performance of native APIs has been improved through an authentication cache.
|
QXT-979
QXT-947
|
1.7+
|
|
When QXtend 1.7 and 1.7.1 are installed against earlier versions of QAD Enterprise Applications, some adapter files for Excelerator are missing, which causes the error “MenuSecurityService.p not found.” These missing adapter files are now included.
|
QXTS-925
|
1.7+
|
|
License code for Excelerator (Initial Data Load) can now be successfully loaded into QXtend on AIX machines.
|
QXTS-1001
|
1.7+
|
|
Previously, installing QXtend on HP machines using PA-RISC chips might fail when unzipping packages for QXtend adapters or the QXO qxevents database. Now this has been resolved.
|
QXTS-1015
|
1.6+
|