SR-B49082 · Issue 308347
Mashup gadget call modified for Microsoft Internet Explorer compatibility
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, triggering a mashup API logoff with the gadget and then accessing the gadget again generated a NullPointerException. This issue only occurred with Microsoft Internet Explorer due to it sending the sendP3P parameter with a value of "true", triggering a doUIAction process that incorrectly accessed "pyHTTPResponseHeaders" and returned it as null. To fix this, the logic in the doUIAction activity has been modified to compensate.
SR-B46268 · Issue 305976
Non auto-gen SubScriptPromptInput buttons rendering properly
Resolved in Pega Version 7.3.1
When using the Add Item action to add to a Page Group, the SubScriptPromptInput HTML screen appears as a modal to allow the user to enter the Page subscript. In order to correct an error where the OK / Cancel buttons on the screen were not rendering correctly when the SubScriptPromptInput is non auto generated, the markup in @baseclass ! SubscriptPrompt has been updated.
SR-B64936 · Issue 314452
Non auto-gen SubScriptPromptInput buttons rendering properly
Resolved in Pega Version 7.3.1
When using the Add Item action to add to a Page Group, the SubScriptPromptInput HTML screen appears as a modal to allow the user to enter the Page subscript. In order to correct an error where the OK / Cancel buttons on the screen were not rendering correctly when the SubScriptPromptInput is non auto generated, the markup in @baseclass ! SubscriptPrompt has been updated.
SR-B64936 · Issue 315666
Non auto-gen SubScriptPromptInput buttons rendering properly
Resolved in Pega Version 7.3.1
When using the Add Item action to add to a Page Group, the SubScriptPromptInput HTML screen appears as a modal to allow the user to enter the Page subscript. In order to correct an error where the OK / Cancel buttons on the screen were not rendering correctly when the SubScriptPromptInput is non auto generated, the markup in @baseclass ! SubscriptPrompt has been updated.
SR-B76473 · Issue 327855
Strategy rule smart prompt exception fixed for Microsoft Internet Explorer 11
Resolved in Pega Version 7.3.1
When using the Execute on Other page SmartPrompt in Microsoft Internet Explorer 11, it was not prompting for values on the Pages & Classes tab. This was traced to an uncaught exception error and has been fixed.
SR-B76473 · Issue 316965
Strategy rule smart prompt exception fixed for Microsoft Internet Explorer 11
Resolved in Pega Version 7.3.1
When using the Execute on Other page SmartPrompt in Microsoft Internet Explorer 11, it was not prompting for values on the Pages & Classes tab. This was traced to an uncaught exception error and has been fixed.
SR-B50863 · Issue 314694
Corrected error for second open of WO history
Resolved in Pega Version 7.3.1
When using the out-of-the-box View History action on the toolbar to show history, the history screen displayed as expected and could be closed with the 'close' button. However, reopening the View History showed an error screen. This has been fixed by modifying the "isWindowOnDesignerDesktop" method to return the correct value for popup cases.
SR-B46520 · Issue 304703
pxRecents correctly updates pxUpdateDateTime for OpenWorkItem
Resolved in Pega Version 7.3.1
When using the pxRecents function to update the pxUpdateDateTime property, the pxRecents update was occurring for OpenSelectedItem but not for OpenWorkItem. This was traced to the the ContentID parameter having a value for the OpenSelectedItem action but not for the OpenWorkItem action, and has been fixed.
SR-B40376 · Issue 300228
XSS filtering added to GenerateHarnessContentHTML
Resolved in Pega Version 7.3.1
XSS filtering has been added to the Show-Harness activity API for longitude, latitude and folder key options.
SR-B35593 · Issue 297558
Fixed multi-click to dismiss Safari cookie message
Resolved in Pega Version 7.3.1
In some cases, Pega Mashup displayed a message to allow cookies for Safari users that required several clicks before the confirmation was accepted and the message was dismissed. This was caused by the system assuming the message was always the first child of a gadget, and has been fixed by using the openCookieConsent method to obtain the child div of the gadget using the "pega-mashup-cookieconsent" class and then remove it.