SR-A88385 · Issue 257722
Thumbnail images consistently displayed in overlay
Resolved in Pega Version 7.2.2
When thumbnails were configured with the control pzAttachmentThumbnail), the overlay showed the image differently based on the location of the thumbnail in the screen, for example one side displaying with a scroll bar while the other did not. The earlier design was purely based on non-autogenerated code using a PopOver API call, which couldn't honor the position of the overlay. To resolve this, the Attach Field configuration has been modified so that all the Thumbnail overlays are shown using Local Action and thumbnails will be shown using autogenerated pxIcon control.
SR-A89637 · Issue 259256
Search for Work gadget updated to accept "StartsWith"
Resolved in Pega Version 7.2.2
When using a fixed portal, the Search for Work gadget was not working for the option "Starts With" when pxOperatorMap rule was being called from newly added Property-Map-Value methods. This was caused by pxOperatorMap not having a return value for StartsWith, causing the default value"=" to be returned. This has been fixed by adding a return value for "StartsWith", "NotStartsWith", "EndsWith", "NotEndsWith", "Contains", "NotContain", "IsNull", and "IsNotNull" in pxOperatorMap.
SR-A90472 · Issue 258243
Population handling added for null value flowType property
Resolved in Pega Version 7.2.2
While launching the case local action, a clipboard error was generated indicating the InternalStageFlow failed to find the named RULE-OBJ-FLOW. This was caused by a null flowType property value in the PegaProComUtilities populateFlowActions--(ClipboardPage, ClipboardPage, PublicAPI) function due to the order of actions, and the system has been updated to seek the flowType property of an assignment if it encounters a null value.
SR-A91743 · Issue 259136
Security update for pxInitials control
Resolved in Pega Version 7.2.2
XSS (Cross Scripting Filter) has been added for potentially exploitable parameters in the pxInitials control.
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.