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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-191371 · Issue 684481

Security update for GetAssignmentDetailsInternal errors

Resolved in Pega Version 8.8

Error handling for pzGetAssignmentDetailsInternal has been updated to return a 403 (forbidden) HTTP status code in place of potentially sensitive information when access is denied.

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-194330 · Issue 708712

Added special character handling for DecisionTable column-label

Resolved in Pega Version 8.8

The label of a decision-table column was being appended to the original decision-table return-value. The column label and comparator were handled differently for columns containing special characters (+, -, *,...), causing the data after the special character to be trimmed and appended to the row output value. This has been resolved by adding handling for special characters so the output and the label are rendered properly.

INC-195793 · Issue 697920

Enhanced ruleset validation for portal creation

Resolved in Pega Version 8.8

Attempting to create a new portal (web channel) from the app studio using the Creation Wizard with "Branch development preferences" enabled resulted in the error message "No valid rulesets in application preferences". Investigation showed this occurred due to CPM-Portal being specified in the application as the UI class: when attempting to create the portal, the system was evaluating the class against ruleset candidates. The class was not visible to the rulesets in the stack and thus the portal could not be created. This has been resolved by adding validation on UI pages, Int and Data classes in the application to ensure that they exist in user rulesets, and by adding an allowance for classes to exist only in branched rulesets and not the base ruleset during check if the ruleset is present in application stack.

INC-202249 · Issue 693323

Corrected doubled ampersand passed to message rule

Resolved in Pega Version 8.8

In drop down the ampersand "&" symbol was displayed correctly, but passing that value as a parameter to a message rule used in the page-set-messages method doubled the "&" symbol. This has been resolved.

INC-205666 · Issue 702935

Database table correctly prevents deletion if there are descendant classes

Resolved in Pega Version 8.8

When deleting a concrete class with descendant classes via an activity (Rule-.Delete), the Rule-Obj-Class.ValidateDeleteInternal activity was throwing an error message indicating the class could not be deleted due to descendant classes. However, the corresponding database table rule was deleted anyway. Investigation showed this was caused by ValidateDeleteInternal not reaching the Obj-Save-Cancel step. This can be fixed by modifying step 11, the post when conditions, to jump to END and set the END label at the Obj-Save-Cancel step instead Exit-Activity, but this issues has been resolved by updating all failure states to run end step. In addition, security has been updated to disallow "Allow invocation from browser".

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-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-209426 · Issue 706803

GetFunctionsForLibrary retrieves 10,000 rows

Resolved in Pega Version 8.8

Some functions were missing from the expression builder browser and search results when pyShowInternalLibrary was set to true for including internal functions in the results. To resolve this, the default value for "Maximum number of rows to retrieve" in pzGetFunctionsForLibrary has been increased to 10,000.

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.

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