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-119239 · Issue 173898

Max limit error localized and variable added for unsaved work items

Resolved in Pega Version 7.1.7

In order to allow a local value for the number of unsaved work items, a new Field value has been created : MAXIMUMTABSALERT. In addition, the error message text "You have reached the maximum limit for pending changes. Please commit/cancel one or more changes to continue" is now available for localization.

SR-119537 · Issue 174774

Improved speed for deleting repeat grid rows with Dynamic Select

Resolved in Pega Version 7.1.7

When deleting rows from a repeat grid with Dynamic Select and heavy HTML, deleting the first one was very fast but a delay appeared when there was one row left in the repeat grid. The browser message "Pegacloud not responding due to a long-running script" would also be displayed. This was found to be caused by a list-to-list control function being invoked for each processOnBeforeSubmit call which generated an increased number of input elements in the form. This has been corrected.

SR-112935 · Issue 166182

Repeating grids enhanced to allow the '&' character as text

Resolved in Pega Version 7.1.7

When values in a repeating grid contained the character "&", the ReloadSection activity failed with an illegal argument tracer and no values were passed to a second Repeating Grid Page List. This was traced to '&' being used by the system to perform a split of value string. In order to allow use of the '&' character in the list values field, it will now be encoded so it is passed without evaluation.

SR-115387 · Issue 164437

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.

INC-188141 · Issue 678160

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-190855 · Issue 681093

Duplicate items resolved for questionnaires

Resolved in Pega Version 8.6.5

When there was only one question page for a questionnaire, the question page title was being displayed twice and the breadcrumb showed duplicate steps. When there was only one step in the screen flow, the survey navigation was hidden. This has been resolved.

INC-191756 · Issue 718551

Corrected dashboard focus highlighting

Resolved in Pega Version 8.6.5

Dashboard links like "My activities"/"My cases"/"Recent"/"Search” were displayed with a yellow focus highlight even though the user was not currently in those screens. Investigation showed the data-menu-id for control_menu was being appended with the workid until selecting another tab caused it to reset to its original value without workid. This change in menu-id was responsible for the issue with focus, and occurred only when render as single checkbox was unchecked. This has been resolved by removing workid from menuid and adding a unique id for the outside menu and inside case same menu.

INC-196186 · Issue 725412

Check added for repeating dynamic layout submit context

Resolved in Pega Version 8.6.5

The postprocess of a local action was not executing when the local action was in a table that contained a repeating dynamic layout, and a null pointer exception was generated. Investigation determined that when a repeating dynamic layout was used inside a grid, the submit action on the layout was incorrectly happening in the context of the grid. To resolve this, a check has been added to determine whether the repeating dynamic layout is inside a grid so the correct context is used.

INC-198784 · Issue 697526

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-199137 · Issue 708165

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

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