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-131124 · Issue 199831

Added enter key access to expand pane

Resolved in Pega Version 7.1.8

The expand pane icon in repeat grid was not accessible through enter key. This has been fixed.

SR-131136 · Issue 199333

Localization added for modal dialog alert boxes

Resolved in Pega Version 7.1.8

Localization has been added for modal dialog alert boxes.

SR-131176 · Issue 200691

Special character handling added to ShowHarness

Resolved in Pega Version 7.1.8

Previously, support was added to Decisioning -> Monitoring -> Adaptive Models Reporting for propositions beginning with special characters. An additional use case has been added to support the same in the activity 'uiactiondisplayharness' for ShowHarness.

SR-131238 · Issue 199372

Corrected dual configuration OpenURL in New Window function

Resolved in Pega Version 7.1.8

If a button configured to open a URL in a new window specified both a data transform and an activity in the configuration, it did not work. If only the activity was specified, the behavior was as expected. This was a problem where escape characters were missing when building markup for data transform parameters, and has been fixed.

SR-131257 · Issue 201800

Set proper gradient inheritance for Microsoft Internet Explorer tabs

Resolved in Pega Version 7.1.8

A skin rule applied on application to apply style on tabs should have shown the active tab with a white background and the inactive tabs should have had a gradient applied on them, but at run time when using the Microsoft Internet Explorer browser the gradient was applied on all the tabs irrespective of the state. The code has now been updated for this browser to prevent accidently inheriting a gradient from parent tabs

SR-131430 · Issue 200005

Resolved error from empty repeating grid

Resolved in Pega Version 7.1.8

If a repeating grid is opened and no rows are added, the Microsoft Internet Explorer 8 browser was generating an error. When the grid is collapsed in the header its dimension parameters such as offsetHeight etc. are zero, so certain calculations in setHeadersWidth function in ui_grid js would fail and wrong dimension values would be assigned to the grid. Other browsers were failing silently in this situation, while Microsoft Internet Explorer 8 showed errors. To avoid any failure, a check has been added to the setHeadersWidth function in ui_grid js.

SR-131470 · Issue 200524

FilePath control refresh set on change

Resolved in Pega Version 7.1.8

The first time a file attachment was browsed in the Google Chrome popup window, the subject name showed up correctly. However, browsing another file did not refresh the subject name and the first file's subject name was still displayed. This was an error in the update logic where the control FilePath had a check such that if the value was already set, it would not set it again. This has been modified to update whenever there is a change in file path.

SR-131504 · Issue 200712

Localization added for 'save' label in Calendar popup

Resolved in Pega Version 7.1.8

The label 'Save' in the Calendar popup has been made available for localization.

SR-131600 · Issue 199942

Modified Accordion display of alerts

Resolved in Pega Version 7.1.8

Validation messages in a section with accordion and UI elements were overlapping with Accordions below. This has been corrected by modifying the script to include the alert message.

SR-131611 · Issue 201761

Currency field 'save draft' function updated

Resolved in Pega Version 7.1.8

Save Draft button when pressed caused a screen error for currency fields, identifying that they were not the proper "decimal value", though the actual flow worked as expected. This was caused by the Save Draft function passing the value in string format instead of decimal, and the API has bene updated to update the value to a number.

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