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-B4772 · Issue 285014

GetXML read-only conflict resolved

Resolved in Pega Version 7.3

When executing the "run" button on the rule form to test a read-only data page sourced by a Rule-Parse-XML, a read-only violation in getXML() resulted when attempting to expand the XML of the page for presentation to the user. This was traced to an unnecessary override IF block in prGetObject() related to overriding context class, and it has been removed.

SR-B47917 · Issue 304886

Improvements in Export to Excel of very large files

Resolved in Pega Version 7.3

When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.

SR-B47958 · Issue 303935

Resolved page group copy error

Resolved in Pega Version 7.3

A WrongModeException occurred while copying a page group due to incorrect clipboard handling for the page mode. This has been fixed.

SR-B48146 · Issue 305146

CheckedOutRulesBulk updated with null check

Resolved in Pega Version 7.3

The MyCheckedOutRulesBulk ruleset was taken as null for operators with rule checkout disabled, causing them to see all the non-rule resolved classes as private edits. To correct this, additional criteria have been added to fetch records only with pyClass starting with 'RULE-' and the List views MyCheckedOutRulesBulk and MyCheckedOutRulesBulkPM have been changed to check for null values.

SR-B48780 · Issue 305215

Oracle/Unix documentation updated with JDBC instructions for urandom instead of random

Resolved in Pega Version 7.3

The Install/Upgrade guides have been updated to reflect that recent changes to Oracle have created the requirement of forcing the JDBC driver to use /dev/urandom instead of /dev/random to improve security as well as connection open and close performance. The guide now recommends customers running Oracle on Unix do one of the following: 1. Update $JAVA_HOME/jre/lib/security/java.security to use securerandom.source=file:/dev/./urandom 2. Set system property -Djava.security.egd=file:///dev/urandom

SR-B509 · Issue 277331

Turkish characters supported in autocomplete filtering

Resolved in Pega Version 7.3

Support has been added for Turkish locale special characters in autocomplete filtering.

SR-B5172 · Issue 275097

SOAP handling for BOM bites fixed

Resolved in Pega Version 7.3

After upgrade, an exception was generated when hitting the PRSOAPServlet. This was due to an error in encoding BOM bytes, and has been fixed.

SR-B51793 · Issue 308487

Extended options for creating Context URI

Resolved in Pega Version 7.3

In order to facilitate the use of Amazon Web Services, an enhancement has been added to extend the methods available for forming Context URI. Previously, Pega Platform mandated both X-Forwarded-Host and X-Forwarded-Proto be present when using HTTP extension headers. The new feature adds HOST support when X-Forwarded-Proto is present without X-Forwarded-Host. The URL will consider X-Forwarded-Proto for protocol (http or https) and take the host name from host header. This change works for any reverse proxy or load balancer, as long as they emit X-Forwarded-Proto and preserve the HOST header.

SR-B5224 · Issue 277207

Fixed intermittent override default template failure

Resolved in Pega Version 7.3

The override default template was displaying inconsistent behavior due to the fromLocalAction function not correctly resetting. This has been corrected.

SR-B5308 · Issue 275351

Special characters correctly encoded in downloaded filenames

Resolved in Pega Version 7.3

While downloading an attachment file containing special characters in file name, the file was getting saved with ASCII codes. This was caused by the file name being encoded in download operations, and has been fixed by providing the encoding type as UTF-8 in the content disposition header for the sendFile() method.

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