INC-222922 · Issue 722995
Validations fire on collapsed accordion layouts
Resolved in Pega Version 8.8
Client validation was not firing on the selected tab of a layout group if the accordion layout was collapsed. If focus was switched to the second tab, the client validation on the first collapsed tab did not work. This has been resolved by modifying the 'else if' condition to pass the validation for the fields places in layout group tabs.
INC-223222 · Issue 723635
Corrected apiContext when using bulkActions
Resolved in Pega Version 8.8
Row selections in the multi-selection table were intermittently not working after opening a table with bulk actions enabled. Investigation showed that opening a table with bulkActions enabled and then navigating to a table where bulk actions are not available but multi-select is enabled led to functions like setSelectedRows and getSelectedRows still being available in apiContext. This has been resolved by correcting apiContext when bulkActions is enabled.
INC-223504 · Issue 723197
Harness handling updated for Tertiary Ajax Container
Resolved in Pega Version 8.8
After configuring a Create Stage with a single step and a second stage with a screen flow configured with Multistep form, creating a case caused the Step under the Create stage to come up on the Tertiary Ajax Container as expected, but on click of create the second stage also started to run the same Tertiary Ajax Container. This has been resolved by updating the harness handling so the Tertiary Ajax container will close and the second stage will open on the main action area within the Cosmos Portal.
INC-223557 · Issue 732143
Integer property allows blank value
Resolved in Pega Version 8.8
When a field with a default value was changed to blank, the value was not updated on the clipboard. This has been resolved by updating the control_textinput file.
INC-223880 · Issue 733556
Handling added for IME input for date and value
Resolved in Pega Version 8.8
Attempting to input numbers in date and price areas generated from an input method editor (IME) Japanese keyboard was not working correctly due to the field not supporting double-byte characters. This has been resolved by adding an if condition for not formatting the date or value until IME input is done.
INC-224059 · Issue 743432
Corrected locking issue in repeating grid for local action
Resolved in Pega Version 8.8
When a grid was configured as readonly and the button in the grid had an open local action which opened up a section via flow action which was editable, on cancel, the grid context was treated as readOnly and was not releasing the lock. To resolve this, the pega.ctx.activeGrid.isOpenLocalAction flag has been added to releaseWOLock when a modal is launched from the grid using openLocalAction.
INC-224253 · Issue 744974
Corrected UI Kit highlighting error
Resolved in Pega Version 8.8
The highlighting in the drop down of a tag was displaying on another tab. This was traced to the activeTab class not being correctly added in the UI Kit for the case worker portal, and has been corrected.
INC-224317 · Issue 723105
Corrected embedded page list render error
Resolved in Pega Version 8.8
Using a page list within a page list was rendering with overlapping field forms. This has been resolved by removing the negative margin from field group legends when presented in a list.
INC-224446 · Issue 724370
Load more works in non-templatized layout
Resolved in Pega Version 8.8
After adding a repeating dynamic layout inside a tab group layout (which is a deprecated feature) to make it non-templatized, the progressive pagination option to show the "load more" button did not work. This was caused by the load more functionality having a dependency on pega.ui.RDL even though pega.ui.RDL was not available in case of a non-templatized grid, with the result of generating an exception which broke the flow. This has been resolved by adding a null check which will allow the flow to proceed whether the grid is used inside non-auto-generated or auto-generated elements. Please note that it is strongly recommend to update any deprecated layouts to Layout Group as it is a best practice to keep the code updated to avoid any compatibility issues.
INC-225236 · Issue 725704
Corrected LiveDesignViewDisplay error handling
Resolved in Pega Version 8.8
When all rulesets were locked and a section was opened from Live UI in a portal, a "rule deleted" message appeared and it was confirmed the rule was deleted even though the rule was in locked ruleset. Investigation traced this to a pzLiveDesignViewDisplay call to pxChooseBestRuleSet which jumped to failure logic when "allow check out" was disabled, and this has been resolved by correcting the error handling in pzLiveDesignViewDisplay.