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-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-118077 · Issue 170104

Excessive logging addressed in Pega Mobile 4.3

Resolved in Pega Version 7.1.7

In PegaMobile, the oLog debugging statements were generating excessive log files. This has been addressed in Pega Mobile 4.3.

INC-159836 · Issue 631205

Resolved unnecessary Apache UIMA Ruta logging

Resolved in Pega Version 8.5.5

A high level of exception logging related to Apache UIMA Ruta was seen under high loads due to annotations in the standard Ruta scripts; this did not impact execution, and has been resolved so only relevant events are logged.

INC-169412 · Issue 648881

Cross-site scripting protections updated for Graph Models

Resolved in Pega Version 8.5.5

Cross-site scripting protections have been updated for Graph Models.

INC-170721 · Issue 658959

Stricter criteria set for reusing an SSAExecutionContext

Resolved in Pega Version 8.5.5

After a Strategy was configured with an existing Proposition Filter and the Explain Results box was unchecked, executing the strategy resulted in the error "Stack is empty, cannot pop any more frames". Investigation showed that the SSAExecutionContext object was reused across the two criteria evaluation in Proposition Filter rule: this works well as long as the input is the same across the two evaluations. However, the SSAExecutionContext object also stashed a reference to a PublicAPI object which became stale in the second evaluation and caused the empty stack issue for the given scenario. This has been resolved by providing stricter criteria in deciding when an SSAExecutionContext can be reused or not in the case of Proposition Filter rule.

INC-171594 · Issue 656182

Spell check correctly applied to email body

Resolved in Pega Version 8.5.5

Spell check was not being applied to email body for text analysis in Email Channel. This has been resolved to work irrespective of case.

INC-173859 · Issue 652639

Corrected compilation error for Decision Data component in Strategy

Resolved in Pega Version 8.5.5

After update, a Decision data component defined in Strategy generated an assembly error when looking for class properties. This was traced to the use of "applies to" Instead of SR class, and has been resolved.

INC-174550 · Issue 658392

Alternative pyLabel source for Auto-generated Proposition Filter added as fall back

Resolved in Pega Version 8.5.5

After using save-as to move an offer/action rule containing eligibility criteria into a new ruleset /branch, the criteria disappeared. Proposition Filter has an explicit dependency on relevant records, and in this scenario investigation revealed all of the relevant records had been previously deliberately deleted. Using save-as on auto-generated CDH rules like actions is also not a best practice. To better handle unexpected actions like these and avoid the hard dependency on Relevant Records, when creating the Proposition Filter via the programatic API the system will fall back to reading the label from the sourcePage if is not possible to get the label from Relevant Record.

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