SR-B33629 · Issue 291139
Tabbing results corrected for main screen search field
Resolved in Pega Version 7.3
Hitting Tab on the Search fields of the Main screen was sending the focus first to the Search icon and then to the search field, the opposite of what was expected. This was an error in the icon placement in the UI kit, and has been fixed by moving the position of the search to extreme right in the dynamic layout
SR-B33756 · Issue 296571
Updated logic check for property panel invalid actions
Resolved in Pega Version 7.3
Configuring invalid actions on the events & actions property panel was not triggering the validation messages when submitted, saved, and checked-in. When the action was re-opened, no changes were saved. This was due to a segment of code called on load of the property panel that remained for backwards compatibility but should not have been called in this scenario. This has been fixed by adding a check at the top of this activity for messages/errors which will route the logic appropriately.
SR-B33827 · Issue 292793
XSS filter added to pxTextAbridge to correct stray characters
Resolved in Pega Version 7.3
pxTextAbridge was not working properly. If the "> characters were used, e.g., Sample Text "> Test, this will be displayed as " Test">Sample Text "> Test". This was caused by text that was passed to pxTextAbridge control's property getting incorrectly to the title attribute, and has been resolved with the addition of a cross scripting filter for title and property value.
SR-B34155 · Issue 292233
Custom attributes fixed for case manager portal
Resolved in Pega Version 7.3
Custom attribute changes in the skin were not being reflected in the case manager portal due to the mapping of a cached value to the wrong key. This has been corrected.
SR-B34165 · Issue 296905
Accessibility improved for grid icons in Firefox
Resolved in Pega Version 7.3
The Sort and Filter icons in a grid were not being read properly when using Accessibility with Firefox. This has been fixed.
SR-B34850 · Issue 297938
Dirty warnings properly cleaned up
Resolved in Pega Version 7.3
After displaying a dirty warning on screen, the warnings remained even when navigating to other screens. This was caused by the complex element used to display the warning not being cleaned up, and has been fixed by refining the HTML markup to ensure proper handling.
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-B35942 · Issue 295191
Grid filter column localization fixed
Resolved in Pega Version 7.3.1
The repeating grid's column filter was not displaying the localized pyStatusLabel value. This has been fixed.