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-202004 · Issue 692353

Hotfix documentation updated to point to Hotfix Manager page

Resolved in Pega Version 8.8

The readme file attached to hotfix downloads contained an outdated reference to use "PRPC Hotfix Installer on the Update Manager landing page." This has been updated to point to the Hotfix Manager landing page.

INC-205453 · Issue 706569

Pega Keystore supported for hotfix signature verification

Resolved in Pega Version 8.8

In order to support custom trust managers which require an alternate method for supplying the root certificate via a platform trust store, an enhancement has been added to allow Pega Keystore to be used as a hotfix verification source. Detailed information on this can be found in https://docs.pega.com/keeping-current-pega/87/verifying-hotfix-authenticity-using-pega-keystore

INC-208516 · Issue 705098

Patchdate values made unique

Resolved in Pega Version 8.8

The hotfix manager was incorrectly indicating that a previous hotfix was not installed or was partially installed and should be reinstated. This scenario was created during security updates where the missing/incomplete hotfix had been deliberately deleted from the database, and has been resolved by adding an update which will force patchdate to be unique when adding duplicate code resources during tests.

INC-209435 · Issue 707374

Column population error downgraded to warning

Resolved in Pega Version 8.8

A Column Population job run after deployment for some classes was logging the error "Class does not exist", but no property was identified and no impact to the system was seen. This error has been downgraded to a warning.

INC-210513 · Issue 710344

Added handling for clustered index on the pr4_rule table during migration

Resolved in Pega Version 8.8

When attempting to migrate the rules schema to RULES85 and temp data schema DATA85, the upgrade was becoming stuck in a loop while working to generate declarative indexes for Rule-HTML-Paragraph. Investigation showed the infinite looping happened only for classes mapped to the pr4_rule and with instance count of more than (num of threads * batch size). This was due to the presence of a clustered index on the pr4_rule table causing the resultset to return an infinite number of records in SQLServer, and has been resolved with an update to leverage the total record count to iterate the resultset instead of depending on the resultset.next().

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