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-140353 · Issue 592214

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-141322 · Issue 594512

Resolved drill up doubling the filter box

Resolved in Pega Version 8.6

When opening a report with a visual graph, clicking on one of the filtered options, leaving this box open (not submitting it) and then clicking on a bar in the visual graph of the report showed the contents of the graph, but then clicking on the report link to go back to the report overview caused a doubled filter box to be displayed. The report would then have to be reopened before being able to continue. The problem was that the value of .pyUI.pyConfigSecToShow was still set to "filter" after the drill down. When the drill back up happened, the report was trying to show the filter configuration section from before but the context was no longer available and it failed. This has been resolved by adding a call to pzCancelFilterLogicChanges in pzDrillUpReport to set the filters to the previous values and reset the value of pyConfigSecToShow.

INC-143191 · Issue 596468

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.6

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

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