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.

INC-174435 · Issue 659479

Survey Complex Question Definition properly displayed

Resolved in Pega Version 8.4.6

Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab".

INC-175533 · Issue 678911

Improved Page compare for page groups

Resolved in Pega Version 8.4.6

Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.

INC-180603 · Issue 661739

Added protections for GetSiblings

Resolved in Pega Version 8.4.6

Cross-site scripting protections have been updated for the GetSibling activity.

INC-182248 · Issue 665782

Added logic to handle manual validate rule creation

Resolved in Pega Version 8.4.6

Manually creating a Validate rule with conditions and then opening the configure view with conditions caused the validation rule to be removed from the flow action rule along with the validation conditions in the validation rule referred in flowAction rule. This has been resolved by updating the logic in the Condition Builder to handle this use case.

INC-191567 · Issue 676158

New application wizard security updated

Resolved in Pega Version 8.4.6

Security around displaying and running the new application wizard has been enhanced.

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