SR-A67932 · Issue 251208
Blank query field in Bulk Actions defaults to none instead of all
Resolved in Pega Version 7.2.2
Due to the MyCheckedOutRulesBulk Listview not adding a default 'when' condition in the query when the query value was blank, using Bulk Actions -> Select All would return a list of all non-resolved rules in the system rather than the expected value of 'none' for the list of checked rules for the bulk processing tool. This has been resolved.
SR-A19246 · Issue 254062
Customized ordering ability for delegated rules added
Resolved in Pega Version 7.2.2
Previously, the order that delegated rules were displayed in was always the reverse of the order they were added to the System-User-MyRules form, showing the most recently delegated items at the top regardless of the order they have on that page. An enhancement has now been added to allow customization of the order through a provided extension point using 'post load processing' of the data page D_pzFilteredDelegation.
SR-A19246 · Issue 254058
Customized ordering ability for delegated rules added
Resolved in Pega Version 7.2.2
Previously, the order that delegated rules were displayed in was always the reverse of the order they were added to the System-User-MyRules form, showing the most recently delegated items at the top regardless of the order they have on that page. An enhancement has now been added to allow customization of the order through a provided extension point using 'post load processing' of the data page D_pzFilteredDelegation.
SR-A22331 · Issue 252650
Blocked EditList rules ignored in listview
Resolved in Pega Version 7.2.2
When attempting to open the Data table list from the Designer studio through DesignerStudio > Data Mode > Data Tables > Data Tables, an exception was generated if the EditList rule was blocked. This was traced to the activity for displaying EditList rules opening the ruleform regardless of the availability of the rule, and has been resolved by adding a check that will filter blocked or withdrawn rules from being processed for the listview.
SR-A77382 · Issue 253160
Requestors correctly populated in Remote Tracer dropdown
Resolved in Pega Version 7.2.2
When running Tracer and selecting the Remote Trace, the connection dropdown loaded the first time but was empty when attempting to change the requestor. The dropdown sometimes loaded on subsequent tries. This was traced to a race condition with custom event handling, and the code has been updated to ensure all requestors load as expected.
SR-A83178 · Issue 254824
Resolved Null Pointer Error in edited complex data transform
Resolved in Pega Version 7.2.2
While editing a data transform, using a "For Each Page" step with a "When" child step and a "Set" grandchild step along with checking "Also use each page as source context" on the "For Each Page" step, the expression builder for the set "Set" did not launch when initially clicked. Clicking to another tab in the Designer Studio and then back to the data transform allowed the expression builder to launch, but once launched it did not have the source value populated. Submitting, closing, or canceling the modal (regardless of whether or not changes were made) resulted in a popup indicating a Null Pointer Error. This was caused by a java script Null Pointer Error in the OpenRuleAdvanced_OverLabel control which led to the sourceElement value being reported as null in the mentioned scenario. This has been fixed.
SR-A96852 · Issue 264159
Resolved OOM error when adding VDB DNode
Resolved in Pega Version 7.2.2
A memory leak was found relating to JBDC PreparedStatement objects (char arrays allocated to hold database query results) used when VBD loads its data partitions. This has been fixed with the addition of code to close the PreparedStatement objects created when loading Actuals partition data.
SR-A99782 · Issue 266250
XSS vulnerability closed in Warning Justification Text field
Resolved in Pega Version 7.2.2
A potential XSS vulnerability has been addressed in the Warning Justification Text field.
SR-A96515 · Issue 267504
Added handling for Qualsys security scan
Resolved in Pega Version 7.2.2
A stack overflow error was being generated when running a Qualsys vulnerability security scan on servers hosting IBM WebSphere and Pega, resulting in two of the three Pega nodes in production becoming unresponsive and requiring a restart. This was caused by the third party tool connecting to port 7003, which is used by Stream data set server, and sending unknown requests. To avoid this, the system has been updated to not send back a response if the channel is closed
SR-A79502 · Issue 253855
Corrected ability to add DNode port via prconfig
Resolved in Pega Version 7.2.2
Adding DNode Port via prconfig was not taking effect due to the configuration values being stored as strings, but the code which reads the storage port configuration treats the setting as integer. This has been fixed.