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-A94166 · Issue 262015
Fixed misaligned headers in decision table
Resolved in Pega Version 7.2.2
A misalignment of column headers was seen in a decision table when the number of columns added exceeded 18-20. This has been corrected by adding pixel adjustment of the scroll width to the decision table header when a range is selected for a column in pzRuleDeclareDecisionTableStandard js.
SR-A92650 · Issue 262402
PackageRuntime error resolved
Resolved in Pega Version 7.2.2
A pzPackageRuntime error when saving instance of custom rule was traced to the variable not being in the scope. This has been addressed.
SR-A97752 · Issue 271947
Test Suite operator ID error fixed
Resolved in Pega Version 7.2.2
After creating and executing a Test Suite, the error "Unable to open an instance using the given inputs: pxObjClass = "Data-Admin-Operator-ID", pyUserIdentifier = "System" appeared on the Dashboard landing page of the Automated Unit Test. This was due to the system not setting the operator identifier when doing the agent login, and has been corrected.
SR-A100251 · Issue 271797
Editing a decision table works on hardened system
Resolved in Pega Version 7.2.2
After enabling URL Encryption and URL Obfuscation in the Production Environment per Pega best practice recommendations to secure/harden an environment, an HTTP 400 error was thrown when attempting to Edit a Decision Table in Pega Marketing. This was an error in the URL decoding for the DisplayModalDialog HTML rules, and has been fixed.
SR-A88818 · Issue 261452
New pzPreMergeSave activity Rule-File- for multiple node propagation
Resolved in Pega Version 7.2.2
After merging rules of type Rule-File-Text across four nodes, there was a delay in the changes being reflected on the other nodes. The issue was caused by a simple save of Rule-File-Text not propagating pulseChange directly, and has been fixed by creating a new pzPreMergeSave activity Rule-File- to handle this merge.
SR-A87492 · Issue 256199
Strip "()" from Page name for Loop and Parameters for post-upgrade compatibility
Resolved in Pega Version 7.2.2
After upgrade, a change in system behavior with RUF Utilities.findClassOfPageReference returned the incorrect class name for pages that contained the string "()". For example, existing pages and classes has the entry TestPage.pxResults(), but the system is looking for an input page named TestPage.pxResults, and the startsWith check failed. To resolve this, the code has been updated with added logic in findClassOfPageReference to remove the empty () if it is present at the end of page and classes entry.