SR-D45360 · Issue 510099
Support added for non-decimal currency notation
Resolved in Pega Version 8.2.5
Previously in the pxCurrency control, the options allowed either specifying Decimal places (2 by default) or using the locale to decide decimal places when "Use currency standard" was selected (creating the default for 2 for en_US, 0 for jp_JP and 3 for ar_JO.) However, this did not account for currencies like JPY, TWD, and HUF, which do not use decimal precision. In order to support these currencies, handling has been added to formatNumaber js and pxFormatNumber for locales which do not have decimal precision in their currency.
SR-D45527 · Issue 512325
Corrected comma in chat appearing as ',null,'
Resolved in Pega Version 8.2.5
When a comma was sent in chat, it appeared as ",null,". For example, " I am applying the loan now,null, thanks ". Investigation showed that this was caused by Pega code that was overriding a JSON parse native API, and it has been resolved by removing the override and handling the Pega parse via a different API.
SR-D45828 · Issue 518020
Added variable null check to resolve refresh condition on dynamic layout not working
Resolved in Pega Version 8.2.5
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 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.