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-B35050 · Issue 293637

Repaired BIX extract rule filters

Resolved in Pega Version 7.3

pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.

SR-B35741 · Issue 292129

Corrected thread contention in BAC

Resolved in Pega Version 7.3

A thread contention condition was found in BAC due to the use of maccesscache. That function and the matching clearAccessCache() function are no longer used in Basic ApplicationContext and BasicApplicationContextImmutableimpl to resolve the issue.

SR-B3591 · Issue 277488

Unit Test Case for DataPage localized for comma decimal indicators

Resolved in Pega Version 7.3

When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.

SR-B3591 · Issue 278006

Unit Test Case for DataPage localized for comma decimal indicators

Resolved in Pega Version 7.3

When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.

SR-B35987 · Issue 296514

Improved backwards compatibility for migrated rules with Declare Expressions

Resolved in Pega Version 7.3

The current activity pzUpdateConditionsList did not have backward compatibility for "AND" and "OR" operators in rules created with older version of Pega Platform that allowed the use of "And" and "Or". This has been resolved by adding a check for equalsIgnoreCase when converting "And" to "&&".

SR-B36091 · Issue 292431

Hazelcast logging added with updated jar

Resolved in Pega Version 7.3

Additional Hazelcast logging has been added and and the prcluster-7.1.jar has been rebuilt for better reliability.

SR-B36134 · Issue 294001

Security fix to prevent URL tampering

Resolved in Pega Version 7.3

Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.

SR-B36134 · Issue 294080

Security fix to prevent URL tampering

Resolved in Pega Version 7.3

Pasting a URL that corresponds to an activity to invoke express on the browser URL allowed end users to get the express experience. To secure the system, the portal switching logic has been hardened to reinforce a portal check against access group privileges and to allow for equivalencies.

SR-B36228 · Issue 292442

Improved RuntimeCacheImpl performance

Resolved in Pega Version 7.3

There was unnecessary contention within the RuntimeCacheImpl when that class was asked to provide information about a blank class name. To correct this and improve performance, a check for the empty class name has been moved out of the synchronized block to the top of this method.

SR-B36307 · Issue 292510

prconfig added to disable tracer checks in census

Resolved in Pega Version 7.3

There was some contention when checking for tracer to log trace events for access denials in a census application. Since tracer is not used in census, a prconfig switch has been added to disable these tracer checks.

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