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-B4749 · Issue 285795

Fixed Guardrail warnings not clearing on Justification

Resolved in Pega Version 7.3

Guardrail warnings that appeared on the Map Structured rule Justification Dropdown were not clearing until the mapping was deleted and readded with proper justification. This was an error related to the value default for property pyJustification not being defined in the prompt list, and has been fixed by adding blank as a valid value for pyJustification property with prompt label "Default", and setting the pyJustification in pyDefault model for the row to be empty string instead of "Default".

SR-B47650 · Issue 301985

Dynamically populated values localized

Resolved in Pega Version 7.3

Dynamically populated values were not getting translated in Data Migration Wizard. In order to improve localization, Property Value has bene modified to use a Localized property value for pyLabel in general settings.

SR-B47650 · Issue 303884

Dynamically populated values localized

Resolved in Pega Version 7.3

Dynamically populated values were not getting translated in Data Migration Wizard. In order to improve localization, Property Value has bene modified to use a Localized property value for pyLabel in general settings.

SR-B4768 · Issue 276160

Global DB Trace timestamp uses UTC

Resolved in Pega Version 7.3

When running Global DB trace, recorded timestamps were not following the 'set timestamp' setting. Timestamps instead corresponded to the requestor context. DB Tracer logging has been updated to ensure appended timestamps are passed as "UTC".

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.

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