SR-A14735 · Issue 257217
Corrected jmxConnector thread termination
Resolved in Pega Version 7.2.2
In an installation with several PRPC JBOSS EAP-based nodes, the node running 'prsysmgmt' ('SMA') was periodically running out of Java Threads. This was due to JMX port connect threads being created for node authentication when SMA is deployed but then not correctly terminating on logoff or timeout (30 minutes). To correct this, logoff, timeout, deletion, or disconnect will now trigger the proper closing of any jmxConnnectors for that node.
SR-A87102 · Issue 257341
Corrected jmxConnector thread termination
Resolved in Pega Version 7.2.2
In an installation with several PRPC JBOSS EAP-based nodes, the node running 'prsysmgmt' ('SMA') was periodically running out of Java Threads. This was due to JMX port connect threads being created for node authentication when SMA is deployed but then not correctly terminating on logoff or timeout (30 minutes). To correct this, logoff, timeout, deletion, or disconnect will now trigger the proper closing of any jmxConnnectors for that node.
SR-A24414 · Issue 260410
Flexibility added for ruleset persistence with dynamic locale
Resolved in Pega Version 7.2.2
When launching an intent in CS, the content sporadically failed to localize all or part the content until the browser was refreshed and the task re-entered. This was caused by a configuration that was trying to set the locale dynamically, an unsupported function. To better support flexibility, changes have been made to honor the current Ruleset List instead of the default Ruleset List so that even if the locale changed dynamically, the changed rulesets will be persisted.
SR-A90790 · Issue 262061
Layout group tab focus issue fixed
Resolved in Pega Version 7.2.2
he user is having a tabbed layout group, by imposing If visibility when conditions were imposed on a tabbed layout group such that only one tab was visible in Section pyCaseContent, the default Information tab did not receive focus upon completion of the assignment and all of the information was not rendered after a manual focus click. This was an error in the expand indication parameter value handling for the tab layout group, and has been fixed.
INC-149466 · Issue 607610
Fixed alias assigned to custom categories to handle Oracle limitations
Resolved in Pega Version 8.5.2
When trying to access CHAT via interaction portal, Oracle SQL was fired with incorrect syntax. This was traced to an Oracle limitation of 30 characters on the length of the table name, table alias name, or column name in database versions prior to 12.2. This is caused an SQL exception if the Pega class name was more than 30 characters. To prevent this, a fixed alias has been assigned to the custom category table.
INC-138501 · Issue 592287
Added VBD support for CSRF token setting
Resolved in Pega Version 8.5.2
Attempting to open any VBD reports in the marketing portal for a simulation test caused the user to be logged out. Investigation showed that this happened when CSRF token check was enabled in System > Settings > Cross-Site Request Forgery, and was caused by the planner not passing the CSRF tokens in its Ajax calls. To resolve this, handling for the CSRF tokens has been added to the necessary Ajax calls.
INC-143531 · Issue 598644
Dirty Flag reset updated
Resolved in Pega Version 8.5.2
After opening a case in Cosmos, making updates, and then navigating away without saving, the dirty flag message appeared as expected and offered the option to save, discard, or cancel. After clicking on save and opening the next case, performing the same steps did not cause the dirty flag to display when navigating away. This has been resolved by updating the reset of the isDirtyDialogOpen inside the hide API of a modal close.
INC-138501 · Issue 592286
Added VBD support for CSRF token setting
Resolved in Pega Version 8.4.4
Attempting to open any VBD reports in the marketing portal for a simulation test caused the user to be logged out. Investigation showed that this happened when CSRF token check was enabled in System > Settings > Cross-Site Request Forgery, and was caused by the planner not passing the CSRF tokens in its Ajax calls. To resolve this, handling for the CSRF tokens has been added to the necessary Ajax calls.
INC-143531 · Issue 598645
Dirty Flag reset updated
Resolved in Pega Version 8.4.4
After opening a case in Cosmos, making updates, and then navigating away without saving, the dirty flag message appeared as expected and offered the option to save, discard, or cancel. After clicking on save and opening the next case, performing the same steps did not cause the dirty flag to display when navigating away. This has been resolved by updating the reset of the isDirtyDialogOpen inside the hide API of a modal close.
INC-146237 · Issue 608744
Corrected popover scroll for AnyPicker
Resolved in Pega Version 8.5.2
Using the AnyPicker control caused display problems. In the initial display of the selection list, the line of choices and the search field overlapped and they were displayed from the second line of choices which forced the user to scroll up to see the first line. After displaying the selection list, clicking outside the selection list without selecting anything to close the list and then displaying the selection again caused the options to be displayed from the 4th line, requiring a scroll up to see lines 1 to 3. This has been resolved to ensure the Scroll on Popover goes to the first element.