SR-B12636 · Issue 280290
CSS updates to improve Microsoft Internet Explorer 11 and Chrome case type label text wrap
Resolved in Pega Version 7.3
The case type labels descriptions were chopped off in Microsoft Internet Explorer 11, while in Chrome, descriptions were intact but labels appeared below the check box. To resolve this, code for a new format for checkboxes called Bold has been added to the style sheet for application config wizard overrides. This updates the case type and data type sections to use a caption for the checkbox instead of two separate controls (checkbox + label) to handle wrapping of label to next line. The updated skin also contains overrides to use an ie-flex-fix class to handle text wrapping issues in Microsoft Internet Explorer 11 due to Flexbox layouts not working properly in that browser.
SR-B12714 · Issue 294429
String comparison logic updated for complex property references
Resolved in Pega Version 7.3
Running a report that has a single page property (.Address.pyCountry) generated an error and the report shows no results. It worked correctly if the column is removed or a filter was added on instances that have .Address.pyCountry not null. This was an issue related to string comparisons, and has been resolved by updating the logic for parsing of complex references in UDFs.
SR-B12737 · Issue 283588
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.
SR-B12737 · Issue 282869
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.
SR-B12770 · Issue 285068
Text areas display OOB error message as expected
Resolved in Pega Version 7.3
In the Text area control, the Pega OOB error message was not generated when there was no value in the required text area. This was an issue with minimum characters validation not considering an empty string to be a valid one, and has been corrected.
SR-B12783 · Issue 285395
Performance improvements for Data Designer Visualizer
Resolved in Pega Version 7.3
In order to improve performance of the Visualizer feature of the data designer, the loading behavior has been changed. Previously, the RD being executed for each node in the graph to get the reference properties was defer loaded; this potentially caused issues if the data was still being loaded in the background for the visualizer and an attempt was made to open BodySite. To fix this issue, the defer loading has been removed and the data will load on click of the "visualizer" button.
SR-B12850 · Issue 283836
SMA Garbage Collector landing page updated to work with updated browsers
Resolved in Pega Version 7.3
SMA's Garbage Collector landing page was not working correctly on the latest versions of Chrome and other browsers due to the document.all JavaScript function being deprecated. The code has been updated to correct this.
SR-B12857 · Issue 285462
Repaired REST Connections with proxy
Resolved in Pega Version 7.3
After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.
SR-B12931 · Issue 283341
VBD planner shows additional KPI values
Resolved in Pega Version 7.3
If there are more than 6 KPI's given, the VBD planner may not show measurement values for KPI that are not part of the initial 6 KPI. This has been fixed.
SR-B12993 · Issue 285730
Property change tracking updates for source shapes and ClipboardPageAdapter
Resolved in Pega Version 7.3
OnChange and Declare Expression rules were unexpectedly triggered during data flow executions that converted clipboard pages from DSM to regular implementation. The triggering also intermittently occurred when loading data from different dataset types while populating the page. This was traced to the handling of property change tracking, and the system has been updated so that source shapes and ClipboardPageAdapter will not track property changes.