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-A21756 · Issue 244285

defined-on class error resolved

Resolved in Pega Version 7.2.1

A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.

SR-A21756 · Issue 243206

defined-on class error resolved

Resolved in Pega Version 7.2.1

A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.

SR-A21792 · Issue 242548

Saver.addBatch updated to log exception details

Resolved in Pega Version 7.2.1

To improve diagnostics, an SQL exception in the Saver class will log the actual exception instead of a null pointer.

SR-A21810 · Issue 231480

PreClose updated to better handle inactive DC documents

Resolved in Pega Version 7.2.1

The PreClose extension point was not always being triggered for inactive DC documents utilizing the pzClearRecentItem and pzClearAllRecentItems APIs due to stale settings. The correct this, the handlegadgetLoad method has been updated to delete the docObj after the document has loaded.

SR-A21810 · Issue 241087

PreClose updated to better handle inactive DC documents

Resolved in Pega Version 7.2.1

The PreClose extension point was not always being triggered for inactive DC documents utilizing the pzClearRecentItem and pzClearAllRecentItems APIs due to stale settings. The correct this, the handlegadgetLoad method has been updated to delete the docObj after the document has loaded.

SR-A21830 · Issue 244836

Improvements made to History Compare

Resolved in Pega Version 7.2.1

The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.

SR-A21830 · Issue 246779

Improvements made to History Compare

Resolved in Pega Version 7.2.1

The SMS treatment rule full history provided by Pega Marketing was not reflecting the actual changes that were applied in each revision and the compare differences functionality was not showing expected differences. The handling of the comparison has been updated to correct this, and the logic has been further improved to include the "initial creation" version when appropriate.

SR-A21835 · Issue 243872

Flow names can now be found when using duplicate search mechanism

Resolved in Pega Version 7.2.1

When using the duplicate search mechanism and trying to resolve a case as duplicate, an error appeared indicating that the flow name could not be found. This was a handling error, and has been fixed.

SR-A21844 · Issue 241153

VBD enhancements

Resolved in Pega Version 7.2.1

The following enhancements have been added to the Visual Business Director feature of PRPC Decisioning: - Support added for changes in field sizes after partitions load - Partitions will be loaded immediately on VBD server startup - Data expiration based on inactivity is disabled to reduce query latency - Timeout added to VBD queries to handle latency when Partitions initially load - Code that processed Actuals query JDBC resultset is optimized

SR-A21905 · Issue 242013

Post value handles editing existing RTE

Resolved in Pega Version 7.2.1

On Change event, the Post Value action was not working when editing RTE that had some content already present in it. This was a harness logic issue, and has been corrected.

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