SR-D45828 · Issue 518021
Added variable null check to resolve refresh condition on dynamic layout not working
Resolved in Pega Version 8.4
Given a setup where a parent section had several section includes, one of which had a property that was set to refresh and disable another section when the property changed, on change the refresh action was not working and hence the disabling did not work. Refreshing the browser corrected the behavior. Javascript errors were noted on the console. This has been resolved by adding a null check on the variable to avoid exceptions.
SR-D45848 · Issue 515527
Added toggle to hold radio button value during multiple service case creation
Resolved in Pega Version 8.4
When a field was implemented with a radio button control in the service case screen, starting two cases of the same or different case type (with the same property and control) resulted in the selected value not sticking in the first case when selections were made for the second case. This was traced to multiple radio buttons with the same name in the dom for different AJAX containers: as per radio buttons behavior, only one could be selected if they have the same name. To correct this issue, updates have been made to change the name on radio buttons which are inside the hidden AJAX container and toggle the changes when the buttons should be shown.
SR-D46532 · Issue 512377
Aria-label added to 'clear search option' icon
Resolved in Pega Version 8.4
After applying a search in the reporting functionality, the Clear Search icon becomes active. In order to improve accessibility, an aria-label attribute for icon/image control has been added to this icon.
SR-D46542 · Issue 514152
Alt attribute removed from non-image content
Resolved in Pega Version 8.4
The links under the reporting categories contained an alt attribute. As Alt attributes should only be used for images, these tags have been removed.
SR-D46543 · Issue 516183
Error messages made more accessible
Resolved in Pega Version 8.4
In order to improve the accessibility of error messages, an aria-describedby attribute will be placed on the input that will link to the error message. To further support screen reader users, the focus will be moved to the first input field with an error after the user clicks submit.
SR-D46545 · Issue 511853
Count of remaining characters in a text box made accessible
Resolved in Pega Version 8.4
In order to improve accessibility, aria-describedby has been added to the Text Area character counter span element's ID so the remaining number of characters to enter in the text field will be read by the screen reader.
SR-D47344 · Issue 519893
Single quotes escaped in RTE title field value
Resolved in Pega Version 8.4
A JSON parse error was caused by single quotes not being escaped in the RTE title field value. This has been corrected.
SR-D47401 · Issue 512618
Corrected multiplying errors on dirty flag
Resolved in Pega Version 8.4
The error message "Value cannot be blank" was appended on the screen every time the browser gave a dirty flag and OK was clicked. This was due to the context for the error message not being set correctly after toggleErrorMessage, and has been corrected. In addition, due to Context being incorrect when there was a check on the errors on the element, further work has been added to set the correct context before checking if errors exist.
SR-D47583 · Issue 518040
IsMobile 'when' configurations are properly displayed in mashup preview
Resolved in Pega Version 8.4
Given two layouts configured based on the 'when' rule pyIsMobile, the mashup preview did not work in the mobile form factor. This was only an issue with App Studio preview of a mashup and did not have an impact on the enduser use of the mashup, and the same mashup code viewed on mobile/desktop worked as expected. Investigation showed that the 'when' rule was evaluated correctly for the application level, but in mashup it was evaluated to false even when opened in mobile view from App studio. The Rule-Utility-Functionchecks to see if an overridden useragent has been specified and if it has, then it uses it for the preview in App Studio, however in mashup the userAgentDetails did not contain any of the satisfying conditions under which the condition might be returned as false. The issue in this case was traced to the Rule-Utility-Functionneeding to handle the scenario of Mashup Preview by checking if the thread was from the mashup preview, and that has been implemented.
SR-D47689 · Issue 520830
EvaluateConditions properly sets context for refresh section
Resolved in Pega Version 8.4
Rule Not Found and Unresolved Assembly Errors were seen in production logs after upgrade. Investigation showed that the method context used by pzpega_ui_changetracker.js in "evaluateConditionsOnXThread" was not reset correctly, causing the refresh section response for the Recents List to not be properly updated. This has been resolved by updating the evaluateConditionsOnXThread method to set the proper context after evaluateClientConditions is run.