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

INC-143820 · Issue 603639

Handling added for App Studio Null pointer exception

Resolved in Pega Version 8.4.4

After adding a property as a relevant record so that it can be used in App Studio development, not all of the properties appeared in App studio. This was traced to an unhandled null pointed exception, and has been resolved.

INC-146424 · Issue 602898

Keyboard users can select DSS records with enter key

Resolved in Pega Version 8.4.4

Keyboard accessible users were not able to select DSS records using the keyboard. This has been resolved by adding the action "Open selected item to the Enter event for the section pzViewInstances.

INC-148440 · Issue 607335

Guardrails Compliance Score correctly excludes test case rulesets

Resolved in Pega Version 8.4.4

When calculating the compliance score of the Application with the "Ignore test rulesets when calculating Guardrails score" option selected, the test case ruleset was still included in the Guardrail score calculation. This was traced to updates made to the pzGetTestRuleSetsList activity used to get the test rulesets for any application, and was due to the returned data not being correctly updated from a named page back to the primary page. This has been corrected.

INC-148853 · Issue 609318

Corrected password comparison handling for CopyMerge Ruleset Wizard

Resolved in Pega Version 8.4.4

When running the CopyMerge Ruleset Wizard, entering the password failed with the error "pyPassword: Invalid Password for" <Temp:01-01-01> for each ruleset. Investigation showed that the system was calling an activity which encrypted the user input, causing the comparison with the stored password of the system to fail the match. This has been resolved by removing the extra encryption so the call to the comparison evaluates correctly.

INC-149728 · Issue 608107

Application wizard security updated

Resolved in Pega Version 8.4.4

A user having PegaRULES:User1 role only was able to run the Create Application wizard until an authorization block was reached, yet some rules were created. No operator records were created as part of this process. This was traced to code left in place after the creation of pxAppConfig and pzAppConfig portals, and has been resolved. The New Application wizard UI will display a message to a user when they lack access to build a new application, and an error will be displayed for any attempt to create a new application directly via pzCreateNewApplication to address a scenario where a user might be trying to call the activity without the front end.

INC-150039 · Issue 608044

Adjusted validation of literal value of a parameter

Resolved in Pega Version 8.4.4

When mapping a parameterized when rule to the proposition filter, parameters passed from the proposition filter page were not getting flown to the when rule. This was caused by special character validation for a literal value of a parameter which necessitated putting the parameter value within quotes and which resulted in a parameter value mismatch at run time. To support this use, this validation has been disabled as parameter values would not get included within quotes. This change does not have any impact on when rule or proposition filter rules java generation.

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.

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