SR-B41815 · Issue 300938
createDateTimeCategories function modified to use operator time zone
Resolved in Pega Version 7.3
A report definition chart using the operator time zone of "Europe/London" and locale "en_US" displayed duplicate date columns. Updating the operator time zone to "America/New_York" removed the problem. This issue was caused by the system always parsing/formatting the date with the default local time zone, and has been resolved by modifying the parseDate/formatDate/createDateTimeCategories function to use the operator time zone instead.
SR-B42110 · Issue 299959
RD "Available & Valid Values" properly populated
Resolved in Pega Version 7.3
The filter conditions in the report definition for the Available and Valid value list was displayed as blank or empty for properties which were exposed for reporting purpose and are at one level below the PyWorkPage. This was traced to an improper splitting of the property when pointed from the Parent, and has been fixed.
SR-B42586 · Issue 299297
Modified RD filtering rule to support custom validation
Resolved in Pega Version 7.3
Custom validation was not stopping a Report Definition from completing due to validation errors not being applied to the correct page when submitting the form. In order to support this customization, pzValidateCustomFilterSection has been modified to put messages on the step page rather than primary page.
SR-B42586 · Issue 300843
Modified RD filtering rule to support custom validation
Resolved in Pega Version 7.3
Custom validation was not stopping a Report Definition from completing due to validation errors not being applied to the correct page when submitting the form. In order to support this customization, pzValidateCustomFilterSection has been modified to put messages on the step page rather than primary page.
SR-B44146 · Issue 300050
Resolved error in adding Association's Page Property in report browser
Resolved in Pega Version 7.3
Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.
SR-B45613 · Issue 302956
Fixed query for RD using dependent classes
Resolved in Pega Version 7.3
A runtime exception was generated when running a summary report due to an incorrect query being built for RD when dependent classes was checked. This was caused by pyGetDistinctRecords being set to true even for summary reports, and has been corrected by ensuring pyGetDistinctRecords is set to false for summary reports.
SR-B6161 · Issue 275612
RD generating checkbox control as T/F image fixed
Resolved in Pega Version 7.3
A report definition was not showing checkbox controls as images for true/false properties when generated automatically. This has been fixed.
SR-B6292 · Issue 276738
New accessibility control for adding explicit text to RB column headers
Resolved in Pega Version 7.3
In order to create report browser column headers with explicit text for accessible users, a new available control named pyReportBrowserControl that uses the parameter "Type" has been added to the pzRBShortcutsGrid7 section.
SR-B796 · Issue 283050
Report Definition updated to handle null value field grouping
Resolved in Pega Version 7.3
Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.
SR-B796 · Issue 277684
Report Definition updated to handle null value field grouping
Resolved in Pega Version 7.3
Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.