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-127392 · Issue 574288

Delegated Decision table rule grid loads in iFrame with SSO

Resolved in Pega Version 8.4.3

The delegated decision table rule grid and checkout options were not displayed when launched from iFrame using SSO sign in. Without SSO, the delegated decision table grids were loading properly for the same Access group. The heart of this issue was that decision tables were using an older style of Designer Studio javascript which was not designed to be embedded in an iFrame due to issues related to Cross-Origin Resource Sharing (CORS). In order to support the usecase of the Pega end user portal/application being integrated to an external domain application using an iFrame, enhancements have been made to the necessary delegated rule function definitions.

INC-132517 · Issue 578984

Correct manager name retained for skill-based routing updates

Resolved in Pega Version 8.4.3

In App Studio, having a manager update a team member's skills changed that team member's reporting Manager name (.pyReportTo) upon save. This was a use case where multiple operator IDs were required for the same person (name and email), so that using the report definition parameter 'BestOperatorValue' for the pzUpdateOperatorInfo activity caused an incorrect manager name to be set to the team member's operator ID. This has been resolved.

INC-128811 · Issue 569283

Operator created with save-as has correct application access

Resolved in Pega Version 8.4.3

Creating an operator using Save As retained access to the applications of the original operator even if they were removed in the creation process. This was due to the saveAs operation of the Operator not retaining consistency between the records in the ValueList pyAccessGroupsAdditional and the page list pyaccessgroups_opid. To resolve this, the PreSaveAs of the Operator ID has been updated to maintain consistency in the records.

INC-129275 · Issue 577018

Resolved errors when refreshing test case

Resolved in Pega Version 8.4.3

On refreshing any test case for decision tables, a "rule no longer exists" error appeared on screen and a pzRuleNotFound exception was generated for all testcases in tracer. This was traced to Rule-Utility-Function lookup parameter handling in the pzGetFreshLabelForRUT decision table: because the Rule-Utility-Function was not able to fetch the label and the caller step in an activity, it was ending with a fail status and generating the errors. This has been resolved by correcting the Rule-Utility-Function calls in the decision table pzGetFreshLabelForRUT to ensure it has the correct parameters.

INC-135095 · Issue 581847

Tracer toolbar shows correctly in IE

Resolved in Pega Version 8.4.3

After upgrade, the developer toolbar for the tracer pop up was not visible in Internet Explorer. Investigation showed that Microsoft Internet Explorer was loading the correct elements, but they were not displaying due to recent updates made to prevent Cross-site scripting vulnerabilities for the tracer. This has been resolved.

INC-135266 · Issue 584589

Cross-site scripting protections updated

Resolved in Pega Version 8.4.3

Cross-site scripting filtering has been added to IDs related to login.

INC-136969 · Issue 585545

Section and Paragraph rule types added to Revision Manager

Resolved in Pega Version 8.4.3

An enhancement has been made to add support for section and paragraph rule types in revision management. With this change, the sections and paragraph rule types can be added to overlay and can be added to change requests and modified.

INC-126942 · Issue 583397

Report Shortcuts resolve datapage parameter references

Resolved in Pega Version 8.4.3

After upgrade, no results were displayed in case manager portal report browser. This was traced to a data page value that was not resolved at runtime when a data page was used in the report definition shortcut to pass a parameter value. Investigation showed this was due to a change made for v8.4 to correct an issue with data page variables that were not persisting if a report was made with pre-exisiting filters. To resolve this, the logic related to pzResolveCopyFilters has been updated.

INC-128880 · Issue 592814

Handling added for angle brackets in legacy Chart control

Resolved in Pega Version 8.4.3

When using Investigative Case Management, some report charts were not rendering correctly. This has been resolved by updating appendFormattedString in to escape angled brackets (< and >) before appending the input.

INC-131942 · Issue 574324

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.4.3

An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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