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-A14151 · Issue 244440

Autocomplete select updates as expected

Resolved in Pega Version 7.2.1

An intermittent problem was found with autocomplete that selected a previously set value if text was typed in the autocomplete box and the value was selected instead of the search text. This was traced to a press of the capslock key being interpreted as an unprintable character, causing an abort of the request and change tracker not having the correct update. The function processkey of autocompleteag.js has now been updated to not abort the request when a non-printable character is typed.

SR-A14168 · Issue 230039

Unique page names generated for nested child work items

Resolved in Pega Version 7.2.1

When multiple child work items were created using pxAddChildWork in one transaction, the same page name was getting used and causing errors. This has been fixed by making pagename unique by appending currentdatetime.

SR-A14230 · Issue 230423

IconRequired fixed for repeating layouts

Resolved in Pega Version 7.2.1

The iconRequired span was only being generated for the first row of any repeating layout structure. This has been fixed in the GenerateCellContent RUF.

SR-A14267 · Issue 230714

Enhancements to SystemCleaner and SystemPulse

Resolved in Pega Version 7.2.1

Insufficient allocated space for passivation data in a shared filesystem can lead to passivated requestors not being properly cleaned up and possible OOM issues. In order to provide better support, SystemCleaner has been enhanced to better diagnose issues related to insufficient allocation, and any resulting information can be found in deleteExpiredDir in com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage . In addition, when the system pulse is disabled via pxSystemNodeStatus set to Unknown, it would silently run in SMA and no log messages were generated. Since critical agents should provide a more visible indication that the processes are not running as expected, both System Pulse and SystemCleaner have been modified to stop the server startup and report when the server status is unknown.

SR-A14267 · Issue 231247

Enhancements to SystemCleaner and SystemPulse

Resolved in Pega Version 7.2.1

Insufficient allocated space for passivation data in a shared filesystem can lead to passivated requestors not being properly cleaned up and possible OOM issues. In order to provide better support, SystemCleaner has been enhanced to better diagnose issues related to insufficient allocation, and any resulting information can be found in deleteExpiredDir in com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage . In addition, when the system pulse is disabled via pxSystemNodeStatus set to Unknown, it would silently run in SMA and no log messages were generated. Since critical agents should provide a more visible indication that the processes are not running as expected, both System Pulse and SystemCleaner have been modified to stop the server startup and report when the server status is unknown.

SR-A14283 · Issue 232771

Service request retry works in async mode

Resolved in Pega Version 7.2.1

The Retry mechanism has been modified to correctly pass the child requestor's status when service is configured in async mode.

SR-A14307 · Issue 228196

Landing page made unique for delegated rules

Resolved in Pega Version 7.2.1

When one delegated rule is opened and 'Manage change' was selected from the dashboard without closing the opened rule, the first opened rule is getting displayed each time. This was caused by the name in the landing page action not being unique, which has now been changed to ensure the expected results.

SR-A14313 · Issue 227652

Autocomplete displays properly after screen rotation

Resolved in Pega Version 7.2.1

A black gap appeared on the screen of iPad and iPhone devices when tying to use the autocomplete window after the screen was rotated between Portrait and Landscape modes. This was due to the autocomplete popover not accepting a % width setting, and the display method of the popover has been modified to display properly.

SR-A14325 · Issue 228543

Repositioned BusyIndicator to cover Target element

Resolved in Pega Version 7.2.1

If the section with busy indicator was taller than the viewport height, the busy indicator mask did not cover the lower part of the section when scrolling and the section was editable. This has been fixed by repositioning the mask to cover the part of the section editable in the viewport and also show immediately on scroll.

SR-A14336 · Issue 230881

Resolved NPE when @checkForSubstitute used

Resolved in Pega Version 7.2.1

If an assignment used the "Check Availability" setting and the operator was not available at that time, a NPE was generated in cases where the timezone needed to be parsed to complete the check. To correct this, the system has been modified to support time zones with more than 3 characters, and support was added for the IST timezone.

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