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

SR-A21908 · Issue 245505

Eliminated new case creation on browser refresh

Resolved in Pega Version 7.2.1

When using the tabbedscreenflow7 harness, refreshing the screen caused a new Case to be created. This was seen in a no-frame portal with the top navigation for every action set to createNewWork, and the same new work URL was hit during the refresh. This has bene fixed by modifying replaceHistory in dynamiccontainer_lite.js to add a condition to skip returning when strHarnessMode is not action.

SR-A21917 · Issue 243020

Added calendar conversion support for Thai locale

Resolved in Pega Version 7.2.1

With locale set to Thailand, the date/time returned caused a substitute operator to be selected. This was an issue with the action time being calculated in the Buddhist calendar used in Thailand whereas the goal time was calculated in the Gregorian calendar. The Buddhist calendar is 543 years ahead of Gregorian, so the isAvailable RUF will convert this date by subtracting the difference.

SR-A21931 · Issue 242711

XY chart Dashboard reports updated to handle empty data

Resolved in Pega Version 7.2.1

Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.

SR-A21931 · Issue 233188

XY chart Dashboard reports updated to handle empty data

Resolved in Pega Version 7.2.1

Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.

SR-A21935 · Issue 247142

Corrected data page Lookup logic

Resolved in Pega Version 7.2.1

While trying to source a Datapage with Lookup, a "No records found" error was generated by the fetch using the pyClassName from parameter and considering that as primary page class instead of the data page page class. This has been corrected by using the pxObjClass from the parameter page, which is an actual data page class.

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