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-129597 · Issue 199328

Added handling for newline character in mail subject line

Resolved in Pega Version 7.1.8

A NPE was being generated by SafeURL if there was a newline character in the subject line of an attached email. The code has been updated to remove the newline characters from the subject and unfold the subject to one line.

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-129898 · Issue 197990

Error handling added for ConnectJava wizard

Resolved in Pega Version 7.1.8

A null check has been added to resolve a null pointer error generated by the Connect-Java Wizard -> GenerateJPForConnect.

SR-129955 · Issue 199160

Extraneous 'save changes' popup removed from PDF viewer

Resolved in Pega Version 7.1.8

A popup asking "Do you want to save changes to pdf before closing" was appearing when closing an unmodified PDF generated from PRPC using the concatenateEforms feature. This was caused by an unneeded appearance setting, which has been removed.

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-130796 · Issue 197804

Enabled restore of persisted Application requestors

Resolved in Pega Version 7.1.8

Prior to this change, service requestors could not be restored from their passivated state because of a code change introduced in PRPC 5.4. This was generally not a problem for most customers, as service requestors tend to be stateless and short-lived. Stateful, long-lived service requestors such as Verizon do need to be restored to their previous state, however. This change retracts the prior fix that prevented that from occurring.

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