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-C1738 · Issue 345628

Timestamp fixed for Export to Excel

Resolved in Pega Version 7.4

When trying to do a Export to Excel on a report definition with one of the columns being a Date time property, an extra 'a' was seen in the date time columns in Excel. In this case, 'a' is valid for formatting Java datetimes while 'AM/PM' is the equivalent for Excel, so the 'a' will be replaced with AM/PM in the summary viewexcel data.

SR-C2850 · Issue 348798

Missing buttons returned to Marketing report browser

Resolved in Pega Version 7.4

After upgrade, the Report Browser in the Pega Marketing portal was missing the 'Add Category' and 'Add Report' buttons. This was due to a difference in the UI-kit for the header, and has been fixed.

SR-C2920 · Issue 344845

Summary report count fixed when using filter prompt

Resolved in Pega Version 7.4

The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.

SR-C9779 · Issue 351372

Performance improvement for data page sourced by RD

Resolved in Pega Version 7.4

Performance improvements have been made to using a Data page sourced by a report definition by removing the step that creates an unneeded parameter page.

INC-119669 · Issue 562588

Special character handling added to filters for table sourced with parameterized RD

Resolved in Pega Version 8.1.9

Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.

INC-145810 · Issue 599463

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.1.9

An update has ben made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.

SR-D90400 · Issue 563187

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.1.9

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

INC-173452 · Issue 666440

Quorum capability check added for external Elastic Search

Resolved in Pega Version 8.6.2

The error "java.lang.UnsupportedOperationException: Not supported for client/server mode at search.indexmanager.internal.ESIndexAdminHTTP.isQuorumAvailable" was appearing when attempting to use external Elastic Search to index a dedicated index, and the queue processor was running but showed multiple broken items. This has been resolved by adding a capability check with ES_INITIALIZE_EMBEDDED_CLUSTER to prevent a quorum check with external elastic search.

INC-174686 · Issue 670540

Handling updated for INativeSQLBuilder with ABAC enabled

Resolved in Pega Version 8.6.2

When trying to import into a data type, the error "Exception occurred during data import pxW-886: java.lang.IllegalArgumentException: INativeSQLBuilder not initialized properly" was generated. Investigation showed that when Add or Update was chosen with ABAC enabled during import, a null pointer exception occurred while getting the class definition. This has been handled by adding an extra null condition check.

INC-175797 · Issue 662046

Date/time filter works in source column

Resolved in Pega Version 8.6.2

The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time".

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