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-143193 · Issue 595940

Handling added for UI overlap issue

Resolved in Pega Version 8.5.2

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-146424 · Issue 602896

Keyboard users can select DSS records with enter key

Resolved in Pega Version 8.5.2

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-149728 · Issue 608105

Application wizard security updated

Resolved in Pega Version 8.5.2

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 608042

Adjusted validation of literal value of a parameter

Resolved in Pega Version 8.5.2

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 606342

OpenRule logic updated for GetRuleInfo

Resolved in Pega Version 8.5.2

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.

INC-200802 · Issue 699967

Line break handling added for setting required question asterisk

Resolved in Pega Version 8.6.4

If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.

INC-177312 · Issue 692111

Added handling for FieldValue issue during Excel export

Resolved in Pega Version 8.6.4

After upgrade from Pega 7 to Pega 8, the export to Excel function for business-rules kept and maintained via Decision-Tables created a file that Excel could not open. This was traced to a function call in the Results tab and the Return Actions in the decision table which caused an issue with the generated Excel to be used for editing. To resolve this, any allowed values will have quotation marks removed before the vales are passed to the export.

INC-194330 · Issue 708710

Added special character handling for DecisionTable column-label

Resolved in Pega Version 8.6.4

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-195790 · Issue 687810

Updated recording test scenario for attachments

Resolved in Pega Version 8.6.4

Recording scenario tests for a case type was not working as expected when attaching a document to a case as part of case flow. This has been resolved as part of the updates made for Pega Test Automation Kit (PTAK) v1.6.

INC-195793 · Issue 697921

Enhanced ruleset validation for portal creation

Resolved in Pega Version 8.6.4

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.

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