INC-142589 · Issue 595489
Corrected tooltip evaluation for multiselect
Resolved in Pega Version 8.4.3
After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.
INC-142714 · Issue 596554
Recent Cases from different applications available to open
Resolved in Pega Version 8.4.3
An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.
INC-143005 · Issue 596954
Fluid Overlay displays as expected in Firefox
Resolved in Pega Version 8.4.3
After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.
INC-125122 · Issue 581253
JMX authentication added
Resolved in Pega Version 8.2.8
Support has been added for JMX authentication through user and password.
INC-135359 · Issue 587036
CORS header configuration added for Stream tier
Resolved in Pega Version 8.2.8
An enhancement has been added that allows setting the CORS header (Access-Control-Allow-Origin) to allow *.DOMAIN.com on Stream tier (/stream/view & /stream/click) calls by way of the setting /stream/httpHeaders .
INC-132963 · Issue 572247
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.2.8
Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.
INC-134412 · Issue 577541
Proposition filter maintains eligibility criteria
Resolved in Pega Version 8.2.8
Eligibility details were occasionally lost when updating Offers. This was traced to a configuration that could cause individual criteria rules to be deleted when rows were added in the middle of the list. To resolve this, validation has been added to each eligibility criteria row to ensure that all expected values are entered for each row, and validation has been added to the logic string when advanced mode is used for offer eligibility criteria.
INC-135823 · Issue 580944
Transient property passivation handling improved
Resolved in Pega Version 8.2.8
Frequent "com.pega.pegarules.pub.PRRuntimeException" errors were seen in the production log file while working on the WO. This was traced to corruption in the blob caused by transient properties during passivation. To resolve this, corrections have been made to the handling for the transient property entries in the blob.
INC-138840 · Issue 599979
Data-Summary reports default will not use the rule resolved setting
Resolved in Pega Version 8.2.8
An intermittent issue was seen where a query could become stuck for ~2 hours in the database. This has been resolved by setting the default for Data-Summary reports to not use the rule resolved setting.
INC-127976 · Issue 566157
Delete Requestor method updated for use with CMT
Resolved in Pega Version 8.2.8
JMS MDB Listeners with Container Managed Transaction (CMT) enabled in Websphere 8.5 had global transactions fail. To initialize a JMS-MDB listener, a requestor of type APP is used. Upon the service being fully initialized, the requestor is removed by executing a delete operation followed by a COMMIT. However, in this scenario, the initialization operation is running within a CMT context and a SQLException was raised indicating that the commit was not allowed. To resolve this, the delete requestor method has been refactored to take into account the CMT context so the commit is not executed if the transaction is managed by the container.