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.
INC-150193 · Issue 613915
Corrected page counts for 'save-as' reports
Resolved in Pega Version 8.6
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 615014
Cross site scripting update
Resolved in Pega Version 8.6
Cross site scripting filtering has been added to Shortcut Handle.
INC-151185 · Issue 618731
OptimizeForLargeResults flag set in BasicListSpecification to avoid OOM
Resolved in Pega Version 8.6
As soon as dedicated indexing started for a data type, the JVM heap occupation went beyond 99 and eventually caused a system crash due to an out of memory error. This was traced to the use of the BasicListSpecification API for retrieving results from the database always having the autocommit mode on, which loaded all instances for indexing into memory and interfered with PostgreSQL's cursors (query encapsulation). This has been resolved by adding an OptimizeForLargeResults flag that will be set to on in the BasicListSpecification activity before fetching the keys from the database.