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-183960 · Issue 675870

Condition check added to trigger search update

Resolved in Pega Version 8.6.4

Following work done to update deleting attachments for cases created through an email bot, search indexing was not updating automatically and a manual re-index was needed to allow the global search to work. This has been resolved with the addition of a condition check which will update the case when there is a delete operation done on the link page.

INC-198725 · Issue 707482

Elasticsearch will split queries to avoid URL length limits

Resolved in Pega Version 8.6.4

Elastic Search Functionality was not working and showed the status as Offline. Investigation showed that when an external Elasticsearch setup had an index prefix length = 200 and a large number of dedicated indexes, the error "too_long_frame_exception, reason: An HTTP line is larger than 4096 bytes" was generated. In this case, the system was working with approximately 87 dedicated indexes and the name for each of them was sent over the URL, resulting in this error message. This has been resolved by updating the system to split queries so as to not exceed the HTTP line limit in Elasticsearch.

INC-200973 · Issue 699266

Added handling for client-side validation errors in sub-reports

Resolved in Pega Version 8.6.4

When a sub-report was trying to access externally mapped fields or an optimized page property by JOIN of another class, the main report was unable to validate the Page property. This has been resolved by updating the activity code to handle client-side validation errors on main reports attempting to access the externally-mapped Page properties of another class in the sub-report.

INC-201625 · Issue 698655

Updated variable handling for filter logic to avoid reuse

Resolved in Pega Version 8.6.4

When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in the filter due to RRFilters_Logic reusing the strFieldName variable, and has been resolved by updating the variable handling to use a unique name, strPropName.

INC-202447 · Issue 698659

Updated variable handling for filter logic to avoid reuse

Resolved in Pega Version 8.6.4

When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in

INC-202480 · Issue 699082

Resolved report filter section freeze

Resolved in Pega Version 8.6.4

When opening a report with a count column, changing the order of one of the report columns resulted in the report freezing and requiring the report to be closed and re-run. This was traced to a double filter popup appearing that did not close after the column sorting, which happened if the report definition was configured as a summary with an aggregated column such as "Count” combined with a "Do not display group headings" setting on the Report Viewer tab. To resolve this, a new step has been added in the Activity pzPopulateSortOrder to call the pzCancelFilterLogicChanges activity.

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