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.
SR-D40523 · Issue 505928
Corrected Pega-Perf cookie adding double quotes
Resolved in Pega Version 8.1.7
After upgrade, issues were seen with mashup not loading properly. In addition, a region in the environment was not able to access the developer portal. This was traced to an issue with pzPega_ui_statetracking.js, which handles adding the Pega-Perf cookie, adding a cookie with double quotes to HTTP requests. The double quotes have been removed to resolve this issue.
SR-D43740 · Issue 514126
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.1.7
The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.
SR-D26133 · Issue 500723
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-D28898 · Issue 501653
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-D28476 · Issue 500889
Corrected exceptions report appearing on user screen
Resolved in Pega Version 8.1.7
When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using Microsoft Internet Explorer 11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.
SR-D34214 · Issue 511814
API available to skip defer loading in Single Page Applications
Resolved in Pega Version 8.1.7
The wait message "Loading ..." was displayed on check on defer load in Single Page Applications. The browser refresh worked as expected if 'defer load' was unchecked. This was traced to SPA not containing the handling necessary to publish the forced replace to other modules: in SPA cases, the dashboard is forcibly replaced with workobject harness, causing defer loads in dashboard to be processed in the wrong thread. To resolve this, there is now an exposed API pega.ui.DCUtil.skipDeferredLoadFrom() to skip defer loading when true in SPA.