SR-D45848 · Issue 515526
Added toggle to hold radio button value during multiple service case creation
Resolved in Pega Version 8.2.5
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 512376
Aria-label added to 'clear search option' icon
Resolved in Pega Version 8.2.5
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 514151
Alt attribute removed from non-image content
Resolved in Pega Version 8.2.5
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 516182
Error messages made more accessible
Resolved in Pega Version 8.2.5
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 511852
Count of remaining characters in a text box made accessible
Resolved in Pega Version 8.2.5
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-D47401 · Issue 512617
Corrected multiplying errors on dirty flag
Resolved in Pega Version 8.2.5
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-D48887 · Issue 512945
Read-only text inputs remain read-only after browser refresh
Resolved in Pega Version 8.2.5
Read-only text inputs were changing to editable after a browser refresh. This was traced to work done to better handle a displayOnPage GET request that was sent with all of the parameters in the parameter page (data-model) that was causing a 400 Bad Request due to the browser URL length limitations. That issue was resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case, to resolve this issue, the readonly parameter for displayOnpage action has been restored and will be passed.
SR-D50372 · Issue 514613
Interaction Driver now supports more than 7 open items
Resolved in Pega Version 8.2.5
After creating 7 items in an interaction so they are open in the interaction driver, adding item number 8 caused the threads in the clipboard to not correspond with the number of items and the interaction driver was not extended with the new items. This was traced to the "parentKey" parameter not being present in the request: the "parentKey" parameter isn't mandatory but is usually used internally for the RECENTS functionality, and was missed only when maxdocs limit was reached because the recents feature was not validated in case of maxdocs. To resolve this, the "parentKey" will now be passed for all use-cases.
SR-D51093 · Issue 515225
Skin Breakpoints work in Layout Mode with "Optimized code" setting
Resolved in Pega Version 8.2.5
In Application Skin settings for dynamic layouts, even through the choice of any format was offered in the dropdown (My Formats and Inherited), if the layout mode was set to "Optimized code" the responsive breakpoints were only working when Inherited format was chosen and not working for My Formats. This was a missed use for flex where the proper key was not mentioned, and has been resolved by updating GenerateFlexLayout.java.
SR-D51330 · Issue 515246
Added toggle to hold radio button value during multiple service case creation
Resolved in Pega Version 8.2.5
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.