SR-B44050 · Issue 319237
Accessibility improved for modal dialog errors
Resolved in Pega Version 7.3.1
When an error occurred in the modal dialog and was displayed at the top of the screen, the focus was not directed to the top of the screen to properly read the error messages for accessibility. Instead, focus shifted to the cancel button at the bottom of the screen for server side validation. To improve accessibility, code changes have been made to make the error section focusable and update the cyclic process (updating boundary elements of modal dialog) for the focus handling.
SR-B44050 · Issue 319888
Accessibility improved for modal dialog errors
Resolved in Pega Version 7.3.1
When an error occurred in the modal dialog and was displayed at the top of the screen, the focus was not directed to the top of the screen to properly read the error messages for accessibility. Instead, focus shifted to the cancel button at the bottom of the screen for server side validation. To improve accessibility, code changes have been made to make the error section focusable and update the cyclic process (updating boundary elements of modal dialog) for the focus handling.
SR-B55736 · Issue 311735
Invalid date field will remain after error message displayed
Resolved in Pega Version 7.3.1
When an invalid date was entered into a date field and the page was submitted, an alert with the message "Please correct flagged fields before submitting the form!" was displayed. Once the alert is dismissed, the value in the date field was reverted/reset to the old pre-populated date instead of the incorrect one. This created confusion as the date field now appeared valid and did not match the error message. To clarify the action needed, the error on the date field will remain and not be reset.
SR-B67239 · Issue 316374
pyCaseWorker offered during portal choice
Resolved in Pega Version 7.3.1
When choosing a portal on the access group, the pyCaseWorker one was not shown even though it was described in the documentation. To resolve this, an activity to update the property "pyDesktopType" to "User" has been added for the pyCaseWorker, pyCaseManager7, and pyPega7Express portals.
SR-B44833 · Issue 311138
"Close All" tabs function made more robust
Resolved in Pega Version 7.3.1
When many tabs are opened in a support portal session using Microsoft Internet Explorer, the "Close all" dropdown became unresponsive did not list all open tabs. This has been fixed by modifying the pega_yui_tabview.js file "showTabsMenu" method to escape special characters.
SR-B46945 · Issue 311492
"Close All" tabs function made more robust
Resolved in Pega Version 7.3.1
When many tabs are opened in a support portal session using Microsoft Internet Explorer, the "Close all" dropdown became unresponsive did not list all open tabs. This has been fixed by modifying the pega_yui_tabview.js file "showTabsMenu" method to escape special characters.
SR-B30385 · Issue 305412
Snapstart popup handling improved for Outlook
Resolved in Pega Version 7.3.1
When opening the same session in different Outlook windows, the original window showed the correct harness while all other windows showed a status good message with http 400 response http://localhost:8717/prweb/diagnostic/status_good.gif. This issue is seen when mail is opened in a new window, a flow is created (contact/opportunity), then focus is moved to the actual Outlook window. The "status good with no content" message appears when switching to other mail. This was traced to the handling related to triggering a new flow from the opened window; the handling for the parameters and instantiation of flow are set in one data page while the application layer request was sending a call to two activities which in this cases did not return any content, causing confusion in where the ActivityStatusSuccess was displayed. To fix this, the JS has been updated with an extra parameter "target", and handling has been updated to ensure the system is passing current parameter page while calling Show-Harness activity.
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.