INC-175394 · Issue 661455
Date Time format corrected for Chinese locale
Resolved in Pega Version 8.7
The DateTime input field displayed the error message "not a valid date/time value" for the Chinese locale when the time zone source configuration was set as "CET". This has been resolved by setting the moment object's locale to the operator locale while converting the date time values to the operator time zone.
INC-208516 · Issue 705098
Patchdate values made unique
Resolved in Pega Version 8.8
The hotfix manager was incorrectly indicating that a previous hotfix was not installed or was partially installed and should be reinstated. This scenario was created during security updates where the missing/incomplete hotfix had been deliberately deleted from the database, and has been resolved by adding an update which will force patchdate to be unique when adding duplicate code resources during tests.
INC-150407 · Issue 605842
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-153109 · Issue 611354
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-153555 · Issue 612228
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
SR-D26815 · Issue 500192
Updated support for numeric values in text columns during Excel export
Resolved in Pega Version 8.4
After creating a report definition that included currency and percentage as a columns, the currency, percentage, and number format were not shown as expected for the locale when the report was exported to Excel. This was an inadvertent side effect of work performed to resolve issues for text columns formatted by non-numeric controls, and has been resolved by moving the support for numeric values in Text columns from ReportUIField to NumericReportUIField.
SR-D55801 · Issue 524293
Corrected HTML error generated on export to PDF
Resolved in Pega Version 8.4
After exporting a report to PDF, the PDF could be viewed but repeated instances of the error "<th> missing ‘>’ for end of tag" were logged. This was traced to missing the closing '>' for th in the pzRRDataListHeaderRow HTML rule when "Enable column command menu" is unchecked in ReportViewer options, and has been corrected.
SR-D53225 · Issue 516318
Rule creation logic updated to include creation branch
Resolved in Pega Version 8.4
When trying to create a new adaptive model rule in Prediction Studio, the “Create” button was not activating. The adaptive model rule was being saved in a branch ruleset, and investigation indicated that the deactivated button could be traced to the lack of an open ruleset version available even though the intention was to create it on a branch. This has been resolved by modifying the rule creation logic to incorporate the branch for creation.
SR-D58194 · Issue 524702
Declarative cache resolved based on tenantId
Resolved in Pega Version 8.4
After upgrade, creating a case type (Assistance request) with a customized Create view was generating an exception error during the RecalcuateAndSave activity (in step 6). This was traced to a NullPointerException when building a declare expression cache entry for a property and was due to the class on which the expression was defined not being present in the current tenant. To resolve this, Declarative cache will be resolved based on tenantId.
INC-181389 · Issue 668678
Unused class reference removed from CaseActionArea
Resolved in Pega Version 8.7
The rule Work-.pyCaseActionArea in Theme-Cosmos was logging error messages related to "clipboard.InvalidParameterException: Class not defined in dictionary: PegaMKT-Work" when opened in Dev Studio. This was traced to a reference to the section "pyCaseActionArea" which was not present by default in PegaMKT-Work, and has been resolved by recreating the section "pyCaseActionArea" to remove the unused class reference.