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-167254 · Issue 651529

Reports database configuration documentation updated

Resolved in Pega Version 8.4.6

Documentation for working with the reports database has been updated to clarify that only a separate database with same schema/table names is supported. The complete information is available in the support documentation under Reporting Capabilities -> Reporting -> Creating advanced reports -> Setting up reports database.

INC-177323 · Issue 672423

Search string wildcard use documentation updated

Resolved in Pega Version 8.4.6

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.

INC-190130 · Issue 678543

Help information updated for using Elastic Search with Report Definition

Resolved in Pega Version 8.4.6

The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity.https://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index

INC-173986 · Issue 668934

Updated survey refresh API for switching radio buttons

Resolved in Pega Version 8.6.3

After configuring a picklist with multiple options in a survey framework, it was not possible to select a radio button when toggling between radio buttons on the UI. Investigation showed the values of the radio buttons were not published to Clipboard, causing pyAnswer to be blank. After detaching the webwb_pzsurvey_ui_userscript.js the value was posted correctly and the visible WHEN was working as expected. This has been resolved by updating pzsurvey_ui_userscript to add a timeout on the refresh API call when switching between radio button options.

INC-175533 · Issue 678910

Improved Page compare for page groups

Resolved in Pega Version 8.6.3

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.

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