SR-B44591 · Issue 301046
Color issue fixed for last value ranges
Resolved in Pega Version 7.3
An "Invalid XML" error was generated when trying to apply different colors for different ranges of values in the advance UI control "Charts" > "Gauge Half Arch". This has been fixed.
SR-B45435 · Issue 301778
GenerateGridHTML updated for JAWS version compatibility
Resolved in Pega Version 7.3
An update to the JAWS program caused it to no longer recognize some Pega grids as tables due to the use of role=presentation, and the table name was not associated with the layout header title leading to the tables not being labeled accordingly. To correct this, the GenerateGridHTML now has an added summary attribute in the ".gridTable".
SR-B45917 · Issue 302415
DisplayReport date made consistent between report and exported PDF
Resolved in Pega Version 7.3
When exporting a report to PDF, the "Generated on" date did not match the format on the report. This was caused by the system using different controls for date in pzDisplayReportSectionForPDF and displayReportSection, and has been resolved by changing the date format specified in pzDisplayReportSectionForPDF to match that in displayReportSection.
SR-B46050 · Issue 302190
Corrected DateTime corruption
Resolved in Pega Version 7.3
If "Display value using read-only formatting" was selected for a Date field, entering an invalid value caused the resulting HTML DOM to be displayed incorrectly when the page was refreshed. This was traced to missing handling for the exception resulting from the invalid data, and has been fixed.
SR-B46365 · Issue 303375
Error check added for ID/label mismatch on field labels
Resolved in Pega Version 7.3
When an UploadFileFlow was created, tabbing through fields with blank values updated most of the field labels with the revised style when an error was present, but Date kept its original style. This was due to an issue setting error styles on a property if the label and identifier of a property were different. To handle this, the code has been modified to such that if the identifier of a control and shown text are different, a check in "findLabelFor()" will fail.
SR-B47384 · Issue 303522
Fixed focus reset for page number click in grid layout
Resolved in Pega Version 7.3
An anchor element generated for the active page in a repeat grid had "#" as href but did not have an onclick handler defined, causing a click of the Page number in a Grid layout to move focus to the top of the page. This has been corrected with the addition of an onclick handler in pzGridActivePage custom control for inactiveLink in 123 pagination.
SR-B509 · Issue 277331
Turkish characters supported in autocomplete filtering
Resolved in Pega Version 7.3
Support has been added for Turkish locale special characters in autocomplete filtering.
SR-B5224 · Issue 277207
Fixed intermittent override default template failure
Resolved in Pega Version 7.3
The override default template was displaying inconsistent behavior due to the fromLocalAction function not correctly resetting. This has been corrected.
SR-B5450 · Issue 274669
Tab layout focus corrected for "show next error"
Resolved in Pega Version 7.3
The "Show Error" and "Show Next Error" functionality in the layout group of type tab were not giving focus to the correct element when clicking the 'show next error' if an autocomplete was present. Instead, focus was given to the element whose CSS property display was set to none. To correct this, an additional filter condition has been added to ensure the expected focus.
SR-B5618 · Issue 281402
Autocomplete works in grid layout
Resolved in Pega Version 7.3
If a data transform was in the data class and the same was used as a source for the autocomplete inside a repeat grid, the data was not present in runtime. The configuration did work if the data was in the work class. This was traced to missing context, and has been fixed by ensuring the pre-datatransform and pre-activity have the grid row page context.