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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-131266 · Issue 199637

Cleared exception during import of RAP by prpcUtils

Resolved in Pega Version 7.1.8

When attempting to import a RAP file through command line by using prpcUtils.sh, the build was successful and all the rules were imported but an SQL exception was generated related to the execution of Stored Procedure. The RAP file did not contain any code to execute stored procedure, so the execution was found to have been done internally by prpcUtils.sh. To prevent this, prpcUtils has been updated to use the data schema as the default schema for the connection while running against either of the DB2 dbs.

SR-131323 · Issue 201113

RD operator filter max value increased

Resolved in Pega Version 7.1.8

The limit for items displayed by the RD filter pxCreateOperator has been increased to 1000.

SR-131347 · Issue 198661

Changed Dependency Checker table-based cataloging to be case insensitive

Resolved in Pega Version 7.1.8

After updating, the Dependency Checker and Packager functions for v5 items in the table-base catalog features were not finding existing cataloged items that contained mixed case IDs. To resolve this, the dependency checking code has been modified to be case insensitive.

SR-131430 · Issue 200005

Resolved error from empty repeating grid

Resolved in Pega Version 7.1.8

If a repeating grid is opened and no rows are added, the Microsoft Internet Explorer 8 browser was generating an error. When the grid is collapsed in the header its dimension parameters such as offsetHeight etc. are zero, so certain calculations in setHeadersWidth function in ui_grid js would fail and wrong dimension values would be assigned to the grid. Other browsers were failing silently in this situation, while Microsoft Internet Explorer 8 showed errors. To avoid any failure, a check has been added to the setHeadersWidth function in ui_grid js.

SR-131470 · Issue 200524

FilePath control refresh set on change

Resolved in Pega Version 7.1.8

The first time a file attachment was browsed in the Google Chrome popup window, the subject name showed up correctly. However, browsing another file did not refresh the subject name and the first file's subject name was still displayed. This was an error in the update logic where the control FilePath had a check such that if the value was already set, it would not set it again. This has been modified to update whenever there is a change in file path.

SR-131504 · Issue 200712

Localization added for 'save' label in Calendar popup

Resolved in Pega Version 7.1.8

The label 'Save' in the Calendar popup has been made available for localization.

SR-131522 · Issue 200840

Localization added for report name tooltips

Resolved in Pega Version 7.1.8

Tooltips in reports for report names are now available for localization.

SR-131538 · Issue 200108

Removed extra blank line from exported SV report

Resolved in Pega Version 7.1.8

An Excel spreadsheet exported from any Summary View (SV) report contained a blank row at the top. This has been corrected.

SR-131600 · Issue 199942

Modified Accordion display of alerts

Resolved in Pega Version 7.1.8

Validation messages in a section with accordion and UI elements were overlapping with Accordions below. This has been corrected by modifying the script to include the alert message.

SR-131611 · Issue 201761

Currency field 'save draft' function updated

Resolved in Pega Version 7.1.8

Save Draft button when pressed caused a screen error for currency fields, identifying that they were not the proper "decimal value", though the actual flow worked as expected. This was caused by the Save Draft function passing the value in string format instead of decimal, and the API has bene updated to update the value to a number.

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