Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number in order to find the associated Support Request.

SR-116508 · Issue 170253

Large flow handling improved for IE8

Resolved in Pega Version 7.1.7

When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.

SR-116818 · Issue 167121

Corrected swim lane routing with shapes

Resolved in Pega Version 7.1.7

While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, and has been corrected.

SR-117228 · Issue 168249

Resolved issues with Flow shapes distributed across Swim Lanes

Resolved in Pega Version 7.1.7

Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.

SR-A14774 · Issue 233421

Number formatting made consistent for Propositions

Resolved in Pega Version 7.2.1

In Proposition landing, a decimal property was rounded to three digits when shown in read-only mode but clicking on the edit option for the Proposition displayed the entire number with all the digits after the decimal. This was not a desired difference, and the presentation setting for Double type property has been modified to show all numbers after the decimal.

SR-A16960 · Issue 233587

Predictive Analytics rulesets excluded from RSA

Resolved in Pega Version 7.2.1

The Pega-provided Predictive Analytics rulesets were being incorrectly being checked and flagged by the Rule Security Analyzer. The PAD rulesets have now been properly excluded from the RSA check, and further analysis was done to find and fix other RSA flags that should have been excluded.

SR-A18333 · Issue 237135

Corrected JSON page group handling

Resolved in Pega Version 7.2.1

If DataSet-Execute method was used to cache a CustomerPage from Clipboard, using the same DataSet-Execute method to retrieve it from the cache using the "Browse by key" operation was not working correctly: If the page contained a page group property, then the retrieved CustomerPage contained additional invalid entries that led to errors in the mapping logic. This was an issue with the Clipboard page JSON converter not properly handling page groups, and has been corrected.

SR-A18550 · Issue 234678

Strategy and data flow behavior more consistent

Resolved in Pega Version 7.2.1

Strategy execution via data flow was producing different results depending on how it was executed. This was caused by the use of different types of pages based on the execution method, and the code has been updated to produce more consistent behavior.

SR-A18909 · Issue 235146

Strategy and data flow behavior more consistent

Resolved in Pega Version 7.2.1

Strategy execution via data flow was producing different results depending on how it was executed. This was caused by the use of different types of pages based on the execution method, and the code has been updated to produce more consistent behavior.

SR-A19104 · Issue 237289

Ability added to set TTL on data sets

Resolved in Pega Version 7.2.1

An enhancement has been added to Data Flow datasets to allow setting the Time To Live (TTL) on DDS stores from the canvas. This allows setting an expiry date on cached data, which is essential when working with large streams of data.

SR-A19355 · Issue 235876

Landing page Header correctly displays VBD Planner

Resolved in Pega Version 7.2.1

The Pega Marketing portal header was overlapped by the VBD Planner header, creating problems accessing the buttons on the portal header. The newly developed VBD Planner client, running as a control, did not take portal layout into consideration, and the header has been adjusted so the portal header is exposed properly.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us