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-A21017 · Issue 239317

Parameter label mismatch corrected for import

Resolved in Pega Version 7.2.1

During upgrade, activities or functions which had Parameter type 'Double' were automatically converted to String data type upon Import into the target Environment even when the XML indicated DOUBLE. This was an issue with rendering the value in the UI: the pyLabel for double parameter type was "Double" not "DOUBLE" in the Data Transform rule pyLoadDataTypes, which didn't match. The activity has now been updated to use DOUBLE.

SR-A21081 · Issue 242397

Strategy rule information added to tracer

Resolved in Pega Version 7.2.1

A tracer invoked with SOAP service --> Activity --> Flow --> Interaction rule --> Strategy was only showing the the executed components in its (reversed) execution order and did not show the execution strategy path. This has been fixed.

SR-A21588 · Issue 241928

Name retrieval updated for node sub-units

Resolved in Pega Version 7.2.1

A retrieval error for the sub-unit name of a node was causing a "Cannot render section" error in the Organization Chart tab. This has been corrected.

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-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-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-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-A22067 · Issue 243520

Corrected passing Current Parameter Page in Collections

Resolved in Pega Version 7.2.1

When attempting to call a rule in a Response Actions entry on a Collection flow, the configuration panel would not submit when "Pass Current Parameter Page" was checked and there were required parameters on the rule being called. This was traced to an unneeded validation being performed, and has been resolved.

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