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-116479 · Issue 170952
Elapsed Time reporting corrected
Resolved in Pega Version 7.1.7
Two out-of-the-box reports, Elapsed Status Time Trend and Average Elapsed Time Per Status, were causing the browser to freeze and stop responding if there were more than 1000 records. This was caused by an invalid value for the datetime units on the category for the chart causing looping behavior. This 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.
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-115749 · Issue 167027
Support added for custom filtering and refresh inside a Repeat Grid
Resolved in Pega Version 7.1.7
If a dropdown control was placed in the column header of a repeating grid to work as a filter and perform a section refresh for the list (based on a column present in the list, but not displayed in the grid), checking the option to freeze the column headers (and use a fixed height/width) caused the dropdown to no longer work and no refresh action could be triggered. This was caused by a second hidden dropdown in the grid with the fixed header configuration that overwrote the selected value in the ASYNC request that is sent when the dropdown value changes. To remedy this, changes were made in the HTML generation to make the hidden header input disabled. This works only when configured as "auto": the control generation logic overwrites all readonly conditions to true if the dropdown is configured as "Editable".