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-116300 · Issue 169067

Added display expansion capabilities for accessibility mode

Resolved in Pega Version 7.1.7

Previously, expanding displays with "+" in the listview category headers required a mouse click. An enhancement has been added to additionally allow use of the enter key at this location to expand and display the attachments of that category type (Notes, Files, Emails, etc.).

SR-116347 · Issue 166799

Error resolved for adding Stage Step Specifications using RTE and Google Chrome

Resolved in Pega Version 7.1.7

While configuring a stage behavior in Google Chrome, if a user had focus within the Rich Text Editor for a specification and submitted the modal, an error was generated. This was caused by an invalid post-value check, and the unnecessary post value has been removed.

SR-116479 · Issue 170952

Elapsed Time reporting corrected

Resolved in Pega Version 7.1.7

Two out-of-the-box reports, Elapsed Status Time Trend and Average Elapsed Time Per Status, were causing the browser to freeze and stop responding if there were more than 1000 records. This was caused by an invalid value for the datetime units on the category for the chart causing looping behavior. This has been corrected.

SR-116587 · Issue 170222

Clarified default values for Create Class

Resolved in Pega Version 7.1.7

The Create Class screen was offering default values that had the potential to lead to classes being created in an incorrect / invalid part of the Class Structure. This has been corrected.

SR-116597 · Issue 169929

Correct report name displaying on chart reports

Resolved in Pega Version 7.1.7

In Case Manager reports, maximizing a report containing a chart showed the URL as the report name if the report title parameter did not have a value. This field has been updated to default to the report's title if the name has not been explicitly set.

SR-116661 · Issue 169635

TrackSecurityChanges enhanced to capture index information

Resolved in Pega Version 7.1.7

While the properties of a pagelist are displayed in the TrackSecurityChanges history tab, the corresponding index of what was changed on the page list was not included. In order to more accurately track what is being changed, an enhancement was added with new field values for tracking the index history.

SR-116679 · Issue 169078

"Save preferences" button visibility corrected

Resolved in Pega Version 7.1.7

The ability to save report filtering preferences for Summary View was only appearing if the report included an interactive chart. The system has been updated to present the 'Save Preferences' button in all report types.

SR-116769 · Issue 174513

Case narrative ordering enhanced

Resolved in Pega Version 7.1.7

The Case Narrative ordering appeared incorrectly when the events are very close together (multiple events within the same second), though the History items displayed in the correct and expected order. When more than one event occurred within the same second, the DATE datatype did not provide a lower level of distinction to allow more granular sorting or ordering. To resolve this, the time value for sorting is now extracted from InsKey.

SR-116893 · Issue 169075

Corrected browser display errors for large decision tables

Resolved in Pega Version 7.1.7

A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.

SR-117937 · Issue 173922

Corrected browser display errors for large decision tables

Resolved in Pega Version 7.1.7

A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.

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