SR-B15497 · Issue 286469
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-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-B15575 · Issue 285206
Accessibility added to flow action label
Resolved in Pega Version 7.3
When an accessibility tool such as JAWS was used, the flow action label was not read out and no indication was given regarding what action was expected. To correct this, the RUF pzGenerateControl has been updated to add tabindex=0 so the section heading can be read out by accessibility tools.
SR-B15575 · Issue 290496
Accessibility added to flow action label
Resolved in Pega Version 7.3
When an accessibility tool such as JAWS was used, the flow action label was not read out and no indication was given regarding what action was expected. To correct this, the RUF pzGenerateControl has been updated to add tabindex=0 so the section heading can be read out by accessibility tools.
SR-B15604 · Issue 286328
Made InputProperty not mandatory for business logic
Resolved in Pega Version 7.3
When business logic is selected, pzToDecisionTreeExpress is selected as the routing activity for the assignment. However, errors occurred due to the mandatory parameter InputProperty property being passed as empty. To address this, the parameter will be marked as not mandatory.
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-B15673 · Issue 288077
DatePicker calendar pop works as expected
Resolved in Pega Version 7.3
Unexpected behavior was seen where the input box of a date control used as Date+calendar popped up the calendar on click when Text entry was not allowed and did not pop up the calendar when Text entry was allowed (both in disabled mode). This was traced to an error in the data-ctl attribute for that span, and has been fixed.
SR-B15673 · Issue 288076
DatePicker calendar pop works as expected
Resolved in Pega Version 7.3
Unexpected behavior was seen where the input box of a date control used as Date+calendar popped up the calendar on click when Text entry was not allowed and did not pop up the calendar when Text entry was allowed (both in disabled mode). This was traced to an error in the data-ctl attribute for that span, and has been fixed.
SR-B15685 · Issue 292401
Flexibility enhancement for mobile dropdown displays
Resolved in Pega Version 7.3
As a part of an enhancement for mobile apps, a checkbox for "Allow scrolling for more results" has been introduced in the property panel of the Autocomplete. By default its value will be unchecked, implying the old behavior which limits the "Dropdown" options on autocomplete to 8 for backward compatibility. If the checkbox is used, it will honor the "Max results displayed" setting used for list based autocomplete. If the max results value is not specified, using the checkbox will cause the dropdown to show all the results.