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-141296 · Issue 592473

Log-access security updated

Resolved in Pega Version 8.6

Access control has been updated for Log-Usage class.

INC-142223 · Issue 598646

Handling added for new case type using reuse case life cycle

Resolved in Pega Version 8.6

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 604015

Cross site scripting update

Resolved in Pega Version 8.6

Cross site scripting protections have been updated in Designer Studio.

INC-143193 · Issue 595939

Handling added for UI overlap issue

Resolved in Pega Version 8.6

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-146098 · Issue 607792

Keyboard shortcuts work in Decision Trees

Resolved in Pega Version 8.6

Keyboard short cuts in Decision Trees used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.

INC-146424 · Issue 602897

Keyboard users can select DSS records with enter key

Resolved in Pega Version 8.6

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-148458 · Issue 623779

docx4j libraries updated

Resolved in Pega Version 8.6

After performing a Microsoft Word merge with a Word template, the error “Word found unreadable content in….” appeared while opening the Word document. This was traced to the older versions of docx4j not handling the latest Microsoft Word features, and has been resolved by upgrading the docx4j and related jars.

INC-148853 · Issue 609317

Corrected password comparison handling for CopyMerge Ruleset Wizard

Resolved in Pega Version 8.6

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 608106

Application wizard security updated

Resolved in Pega Version 8.6

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 608043

Adjusted validation of literal value of a parameter

Resolved in Pega Version 8.6

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.

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