|
Fix Description
|
Internal ID
|
Issue Affected Versions
|
|
The Installer now deploys the correct version of QRA library depending on the Progress version when QRA Library is absent from QAD ERP.
|
QXT-1580
|
1.7+
|
|
Inbound now returns the correct error when an SI API QDoc has no username/password or sessionID and there is no username/password defined in the connection pool. Previously, in this situation with QAD 2014 EE and QAD 2015 EE, Inbound returned success without processing the QDoc.
|
QXT-1768
|
1.8.6
|
|
Previously, if the Queue Manager was configured for Inbound, error messages were found in Install Log when starting Inbound. Now this issue has been fixed.
|
QXT-1779
|
1.8+
|
|
When QXtend 1.8.6 was installed against QAD SE, the default configuration failed. This issue has been fixed.
|
QXT-1784
|
1.8.6
|
|
Previously, in some situations Inbound would report ConcurrentModificationException error when processing SIAPI QDocs. This issue has been solved.
|
QXT-1785
|
1.7+
|
|
Previously, in some situations when MFG/PRO error message was long, QXtend Inbound could not return the error message properly. This issue has been solved.
|
QXT-1824
|
1.7+
|
|
Now the Queue Manager does not stop processing when there are pending QDocs. Previously, it could get stuck and required a restart.
|
QXT-1830
|
1.7+
|
|
When loading data from Excelerator, the corresponding log entry in qdocSummary log no longer has a line break after the first field.
|
QXT-1850
|
1.8+
|
|
When posting UIAPI QDocs, Inbound now takes the domain time zone instead of the QXtend server time zone.
|
QXT-1851
|
1.7+
|
|
QXtend Inbound no longer throws AdapterException003 when processing QDocs.
|
QXT-1853
|
1.7
|
|
Inbound now can catch the null appServer connection and throw a meaningful error QdocException 94 for SIAPI QDocs.
|
QXT-1871
|
1.7+
|
|
The Session ID from the connection pool cache is used in place of a blank Session ID in the QDoc request. Previously, if the Session ID in the request was blank, then the User and Password from the connection pool were used and a new session was created every time.
|
QXT-1882
|
1.7.1+
|
|
A queue can always continue processing after restarting. Previously, the queue could get stuck if it was started while processing multiple requests.
|
QXT-1893
|
1.7+
|