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-129733 · Issue 199324

Enabled word wrap for RD export to PDF

Resolved in Pega Version 7.1.8

After export to PDF from RD, values were getting truncated or being displayed under the column and the column alignment was disrupted. Word wrap has been enabled to fix this display issue.

SR-128430 · Issue 194956

Pagination removed from OwnersList to facilitate large category lists

Resolved in Pega Version 7.1.8

After having created a large number of categories from the "Reporting" landing page, the list of available owners was not the expected one when creating a new shortcut. The owner drop down list is generated by the ListView called "Rule-Category.pzGetCategoryOwnersList." Unfortunately this ListView is a FINAL rule and paging was enabled with a default count of 50 entries. In order to allow for customizations like the above, OwnersList has been modified to disable paging.

SR-128696 · Issue 195043

Fixed alignment of columns and headers in RD scroll headers setting

Resolved in Pega Version 7.1.8

If "Do not scroll header" was checked in Report Definition, there was an alignment issue with the header and report Data. This has been fixed by updating "GenerateCellContent" to generate the CSS classes in the markup, and the CSS style was added to "pyReportEditorStyling" and is commented to make it available there if desired.

SR-130224 · Issue 200002

Fixed class pickup when Ticket Urgency is used as reference

Resolved in Pega Version 7.1.8

It was not possible to convert a summary report to a list report if the report had Ticket.Urgency as a reference and Ticket was a single page pointing to data class type property in the work class. This was traced to the drill down picking up the Urgency property from the work class, and has been resolved.

SR-130401 · Issue 201418

Fixed listview filtering header shift

Resolved in Pega Version 7.1.8

When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.

SR-130401 · Issue 200029

Fixed listview filtering header shift

Resolved in Pega Version 7.1.8

When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.

SR-131323 · Issue 201113

RD operator filter max value increased

Resolved in Pega Version 7.1.8

The limit for items displayed by the RD filter pxCreateOperator has been increased to 1000.

SR-131522 · Issue 200840

Localization added for report name tooltips

Resolved in Pega Version 7.1.8

Tooltips in reports for report names are now available for localization.

SR-131538 · Issue 200108

Removed extra blank line from exported SV report

Resolved in Pega Version 7.1.8

An Excel spreadsheet exported from any Summary View (SV) report contained a blank row at the top. This has been corrected.

SR-132135 · Issue 202410

Smoothed 'save as' for private reports without checkout privs

Resolved in Pega Version 7.1.8

When a user did not have checkout option either at the operator level or at the design time rule-set level, trying to use 'Save As' on Report definition rules reports in Private category resulted in an error but actually saved the report at the back end. Opening the Case Manager portal and trying to do a 'save as' of an existing report led to the report category being populated as private but the standard categories got populated in the drop down. If OK was clicked, then the standard categories were replaced with private category. To improve this, a check has been added to detect a non-developer operator, who is then allowed to save in their personal category.

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