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.

INC-176158 · Issue 664346

Max number of rows setting properly honored

Resolved in Pega Version 8.5.5

The setting for the maximum number of rows to retrieve was still used in a report definition even when it was disabled. This was traced to the report definition being sourced from a data page and having pagination enabled, and has been resolved by updating the handling for this use case.

INC-176205 · Issue 655937

Secure shared link generation added to scheduled reports

Resolved in Pega Version 8.5.5

When a scheduled report with a link was sent in email, clicking the link displayed an access denied message. To support this use, logic has been added to pytaskoutputprocessor in the pega-scheduledtask-reporting and pega-scheduledtask classes that will create a secure encrypted URL using the PublicLinkURL function.

INC-176385 · Issue 657669

Corrected blank lines for hidden report filter criteria

Resolved in Pega Version 8.5.5

When the report browser had five filter criteria for a report and only the last two were made visible due to conditions, three blank lines were shown above the visible filters. This was traced to the Report Definition column filter showing the grid row as empty space when "Filter Not Visible in Viewer" was selected, and has been resolved by adding an inline style to PzPromptGrid.

INC-179362 · Issue 658630

Display limitation removed for scheduled reports

Resolved in Pega Version 8.5.5

When looking at Configure >> Reports >> Scheduled Reports only 50 reports were shown across two pages instead of all of the reports retrieved by pzGetScheduledTask. This was a limitation set in pyScheduledTasksGadget, and has been removed.

INC-181394 · Issue 662099

Handling added to avoid incorrect manifest count

Resolved in Pega Version 8.5.5

Extracted Record counts in the manifest file were incorrect if any updates were made during the extraction process. This has been resolved by modifying the code to prevent the issue.

INC-182375 · Issue 664342

Report filter description correctly displayed

Resolved in Pega Version 8.5.5

When a function alias was used in the filter of a report definition without the caption and with some value assigned, the FilterName was not getting displayed when the report was run. This has been resolved by updating RRFilters_Logic.

INC-185824 · Issue 676628

Corrected filtered column list sorting in Report Browser

Resolved in Pega Version 8.8

Sorting was not working in Report Browser for a column list when a filter category was selected. This has been resolved by modifying the pzReportListSort activity to set the correct parameters in step-1 and setting pzSetCategoryParam to retain the sortTitle parameter in step 1 with an added step -2 to call the pzReportListSort activity.

INC-198725 · Issue 707483

Elasticsearch will split queries to avoid URL length limits

Resolved in Pega Version 8.8

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-201219 · Issue 696610

Updated chart button markup

Resolved in Pega Version 8.8

Some of the buttons were incorrectly displayed while clicking "Edit Report" from the Cosmos report browser. This was due to the buttons generating markup that was used to support older browsers in pzChartButtons, and has been resolved by updating the button markup.

INC-202447 · Issue 698658

Updated variable handling for filter logic to avoid reuse

Resolved in Pega Version 8.8

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.

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