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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-122618 · Issue 185154

SetNewReportColumn now defaults to 20px

Resolved in Pega Version 7.1.8

No nominal column width was assigned to new columns added to a report. If the other columns in the report had an assigned cumulative width that exceeded the width of the browser window, the added column was not visible or selectable either in the Report Editor or in the Report viewer. The added column behaved as if it had zero width. To resolve this, SetNewReportColumn has been modified with a default of FieldWidth as 20 and FieldWidthUnit as px.

SR-122619 · Issue 188285

Ensured Excel reports contain fresh data

Resolved in Pega Version 7.1.8

A sporadic issue was found when running multiple reports and exporting them to Excel where new reports sometimes contained data from previously exported results. This was found to be an issue with stale data being left on the TmpExportResultsPageOrig because this page was not listed in the Page-Remove at the end of the RDExportWrapper activity. This has been corrected.

SR-122637 · Issue 183016

MaxFileLength property added to avoid truncating attachment names

Resolved in Pega Version 7.1.8

While adding the attachments to the case using drag and drop functionality, the file name and file description were being truncated. However, a new property named "pyMaxFileLength" is now available as an override in pyDefault Model to set a different name limit. If this property is not set, it will take the default value of 60 and proceed. Also for UI error messages, pyNote property in Data-WorkAttach-File and Embed-DragDropFile in the application ruleset must have the max length limitation removed from there or the MaxFileLength will be overridden by that setting.

SR-122641 · Issue 182813

Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.8

Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.

SR-122641 · Issue 181600

Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.8

Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.

SR-122660 · Issue 185609

Corrected button label issue

Resolved in Pega Version 7.1.8

A button label configured as "&Cancel" was not displaying correctly due to the label being double-encoded in the generatebutton RUF. This has been corrected.

SR-122670 · Issue 182261

Attach a file' modal dialog dropdown now displays Label instead of RuleName

Resolved in Pega Version 7.1.8

In the "Attach a file" modal dialog, the file category dropdown recently changed from DynamicSelect control to Dropdown control. As a result, the dropdown displayed the rule name instead of its label, which was unexpected. To remedy this, the 'Property for display text' of the Category drop down field for the rulesets has been updated to display 'pyLabel'.

SR-122689 · Issue 183471

Corrected display issue for tabbed Summary View charts

Resolved in Pega Version 7.1.8

When using Summary View charts in a Tabbed Section, the chart loaded correctly on the first viewing. However, on moving to a different tab and coming back to the same tab again, the Summary View was getting distorted (elongated). There was a local workaround on using RefreshWhenActive, but this has been resolved.

SR-122689 · Issue 183713

Corrected display issue for tabbed Summary View charts

Resolved in Pega Version 7.1.8

When using Summary View charts in a Tabbed Section, the chart loaded correctly on the first viewing. However, on moving to a different tab and coming back to the same tab again, the Summary View was getting distorted (elongated). There was a local workaround on using RefreshWhenActive, but this has been resolved.

SR-122732 · Issue 182663

Cleaned up error logging for Oracle split schema multi-tenant upgrade

Resolved in Pega Version 7.1.8

When upgrading a multi-tenant environment with an Oracle split schema database, the log file was filling with warning messages on all tenant IDs during Rules upgrade. While errors are expected if there are tenants in the database that are no longer valid, the failure to resolve the tenant ID was being reported twice. In order to smooth the upgrade process, the log messages in this environment have been changed from warnForced to info, and each error will only be logged once.

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