INC-125803 · Issue 568662
Cross-site scripting updated on activities
Resolved in Pega Version 8.2.8
Additional Cross-site scripting work has been done on activities.
INC-135095 · Issue 581846
Tracer toolbar shows correctly in Microsoft Internet Explorer
Resolved in Pega Version 8.2.8
After upgrade, the developer toolbar for the tracer pop up was not visible in Internet Explorer. Investigation showed that IE was loading the correct elements, but they were not displaying due to recent updates made to prevent Cross-site scripting vulnerabilities for the tracer. This has been resolved.
INC-135349 · Issue 583002
Unit Test Ruleset rules do not count against Guardrails
Resolved in Pega Version 8.2.8
Although the documentation indicates that rules in a Unit Testing ruleset should not count against the guardrail score or unit test coverage, when branching a unit test ruleset, the branch did not carry the same unit test flag value as the source ruleset and the rulesets were counted as a result. This has been resolved with an update to ignore testrulesets in guardrail and pegaunit calculations.
INC-141179 · Issue 591821
Repaired test cases for When rules
Resolved in Pega Version 8.2.8
When running a Pega test case for a When rule, values that were set up before the rule execution on RunRecordPrimaryPage disappeared from this page. This has been resolved by creating the RunRecordPrimaryPage before loading Setup Pages.
INC-132590 · Issue 590491
Exported Excel from Decision Table wraps correctly
Resolved in Pega Version 8.4.4
After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).
INC-140789 · Issue 597799
Added handling for validation after inactivity
Resolved in Pega Version 8.4.4
A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.
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-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-143136 · Issue 604017
Cross-site scripting update
Resolved in Pega Version 8.4.4
Cross-site scripting protections have been updated in Designer Studio.
INC-143193 · Issue 595938
Handling added for UI overlap issue
Resolved in Pega Version 8.4.4
Elements of the window "Test Case Record Configuration" were shifted into one another when the Application name was too long that it overlapped with the other UI Elements. This has been resolved by adding a style sheet with overflow hidden.