SR-C53999 · Issue 402911
Added missing validation trigger for survey question page
Resolved in Pega Version 8.1.1
Validate rule or preaction was not firing as expected for the Question page in Pega Survey. This was due to a missing step which has now been added to pzDisplayQuestionPagePostAct.
SR-C54754 · Issue 402915
Work by Work Queue modified to use RD in place of deprecated list view
Resolved in Pega Version 8.1.1
When the "Find" button was selected in Designer Studio >> Case Management >> Tools >> MyWork >> Work by Work Queue, a series of dotted lines that exceeded the section limitation appeared. This was traced to the use of the deprecated function List-view in workbasketlistPopup. In order to support the needed display, the Pega-Landing.pzProcessAndCaseRulesMainMenu Navigation rule has been modified to call a report definition Assign-WorkBasket.pyASSIGNMENTSFORWORKBASKET instead of the deprecated list view. While there is a small difference in user experience and behavior, all the columns being fetched and filters being added will be similar to that of the ones previously seen in the list view.
SR-C55017 · Issue 402951
Mapping corrected for Constraints rule properties
Resolved in Pega Version 8.1.1
The Constraints rule was not working for page list due to Page context and Page Context class both referring to the same property of pyPageContextClass. This was an error introduced during a UI Ruleform upgrade, and has been resolved by correcting the mapping of the "Page Context" field to pyPageContext.
SR-C55058 · Issue 402925
Stream Service stability improvements and Kafka upgrade
Resolved in Pega Version 8.1.1
A number of improvements have been made to Stream Service stability, and apache-Kafka has been updated to v1.1.0.1.
SR-C55269 · Issue 402958
Custom filter values correctly pass to custom drilldown filters
Resolved in Pega Version 8.1.1
Reports with summarize column, drilldown, and custom inline sections were not forwarding values from the custom filter to the drilldowns custom filter. This was a missed use case in earlier work done to ensure custom filter values are populated during runtime, and has been added.
SR-C55337 · Issue 402905
Removed duplicated parameter encoding from Create Work action string generation
Resolved in Pega Version 8.1.1
Multibyte characters such as Japanese or Chinese passed as parameters to the Create Work action of a button were being encoded/decoded twice. This resulted in parameters being incorrectly interpreted in the newly created Work. To correct this, the parameters will not be encoded during the action string generation for Create New Work, and the necessary encoding will be handled only by SafeURL.
SR-C55724 · Issue 402954
SetTracerOptions modified to correctly pass needed parameter for displaying changes on the UI
Resolved in Pega Version 8.1.1
When opening trace from any rule form's Action > Trace option and modifying the settings, the changed settings were not reflected on the UI until the tracer window was closed and opened again. This was caused by the data page used to store Tracer Settings not getting its parameters properly and hence was getting duplicated. This has been fixed by modifying the activity SetTracerOptions to pass the missing parameter.
SR-C57025 · Issue 402913
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.1.1
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-C57259 · Issue 402875
Reference Rules gadget shows results for GET >> Service Activity
Resolved in Pega Version 8.1.1
Even if a Rule had activities in the GET >> Service Activity portion of the rule, the References panel did not show them. This was a missed use case and has been addressed by using Start-Validate and End-Validate in Rule-Service-REST.Validate activity.
SR-C57445 · Issue 404782
Test Cases tab visible to delegated rules
Resolved in Pega Version 8.1.1
When the Revision Manager assigned rules in the CR, the TestCase tab was not available to the rules. This has been fixed by adding the test cases tab to "RevisionRuleFormLayout" and "pyRMRuleFormLayoutDE".