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-D19081 · Issue 490370

Logic updated to handle Report Definition with a join

Resolved in Pega Version 8.3

When using a multi-select element on the UI with a report definition as a data source where the report used a join to another class where it was referenced by a prefix, setting that data source property as prefix.property resulted in the multi-select no longer showing any results when tested on the UI although the report definition returned results when run manually. This was traced to platform differences revealed by an upgrade, and the idGenerator function has been updated to handle a report definition with a join to resolve this.

SR-C89619 · Issue 429573

Custom section filters retained during refresh

Resolved in Pega Version 8.3

Filtered values were not retained on refresh when filtered using a custom section. This has been resolved.

SR-C95253 · Issue 435786

Custom datetime controls correctly appended to Excel export

Resolved in Pega Version 8.3

The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.

SR-D10309 · Issue 482476

Custom datetime controls correctly appended to Excel export

Resolved in Pega Version 8.3

The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.

SR-B38578 · Issue 295917

Fixed null-pointer exception in external DB extract

Resolved in Pega Version 7.3

When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.

SR-B38578 · Issue 272419

Fixed null-pointer exception in external DB extract

Resolved in Pega Version 7.3

When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.

SR-B6992 · Issue 277289

Fixed default first record focus in modal repeating grid with Internet Explorer 11

Resolved in Pega Version 7.3

After upgrade, it was observed that when a repeating grid layout is opened in a modal window, the first record was selected or focused by default when using Internet Explorer 11. This has been fixed by adding a check for accessibility.

INC-164308 · Issue 634409

UseNoCacheHeaders default expiration set to "0"

Resolved in Pega Version 8.6.1

When the prconfig/HTTP/UseNoCacheHeaders/default was set true it used the value "Expires: Thu, 01 Dec 1994 16:00:00 GMT". This has been updated to the more commonly used setting "0".

INC-172521 · Issue 651552

Email template content visible in user application

Resolved in Pega Version 8.6.1

An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.

SR-B12857 · Issue 285462

Repaired REST Connections with proxy

Resolved in Pega Version 7.3

After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.

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