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-A14862 · Issue 231106

TrimLog performance improved

Resolved in Pega Version 7.2.1

Activity log.trimlog is called several times from the systemCleaner agent to clean up old entries of generally unused Log- classes. In order to improve performance on large logs, the previous partial load and delete method has been updated to a bulk cleanup using the purgeTableContainingClass() API in the Pega Database.

SR-A23178 · Issue 248200

Checkout to branch ruleset handling improved

Resolved in Pega Version 7.2.1

The Checkout to branch option was not able to find a list of branches in Pega Marketing after a minor ruleset migration. To resolve this, the system will make use of a non versioned ruleset name for showing branches if an application is referring a ruleset whose major or minor version is different from the Ruleset of the Rule that is being checked out.

SR-A23282 · Issue 245229

Checkout to branch ruleset handling improved

Resolved in Pega Version 7.2.1

The Checkout to branch option was not able to find a list of branches in Pega Marketing after a minor ruleset migration. To resolve this, the system will make use of a non versioned ruleset name for showing branches if an application is referring a ruleset whose major or minor version is different from the Ruleset of the Rule that is being checked out.

SR-A20761 · Issue 247086

New test Suite ruleform display resolved

Resolved in Pega Version 7.2.1

When attempting to create a new unit test suite, no ruleform was presented. Instead, raw XML was displayed. To correct this, the TestSuite Rule Form has been autogenerated so that it is viewable and openable in 7.2 in supported browsers.

SR-A19159 · Issue 237816

Enabled custom parameter input for PushBodyCountVar

Resolved in Pega Version 7.2.1

After importing custom markup language based on JSP 2.0 tlds and mustache templates and writing a custom HTML rule to generate JSP, the error s were generated relating to the default value of aTagPushBodyCountVar parameter. To enable the custom input, the generateCustomStart() method has been modified to use a passed-in parameter by way of aTagPushBodyCountVar instead aVisitor.getPushBodyCountVar().

SR-A20450 · Issue 239606

Locale validation step added to match accepted formats

Resolved in Pega Version 7.2.1

It was noticed that if a locale was specified on the Operator rule using a hyphen rather than an underscore (such as en-GB vs en_GB), the operator defaulted to the US locale for date and time formats and no check or error would be generated. To ensure expected behavior, a step has been added to validate the format of locale to match either "blank", xx, or xx_XX.

SR-A23012 · Issue 242327

pega.u.d.onViewUpdatecorrectly triggered from Master-Detail

Resolved in Pega Version 7.2.1

The "pega.u.d.onViewUpdate" function invocation was not being triggered as expected when the details screen was opened from a master list while offline. To fix this, the "actionInfo" pzInskey has been updated to obtain the Page Context on which the RDL is configured.

SR-A23862 · Issue 246796

VPD Data Page passes custom properties

Resolved in Pega Version 7.2.1

When trying to set up Oracle VPD custom properties as instructed in a PDN article, an exception was generated due to missing handling for custom class/property definitions. The new pyCustomProperties if PageList has been added to Code-Pega-DBApplicationContext .

SR-A20067 · Issue 243517

Fixed thread locking for authenticated SOAP

Resolved in Pega Version 7.2.1

Exception messages were being logged when the authenticated inbound SOAP service was called from a client application due to two threads simultaneously trying to load a data page at node level. The locking has been corrected to resolve this.

SR-A23915 · Issue 247392

Apache Struts updated for security

Resolved in Pega Version 7.2.1

Apache Struts has been updated to version 2.3.28 to protect against potential security vulnerabilities exposed when Dynamic Method Invocation is enabled, removing the ability for remote attackers to execute arbitrary code via method: prefix, related to chained expressions.

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