INC-174435 · Issue 659478
Survey Complex Question Definition properly displayed
Resolved in Pega Version 8.7
Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab".
INC-150845 · Issue 606354
OpenRule logic updated for GetRuleInfo
Resolved in Pega Version 8.4.4
The exception "InsufficientPrivileges:RuleExecutionDenied RULE-OBJ-ACTIVITY @BASECLASS PZGETRULEINFO" was thrown for some access groups when attempting to view a section from the end-user perspective on the Opportunity screen. Investigation showed this happened when a section had a table in which "Optimize code" was unchecked. If "Optimize code" was checked, then the exception was not thrown. This was traced to recent security changes in pzGetRuleInfo which affected the BAC registration process, and has been resolved by updating the way the openRule action registration logic invokes the activity.
INC-220385 · Issue 720008
Corrected Branch Code Score / Unit Test Rule count issue
Resolved in Pega Version 8.8
When reviewing branch quality, the "Rules with Test Cases" indicated 5 out of 7 rules were covered, but no rules were listed in the "rules without unit tests" tab and all rules within the branch had unit tests where applicable. Investigation showed the filter for withdrawn rules was not working correctly and they were shown as not having test cases. In addition, when a test case was in a branch but its tested rule was not in the branch, the test pass percentage calculation was being skipped and displayed as 0%. These issues have been corrected.
SR-B2228 · Issue 273457
WordTextArea control updated for IE
Resolved in Pega Version 7.3
Erratic behavior was seen in saving and displaying a Word document when launched from the WordTextArea control. This was a compatibility issue with IE, and the DoLaunchExtWord function has been modified to fix this.
INC-182248 · Issue 665781
Added logic to handle manual validate rule creation
Resolved in Pega Version 8.7
Manually creating a Validate rule with conditions and then opening the configure view with conditions caused the validation rule to be removed from the flow action rule along with the validation conditions in the validation rule referred in flowAction rule. This has been resolved by updating the logic in the Condition Builder to handle this use case.
INC-189511 · Issue 679184
Column width adjusted for Survey simple question text area
Resolved in Pega Version 8.7
When a number of columns were entered in a simple question (Answer tab) for a text area, the width was not reduced or increased for the text area. This has been resolved by setting pySpecifyWidth to custom for textarea.
INC-189933 · Issue 677798
Corrected deleting a ruleset with the refactor wizard
Resolved in Pega Version 8.7
In the case of Access Whens applied for the modification and deletion of any rule and data instance, the haveAccess() function was executed on a null page and resulted in a PRRuntimeError that caused Ruleset refactor to fail. This has been resolved.
SR-B45093 · Issue 301258
Fixed invalid reference for auto-populate
Resolved in Pega Version 7.3
An invalid reference exception was generated while trying to do Property-Ref on two properties inside Auto populate. This was caused by a coding error in a check used to avoid doing a getSourceProperty in case of a reference to a top level page, and has been fixed by modifying the setAsReference API in ClipboardProperty to gracefully handle Autopopulate scenarios.
SR-B8793 · Issue 278410
Flow warnings show consistently
Resolved in Pega Version 7.3
Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages
SR-B8793 · Issue 278405
Flow warnings show consistently
Resolved in Pega Version 7.3
Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages