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-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-131199 · Issue 201548

Smoothed editing of data tables mapped to external DB

Resolved in Pega Version 7.1.8

It was not possible to edit a data table mapped to an external database table with column name different from that of the property. To resolve this, the system will ensure that the external mappings take precedence while trying to update the data table.

SR-131266 · Issue 199637

Cleared exception during import of RAP by prpcUtils

Resolved in Pega Version 7.1.8

When attempting to import a RAP file through command line by using prpcUtils.sh, the build was successful and all the rules were imported but an SQL exception was generated related to the execution of Stored Procedure. The RAP file did not contain any code to execute stored procedure, so the execution was found to have been done internally by prpcUtils.sh. To prevent this, prpcUtils has been updated to use the data schema as the default schema for the connection while running against either of the DB2 dbs.

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-131347 · Issue 198661

Changed Dependency Checker table-based cataloging to be case insensitive

Resolved in Pega Version 7.1.8

After updating, the Dependency Checker and Packager functions for v5 items in the table-base catalog features were not finding existing cataloged items that contained mixed case IDs. To resolve this, the dependency checking code has been modified to be case insensitive.

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