SR-B73478 · Issue 325315
Chart date column duplication resolved
Resolved in Pega Version 7.3.1
Report definition charts were displaying duplicate date columns when the operator time zone was set to "Europe/London". To correct this, the system will conditionally set the time zone only when it's a datetime when normalizing the data.
SR-B73531 · Issue 325518
Missing check added for "Column Command Menu" on summary type report
Resolved in Pega Version 7.3.1
For a summary type report, the column command menu was still displayed even though the "Enable Column Command Menu" was unchecked on the report definition Report Viewer tab. This was due to a missing check for "Enable column command menu" before adding the showReportRCMenu onclick event, and has been fixed.
SR-B74586 · Issue 325692
Fixed save-as for RD with sub-report and join
Resolved in Pega Version 7.3.1
A save-as for the existing Report Definition rule :USCANSaleEstimate was not working for a new ruleset version. This was an issue with an existing RD that had a sub-report and was joined by a column in the sub-report that was a function, and pzGenerateMsgForUderDefinedFunctions has been modified to correct this.
SR-B76880 · Issue 326010
Repeat grid filtering option fixed for Microsoft Internet Explorer 11
Resolved in Pega Version 7.3.1
The repeat grid populated when running report definition was prompting for the filter of the data properly in Microsoft Internet Explorer 11, but no action was performed when clicking on it. This was an issue with missing navigation rule changes, which have been added.
INC-143925 · Issue 597289
Documentation update to alternate URL for mobile build
Resolved in Pega Version 8.5.3
The documentation located at https://community.pega.com/knowledgebase/articles/mobile/85/setting-alternative-host has been updated to reflect current information and instructions for setting an alternative host.
INC-147844 · Issue 612899
Check added for type of value in scheduling adaptive reports
Resolved in Pega Version 8.5.3
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-149143 · Issue 613143
Report category error messages made accessible
Resolved in Pega Version 8.5.3
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 613916
Corrected page counts for 'save-as' reports
Resolved in Pega Version 8.5.3
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 615016
Cross-Site Scripting update
Resolved in Pega Version 8.5.3
Cross-Site Scripting filtering has been added to Shortcut Handle.
INC-151185 · Issue 618730
OptimizeForLargeResults flag set in BasicListSpecification to avoid OOM
Resolved in Pega Version 8.5.3
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.