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-115242 · Issue 164582

Last row delete in Grid Repeat generated an error

Resolved in Pega Version 7.1.7

If a Grid Repeat contains only one row, hitting 'delete' properly removed the row, but the java script error "this.rightBodyTbl.rows[...].cells is null or not an object" appeared. This error was caused by a missing null check inside the focusing api, and has been fixed.

SR-115268 · Issue 166797

Cleanup improved for resolved work-items

Resolved in Pega Version 7.1.7

An error in the logic for Stage Flows caused improper cleanup of resolved work items, leading to outsized assignment tables. This has been corrected.

SR-115272 · Issue 167336

Corrected clipboard mismatch for refreshed Repeating Grid pages

Resolved in Pega Version 7.1.7

When using Repeating Grid pagination in Screen Flow, refreshing the screen by choosing that option from the context menu displayed with a right-click followed by selecting 'Next' on the repeat grid caused a NPE. This was caused by a mismatch with the clipboard page, and has been corrected.

SR-115308 · Issue 173906

Japanese character support added to Report Definition PDFs

Resolved in Pega Version 7.1.7

When Report Definition contains Japanese characters in its report name, column, value, etc., the exported PDF was not showing the Japanese characters incorrectly. This was due to a missing font-family for the PDF export mode, and has been corrected.

SR-115313 · Issue 164520

BIX execution history did not update all Extracted rules

Resolved in Pega Version 7.1.7

If a BIX (Business Intelligence Exchange) extract was run with two extracts from the same shell script, the execution history was updated for only one of the extract rules. This was caused by the entry in the execution history (pr_log) is being overridden when the -i command line option is used. To ensure complete logging, the system has been updated to add a new entry to pr_log for every value when invoking the -i option.

SR-115378 · Issue 168818

Corrected horizontal scroll bars for listviews with custom searches

Resolved in Pega Version 7.1.7

Horizontal scroll bars were not appearing when using custom search section in a list view. This error was caused by missing logic for resizing the window width, and has been corrected.

SR-112785 · Issue 166486

Flow Action support tuned for MenuBar keyboard navigation

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouseclick was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.

SR-115387 · Issue 166507

Flow Action support tuned for MenuBar keyboard navigation

Resolved in Pega Version 7.1.7

Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouse click was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.

SR-115392 · Issue 164192

Added customization for PDF page numbers

Resolved in Pega Version 7.1.7

Previously, it was not possible to designate the initial page number in the PDF generated by HTMLToPDF activity. Two parameters have been added to allow for greater customization: "header" activates page number support in the document header, and "startPage" is used to set the initial page number for the document. The "startPage" parameter can be used for both the header and footer.

SR-115492 · Issue 169327

Obj-save and commit working for fully-exposed classes

Resolved in Pega Version 7.1.7

If an exposed class was implemented by creating an underlying database table, trying to perform an Obj-Save (or commit) on an exposed class generated errors regarding some properties not having corresponding database columns. This happened when one of the Page names was also the beginning part of a name of one of the simple types, and was caused by a flaw in the logic used to determine if the property is an embedded reference. 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