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-B39280 · Issue 298376
HTML updated to replace "\u" in the pyLabel before JSON call
Resolved in Pega Version 7.3
Placing a "\u" in the pyLabel field of a work object caused an "Invalid Unicode escape sequence" JavaScript error and part of the UI became unresponsive. This happened when the call was made to convert the json to values (JSONToValues) when a work object is opened. To avoid this error, the pzClientDynamicData HTML rule has been updated to replace the \ u character before the strPyLabel is set.
SR-B3943 · Issue 279666
NewCorrSummary rule resolution modified for CommunicationType
Resolved in Pega Version 7.3
The Received Via section of the out-of-the-box NewCorrSummary rule was being mapped to the property rule CommunicationType despite that property rule being configured locally. This has been fixed by setting the function to take the class name using dictionary instead of section xml.
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-B39673 · Issue 297670
Fixed grid row editing for Remote List
Resolved in Pega Version 7.3
When trying to create a property with table type as Remote List, it was not possible to edit or add the rows. This was due to the grid using the row editing option 'None' when the grid row-editing property has been changed to 'inline', and the table editing has been changed to inline.
SR-B3980 · Issue 273916
Scrollbar added for Microsoft Internet Explorer 11 window sizing overflow
Resolved in Pega Version 7.3
In Microsoft Internet Explorer 11, reducing the screen width caused grid data to overflow onto the tree navigation menu. This has been resolved with the addition of scrollbars to the Action area to handle overflowing content.
SR-B3980 · Issue 282061
Scrollbar added for Microsoft Internet Explorer 11 window sizing overflow
Resolved in Pega Version 7.3
In Microsoft Internet Explorer 11, reducing the screen width caused grid data to overflow onto the tree navigation menu. This has been resolved with the addition of scrollbars to the Action area to handle overflowing content.
SR-B39878 · Issue 299678
Fixed encoding of colon for exported report title
Resolved in Pega Version 7.3
A file exported using Chrome or Mozilla displayed %3A instead of Underscore (_) when replacing a colon in the title. This was an error in the encoding, and has been fixed.
SR-B40038 · Issue 298378
Column alignment with filter icon fixed for Chrome and IE
Resolved in Pega Version 7.3
When a grid was configured with filtering and 'Freeze Grid Header' option was enabled, at runtime the column header did not align as expected with the filter icon when using Chrome or IE. In IE, the anchor element for filter icon needs to have height set to render properly. In Chrome, the oflowDiv gets a height which caused the problem. To resolve the issue, the addHeightToFilterIcon function in ui_grid JS has been modified to consider freeze header cases.
SR-B40177 · Issue 297056
Resolved harness error after using pagination 'load more'
Resolved in Pega Version 7.3
After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.