SR-C87757 · Issue 431644
Country Code for Austria saved correctly
Resolved in Pega Version 8.2.2
When trying to save an address with CountryCode=AT, the code was saved as "at" instead. This was caused by a temporary field value not being correctly cleared, and has been resolved.
SR-C89619 · Issue 429574
Custom section filters retained during refresh
Resolved in Pega Version 8.2.2
Filtered values were not retained on refresh when filtered using a custom section. This has been resolved.
SR-C91121 · Issue 430389
Data Page seatch results have expanded data available to view
Resolved in Pega Version 8.2.2
It was not possible to expand a search result and see Ruleset, Updated by, etc, for Data Pages. This was traced to the Layout Properties of section pzSearchDrilldown having a visibility condition of .pzCategoryActionKeys != 'Rule-Declare-Pages' after being reconfigured during prediction studio implementation for rule transition. To resolve this, the necessary related table for data pages has been added to the pzSearchDrilldown section.
SR-D3494 · Issue 439416
Enhanced REST acceleration wizard handling of existing properties during rule generation
Resolved in Pega Version 8.2.2
A resolution provided in an earlier release addressed the REST accelerator wizard failing when there was a property present in the @baseclass and that property was also present in the JSON input for data model generation. The error generated was "Cancelling rule generation. Definition required to conform to @baseclass.Name instance". This update further enhances that Rest wizard resolution to address case sensitivity issues in the naming, and adds additional support for scenarios where the property does not exist in the integration class or parent class by checking if the property exists in pyIntContextClass.
SR-C96297 · Issue 433776
Enhancements added in support of AES/PDC integration
Resolved in Pega Version 8.2.2
The following enhancements have been added in support of AES/PDC integration: - QueueStatistics for Oracle and multi-tenant environments -Postgres statistics are reset after every push (this can be disabled by changing the DSS ResetTableStats) -Enabled Debug statements before all connect-rest/connect-soap calls -Handling for Listener Information issues -Elastic search updates -The connect timeout has been enhanced from 30 sec to 60 sec for all REST connectors. -Data pages can be used for picking the End point URL -Elastic Search Count details can be pushed to PDC
SR-D4027 · Issue 439898
Explicit property evaluation added to correct visibility in Proposition Management sorting
Resolved in Pega Version 8.2.2
After navigating to the Decisioning: Proposition Management landing page (Configure->Decisioning->Decisions-> Proposition management -> Hierarchy), opening any Decision data and then switching to the Form tab to perform any sorting on the Form fields grid caused the UI to become unresponsive and generate the error "Uncaught SyntaxError: Unexpected end of input at pega.ui.Doc.evaluateVisibleWhens". This issue was traced to a 'when' condition which demanded explicit mention of whether the property value had been evaluated as true or false, and that result has now been added.
SR-D1716 · Issue 438108
Fixed expand when issue on dymanic layout with custom header
Resolved in Pega Version 8.2.2
After upgrade, a Dynamic layout with collapsible type Container setting which included a custom section to show the text and image in place of text had an 'expand when' condition applied that caused the entire dynamic layout to be malformed and show the raw HTML code if there was an error. This was traced to the system rendering the dynamic layout in non-template form if the header has a JSP section include, leading to the expandable layout header div HTML elements getting mixed up with the custom header sections HTML code due to the aria-label attributes. This has been resolved by removing the section stream from aria-label in RUF - GridHeaderElements.
SR-C89135 · Issue 434747
Formatting tag updated to ensure skin rule styles are correctly applied
Resolved in Pega Version 8.2.2
After a style was configured in the skin rule for TABS laouts -> Repeating Formats, the configured style was not being correctly applied to the skin. This was related to the anchor tag not picking up the changes, and has been resolved by replacing that with a span tag.
SR-C89250 · Issue 429742
Guardrail score ignores test rulesets
Resolved in Pega Version 8.2.2
Test rulesets for a branch were unexpectedly being considered when calculating the Guardrail score. This has been corrected.
SR-C93341 · Issue 433630
Hash handling security updates
Resolved in Pega Version 8.2.2
Several updates have been made to improve hash handling security.