SR-A76776 · Issue 254774
Pega Pulse Link Description text box handled dynamically
Resolved in Pega Version 7.2.2
To correct an issue where the Pega Pulse Link Description text box was not visible due to screen size (i.e., the Pega Pulse fields were not getting wrapped on the screen, the container for the pzLinkDescription section has been changed to use dynamic layout so it correctly adjusts according to the width.
SR-A91228 · Issue 258648
ConsiderLockingMode passed to GetNextWork
Resolved in Pega Version 7.2.2
When calling the OpenAndLockWork activity in the MoveToWorkList activity, the ConsiderLockingMode parameter was not being passed. This parameter value is checked to determine whether it is optimistic locking or not. To enhance the system, the First step of Assign-WorkList now sets the parameter ConsiderLockingMode to true/false based on based on the GetNextWork_MoveAssignmentToWorklist system setting so that optimistic locking is considered.
SR-A91228 · Issue 264407
ConsiderLockingMode passed to GetNextWork
Resolved in Pega Version 7.2.2
When calling the OpenAndLockWork activity in the MoveToWorkList activity, the ConsiderLockingMode parameter was not being passed. This parameter value is checked to determine whether it is optimistic locking or not. To enhance the system, the First step of Assign-WorkList now sets the parameter ConsiderLockingMode to true/false based on based on the GetNextWork_MoveAssignmentToWorklist system setting so that optimistic locking is considered.
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-A99962 · Issue 266646
Wait enhanced to maintain case status for multiple children
Resolved in Pega Version 7.2.2
A Parent case that was configured to resume when the sub-case reached a particular status using "Pending-ParentCaseResume" was not working as expected if there were multiple child cases for a single parent. This was due to the Wait shape taking the current status of the activator (first child case resolved) instead of the dependency status for which the wait shape should be looking for (subsequent child case), and has been fixed by establishing a new property on the Activator page to hold the dependency status and rely on this while checking if the activator has crossed the desired status.
SR-B1873 · Issue 271608
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.
SR-B238 · Issue 271610
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.