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-A20581 · Issue 242760

Added checks to pagelist indexes for processing and recovery

Resolved in Pega Version 7.2.1

Sporadically, work objects saved to the database generated the error "The Flow Action pre-processing activity pyPopulateCaseContentsWrapper failed: cannot be null or blank. page: . Details: Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getProperty(String, char)" This happened when changes to Indexes in pagelists were getting overridden with another pagelist index, causing data to be lost on database save. A check has now been added to identify whether the entry has been processed in the current encode, and a hard check has been inserted to prevent data loss of page lists.

SR-A20593 · Issue 238898

Pagination added to Hotfix Manager

Resolved in Pega Version 7.2.1

If there were more than 10 uncommitted hotfixes, the Hotfix Manager was not able to display them all due to a page limit and pagination being disabled by default. The pagination footer has now been made visible to allow viewing of the full list of uncommitted fixes.

SR-A20603 · Issue 241334

Post-upgrade Connect-SOAP multi-ref mapping fixed

Resolved in Pega Version 7.2.1

After upgrade, the Connect-SOAP responses including multi-refs were not getting mapped correctly and there were problems viewing the response message from the SOAP service. This has been fixed.

SR-A20634 · Issue 248378

Added handling for missing blob from external data class

Resolved in Pega Version 7.2.1

When using an external data class, an error was generated complaining of "trying to retrieve property pxInsHandle from a fully exposed table that does not contain it". This happened because the external table did not have a blob column but did have pxObjClass and pzInsKey, and handling has been added to correct this.

SR-A20639 · Issue 239986

Special Character conversion added to ExportToPDF

Resolved in Pega Version 7.2.1

If the file name used in the ExportToPDF activity contained special characters like ", ?, *, , |, :, a JS exception occurred. To resolve this, special characters like ", ?, *, , |, : will be replaced with "_" as these special characters are not supported in file names.

SR-A20675 · Issue 243568

Repaired encrypted remote tracing

Resolved in Pega Version 7.2.1

Remote tracing was not working when URLEncryption was enabled due to an error calling SafeURL. This has been fixed.

SR-A20761 · Issue 247086

New test Suite ruleform display resolved

Resolved in Pega Version 7.2.1

When attempting to create a new unit test suite, no ruleform was presented. Instead, raw XML was displayed. To correct this, the TestSuite Rule Form has been autogenerated so that it is viewable and openable in 7.2 in supported browsers.

SR-A20790 · Issue 239549

Refresh section works after spellcheck

Resolved in Pega Version 7.2.1

When using a radio button with section refresh and conditional layouts and an additional spell check icon, clicking on the spell check icon and then changing the radio button value did not refresh the section. Instead, the busy indicator symbol appeared and caused the system to hang. This was traced to a permission denied JS error occurring on the refresh section after spellcheck when the getListeners API tried to access an orphaned RTE body. This has been fixed.

SR-A20815 · Issue 242354

Resolved Chart Wizard crash

Resolved in Pega Version 7.2.1

Attempting to update the colors of a chart through the Chart Wizard caused a crash if the color picker icon was double-clicked instead of single-clicked. This was an issue with the clipboard page handling, and has been fixed.

SR-A20832 · Issue 239823

Fixed stateless SOAP timeout after upgrade

Resolved in Pega Version 7.2.1

After upgrade, stateless SOAP services were timing out. This was caused by lost values for the Max Active, Max Idle requestors count, and Max wait time in the service package. The configurations have been modified to retain these values.

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