INC-184109 · Issue 671195
Handling updated for customDateTime formatting
Resolved in Pega Version 8.7
When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved.
SR-130963 · Issue 201149
Corrected Dynamic Select with refresh section
Resolved in Pega Version 7.1.9
Dynamic Select with refresh section was causing an unexpected change of focus in the Pega Survey component of the Care Management Framework (CMF), resulting in an erratic scrolling behavior for pages that have many questions that dynamically update the survey section by adding or removing questions. When these selections are made, the screen was consistently scrolling to the bottom of the question list. This was caused by a previous change made to focus the element based on ID to enhance accessibility, but this was missing the necessary accessibility check to limit it. That has now been added.
INC-173944 · Issue 660180
Cancel button on embedded GridRow cancels single action
Resolved in Pega Version 8.7
When a modal Flow Action contained a Table with the Row operations configured as Master-detail and the Detail flow action was specified, if a validation error defined in a Validation rule (i.e. other than required field error) occurred while entering details for one of the rows and the Cancel button for that row was clicked, the entire action was cancelled and the modal window was closed without saving anything. This has been resolved by updating the system to prevent the modal closure if a row is added and then cancelled.
SR-A2205 · Issue 206937
Added handling for stack overflow errors in Designer Studio
Resolved in Pega Version 7.1.9
After upgrading, Stack Overflow errors were being generated when opening a section rule in Designer Studio if the section view met the following conditions: 1) Page context is a separate clipboard page; 2) clipboard page is of the format: MyPage.EmbeddedPageGroup(Subscript): 3) Class is a different class than current primary page class; 4) Included section has the same name as the primary section. This did not happen if the system-generated Pages & Classes entry was modified before saving to include the page group's subscript. However, since specifying subscripts wasn't allowed in some earlier versions, all of the old section rules that have section include layouts that fit the above profile can't be opened without getting this StackOverflowError after migration from those versions. To resolve this, the activity GetDesignViewXML now includes a fallback to check for class with subscripts removed.