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-C74642 · Issue 424004

Data page reference properties will not be resolved if hidden

Resolved in Pega Version 8.3

In order to improve code efficiency, in conditions where a text input field configured with a 'When' visibility condition references a property which is present in a data page, the system will skip the process of resolving the property name if the 'When' rule is evaluated as false.

SR-C85312 · Issue 424036

Check added for custom section use in Summary report exported to Excel

Resolved in Pega Version 8.3

Criteria were missing when Export to PDF was used for Summary reports filtered by a custom section. This was caused by the needed pyQueryTokenList not being repopulated for the export in the case of custom section use, and has been resolved by adding a summary report check in the pzIncludeCustomFilterSection section before invoking pzClearRDTempFilters function.

SR-C83058 · Issue 424153

Assertion parse rule XML regenerated to resolve data mapping issue

Resolved in Pega Version 8.3

The parse-xml rule(NS-366601360 • Assertion) has been regenerated to resolve an assembler issue with mapping data to properties.

SR-C84921 · Issue 424316

Connection Manager uses keyring for null prconfig password

Resolved in Pega Version 8.3

After upgrade, credentials from BIX keyring were failing when using BIX via commandline rather than prconfig. This was traced to a behavior change in the Connection Manager, and has been resolved by modifying the Connection Manager to look up the password from the keyring when given a URL configuration where the password is null in prconfig (URL connection only).

SR-C78956 · Issue 424433

cross-site scripting improvements for modal dialog

Resolved in Pega Version 8.3

cross-site scripting protections have been added to pzDisplayModalDialog.

SR-C75205 · Issue 424475

moment js "Invalid Date" string error fixed

Resolved in Pega Version 8.3

Inconsistent behavior was seen between entering an invalid date in numeric vs text format. Entering an invalid date in number format resulted in the system replacing the entered value with the text “Invalid date”. Entering an invalid date in text format caused the system to retain the value and not show a validation error. This has been corrected by modifying the date/time formatting for both text and numerical input to return the timestamp in case the entered value is incorrect.

SR-C84135 · Issue 424530

Metadatatree updated to be function-scoped in UI to resolve custom tab control display issue

Resolved in Pega Version 8.3

When switching rapidly between two custom tabs, especially clicking in and then clicking away before the busy icon could be displayed, the section containing the tab controls was intermittently refusing to display. Refreshing the browser or clicking on the Pega button made the section visible again. This was traced to the template "metadatatree" getting overlapped with subsequent template processing due to a timing issue as "metadatatree" was being maintained in the global window object. To resolve this, "metadatatree" has been updated to be function-scoped in renderUI to avoid timing issues.

SR-C79482 · Issue 424535

DSS added to allow custom timeout for BIX query

Resolved in Pega Version 8.3

The BIX query to retrieve the blob column was taking up to 60 seconds for large volume, causing timeouts. Previously, the extract defaulted to using repost pzSample which is internal/final and has a default timeout of 30 seconds. In order to avoid timeouts, the new DSS "BIX/selectQueryTimeout" has been added to allow setting a custom value.

SR-C86213 · Issue 424583

Corrected PRAuth URL handling for sessions on restarted nodes

Resolved in Pega Version 8.3

If a user session was in progress and the node restarted, attempting to refresh the session when the node came back up was not working. Launching a new browser session cleared the problem. A trace showed that the Authentication Selector screen was not loading because the PRAuth URL redirection was going into an infinite loop, and this has been corrected.

SR-C87665 · Issue 424610

CPU time will be fetched from MBeanServer instead of the JRE application to provide consistency

Resolved in Pega Version 8.3

The value of CPU time in the Enterprise health metrics was being given in nanoseconds instead of seconds after the IBM JRE version was upgraded by applying Websphere Application Server patches. The CPUTimer is a platform class which has logic specific to different JRE vendors; in order to provide consistent results regardless of which JRE is used, the system has been updated to always fetch the values from the MBeanServer.

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