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.

INC-132590 · Issue 590491

Exported Excel from Decision Table wraps correctly

Resolved in Pega Version 8.4.4

After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (

INC-140789 · Issue 597799

Added handling for validation after inactivity

Resolved in Pega Version 8.4.4

A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.

INC-141895 · Issue 601985

Options not cached by default for picker controls

Resolved in Pega Version 8.4.4

Properties created in the data model of the case type were not showing in the drop down of custom conditions in a decision step. The property did not appear on the left hand side 'when' rule of the case designer in App Studio or Dev Studio, but did appear on the right hand side of the same 'when' rule. The issue temporarily resolved when the context class parameter was hardcoded with the class name. This was traced to the properties being cached by pzInnerEmbedConditions, and has been resolved by unchecking "Enable caching of options" for any picker control.

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.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us