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-133715 · Issue 204978

RTE <br> handling resolved when using pega:when = false

Resolved in Pega Version 7.2

Inconsistent behavior was seen when using rich text editor in paragraph rule if the pega:when was false. This was an issue with the handling of the
tags under this condition, and has been resolved.

SR-133715 · Issue 209655

RTE <br> handling resolved when using pega:when = false

Resolved in Pega Version 7.2

Inconsistent behavior was seen when using rich text editor in paragraph rule if the pega:when was false. This was an issue with the handling of the
tags under this condition, and has been resolved.

SR-A3803 · Issue 212217

Better handling for menus when using JAWS

Resolved in Pega Version 7.2

When accessibility was invoked, the Navigation menu did not indicate arrow up/down options in links with showmenu role='link' generated on them, and JAWS was not reading out that it was a link with a menu. This was an unintended side-effect of updates to avoid reading out a URL in a label/text, and corrections have been made to support accessibility so that navigational menus are read out more intuitively with JAWS.

SR-A9773 · Issue 221357

Fixed repeating row focus when using Accessibility

Resolved in Pega Version 7.2

When Accessibility was enabled and the add icon was clicked to add a section to a row repeat, it was not possible to access the first item in first row with the keyboard. Additional added rows had the correct focus. This was traced to an issue where getFocusOnNewRow was not being called correctly, and as been resolved.

SR-A6169 · Issue 214467

Corrected compilation error when using param.value in Repeat Layout label

Resolved in Pega Version 7.2

A compilation issue was encountered when a parameter was used in a repeat section cell due to the paramStrValue being double encoded. This has been resolved by adding a check that will skip the extraneous encoding.

SR-A5746 · Issue 213321

Ensured DateTime maintains read-only state when used with editable dates

Resolved in Pega Version 7.2

In a DateTime control with a read-only format set differently from an editable date format, the read-only format was being set to an editable date format when other fields were refreshed. This was an issue with calling the API, and has been corrected.

SR-A10406 · Issue 223580

Check added for page context when dropdown used in nested repeating grids

Resolved in Pega Version 7.2

A Dropdown placed in nested repeating grids with the event request onclick action "Post value" disappeared from the DOM on select of an option. This was due to an incorrect page parameter, and a check has been added to send the correct contextPage.

INC-178417 · Issue 670114

Flag reset added for grid with 'Expand When'

Resolved in Pega Version 8.7

A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.

SR-A7105 · Issue 215067

Corrected When Display format handling for DateTimeControl

Resolved in Pega Version 7.2

If the read-only formatting value was checked in the pxDateTime control for the When Display value, selecting the same value twice from the calendar caused the formatted value to be lost. To correct this, the populateSubmitableField API in pzpega_ui_calendar_dbp js file has been updated to set the data-display-value attribute before setting the value and enabling the data-formatting attribute.

SR-A7485 · Issue 216800

Visible When Conditions working for buttons in Harness

Resolved in Pega Version 7.2

Due to changes in the condition expression formatting, Visible When Conditions were not working as expected for buttons in the harness after upgrade. A check has been added to evaluate the structure and apply the correct visibility expression.

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