Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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".

SR-A7996 · Issue 219733

Fixed handling for updating decision trees

Resolved in Pega Version 7.2

A Decision Table was inconsistently updated when adding or deleting columns due to an error in the conditional handling for the decision tree that fetched the list of function aliases. This has been fixed.

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-A12056 · Issue 223829

Removed paging limit on pxGetDefinitionsForTemplate

Resolved in Pega Version 7.2

In installations having more than 50 circumstance definitions associated with a number of section rules, using pxGetDefinitionsForTemplate in the report definition caused only the first 50 definitions to be visible. pxGetDefinitionsForTemplate was a final rule with a max page size of 50, and this paging limit has now been removed.

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.

SR-A3950 · Issue 209476

Corrected order of tabbing focus in Activity rules

Resolved in Pega Version 7.2

After opening an Activity rule, the Description text field did not receive focus at the expected point when tabbing through the steps. The activity steps have been rebuilt to correct the tabbing order.

SR-A8075 · Issue 217226

Resolved NPE for large cache Factory Report generations

Resolved in Pega Version 7.2

When generating Factory reports from SMA, an exception was generated if it included a very large Property Reference cache. An enhancement has been added to skip null values and speed processing in these cases.

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-A7750 · Issue 220071

Decision Tree Rule Form shows custom actions

Resolved in Pega Version 7.2

In some installations, values configured in the "Take Actions" or "Actions" dialog were not visible even though they had been configured. The values could be seen in the rule XML and the rules worked as expected. This was traced to the configuration using a custom Function "AddActionRecord" Alias, and a new step has been added to make such values visible.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us