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-A23134 · Issue 243870

Resolved upgrade exception caused by non-standard requestor setting

Resolved in Pega Version 7.2.1

Upgrading to v7.2 was failing if the 'Requestor Types' (DATA-ADMIN-REQUESTOR instances) ACCESS GROUPs had been modified in the previous version for the System Name 'prpc'. This modification caused the PRPC requestors to not be replaced during upgrade. To address this issue, the installation will create a RAP to import into the SDE that will check for this condition, and the PRPC Requestors have been updated such that they cannot be modified. See also: Process Commander V6 help "About Requestor Type data instances" and "When and how to change a system name" for more background information about Requestor Types.

SR-A23339 · Issue 247921

Non-versioned class rule forms updated during upgrade

Resolved in Pega Version 7.2.1

The non-versioned class rules in an environment were skipped during upgrade due to an error in the RevalidateAndSave function. This has been corrected.

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-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-A23979 · Issue 246353

Revamped help docs to clarify ServiceExport directory config

Resolved in Pega Version 7.2.1

An error in the help documentation did not correctly outline the method for changing the ServiceExport directory by modifying prconfig.xml. The directory location is hard coded to StaticContent/global/ServiceExport in the temporary directory, but the location of the temporary directory is configurable using the Initialization/explicitTempDir setting. Changes have been made to the help files to clarify this.

SR-A24052 · Issue 248427

Orphaned work objects purged by class

Resolved in Pega Version 7.2.1

Orphaned work objects were not purged when their parent was deleted from the database. To resolve this, selecting a Work- object class for purging will also purge all of the orphans in that class.

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