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.
SR-B67293 · Issue 316457
Autocomplete fixed for complex repeating dynamic layout
Resolved in Pega Version 7.3.1
When using a repeating dynamic layout where each of the records in it had an autocomplete field, selecting a value for any autocomplete always entered the first record's autocomplete. This was an issue with templatization that caused autocomplete to replace the step page with the context's entry handle on the client for data-attributes in cases where it sat inside a repeating structure like RDL. This has been fixed. In addition, the API pega.ui.template.DataBinder.resolveIndex() has been deprecated and the call to it has been removed.