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

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.6

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-144333 · Issue 603261

Documentation updated for reindexing of specific classes

Resolved in Pega Version 8.6

The documentation for rebuilding search indexes has been updated to specify that selected class is the only one taken into account for re-indexing; child classes need to be added separately.https://community.pega.com/knowledgebase/articles/system-administration/85/rebuilding-search-indexes-user-interface

INC-145810 · Issue 599464

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.6

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

INC-147166 · Issue 601800

AvailableProperties cleanup added after save

Resolved in Pega Version 8.6

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 604283

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.6

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 605387

Corrected filtering logic for Report Definition with declarative join

Resolved in Pega Version 8.6

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-147844 · Issue 612898

Check added for type of value in scheduling adaptive reports

Resolved in Pega Version 8.6

When scheduling the pyAdaptiveModelsOverview, pyAdaptiveModelsPredictorOverview and pyModelsActivePredictorsOverview reports, the error "atest.Snapshot_Time is not a valid date/time value" was occuring in step 1 of the pzRDExportWrapper activity. The reports worked as expected when run standalone; the failure only occurred when running from scheduled tasks. Investigation showed that the system was trying to parse a property reference as a datetime, and the failure and error caused the report scheduler to refuse to send the generated report. This has been resolved by adding logic to ReportFilter.java to check if the value is a property reference before attempting to parse it as a datetime value.

INC-147856 · Issue 607133

Description input for new reports restricted to 64 characters

Resolved in Pega Version 8.6

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 613142

Report category error messages made accessible

Resolved in Pega Version 8.6

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

INC-150054 · Issue 607388

Drilldown works for display of all locks

Resolved in Pega Version 8.6

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.

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