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-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-A23457 · Issue 245079

Tab

Resolved in Pega Version 7.2.1

In a tabbed layout, opening a modal window resulted in the tab name being changed to that of any active window. This was an error in the drilldown window logic, and has been corrected.

SR-A23665 · Issue 248776

Percentage calculated by control carried into Excel export

Resolved in Pega Version 7.2.1

If a Report Definition calculated the percentage by using the control, the percentage would display in the report browser but 0.00% would be displayed in the Export to Excel. The step page for the control being executed at display time and export are different, so the activity is unable to get the ".pySummaryCount(1)" from the step page. To fix this, pzGetHTMLPropertyValue has been modified so it acts on the step page of the property rather than the primary page the function was executed against.

SR-A23692 · Issue 245660

Scheduling dialogue correctly releases lock on browser pop-up exit

Resolved in Pega Version 7.2.1

Opening the scheduling dialogue for a currently scheduled report created the proper locking, but "X"-ing out of the pop-up report window without editing it was not releasing the lock and the report was then not executed as scheduled. To avoid this, a Rule-Obj-Casetype has been added to control when the schedule is locked and will also release the lock when the changes fail validation.

SR-A23709 · Issue 247989

Performance improvements for Scheduled Export to Excel

Resolved in Pega Version 7.2.1

Some memory usage improvements have been made for exporting reports to Excel through the scheduler.

SR-A23735 · Issue 248542

Image/Label of Report checkbox clickable

Resolved in Pega Version 7.2.1

In the Report Browser, icons and text labels have been linked to the checkbox and are clickable to check/uncheck the list/chart/summary filters.

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-A23912 · Issue 246952

Custom filters won't display header container icons

Resolved in Pega Version 7.2.1

Unwanted icons were appearing when using a custom filter section that has a grid with a header/title, such as an 'X' close icon displaying next to an included section/repeat grid coupled to the filter section launched from the report browser for a report definition. The harness that displays the filter section has been modified to not include the icons that come with a container that has a header.

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.

SR-A24402 · Issue 246696

Tuned scheduled reports start calculations

Resolved in Pega Version 7.2.1

In recurring schedule - daily pattern, if the start date was more than one day in the future, either the next scheduled run time was wrongly calculated as tomorrow with the right hour or if the start date was tomorrow, the next scheduled run time was wrongly calculated as today with the right hour. To fix this, the Next execution time calculation in DailyPattern.java now considers the mStartDateTime value.

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