SR-B15497 · Issue 295707
Styling corrected for last row in tree grid sourced from RD
Resolved in Pega Version 7.3
Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.
SR-B15499 · Issue 294497
SMA Remote Tracing works with URL encryption
Resolved in Pega Version 7.3
When URL encryption is enabled, Remote Tracing was not working from SMA. This occurred because the handling for the trace request coming from SMA was not triggering the URL encryption as needed, and has been fixed.
SR-B15663 · Issue 289919
Trend chart drilldown made consistent with chart display
Resolved in Pega Version 7.3
Trend chart drilldown did not match chart display due to issues with time zone being converted on the chart display but not on the the drilldown. When drilling down into a datetime group, the value of that group was used to create a single filter that matched the group (e.g., "Day of [.DateTime] = 20170101"). This caused the filter to match that time based on the server's time zone settings, not the user's (e.g., if the server was using GMT, then days always began at midnight GMT, so a user could drill down into a single day and get results spanning two days). To correct this, FusionChartDataGeneration.normalizeDateCal no longer localizes for the user's time zone if the time unit is larger than an hour, e.g. day or month units won't be normalized.
SR-B16328 · Issue 286668
BLOB data save performance improved
Resolved in Pega Version 7.3
In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.
SR-B1734 · Issue 272443
Added content to blank headers for screen readers
Resolved in Pega Version 7.3
The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.
SR-B1734 · Issue 272039
Added content to blank headers for screen readers
Resolved in Pega Version 7.3
The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.
SR-B26257 · Issue 288790
Fixed SMA broken item requeue
Resolved in Pega Version 7.3
When attempting to requeue a broken item using the SMA, the requeue failed with an error about Attribute Based Access Control. This was traced to the API passing a thread object that did not have any executable associated with it; the system will now create a new executable instance if the getThread().retrieveContext() is null.
SR-B2709 · Issue 276670
Fixed OOM exception during DL import on JVM
Resolved in Pega Version 7.3
An OOM exception was generated during DL import on JVM when the DL being deployed had an very large number of hotfixes relating to CarDirectories. This was traced to each directory deployment creating a new instance of JarLoaderTool to internally build the cache (VersionedJdbcJarReader) which was then never cleared from the Mbean cache. This has been corrected by adding a check to release memory.
SR-B30410 · Issue 294913
Report drilldown works with 'do not display group headings'
Resolved in Pega Version 7.3
When sub-report properties were used in the main reports column source, the report definition displayed the expected results when clicking on a configured drilldown report and chart but displayed no results when listview dataset was clicked. This was traced to having "Do not display group headings" enabled in combination with drilldowns, and has been resolved.
SR-B30713 · Issue 296998
New activity pyCustomValidator added to pzValidateCustomFilterSection
Resolved in Pega Version 7.3
When a report definition enables "Prompt for filter changes before displaying report", and the report specifies a custom filter section, the harness that displays the custom filter section (pzRRDisplayCustomFilterSection) is Final and was not available to validate the fields in the custom filter section. To enable this use, a new available activity "pyCustomValidator" has been added and can be called from pzValidateCustomFilterSection.