SR-B34248 · Issue 293070
Performance improvements for Work-Cover-.pyLoadMyCases
Resolved in Pega Version 7.3
Performance issues in Work-Cover-.pyLoadMyCases were traced to code in pyLoadMyCasesNested that made an unnecessary page copy and triggered several data page loads. To improve response time, the page copy activity has been removed and the system will instead use a Boolean value to determine whether to read data from the DB or from the clipboard page.
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-B35117 · Issue 292760
Split-for shape "open flow" works as expected
Resolved in Pega Version 7.3
When working with a flow that contains a Split-for each shape which loops pyWorkParty and executes a flow on Data-Party class, an error was generated if there was a right-click on the sub-flow shape and "Open flow" was chosen. The sub-flow opened properly if there was a right-click on the sub-flow shape, "View Properties" was chosen, then a click on the "Open" icon right of the flow name. This was traced to the Top Class being passed for opening the flow rule in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" class. To fix this, the class has been changed from Top to ".pyPageClass" in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" to open the flow rule
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-B36134 · Issue 294119
Security fix to prevent URL tampering
Resolved in Pega Version 7.3
Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.
SR-B36134 · Issue 294006
Security fix to prevent URL tampering
Resolved in Pega Version 7.3
Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.
SR-B36134 · Issue 294147
Security fix to prevent URL tampering
Resolved in Pega Version 7.3
Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.
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.