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-193700 · Issue 685077

Support added for calling Strategy rule from When Rule

Resolved in Pega Version 8.8

An enhancement has been added to support manually referencing Strategy rules in the When rules using Dev studio.

INC-211248 · Issue 713157

Survey navigation type set for use with complex CB refresh

Resolved in Pega Version 8.8

After upgrade from Pega 7.1 to Pega 8.5, creating a legacy survey used in pxSurveySection with a complex CB question page that contained a refresh option had collapsed tree navigation, the survey name was blank, and duplicate labels were found in picklist questions. To resolve this, an update has been added which will set the navigation type in parameters after a complex CB refresh and skip page copy while upgrading survey work objects.

INC-219656 · Issue 717375

Null check added for Application/AccessGroup system pages

Resolved in Pega Version 8.8

In some scenarios the Application/AccessGroup system pages used by the Choose Best RuleSet API to group/cache the user's ruleset could be null, resulting in a null pointer exception when using the pxCreateRecord Activity for the data instance creation. A null check has been added to avoid the exception, and a complete resolution for the null pages will be available in a future release.

INC-218309 · Issue 722157

Helper text added to X icon in Theme Cosmos delegated rules

Resolved in Pega Version 8.8

There was no helper text on the X icon in delegated rules when using Theme-Cosmos. This has been resolved by updating the close icon in Rule-Obj-Class!pzDataTypeActionsnow with the text "Click to close".

INC-209158 · Issue 722414

Loop handling updated for Decision Table OR conditions

Resolved in Pega Version 8.8

The system was crashing when saving or checking in a decision table with 21 columns and 20 rows where each cell contained 1, 2, or 3 OR conditions. Investigation showed this was caused by an indefinite number of loops when 'or' conditions were used in the test consistency activity, and this has been resolved with an update which ensures only the specified number of loops are performed.

INC-220770 · Issue 718026

Null check added to getBaseRef

Resolved in Pega Version 8.8

When using a customized Cosmos portal that included tabs, some of the Pega APIs were not available in the child frame and javascript errors were generated when calculating the clipboard path for live UI elements. This was traced to invalid references to "pega.api.ui.util.getBaseRef", and has been resolved by adding null checks to the getBaseRef API call to make sure javascript errors are not thrown.

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 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-207210 · Issue 704137

Empty check added to OpenRuleAdvanced

Resolved in Pega Version 8.8

A blank screen was displayed when attempting to open a requirement set rule in Dev Studio. This was a missed use case while updating the OpenRuleAdvanced control to handle BAC compatibility, and has been resolved by adding an empty check in addition to the existing null check along with an 'if' condition to check for pyActivity input.

INC-227714 · Issue 730395

Empty check added to OpenRuleAdvanced

Resolved in Pega Version 8.8

A blank screen was displayed when attempting to open a requirement set rule in Dev Studio. This was a missed use case while updating the OpenRuleAdvanced control to handle BAC compatibility, and has been resolved by adding an empty check in addition to the existing null check along with an 'if' condition to check for pyActivity input.

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