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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B74214 · Issue 329140

Null check added to contextClass

Resolved in Pega Version 7.4

If a contextClass was empty, multiple activities, including out-of-the-box activities, would intermittently fail with a NullPointerException. A null check has been added to resolve this.

SR-B75227 · Issue 330906

Performance improvements for opening a Data instance

Resolved in Pega Version 7.4

Logic improvements have been made to improve the performance of opening a Data instance from rule explorer.

SR-B75670 · Issue 328342

Lock & Roll correctly copies data types to new application copy

Resolved in Pega Version 7.4

After upgrade, using the "Lock & Roll" feature to create a new version of the application resulted in the data types not being correctly copied. This was due to a code error in the step "Locking the release", and has been fixed.

SR-B75713 · Issue 336535

Addressed "Cover count -1" error when resolving case with parent and child

Resolved in Pega Version 7.4

A "Cover count -1" error was appearing when resolving a case with both parent and child cases. The "Resolve" activity has been updated to remove the pyTopCaseWork page if findPagebyHandle returns that page and then do findPagebyHandle to get correct cover page. A null check for updatedatetime has also been added.

SR-B77120 · Issue 330083

Writability check added to ClipboardPage

Resolved in Pega Version 7.4

A node level declare page was failing with a readonly exception. This was caused by the assembler generating code to write to a ClipboardPage without checking whether it was writable, and has been corrected by adding a check for isReadOnly on ClipboardPage prior to calling putString on it.

SR-B77229 · Issue 332429

SQL error codes not displayed in getContent activity execution

Resolved in Pega Version 7.4

Due to a missing catch block in the exception handling, minor SQL error codes were unnecessarily displayed in the getContent activity. This has been fixed.

SR-B77643 · Issue 327227

Apache Struts updated

Resolved in Pega Version 7.4

Apache Struts has been updated to v2.3.34 .

SR-B77778 · Issue 339718

Handling added for Microsoft Internet Explorer resize harness looping

Resolved in Pega Version 7.4

When using Microsoft Internet Explorer, the resizeHarness would intermittently enter an infinite loop after being triggered, resulting in the Menu appearing and disappearing. This has become a known issue with Microsoft Internet Explorer, and the pzpega_ui_doc_harnesssizing.js resizeHarness method has been modified to compensate.

SR-B78460 · Issue 335973

Assembly errors sent to PDC and AES

Resolved in Pega Version 7.4

A large number of com.pega.pegarules.pub.generator.UnresolvedAssemblyError exceptions were found in the PegaRULES logs with no corresponding data in PDC-Central. LogHelper methods take a Throwable as an argument to trigger an alert, and Pega7 exceptions are supposed to generate EXCP0001 alerts which are sent to PDC. However, a review of EXCP0001's show that there were no messages for com.pega.pegarules.pub.generator.UnresolvedAssemblyError -- thus the exceptions were never sent to PDC and there was no visibility to system managers. This issue also occurred with AES. To correct this, a Throwable argument has been added in oLog.error() at all the places where this alert was needed.

SR-B80222 · Issue 339229

Assembly logging enhancements

Resolved in Pega Version 7.4

Logging enhancements have been made to capture information for errors thrown at Assembly Runtime to make diagnosing these types of problem easier.

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