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-143191 · Issue 596469

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.5.2

Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.

INC-144103 · Issue 599681

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.5.2

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-145810 · Issue 599465

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.5.2

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

INC-147166 · Issue 601799

AvailableProperties cleanup added after save

Resolved in Pega Version 8.5.2

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 604282

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.5.2

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 605386

Corrected filtering logic for Report Definition with declarative join

Resolved in Pega Version 8.5.2

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 607132

Description input for new reports restricted to 64 characters

Resolved in Pega Version 8.5.2

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-150054 · Issue 607387

Drilldown works for display of all locks

Resolved in Pega Version 8.5.2

In Developer studio, drilling down from the summary count of all locks to see the actual cases locked gave a generic error screen. This was a missed drilldown use case for List Views during security updates, and has been resolved.

SR-D91660 · Issue 555724

Updated document ID handling for deleting indexes

Resolved in Pega Version 8.5.2

When trying to delete a document for index name "work*", intermittent errors were seen indicating an invalid index name or index does not exist value. This has been resolved by updating the handling for delete by ID.

INC-127102 · Issue 602699

Synchronized BatchStatus email available for multi-node

Resolved in Pega Version 8.4.4

An enhancement has been added which will handle synchronization between BatchStatus used in different events on different nodes and send email notifications.

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