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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C91370 · Issue 429578

System updated to jackson-databind-2.9.8.jar

Resolved in Pega Version 8.3

The jackson-databind jar has been upgraded to v2.9.8.

SR-C90467 · Issue 429607

Validations are correctly run on rescheduled reports

Resolved in Pega Version 8.3

When using the out-of-the-box schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.

SR-C91750 · Issue 429615

Summarized report after editing shows Count as expected

Resolved in Pega Version 8.3

When creating a report with a number of fields and summarizing it in the report browser, the summary gave proper counts. However, after clicking on "edit report" and then running summarize on the same column, the generated report gave the Sum of the number column instead of the Count. To resolve this, the implementation used to update a hidden value for the dropdown has been set to initialize to the Count option.

SR-C91156 · Issue 429628

Autocomplete Menu Selection for privileges tab Role updated

Resolved in Pega Version 8.3

When a few characters were typed in the autocomplete for "Role" in the privileges tab and the desired value was selected, the selection did not stick. The second time the value was selected it was retained. Investigation showed that the post value source element had a stale reference after section reload, and this has been resolved by adding code to re-initialise the reference with the latest element.

SR-C89250 · Issue 429741

Guardrail score ignores test rulesets

Resolved in Pega Version 8.3

Test rulesets for a branch were unexpectedly being considered when calculating the Guardrail score. This has been corrected.

SR-C87309 · Issue 430089

Shortened cleanup time for unauthenticated requestors

Resolved in Pega Version 8.3

Any type of probing done to the system with a public URL was generating many unauthenticated requestors that had a one hour lifetime if the user hit /PRAuth and left before reaching the postAuthenticationActivity. In order to speed cleanup in such cases, the system has been updated to ensure the postAuthActivity that sets setShortTimeout(true) is called even if the authentication isn't completed.

SR-C91220 · Issue 430362

Modified pzpega_ui_dynamiccontainer to resolve issue with editing the Operator rule form when using IE

Resolved in Pega Version 8.3

The Operator rule form was not opening a second time after being updated in IE. The form worked as expected with other browsers. This has been resolved by modifying the openRuleByKeys function in pzpega_ui_dynamiccontainer to pass a new cloned object to the JSON.stringify function instead of the embedded object.

SR-C79851 · Issue 430383

Filter logic updated for Warning Summary guardrail report

Resolved in Pega Version 8.3

After scheduling a Guardrail report for Warning Summary, the warning summary reports received in email were blank irrespective of the filter criteria. The logic filters have been modified to resolve this issue.

SR-C91121 · Issue 430388

Data Page seatch results have expanded data available to view

Resolved in Pega Version 8.3

It was not possible to expand a search result and see Ruleset, Updated by, etc, for Data Pages. This was traced to the Layout Properties of section pzSearchDrilldown having a visibility condition of .pzCategoryActionKeys != 'Rule-Declare-Pages' after being reconfigured during prediction studio implementation for rule transition. To resolve this, the necessary related table for data pages has been added to the pzSearchDrilldown section.

SR-C92202 · Issue 430394

Improved error handling and logging added for null partitions encountered in VBD aggregation

Resolved in Pega Version 8.3

A NPE was thrown during VBD aggregation when a partition was found with no data, a condition likely created by a failed insert or failed replication. To better handle this scenario, code has been added for better error handling and more informative logging.

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