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-A2009 · Issue 206469

Fixed inconsistent tab 'visible when' behavior

Resolved in Pega Version 7.1.9

In a section with a tabbed repeat using 'body visible when', invoking a list which changed the when condition so that the tab becomes visible in the tabbed repeat created various issues after checking the visibility including invisible data, empty tabs, and duplicate tabs. This was traced to the placement of visible when conditions in the RUF causing the DIVs to be closed incorrectly, and has been fixed.

SR-A2107 · Issue 206837

Updated Reloadharness Activity to correctly render older menus after upgrade

Resolved in Pega Version 7.1.9

When menus were rendering with old menu generation code, the required parameters were not properly generating. This was caused by a missed Primary page name parameter in the update process for menu generation originally done under older versions of the software. While there was a workaround of regenerating the menus within the updated system, the transitional parameter has now been added for the reload harness action.

SR-A2125 · Issue 208860

Fixed scrolling for Autocomplete dropdown

Resolved in Pega Version 7.1.9

After opening a new harness with a button in the fixed div of the harness, the Autocomplete dropdown was detaching from the control and sticking to the screen when the browser scrolled. This was due to an inline style tag that interfered with repositioning the Autocomplete results popover. To fix this issue, a condition has been added to the style tag triggered on a harnessContent div to call an API for repositioning pop overs.

SR-A2141 · Issue 205867

Refined refresh focus logic for radio buttons using on OnChange

Resolved in Pega Version 7.1.9

In a list of Radio Buttons, using the Down Key caused focus to move to the corresponding Radio Button for a split second but immediately shift back to the first Radio Button. This was caused by the OnChange of the radio button having a refresh-this-section, so ReloadSection was being called and the focus was shifted to the first radio button irrespective of the option which was selected. This was confusing behavior, so the system has been modified such that after refresh, focus() element will be called to set focus on the element which caused the refresh.

SR-A2141 · Issue 205271

Refined refresh focus logic for radio buttons using on OnChange

Resolved in Pega Version 7.1.9

In a list of Radio Buttons, using the Down Key caused focus to move to the corresponding Radio Button for a split second but immediately shift back to the first Radio Button. This was caused by the OnChange of the radio button having a refresh-this-section, so ReloadSection was being called and the focus was shifted to the first radio button irrespective of the option which was selected. This was confusing behavior, so the system has been modified such that after refresh, focus() element will be called to set focus on the element which caused the refresh.

SR-A2143 · Issue 208439

Localization added for "Grand Total" FieldValue.

Resolved in Pega Version 7.1.9

Localization has been added for the pyFieldCaption property of the "Grand Total" FieldValue.

SR-A2205 · Issue 206937

Added handling for stack overflow errors in Designer Studio

Resolved in Pega Version 7.1.9

After upgrading, Stack Overflow errors were being generated when opening a section rule in Designer Studio if the section view met the following conditions: 1) Page context is a separate clipboard page; 2) clipboard page is of the format: MyPage.EmbeddedPageGroup(Subscript): 3) Class is a different class than current primary page class; 4) Included section has the same name as the primary section. This did not happen if the system-generated Pages & Classes entry was modified before saving to include the page group's subscript. However, since specifying subscripts wasn't allowed in some earlier versions, all of the old section rules that have section include layouts that fit the above profile can't be opened without getting this StackOverflowError after migration from those versions. To resolve this, the activity GetDesignViewXML now includes a fallback to check for class with subscripts removed.

SR-A2323 · Issue 206066

Other Actions submit API updated

Resolved in Pega Version 7.1.9

When using the out-of-the-box Other Actions button, selecting 'Refresh' caused a blank page to display and resulted in an 'ERR_CONNECTION_RESET' script error. This happened when a form submit URL including all input parameters exceeded the max length expected. The API used for the submit function has been updated as of this release along with the Ajax engine call, and the problem is no longer seen.

SR-A2323 · Issue 206125

Other Actions submit API updated

Resolved in Pega Version 7.1.9

When using the out-of-the-box Other Actions button, selecting 'Refresh' caused a blank page to display and resulted in an 'ERR_CONNECTION_RESET' script error. This happened when a form submit URL including all input parameters exceeded the max length expected. The API used for the submit function has been updated as of this release along with the Ajax engine call, and the problem is no longer seen.

SR-A2567 · Issue 207309

Corrected Refresh based on clipboard property changes

Resolved in Pega Version 7.1.9

Refreshing the Dynamic layout whenever a property in the clipboard changes was not working in one of the cases in base CPM: when passing "ProcessAction" activity as a pre-activity for any flow action, change tracker did not send the changed values from the newAssignPage. This has been resolved by adding a condition for "ProcessAction" on pre-activity.

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