SR-B38619 · Issue 298574
Action item refresh properly triggers
Resolved in Pega Version 7.3
Refresh was not clearing the temporary filters applied on the report definition results if the refresh option was triggered by the actions button. This has been fixed by adding a new java step to pzRunWrapper activity to clear the previously applied filters.
SR-B38674 · Issue 301022
Descendant class logic made more robust
Resolved in Pega Version 7.3
The 'Report on descendant' option in the report definition/Listview was giving incorrect results. This was caused by the code used to execute the RD looking up the descendant class from the current application that inherits from the applies-to class (tools.getDatabase().getConcreteDescendantsInCurrentApplication(class name);) of the RD and executing the RD against this class. While this is appropriate when an application is built on another and case types are directly inherited into the new layer, this will not work when application layers are added which do not include equivalent case types for every case from the built upon applications. This becomes a more common problem when the MBO feature starts getting used more often on the customer implementations. To ensure the descendant class is correct, the Useimplemenation class has been updated 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-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-B40812 · Issue 304049
New section made available for customized RB report generation date
Resolved in Pega Version 7.3
In order to support customized formats in the generated date used by Report Browser, the new section PYDISPLAYREPORTGENERATEDDATETIME has been made available. This is accessed through pzDisplayReportSectionForPDF, and replaces the "generated on" datetime property used previously.
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.
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.