SR-D52969 · Issue 514705
Column population honors thread count of 1
Resolved in Pega Version 8.1.7
The thread count parameter in the column population activity was not being honored, causing repeated deadlocks when trying to populate columns. Investigation showed that the ExposeCols process did not honor the thread count when it was 1 (the default is 4), and this has been fixed by adding the necessary code so that if the thread count is 1, it will not run in multhreaded mode.
SR-D16543 · Issue 487946
Thread cleanup improved for application switching to resolve skin issue
Resolved in Pega Version 8.1.7
After opening a Case from the HR application and then switching to another application to open another case, the Review Harness skin control was not loading correctly. This was traced to a thread cleanup issue relating to the Portal: on application switch, the system should clean up all threads created on the current application before switching to new application, but in this case thread cleanup was not happening as expected due to conflicts in the unload event handling. This has been corrected.
SR-D40938 · Issue 509687
Free form layout controls will be converted to dynamic layout
Resolved in Pega Version 8.1.7
After upgrade, a a pzActionDropdown control that was inside a pyActionDropdownSection was not visible anymore. Using the pzActionDropdown control directly worked as expected. Investigation showed that pyActionDropdownSection was using Freeform layout instead of the upgraded Dynamic Layout, and that the custom control was failing to generate the markup whenever drag/copy-paste was used for the control in any layout. To resolve this, the system has been updated so it will remove the control from a free form layout and use dynamic layout instead.
SR-D48881 · Issue 514602
Corrected alignment of column header and content when fixed header is used
Resolved in Pega Version 8.1.7
The tables header column was misaligned with the context columns when a fixed header was used. This has been resolved by correcting the code calculating the width of the header cells.
SR-D23174 · Issue 499569
Check logic added for change in datetime
Resolved in Pega Version 8.1.7
After selecting a valid date in the calendar UI, clicking outside of the DateTime control caused the date to disappear when using the Microsoft Internet Explorer browser. Investigation showed that the order of events execution is different in Microsoft Internet Explorer and Google Chrome, so that by the time the getReadOnlyFormatting method was called, the data-changed attribute had already been updated to 'false'. This caused the read-only formatting to not be applied so the data-display-value was considered to be empty. To resolve this, a check has been added to better detect the change so that read-only formatting gets applied.
SR-D31599 · Issue 503201
Table layout filter by format works for empty value
Resolved in Pega Version 8.1.7
If a DateTime property with empty values in a table layout grid was filtered by format, no result was returned even though the grid had the Records for empty DateTime property. This was traced to null value filtering being done with empty values instead of a formatted null value, a difference that could produce different results depending on the control. To resolve this, the activity has been updated to support null values filtering.
SR-D32525 · Issue 505469
Dirty check added to offer save/discard changes when closing tab
Resolved in Pega Version 8.1.7
With the out-of-the-box section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty.
SR-D36335 · Issue 504335
Post Value action properly displayed in upper case after validation
Resolved in Pega Version 8.1.7
After upgrade, if a property with Edit Input toUppercase was created and placed it on a section where the text input has Post Value on Change, validating the uppercased property on the clipboard resulted in the non-uppercase value displaying on the screen. This was traced to the target element with the response value not being updated with the server response for the post value action. Only the attribute value was updated, which is not shown to the user. In order to properly display the value, logic has been added to update the target element value with the response value.
SR-D36970 · Issue 504987
Calendar icon updated to properly display the set number of years
Resolved in Pega Version 8.1.7
By default, the Calendar icon showed a date range of 10 years when -/+100 was expected. This issue was traced to the existing DSS setting (pyNumberofYears under Pega-UIEngine), which enables overriding the date year range, not being honored when the pyNoOfYears property was set to -1. To honor the pyNumberofYears setting, pyNoOfYears should be 21. This has been corrected so the value will be set properly. To see custom calendar range, attached snippet should be added to UserWorkForm. To see custom calendar range, the below snippet should be added to UserWorkForm: <script> pega.u.d.overrideCalendarDefaultRange = { past: 20, future: 20 } </script>
SR-D38581 · Issue 504777
Removed unnecessary cross-site scripting filtering on paragraph rule
Resolved in Pega Version 8.1.7
When a link was set in a paragraph rule, the target option was removed in the returned layout structure. This was traced to unnecessary cross-site scripting filtering which has now been removed.