SR-B51546 · Issue 310076
PromptSelect control action set repaired for class key config
Resolved in Pega Version 7.3.1
When prompt selects were configured to use a class key validation for the source, action set events did not fire. (e.g. onchange, refresh section & data transform). This was traced to missing ClientValidation inclusion for a ClassKeys configuration in PromptSelect Control, and has been fixed to generate the necessary pega_attributes for action execution.
SR-B43996 · Issue 307700
Column header tags generated as span for accessibility
Resolved in Pega Version 7.3.1
When tables were generated, column header label tags were not given FOR values that were needed for accessibility. To correct this, spans will be generated instead of labels.
SR-B15685 · Issue 317905
Mobile autocomplete dropdown selections fixed
Resolved in Pega Version 7.3.1
When the 'Enable lightweight autocomplete on phone' and 'Allow scrolling for more results' were enabled, the incorrect data was selected (e.g., using the autocomplete to select "John" from the list instead displayed "Mark"). This was due to a logic issue around the scroll feature for mobile list based autocomplete, and has been fixed.
SR-B53383 · Issue 313525
Fixed JAWS reading icon header incorrectly in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, JAWS was reading the icon headers of a repeat grid configured with a filtering option as 'Click to sort' instead of 'Click to filter'. This was due to the aria-label being missed on filter links, and has been fixed.
SR-B43602 · Issue 306874
Check added to handle unexpected RTE scroll in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, pressing the enter key in the RTE field caused the page to scroll down even when the RTE area with the cursor in it was completely visible on page. This was caused by an error in the position calculation for scrolling in quirks mode, and has been resolved with the addition of a check which will avoid calling the scroll function when using RTE with Microsoft Internet Explorer.
SR-B43602 · Issue 311133
Check added to handle unexpected RTE scroll in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, pressing the enter key in the RTE field caused the page to scroll down even when the RTE area with the cursor in it was completely visible on page. This was caused by an error in the position calculation for scrolling in quirks mode, and has been resolved with the addition of a check which will avoid calling the scroll function when using RTE with Microsoft Internet Explorer.
SR-B49082 · Issue 307656
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-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.