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-D14159 · Issue 493081

Toggle added for displaying exception stack trace

Resolved in Pega Version 8.3

When text like "%25" was added to the login URL, the full exception stack was displayed on the screen. To resolve this, when the prconfig 'initialization/displayexceptiontraceback' is set to false (default value), the system will render the status.jsp instead of error.jsp and will not populate any sensitive data in the request object. If its set to true, the system will fall back to the old approach which renders error.jsp and emits the stacktrace.

SR-D23417 · Issue 493542

Image Attachment File Type error localized

Resolved in Pega Version 8.3

Localization has been added to the error message generated when an unsupported image is uploaded while in live-chat.

SR-D20144 · Issue 493561

Function LengthOfPageList resolves correctly for Insure framework

Resolved in Pega Version 8.3

When using the Insure framework, it was not possible to expand any steps in the activity. Investigation showed that the rule 'LengthOfPageList' was present in the library Utilities in two different rulesets – Pega Rules and Pega Insure CSB. When the rule was cached with an application stack containing Pega Insure CSB, it generated a "Failed to find instance" error for applications that did not use Pega Insure CSB in the stack. During the run-time call to the correct LengthOfPageList() RUF was not resolved because of ambiguity in the resolution. To correct this, the call to the RUF will now contain a fully qualified name.

SR-D26101 · Issue 494891

Added explicit step page to resolve NPE with custom error message

Resolved in Pega Version 8.3

A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the NPE on harness reload.

SR-69015 · Issue 619995

Unescaping characters implemented for expressions

Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6

An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.

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