INC-142223 · Issue 598648
Handling added for new case type using reuse case life cycle
Resolved in Pega Version 8.4.4
Creating a new Case Type in a branch ruleset using the 'Reuse case life cycle' option was not working, and the error "branch rulseset not a candidate" was generated. pxCreateCaseDataPages that are called as part of creating a case rely on Param.RuleSetName; generally this parameter is set in the param page when other assets are created. When Reuse case life cycle was selected, other assets were not created and param.RuleSetname was not set. This affected pxCreateCaseDataPages when branch parameter was provided. This was a missed use case, and has been resolved by setting param.RuleSetName from param.ruleset to fix the issue.
INC-150039 · Issue 608044
Adjusted validation of literal value of a parameter
Resolved in Pega Version 8.4.4
When mapping a parameterized when rule to the proposition filter, parameters passed from the proposition filter page were not getting flown to the when rule. This was caused by special character validation for a literal value of a parameter which necessitated putting the parameter value within quotes and which resulted in a parameter value mismatch at run time. To support this use, this validation has been disabled as parameter values would not get included within quotes. This change does not have any impact on when rule or proposition filter rules java generation.
INC-148440 · Issue 607335
Guardrails Compliance Score correctly excludes test case rulesets
Resolved in Pega Version 8.4.4
When calculating the compliance score of the Application with the "Ignore test rulesets when calculating Guardrails score" option selected, the test case ruleset was still included in the Guardrail score calculation. This was traced to updates made to the pzGetTestRuleSetsList activity used to get the test rulesets for any application, and was due to the returned data not being correctly updated from a named page back to the primary page. This has been corrected.
INC-153697 · Issue 625984
Dragon successfully navigates to user profile icon
Resolved in Pega Version 8.5.3
Attempting to navigate to the user profile icon when using Dragon software was not working. This is an issue with how Dragon interacts with the "< I >" element operator icon, and has been resolved by replacing "< i >" with a button and appropriate aria label.
INC-151669 · Issue 618042
Formulas corrected for GenerateExcelFile
Resolved in Pega Version 8.4.4
After upgrade, using pxGenerateExcelFile to generate an Excel file resulted in some formulas and values not displaying. This scenario used an Excel template with two tabs - one showing direct page values and the second displaying the calculated values of first sheet. In the exported file, the formula was not getting evaluated unless and until the cell was activated with the enter key. This is a known limitation, and a temporary solution has been made here to add parameters that force the formula evaluations on the saved Excel document when editing is turned on. A more complete solution will be included in the next patch release.
INC-151669 · Issue 618041
Formulas corrected for GenerateExcelFile
Resolved in Pega Version 8.5.3
After upgrade, using pxGenerateExcelFile to generate an Excel file resulted in some formulas and values not displaying. This scenario used an Excel template with two tabs - one showing direct page values and the second displaying the calculated values of first sheet. In the exported file, the formula was not getting evaluated unless and until the cell was activated with the enter key. This is a known limitation, and a temporary solution has been made here to add parameters that force the formula evaluations on the saved Excel document when editing is turned on. A more complete solution will be included in the next patch release.
INC-151662 · Issue 626578
Handling added for application which includes production ruleset
Resolved in Pega Version 8.5.3
When creating the Email channel or Webchat channel, the Text Analyzer and its respective class (Data-Decision-Request-MCP-WebChat-xxxxx) was being saved in the ruleset of the built-on application while there were rulesets open in the top application. This was a missed use case, and has been resolved by updating the logic to account for the scenario where an application includes a production ruleset.
INC-141895 · Issue 601985
Options not cached by default for picker controls
Resolved in Pega Version 8.4.4
Properties created in the data model of the case type were not showing in the drop down of custom conditions in a decision step. The property did not appear on the left hand side 'when' rule of the case designer in App Studio or Dev Studio, but did appear on the right hand side of the same 'when' rule. The issue temporarily resolved when the context class parameter was hardcoded with the class name. This was traced to the properties being cached by pzInnerEmbedConditions, and has been resolved by unchecking "Enable caching of options" for any picker control.
INC-143820 · Issue 603639
Handling added for App Studio Null pointer exception
Resolved in Pega Version 8.4.4
After adding a property as a relevant record so that it can be used in App Studio development, not all of the properties appeared in App studio. This was traced to an unhandled null pointed exception, and has been resolved.
INC-146424 · Issue 602898
Keyboard users can select DSS records with enter key
Resolved in Pega Version 8.4.4
Keyboard accessible users were not able to select DSS records using the keyboard. This has been resolved by adding the action "Open selected item to the Enter event for the section pzViewInstances.