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-123313 · Issue 185096

Drilldowns fixed for reports containing text values

Resolved in Pega Version 7.1.8

In Summary view reports, Onclick functionality to open the drilldown report is not working for the non numeric values. This was an issue with the SummaryViewBodyTag.java not properly handling quotes around database values, and the code has been modified.

SR-123430 · Issue 185464

Right-click info calls corrected for tabs

Resolved in Pega Version 7.1.8

Calling an activity under "Right Click Smart Info Settings" section in Format tab in list view rule was not working properly. This was an issue with the smartinfo code when mousing out from the row, and has been fixed.

SR-123636 · Issue 184161

Trojan horse protection auto-enabled

Resolved in Pega Version 7.1.8

The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.

SR-123636 · Issue 181701

Trojan horse protection auto-enabled

Resolved in Pega Version 7.1.8

The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.

SR-123686 · Issue 184976

Properly resolved HTML tags in ListView

Resolved in Pega Version 7.1.8

If any HTML tags such as were used inside the Full Description of ListView, the tags are were not being resolved and were instead displayed as-is. This was caused by how the XSS filter affected the way the tags were reference when returned to the browser, and has been fixed.

SR-123809 · Issue 185686

Report schedule icon display fixed for SQL

Resolved in Pega Version 7.1.8

When disabling then re-enabling the task for a scheduled report through the report browser, the icon that indicates whether the report is scheduled will sometimes not show. That is, the report is actually scheduled, and will run at the appointed time, but there will be no icon in the report browser to show that it is scheduled. The SQL query to retrieve the list of scheduled reports was being generated incorrectly for certain databases (e.g., MS SQLServer). Therefore the rescheduled reports were omitted from the list, and no icon would be displayed for them. To resolve this, the custom getcontent activity 'pxgetRRContentForRB' has been inserted.

SR-123820 · Issue 185192

Fixed truncated custom datetime in RD

Resolved in Pega Version 7.1.8

If a report was created on work objects that used a property of type DateTime in Report definition output, custom datetime settings were truncated. This was a problem with the grid implementation where the modified GenerateGridHTML. "D" was set always to propTypeForFormatting even for DateTime. It has bene fixed.

SR-123911 · Issue 189019

Changed timing for retrieving autocomplete values after modifications

Resolved in Pega Version 7.1.8

When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.

SR-123911 · Issue 192195

Changed timing for retrieving autocomplete values after modifications

Resolved in Pega Version 7.1.8

When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.

SR-123960 · Issue 184251

Error message updated for report 'save as'

Resolved in Pega Version 7.1.8

The error message created when doing a 'Save As' report to a private category has been updated for clarity. Previously, the error generated was "The name you entered is not valid". This has been changed to "The name should start with letter followed by letter or digit or underscore".

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