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-B39484 · Issue 296141
Calculation Builder made more robust for use in segments
Resolved in Pega Version 7.3
An error was generated when using the Calculation Builder in a segment, though the Calculation Builder for Report Definition worked. This was traced to code in the Calculation Builder which assumed the report page class would always be "Rule-Obj-Report-Definition", which failed for segments. To correct this, the logic has been modified to be more robust.
SR-B38980 · Issue 299227
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-B41652 · Issue 299895
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-B41815 · Issue 303258
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-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.
INC-182375 · Issue 664344
Report filter description correctly displayed
Resolved in Pega Version 8.7
When a function alias was used in the filter of a report definition without the caption and with some value assigned, the FilterName was not getting displayed when the report was run. This has been resolved by updating RRFilters_Logic.
INC-147643 · Issue 605386
Corrected filtering logic for Report Definition with declarative join
Resolved in Pega Version 8.5.2
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-144103 · Issue 599681
Updated filter logic for filtering on a DateTime column
Resolved in Pega Version 8.5.2
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-147621 · Issue 604282
Updated filter logic for filtering on a DateTime column
Resolved in Pega Version 8.5.2
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.