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.

INC-175622 · Issue 652277

Screen reader announces report names

Resolved in Pega Version 8.5.5

An update has been made to pyReportBrowserItem to ensure names of the reports on the report browser are read correctly.

INC-175797 · Issue 662049

Date/time filter works in source column

Resolved in Pega Version 8.5.5

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".

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-169186 · Issue 655536

Disconnect button availability extended

Resolved in Pega Version 8.5.5

A case was not refreshing when the disconnect button was selected while using the standard section for authorization grant type authentication. This was traced to a query executed to find a div with attribute pzInsHandle, but that attribute was not applicable in the user portal. To support this use, the query has been extended to be applicable for user portal (attribute data-ui-meta) and Dev Studio landing page.

INC-171875 · Issue 653891

Skip restored for browser request CSRF token

Resolved in Pega Version 8.5.5

Many SECU0008 alerts were seen in the production logs. This was the result of a CSRF token check on requests without pyActivity or pyStream, and has been resolved by restoring a conditional skip of the check as those other browser requests do not contain a CSRF token.

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