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.

INC-217655 · Issue 723564

Resolved validation check freeze for Dynamic Layout Group

Resolved in Pega Version 8.6.5

After creating a multi-step form where step 1 had a Dynamic Layout Group(tabbed) that used form fields configured with validations, clicking next with empty/invalid values in the form intermittently caused the screen to freeze and a javascript exception was logged. This was traced to a missed use case related to templates in the childNode, and has been resolved by adding the necessary safe checks in lgtemplate and lgcelltemplate.

SR-A14619 · Issue 229625

Alignment resolved for repeating grid headers

Resolved in Pega Version 7.2.1

Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.

SR-A17411 · Issue 234053

Alignment resolved for repeating grid headers

Resolved in Pega Version 7.2.1

Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.

SR-D49507 · Issue 521413

Support added for Oneof/AllOf association prefix in ABAC policies

Resolved in Pega Version 8.4

The Report browser was freezing when attempting to save a report with an association rule where ABAC policies prevented access to one of the classes in the association. This has been resolved by updating the system to append the correct prefix in cases where the ABAC rule has Oneof/Allof Functions so the association is resolved correctly.

SR-A16904 · Issue 234334

Wrapper added to expression builder for the jump transition on a step

Resolved in Pega Version 7.2.1

While using expression builder, selecting the option for "Enable conditions after this action" in an activity and submitting the expression did not show the expected result in the When input box. Attempting to use the expression builder again and submitting it then resulted in the screen freezing and requiring a refresh. To resolve this, a "pyStepsTransSection" wrapper section was been added for the "pyStepsTransParamsWhen" when condition.

SR-A15490 · Issue 233417

Grid layout correctly displays columns with empty rows

Resolved in Pega Version 7.2.1

In a repeating grid, when Width of content -> Pixels(Fit Content) and Fixed (pixel) size grid : Grid size (in pixels): 1000 px (Width) and 0 px(Height), Freeze grid header are selected, all the columns are not shown when there are no records in the grid. This was traced to a div function that did not sync properly and clipped columns in this circumstance, and a check has been added to correct the display when using progressive loading.

SR-A15695 · Issue 233521

Grid layout correctly displays columns with empty rows

Resolved in Pega Version 7.2.1

In a repeating grid, when Width of content -> Pixels(Fit Content) and Fixed (pixel) size grid : Grid size (in pixels): 1000 px (Width) and 0 px(Height), Freeze grid header are selected, all the columns are not shown when there are no records in the grid. This was traced to a div function that did not sync properly and clipped columns in this circumstance, and a check has been added to correct the display when using progressive loading.

SR-D52144 · Issue 515673

When no active document is available on login, first document will be marked active

Resolved in Pega Version 8.4

After logging into the user portal, attempting to perform operations like (opening a case/work object, opening reports etc.) caused the browser request to spin or freeze. The only way to recover was to close and re-launch the browser window/session and re-login. This issue occurred when there was an active reportdefinition document before the browser/node crash in the tabless dynamic container(DC) portal. After recovery, the dynamic container did not recreate the report definition document but instead tried to activate the first document in the portal, which in this case was the default harness configured in the Dynamic Container. As it was not yet loaded, exceptions were thrown. To resolve this, when no active document is available, the first document will be marked as the active document.

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