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-A12980 · Issue 227344

Added dropdown to select applications for new requirements

Resolved in Pega Version 7.2.1

A dropdown has been added to the Requirements screen to display the existing applications for the current user when creating new requirements.

SR-A20072 · Issue 238701

Portal markup in PDF resolved

Resolved in Pega Version 7.2.1

When using the Google Chrome browser, the portal harness markup was being included in PDFs generated from the user portal due to the frameless dynamic container. This has been corrected.

SR-A20094 · Issue 238591

Localization handling updated for High Level Overview documents generated in Word

Resolved in Pega Version 7.2.1

In a localized environment, High Level Overview documents generated in Word included some garbled characters if there were images or attachments in between the content of sections. The localization code has been updated to properly handle this format.

SR-A20183 · Issue 238612

Localization handling updated for High Level Overview documents generated in Word

Resolved in Pega Version 7.2.1

In a localized environment, High Level Overview documents generated in Word included some garbled characters if there were images or attachments in between the content of sections. The localization code has been updated to properly handle this format.

SR-A21569 · Issue 242079

Corrected persistence of deleted requirements links with multiple actors

Resolved in Pega Version 7.2.1

When checking in a specification with more than one actor specified on it, deleted requirement links re-appeared after the rule was closed and re-opened. This was due to an unnecessary section refresh, which has been removed.

INC-127667 · Issue 581851

Documentation updated to clarify displaying property values for Declare Expressions

Resolved in Pega Version 8.7

The documentation regarding Declare Expressions rules has been updated to clarify that declare expressions do not support displaying values of target properties in the user interface if the target property is an embedded property and if the calculation engages forward chaining. Declare expressions always display property values if the calculation uses backward chaining. During forward chaining, the system might render the UI before populating the clipboard, and the properties are not visible in the UI. To show updated values, define refresh conditions in the UI to get new values from the server when the values change.

INC-134737 · Issue 589968

Storage repository documentation updated

Resolved in Pega Version 8.7

The documentation detailing different content storage options has been updated to clarify the restrictions around modifying repositories.

INC-159677 · Issue 625174

Upgrade reversal limitations clarified

Resolved in Pega Version 8.7

The reversal script section on the 8.x upgrade guides has been updated to clarify the limitations in reversing upgrades.

INC-168254 · Issue 659297

Documentation updated for accents and special characters used in search

Resolved in Pega Version 8.7

The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character.

INC-177323 · Issue 672420

Search string wildcard use documentation updated

Resolved in Pega Version 8.7

The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.

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