|
Fix Description
|
Internal ID
|
Issue Affected Versions
|
|
Previously, the QXtend installer wrote the event file with the QDoc version as a suffix during upgrade, which caused a problem. Now the installer does not change the QDoc event files during upgrade.
|
QXT-1833
|
1.8+
|
|
For an MFS-QXtend integration, the data in the response QDoc sometimes was inconsistent with the API dataset sent to QXtend. The issue has been fixed.
|
QXT-1913
|
1.8+
|
|
Previously, when setting the maxuses value of UI connection pool in connectionManagerConfig.xml to 1 and suppressResponseDetail to false, the response QDoc got the error “No response from MessageServlet for HTTPPost to get API User data”. This issue has been fixed.
|
QXT-1915
|
1.8+
|
|
Previously, a “File not found” or “Could not read request file” error could occur during processing queue. Now this issue has been fixed.
|
QXT-1916
|
1.8+
|
|
Previously, if there was an error during Inbound upgrade in a YAB environment, Inbound configurations would be missing after the issue was solved and upgrade was rerun. This issue has been fixed.
|
QXT-1923
|
1.8.7
|
|
Previously, the perpetual Excelerator license was removed during QXtend upgrade. In this case, you had to enter the license after upgrade. Now the license is kept during upgrade.
|
QXT-1929
|
1.8+
|
|
For 2015 EE or later versions, when a UI API agent was reused with a different set of credentials or domain, it failed to log out of the session. As the orphaned sessions were built up, the login process slowed down as the login procedure tried to clean up the orphaned sessions. Now this issue has been fixed.
|
QXT-1936
|
1.8.6+
|
|
A memory leak in QXtend Inbound Alert Configuration Manager (responsible for sending out alert emails) has been fixed.
|
QXT-1941
|
1.8+
|