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-A24855 · Issue 253637

Fixed Export to Excel with Microsoft Internet Explorer 11

Resolved in Pega Version 7.2.2

When using Microsoft Internet Explorer 11, Export to Excel from report definition generated the sporadic error "Unable to read file." After consulting with Microsoft, the cause was traced to the browser attempting to open the file before it was downloaded, and code has been added to check for the browser and handle the download/open appropriately.

SR-B2033 · Issue 272929

Help doc corrected for Clipboard save location

Resolved in Pega Version 7.2.2

An error in the help file indicated the Save feature in the Clipboard Viewer should save to the database. In Pega 7, the Save feature in Clipboard Viewer only saves the page in memory and does not perform any database transactions, and the documentation has been updated to reflect this.

SR-A99473 · Issue 266934

Documentation updated for Obj-Delete-By-Handle method

Resolved in Pega Version 7.2.2

The documentation for the Obj-Delete-By-Handle method has been updated to clarify that the Obj-Delete-By-Handle method will require the object to be locked if either the class or class group allows locking.

SR-A95291 · Issue 270315

Deprecated Access Groups documentation updated

Resolved in Pega Version 7.2.2

The documentation lead-in to the Deprecated Access Groups section has been updated for clarification: These access groups are retained after upgrades to support applications created in Version 4.2 and Version 5.X systems. They are deprecated and not recommended for continued use. These access groups appear only on systems that are upgraded from PRPC 6.x or earlier.

SR-A98702 · Issue 266129

Minor update to help doc for property optimization run time

Resolved in Pega Version 7.2.2

The help file for Property optimization using the Property Optimization tool has been updated with non-critical corrections to the phrasing regarding the length of time that might be required to perform background processing.

SR-A99855 · Issue 266703

Help file corrected for JSP tag

Resolved in Pega Version 7.2.2

The help for the JSP Tag "" is incorrect: It reads: example string of 'pyActivityName', but it should be 'pyActivity'. This has been fixed.

SR-A94342 · Issue 263882

Inserted missing word in property-set-html doc

Resolved in Pega Version 7.2.2

The missing word "is" has been added in In the doc article that comes up when the "?" is clicked while filling in the parameters for the property-set-html activity method, which previously read "Identify the property that to receive its value from stream processing".

SR-A76148 · Issue 251342

Documentation updated for running BIX from the command line

Resolved in Pega Version 7.2.2

When attempting to run BIX from the command line within a Linux environment, an error is thrown: Error: Could not find or load main class com.pega.pegarules.data.internal.access.ExtractImpl This was a local error in the setup of the bix.sh script, and the BIX documentation has been updated to clarify the requirements.

SR-A94871 · Issue 263314

Handling added for summary report paging mode changes

Resolved in Pega Version 7.2.2

After switching a summary report previously configured to use the "Next Previous" paging mode to a list report using the "List" action in the "Actions" menu, changing to a new page caused an error to be shown and no records displayed. This has been corrected by adding a step to the activity pzPostReportSummarizeConfig to reset the paging of a report when converting from a summary report to a list report.

SR-A99642 · Issue 266586

Fixed special character encoding for Report Definition

Resolved in Pega Version 7.2.2

Double encoding of the Axis label caused issues with special characters such as apostrophes in Report Definition. This has been corrected.

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