SR-C40586 · Issue 385730
Removed cluster notification executed by the VBD client on start/stop
Resolved in Pega Version 8.1
A cluster notification executed by the VBD client on start/stop can put unnecessary pressure on the Hazelcast cluster executor during node restarts. The system has now been modified to remove the loop during the cluster scan.
SR-C40587 · Issue 383106
Custom CSS for hover preserved at runtime
Resolved in Pega Version 8.1
Customer-defined CSS styles for the hover: state of a link control format in appSkin were being overridden in run time. An unexpected clipboard border page was being generated for links, and at generation of styles the system proceeded even if the value was empty or null. This auto-generated empty style came after the custom-defined styles, so the CSS parser assumed the latest style should override the custom style and would therefore remove it during parsing. This issue has been fixed with the addition of an empty value check so custom styles will be preserved.
SR-C40603 · Issue 383184
Europe/Ulyanovsk time zone will be handled as Europe/Samara to maintain local datetime values
Resolved in Pega Version 8.1
For some time zones, when a datetime value was provided it was changed to a default GMT value after a section refresh. This was caused by the Moment APIs utilized by Pega for time zone-based conversion on the client not including support for "Europe/Ulyanovsk". In order to work around this, if the operator time zone is "Europe/Ulyanovsk" it will be handled as "Europe/Samara" in the pzpega_ui_formatDateTime.js file.
SR-C40604 · Issue 378650
File Listener variable modified to resolve authorization exceptions
Resolved in Pega Version 8.1
An authorization exception was generated while running File Listener. This error was traced to a situation where the variable mEvaluateAuthorizationCheck was getting modified by more than one listener at the same time, and has been resolved by changing mEvaluateAuthorizationCheck from a static variable to an instance variable.
SR-C40673 · Issue 383958
Validation checks added to catch upgraded Application Rules with invalid characters
Resolved in Pega Version 8.1
When a system has been upgraded from 7.2 to Pega 7.4, the Application Rule created in 7.2 can inherit characters that are invalid in Pega 7.4 such as ":". These invalid characters result in exceptions being thrown on every rule. In order to better handle this difference, the system will now validate on 'New' and 'Save As' according to the current standard of "starts with a letter and can contain letters, ampersands, numbers, underscores, and dashes".
SR-C40759 · Issue 385658
Hover event works for modal text area
Resolved in Pega Version 8.1
A Hover event was not working in modal dialog on a text area or text input. If a link was placed then the issue did not happen. This was traced to the console being unable to get the property showsmartinfo because it was of undefined or null reference, and the shouldIncludeSIScript method has been updated to include text input and text area in ControlsInfo to correct this.
SR-C40884 · Issue 378655
Check added for button labels using keyboard access key markup
Resolved in Pega Version 8.1
If a button label was configured with a keyboard shortcut in nontemplate mode, the action string was not getting generated properly. This was due to the button label using access key mark up, and has been fixed by adding a check.
SR-C41067 · Issue 382608
Number type conversion from DSMClipboardPage matches platform page
Resolved in Pega Version 8.1
The DSMClipboardPage implementation behaved differently than the platform page regarding converting numbers to decimal and when rounding took place. To correct this, the behavior of number type conversion from DSMClipboardPage has been aligned with the behavior from the platform page by calling an API provided by the platform.
SR-C41076 · Issue 379073
Mobile buttons revised to workaround iOS browser click bug
Resolved in Pega Version 8.1
When using the iOS browser, buttons were getting stuck or frozen and requiring multiple clicks to execute. This was traced to an error in the iOS browser version 11.4 where click events are triggered with event.timeStamp as a negative number. To avoid this, the system will not rely on event.timestamp, but will instead get the current datetime and maintain it in prevEvent object.
SR-C41426 · Issue 378692
Resolved survey userscript JS error on mobile logoff
Resolved in Pega Version 8.1
A JS error was being generated from survey_ui_userscript_offline.js when logging out of the mobile application. This was caused by a missed null check for the QPREFPage before referencing property on it, and has been fixed.