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-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.

SR-132569 · Issue 201349

Corrected portal refresh after chart unload

Resolved in Pega Version 7.1.8

When a chart is unloaded, a separate request was sent to the server to remove all chart-bounded data pages, i.e. pzRuntimeChartCleanup. If nothing is returned, the ActivityStatusSuccess Message was seen instead of the Work Item when the portal was refreshed. The API has been updated to return the correct information.

SR-128463 · Issue 193907

Create KeyRing updated for split schema

Resolved in Pega Version 7.1.8

If a command line script is configured (viz. keyringGen.sh) to encrypt user passwords for prconfig.xml databases using Keyring utility, a prconfig.xml could have three database entries but the keyring tool only prompted for two databases and did not allow encrypting password for the user for the third database. The prconfig.xml file requires very specific location information to run: to resolve this, the variables to hold schema name in case of split schema configuration have been added.

SR-113149 · Issue 168421

Ensured tabbed section refresh for new sessions

Resolved in Pega Version 7.1.7

When a new session had only 2 tab groups configured with dynamic container, the first tabbed section refresh was not working as expected. This was caused by a missing null check, and has been corrected.

SR-113431 · Issue 161621

Corrected use of Navigation URLs in Detailed view

Resolved in Pega Version 7.1.7

The detailed view drilldown from a summary view was not passing the correct set of filters down to the server when the breadcrumb trail link was clicked, causing any included Navigation URLs to fail. There was a workaround of using list view in place of detailed view, but the HTML has been updated to pass the proper parameters to the activity and show the correct information.

SR-113624 · Issue 167070

Enabling out-of-the-box Security Policies now redirects immediately

Resolved in Pega Version 7.1.7

When enabling out-of-the-box Security Policies, it was not immediately redirecting to the change password screen but instead requiring the timeout interval to expire before redirect happened. This has been corrected.

SR-115133 · Issue 166141

Localization added for column section summaries in Report Definition

Resolved in Pega Version 7.1.7

The summarize column section displayed while running the Report Definition now accepts localization.

SR-115308 · Issue 173906

Japanese character support added to Report Definition PDFs

Resolved in Pega Version 7.1.7

When Report Definition contains Japanese characters in its report name, column, value, etc., the exported PDF was not showing the Japanese characters incorrectly. This was due to a missing font-family for the PDF export mode, and has been corrected.

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