SR-D87203 · Issue 550994
Required field accessibility improved
Resolved in Pega Version 8.3.3
In some instances, there is no non-visual indicator that a field is required. Because the asterisk character is commonly ignored by screen readers, the <required> attribute or <aria-required> should be used so that non-sighted users have explicit information about the required status of the field. To enable this, when client-side validations are disabled on the harness and clientValidation attributes are absent, the system will run an additional check so that aria-required is added.
SR-D85400 · Issue 549060
Reset focus to Rich Text Editor after Spellchecker use
Resolved in Pega Version 8.3.3
After correcting the misspelled words as suggested by SpellChecker, the corrected words were not reflected in the email. This was traced to a focus issue in Rich Text Editor, and has been resolved by ensuring the focus is returned to Rich Text Editor once the suggested corrections are accepted.
SR-D81924 · Issue 548648
Resolved Ajax and autocomplete errors in mobile offline
Resolved in Pega Version 8.3.3
When logging into the app for the first time on a new session to navigate to scheduled contacts and reschedule one, clicking the right or left arrow icons to move through dates resulted in an "AJAX request failed" error. POST 500 errors were also logged in the Developer Tools console with every click of the icon. It was possible to close the error and continue, and navigating to another screen and returning or leaving the app and restarting it resolved the issue. This has been resolved by adding dataOnly for getParentWorkItem to support a Parent online and child offline scenario. In addition, an issue with console errors caused by a popup when autocomplete did not have any results has been corrected with the addition of a null check to clear the results div only if it exists.
SR-D78659 · Issue 545758
Resolved CSV validation overflow in Google Chrome
Resolved in Pega Version 8.3.3
When using Google Chrome, validation of records was getting stuck in the UI at 32000+ while importing a CSV file with many invalid records when using the import option in Data type’s local data storage. Investigation showed the Call Stack size limit was exceeded in the Google Chrome dev tools due to the ":first" selector being passed to the Jquery find() method to find the element from the first element child of the XML doc. This selector causes maximum callstack exception when the document is large, and this is a deprecated selector in later versions of Jquery. To resolve this issue, the XML function in pzpega_tools_asyncprocess has been updated to replace the ":first" selector.
SR-D84882 · Issue 551988
Resolved duplicate messages from HarnessErrorList section
Resolved in Pega Version 8.3.3
When using pyCaseErrorSection to call HarnessErrorList and display any errors on Clipboard page, when the Clipboard page had more than one error then the error message was shown multiple times. This has been resolved by adding a check that will iterate through the errors to see if it is present on the page already. If it is present it will be ignored, and if it is not present, then it will be added.
SR-D80825 · Issue 546571
Resolved tab appearance issues related to resolution support
Resolved in Pega Version 8.3.3
When trying to add multiple tabs on larger screens, once the first row was filled with tabs then new tabs began appearing at the bottom of the layout group. The layout group worked as expected with the tab overflow having the right and left arrows with the dropdown on smaller screens. In addition, @1440px the overflow arrow on the right side was not working correctly, showing as grayed out even though focus was not on the last tab. These issues were traced to taboverflow with add icon not working correctly at certain resolutions. To resolve this, the todisableslide function has been updated to consider add icon width and layoutgroup has been updated to consider parent width.
SR-D86200 · Issue 549030
Resolved tab appearance issues related to resolution support
Resolved in Pega Version 8.3.3
When trying to add multiple tabs on larger screens, once the first row was filled with tabs then new tabs began appearing at the bottom of the layout group. The layout group worked as expected with the tab overflow having the right and left arrows with the dropdown on smaller screens. In addition, @1440px the overflow arrow on the right side was not working correctly, showing as grayed out even though focus was not on the last tab. These issues were traced to taboverflow with add icon not working correctly at certain resolutions. To resolve this, the todisableslide function has been updated to consider add icon width and layoutgroup has been updated to consider parent width.
SR-D84180 · Issue 550228
Resolved tab appearance issues related to resolution support
Resolved in Pega Version 8.3.3
When trying to add multiple tabs on larger screens, once the first row was filled with tabs then new tabs began appearing at the bottom of the layout group. The layout group worked as expected with the tab overflow having the right and left arrows with the dropdown on smaller screens. In addition, @1440px the overflow arrow on the right side was not working correctly, showing as grayed out even though focus was not on the last tab. These issues were traced to taboverflow with add icon not working correctly at certain resolutions. To resolve this, the todisableslide function has been updated to consider add icon width and layoutgroup has been updated to consider parent width.
SR-D86274 · Issue 552507
Resolved validation conflict with error message display
Resolved in Pega Version 8.3.3
Error messages set through property-set- messages or edit validate were disappearing when out of focus from the date field if the field had a mandatory condition. This was traced to an edge condition where required validation was conflicting with another error message, and has been resolved by modifying the code so the system will not validate required on blur if the input has another error message.
SR-D80916 · Issue 544966
Special characters encoded to resolve Tomcat error
Resolved in Pega Version 8.3.3
When hitting down-arrow in a subprocess shape's "flow name" box, the error "Server Error, status = 400" appeared on screen. Investigation showed this was caused by Tomcat rejecting any request it considered to have unsafe characters. To resolve this, encodeURI will be used on the query string in the HTTP wrapper of the smartprompt, to encode the query string.