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-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.
INC-166845 · Issue 640299
Hazelcast remote execution not called from synchronized context
Resolved in Pega Version 8.7
After navigating to the Admin Studio portal to view the nodes, the portal was temporarily freezing. Investigation of the thread dump revealed this was caused by a DDS pulse sending a remote execution call to all nodes to update logger settings even though the site was not using DDS. This has been resolved by updating the system to avoid calling Hazelcast remote execution from a synchronized context.
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-C82480 · Issue 421488
Column Headers properly aligned after expand/collapse of Tree Grids
Resolved in Pega Version 8.1.3
When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row.
INC-180233 · Issue 660578
Offline.Rulecache UI module capacity increased
Resolved in Pega Version 8.7
Clicking the save button on a modal window caused the application to freeze and all the buttons were disabled. This was traced to the pega.offline.rulecache UI module having a default hard limit of 500 rules. Once the hard limit was reached, the system intermittently silently refused caching additional rules depending on the amount of rules packaged or the order in which the rules are loaded to the cache. To resolve this, the system has been updated to only log a console warning once the maximum threshold is reached, allowing the application to operate normally and at the time inform about the potential impact of having too many rules in memory.