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.

SR-128081 · Issue 193016

Session Timer / Log Off corrected

Resolved in Pega Version 7.1.8

After upgrade, the Session Timer control was not working correctly when created as a script in the section and then embedded in a portal harness. In ML7, the usage of window.showModalDialog was altered because Google Chrome and Firefox no longer support it. This included modifying the desktop app TimeoutLogoffDialog to use a modal dialog, but a syntax error was introduced in oSafeURL; correcting this resolved the display issue with the timeout dialog. In addition, the LogOffTimer has been modified to use the updated windows.close() function and pxSessionTimer has been marked as available.

SR-123686 · Issue 184976

Properly resolved HTML tags in ListView

Resolved in Pega Version 7.1.8

If any HTML tags such as were used inside the Full Description of ListView, the tags are were not being resolved and were instead displayed as-is. This was caused by how the XSS filter affected the way the tags were reference when returned to the browser, and has been fixed.

SR-123911 · Issue 189019

Changed timing for retrieving autocomplete values after modifications

Resolved in Pega Version 7.1.8

When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.

SR-123911 · Issue 192195

Changed timing for retrieving autocomplete values after modifications

Resolved in Pega Version 7.1.8

When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.

SR-128171 · Issue 196940

Drill down corrected for leaf node in RD summary report

Resolved in Pega Version 7.1.8

When a summary type report definition as used to source a tree grid, double-clicking a leaf node in the tree did not open the associated detailed view from the report definition. This was traced to a missing null check for the clipboard in the drill down activity, and has been resolved.

SR-124477 · Issue 187138

Logic updated for Ruleset Refactor - Merging Ruleset

Resolved in Pega Version 7.1.8

When using the rule set refactor wizard to merge the rule set from lower version to higher version, the wizard did not show the rules in the source rule set on the second screen (Rules Impacted are "0") which had a number of rule conflicts. In addition, the error "StringIndexOutOfBoundsException" was logged. This was caused by the RuleSetMaintImpl buildRuleSetInventory method not filtering out data instances correctly, causing errors when trying to validate a Data instance as a rule. This has been corrected.

INC-138309 · Issue 591150

Added busy state reset to reenable buttons after custom frame cancel

Resolved in Pega Version 8.3.5

When using a custom iFrame in a section that called a third-party URL, clicking on cancel for the popup "Do you want to stay on this page or leave it?" caused the screen to freeze. This was traced to the cancellation of the dirty page setting a busy state which disabled all the buttons and did not have a path to recovery. This has been resolved by updating the busy state so it will reset when the user chooses to cancel the changes and reenable all the buttons.

INC-145119 · Issue 601712

Client side validation works with Reference page property

Resolved in Pega Version 8.3.5

A reference page property in a 'when' rule was not evaluating properly for checking a Date field when client side validation or Client side template UI was checked on the Harness level. This was traced to pyRequired being boolean: the boolean being compared to a string false value yielded a wrong comparison, leading to the wrong validation type required. To resolve this, the system will use the === comparator to compare boolean false in datetime to remove the required validator.

SR-128220 · Issue 195539

Screen layout options now visible before saving a new harness

Resolved in Pega Version 7.1.8

When using a screenlayout in a harness, the options for defining the properties were not displayed. This was due to changes made to replace panel sets with screen layouts in this area, and was only an issue if the harness had not been saved yet. In order to facilitate development, these options will now also be present before saving.

SR-128320 · Issue 193581

Updated chart export handling for Safari

Resolved in Pega Version 7.1.8

The charts in reports are getting disappeared on click of When using the Safari browser, clicking on Export to Excel/Export to PDF caused the charts in reports to disappear. This was traced to the form target being blanked in the browser handling, and a browser check has been added to invoke special handling for Safari..

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