SR-D40617 · Issue 507564
Escape added to Radio button field value to handle HTML tags
Resolved in Pega Version 8.3.1
A radio button with a field label to display a help icon and to open the help URL when the icon was clicked did not display as intended. Changing the control to text area produced the desired results. This was traced to the radio button's label being assigned to a field value which returned a string that at some points contained HTML tags, and has been resolved by escaping the pyLabelFor value before assigning it to the aria-label attribute of the radio button's div tag.
SR-D36335 · Issue 504332
Post Value action properly displayed in upper case after validation
Resolved in Pega Version 8.3.1
After upgrade, if a property with Edit Input toUppercase was created and placed it on a section where the text input has Post Value on Change, validating the uppercased property on the clipboard resulted in the non-uppercase value displaying on the screen. This was traced to the target element with the response value not being updated with the server response for the post value action. Only the attribute value was updated, which is not shown to the user. In order to properly display the value, logic has been added to update the target element value with the response value.
SR-D36970 · Issue 504984
Calendar icon updated to properly display the set number of years
Resolved in Pega Version 8.3.1
By default, the Calendar icon showed a date range of 10 years when -/+100 was expected. This issue was traced to the existing DSS setting (pyNumberofYears under Pega-UIEngine), which enables overriding the date year range, not being honored when the pyNoOfYears property was set to -1. To honor the pyNumberofYears setting, pyNoOfYears should be 21. This has been corrected so the value will be set properly. To see custom calendar range, attached snippet should be added to UserWorkForm. To see custom calendar range, the below snippet should be added to UserWorkForm: <script> pega.u.d.overrideCalendarDefaultRange = { past: 20, future: 20 } </script>
SR-D37290 · Issue 506283
Null check added to ensure value "yyyyMMdd" displays correctly in DateTime Input
Resolved in Pega Version 8.3.1
An issue where the input value "yyyyMMdd" was not displayed correctly in a DateTime input field was traced to moment.calendar returning invalid formatting when executed on a null property. To resolve this, a check has been added to assess whether the datetimeframe has any properties or not.
SR-D37326 · Issue 504934
Resolved clipboard formatting issue in Reply Thread and Send Correspondence
Resolved in Pega Version 8.3.1
Issues were seen with the table formatting of client data after mail was sent. This has been resolved by ensuring all borders are retained in RTE when used in both "Send Correspondence Task" and "Reply Thread".
SR-D38581 · Issue 504774
Removed unnecessary cross-site scripting filtering on paragraph rule
Resolved in Pega Version 8.3.1
When a link was set in a paragraph rule, the target option was removed in the returned layout structure. This was traced to unnecessary cross-site scripting filtering which has now been removed.
SR-D33445 · Issue 505993
Handling added for context switching with Ajax container in Timeline
Resolved in Pega Version 8.3.1
When using Interaction Portal -> Overview -> Timeline and opening a case that uses an AjaxContainer, clicking on an icon in the Timeline without having first clicked anywhere in the document was generating an exception. If there was a click in the document body first, clicking on the icon worked as expected. This has been resolved by adding a parameter to registerContextSwitching method to handle customeDOMEvents along with a condition to check if pega.u.d.isAjaxContinerExists is a function, which will register the Context if 'true'.
SR-D45360 · Issue 510098
Support added for non-decimal currency notation
Resolved in Pega Version 8.3.1
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-D40055 · Issue 507420
Work List loads as expected in IE
Resolved in Pega Version 8.3.1
After upgrade, the Work List was not loading in IE. This was an unintended side effect of work done to handle resizing the Recents list when another tab was open, and that change has been reverted to resolve this issue.
SR-D36176 · Issue 508405
Work List loads as expected in IE
Resolved in Pega Version 8.3.1
After upgrade, the Work List was not loading in IE. This was an unintended side effect of work done to handle resizing the Recents list when another tab was open, and that change has been reverted to resolve this issue.