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-144103 · Issue 599682

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.4.4

When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.

INC-144756 · Issue 602725

Security improved for searches

Resolved in Pega Version 8.4.4

Authentication requirements have been added to activities associated with searching.

INC-145810 · Issue 599466

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.4.4

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

INC-147166 · Issue 601801

AvailableProperties cleanup added after save

Resolved in Pega Version 8.4.4

The Report filter value auto-complete was displaying an incorrect list of values. This was traced to pyAvailableProperties not being cleaned up after being created and used in a prior process, and has been resolved by ensuring pyAvailableProperties is removed on save so it can be cleanly built when needed.

INC-147621 · Issue 604284

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.4.4

When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.

INC-147643 · Issue 605388

Corrected filtering logic for Report Definition with declarative join

Resolved in Pega Version 8.4.4

When using a report definition with declarative join enabled, running the report produced the correct results, but filtering on any other column resulted in all values being shown. This has been resolved by modifying the logic used for pzGetGridColUniqueValues.

INC-147856 · Issue 607134

Description input for new reports restricted to 64 characters

Resolved in Pega Version 8.4.4

After saving a report with a description containing more than 64 characters, trying to delete the same report generated error messages saying the report description exceeds 64 characters. There was no maximum character limit set on the description input when creating/editing/save as a report. The delete modal shows any page-level warnings, so the guard rail warnings show up at that time. This has been resolved by disallowing the creation of a description greater than 64 characters in length.

INC-149143 · Issue 613141

Report category error messages made accessible

Resolved in Pega Version 8.4.4

In order to improve accessibility while creating new reports, labels have been added to the error messages on the category name field.

INC-150193 · Issue 613914

Corrected page counts for 'save-as' reports

Resolved in Pega Version 8.4.4

The total pages count and last page icon were not displaying when the Preview button was clicked after a save-as of a report in the Report Browser. Investigation tracked this to a visible when condition on those fields that was being changed to the default of false during the save-as, and this has been resolved.

INC-151102 · Issue 615015

Cross-site scripting update

Resolved in Pega Version 8.4.4

Cross-site scripting filtering has been added to Shortcut Handle.

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