Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A92706 · Issue 260877

out-of-the-box Approval step section checking improved

Resolved in Pega Version 7.2.2

The out-of-the-box Approval step which takes custom section name as parameter did not work if the section was in the Framework/At work group level because the pzApprovalPreProcessing activity checked section existence using Obj-Browse, which checked only in the existing class and not in the work pool. The system has been updated to use Obj-Open in the pzApprovalPreProcessing activity to check if the section exists. This also checks if the section exists in its parent hierarchy.

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-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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us