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.
SR-C82353 · Issue 426014
CorrNew loop logic updated to handle custom notifications
Resolved in Pega Version 8.2.1
When CorrNew was used to configure a email smart shape in a custom notification, having a 'not available' party as the last parameter was leading to the mail not being sent. To resolve this, the 'while' loop logic has been updated to iterate over the workparties for every party role.
SR-C85312 · Issue 424037
Check added for custom section use in Summary report exported to Excel
Resolved in Pega Version 8.2.1
Criteria were missing when Export to PDF was used for Summary reports filtered by a custom section. This was caused by the needed pyQueryTokenList not being repopulated for the export in the case of custom section use, and has been resolved by adding a summary report check in the pzIncludeCustomFilterSection section before invoking pzClearRDTempFilters function.
SR-C90261 · Issue 428122
Hotfix installer updated to adhere to installorder file included in the package
Resolved in Pega Version 8.2.1
In order to ensure hotfixes are always installed in the proper order, the installer has been updated to iterate over a set that is ordered according to the INSTALLORDER.PEGA file included in the DL file at packaging time.
SR-C83050 · Issue 422977
IE width calculation fixed for imported built-on with dymanic layout
Resolved in Pega Version 8.2.1
After upgrade, the Built On input for the application screen in Designer Studio was not rendering in the IE11 browser if dynamic layout was used. This was caused by a browser-specific issue with width calculation for pzDefinition, and code has been added to handle this issue.
SR-C89316 · Issue 426077
Lower major ruleset versions will not be considered during design time validation
Resolved in Pega Version 8.2.1
After circumstancing a rule by property and withdrawing the rule in higher version, the same rule was circumstanced by template. Later after major skimming, attempting to perform a save-as of the circumstanced template rule resulted in an error stating that the circumstanced property already existed. During design time, the system validated the rule with rules from all other ruleset versions. In this corner case where a property-based circumstanced rule was withdrawn and then skimming was performed, the error occurred because it was being saved in a different major ruleset instead of into the same major ruleset. In order to better handle this condition, the system will not consider rules from lower major versions during design time validation.
SR-C75723 · Issue 421826
Rollback filter query updated to handle very large classes mapped to the same history table
Resolved in Pega Version 8.2.1
When rolling back the imported product file using deployment manager, the error "DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: column "pzinskey" does not exist" was seen. This was traced to the rollback process picking the already processed items from the history table due to an incomplete filter query that occurred when there were more than 1000 classes mapped to same history table. This has been resolved.
SR-C81410 · Issue 422137
Radiobutton aria-label enhanced to retrieve localized field value
Resolved in Pega Version 8.2.1
Localization code has been added to the pzpega_ui_template_radiogroup file to support using RadioButton aria-labels for Field value.