SR-B34888 · Issue 292535
null-pointer exception handling added to Outlook autocomplete field
Resolved in Pega Version 7.3
When using the Outlook plugin, multiple quick presses of the down arrow key in the auto complete field generated an error popup due to a null pointer exception in the autocompleteag js. To avoid this, null checks have been added.
SR-B35405 · Issue 292363
AddressMap properly rendered
Resolved in Pega Version 7.3
Using pxAddressMap control showed longitude and latitude values on the review harness and did not render the MAP until refreshed. This was due to the Address map being generated with one more 'if' condition around the editable condition. If this condition is present for the address map it may be marked as Editable control while its behavior is Action, causing the rendering issue. This has been fixed.
SR-B35861 · Issue 292611
Corrected distorted tab layout
Resolved in Pega Version 7.3
A complex tab layout with visible when conditions combined with deferload and refreshonactive was causing a distorted presentation at runtime if the first tab's visible when defaulted to false. This has been fixed with modifications to the setActiveTabIndex function.
SR-B36254 · Issue 293924
Removed error appearing on multiple tabs
Resolved in Pega Version 7.3
On a multiple tab scenario when client side validation was triggered on a specific tab ad that layout was under a tabbed repeat in a section, a warning icon appeared on other tabs as well. This is due to marking for tab repeat not being supported at this time: in these conditions, the system will skip the marking error.
SR-B3633 · Issue 274006
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-B36556 · Issue 301271
Internet Explorer text input focus fixed
Resolved in Pega Version 7.3
In IE, the mouse could not be used to return focus to a text field once there was text input followed by other clicks around the screen. This was traced to a grid inside the modal dialog launched by a button with an incorrect div that led to the text box losing editability. To resolve this, a check has been added.
SR-B36567 · Issue 296311
Full year date data made available to Excel for consistency
Resolved in Pega Version 7.3
Inconsistencies were seen in the handling of the year field on dates using Date or pxDateTime as a control, at times displaying the same input as 01/01/1917, 01/01/17, and 01/01/2017. To fix this, the date format in pzExport_Date_RD control has been modified from DEFAULT_DATE_SHORT to DEFAULT_DATE_SHORT_YYYY so the full year component is available for Excel.
SR-B36880 · Issue 294350
Fixed SmartInfo positioning
Resolved in Pega Version 7.3
When any action like Refresh section, Post Value, or set value was configured before the Show SmartInfo, the smartinfo was suppressed. This was because the TargetElement was coming as stale and positioning the smartinfo based on a stale element resulted in it not getting displayed. This has been fixed by adding code to update the latest target element before positioning the smartinfo.
SR-B37039 · Issue 293524
Security upgrade for Struts2
Resolved in Pega Version 7.3
To improve security, Apache Struts2 has been upgraded to version 2.3.32 .
SR-B3704 · Issue 276504
Added check for cancel modal in expand-pane grid
Resolved in Pega Version 7.3
A modal window would not close if the modal dialog was launched after a row of an expand-pane grid was expanded. The issue was caused by a call to an incorrect version of the cancel modal for this configuration, and a check has been added to ensure the proper version is used.