SR-C82530 · Issue 420608
Atmosphere XSS Vulnerability fixed
Resolved in Pega Version 8.2.1
Atmosphere has been updated to close a potential XSS vunerability.
SR-C84788 · Issue 422937
Handling added to maintain custom modal template name after errors
Resolved in Pega Version 8.2.1
When using a grid where each grid row had an Edit button which launched a modal dialog with a custom modal template, the post action activity of the flow action introduced error messages on a top level page (not on primary or pyWorkPage). Clicking the submit button again caused the modal dialog size to shrink and not work after that. This was traced to the second submit using the system's pyGridModalTemplate instead of the custom modal template due to the modal submit button being replaced with new markup. To resolve this, the modal launch will now use the "pega.u.d.submitModalDlgParam.modalSection" variable which will have the modal template name. In addition, a check has been added to ensure this is not passed as null.
SR-C75205 · Issue 424476
Invalid text entry in Date control field now returns current timestamp
Resolved in Pega Version 8.2.1
Inconsistent behavior was seen between entering an invalid date in numeric vs text format. Entering an invalid date in number format resulted in the system replacing the entered value with the text “Invalid date”. Entering an invalid date in text format caused the system to retain the value and not show a validation error. This has been corrected by modifying the date/time formatting for both text and numerical input to return the timestamp in case the entered value is incorrect.
SR-C85096 · Issue 423236
XSS check logic updated for pyPosition
Resolved in Pega Version 8.2.1
Additional logic has been added to prevent the injection of javascript into script tags while rendering Smart Tips.
SR-C87881 · Issue 427100
Additional dropdown options exposed for RD column definitions
Resolved in Pega Version 8.2.1
When using Column formatting in Report Definition ruleform, the "Negative format" option was losing its custom style after opening and submitting the "Format" popup using the magnifying glass. This was caused by the submitted popup overwriting the inherited style reference. Previously, the style ref options were hidden from the dropdown because the same UI is shown in the ruleform and the end user portals and the desire was to avoid end user confusion. In order to support developer use, pzPopulateNegativeFormat has been updated to expose the missing options in the dropdown.
SR-C75497 · Issue 427436
Resolved "no items for filters applied" error in column filtering
Resolved in Pega Version 8.2.1
When trying to filter a column, the options did not appear on the filter and the error "No items for the filters applied" was displayed. This was due to the Declarative index join being removed on save and on run even though it was referenced in the class join filters. To resolve this, logic has been added to the pzCopyPySource activity to loop through all class joins and their filters so both sides of the filter are checked for references to a declarative index join.
SR-C84116 · Issue 423756
Added container handling to make optimized grid table visible in action top
Resolved in Pega Version 8.2.1
After upgrade, if the Optimize code checkbox was checked on a table and visibility was applied over grid header, the table was not visible in the UI. This scenario only happened when a grid was upgraded from non-optimized to optimized with some visibility condition added, and was caused by the system not yet supporting the visibility features in action top for an optimized grid. To resolve this at this time, the system has been updated to not honor the visibility at container for an optimized grid so the table will be visible.
SR-C81855 · Issue 421403
Check added to format simplified Chinese date generation to match system expectations
Resolved in Pega Version 8.2.1
HOLDER FOR TEXT
SR-C74648 · Issue 422905
Autocomplete arrow placement corrected in Right to left local mode
Resolved in Pega Version 8.2.1
When using the Autocomplete control, the blue arrow was seen to have an incorrect placement/orientation in RTL mode. This was traced to the autocomplete background-image in RTL mode being the same as that for LTR, and has been resolved by adding specific background-image for RTL.
SR-C87665 · Issue 424611
CPU time will be fetched from MBeanServer instead of the JRE application to provide consistency
Resolved in Pega Version 8.2.1
The value of CPU time in the Enterprise health metrics was being given in nanoseconds instead of seconds after the IBM JRE version was upgraded by applying Websphere Application Server patches. The CPUTimer is a platform class which has logic specific to different JRE vendors; in order to provide consistent results regardless of which JRE is used, the system has been updated to always fetch the values from the MBeanServer.