SR-C40033 · Issue 379079
Import of revision package fixed
Resolved in Pega Version 8.1
The importing of a Revision package was not working as expected, and the site was not able to import new revisions in revision management. This was an issue with incorrect property initialization causing a failure in the update of the access group when doing a rollback of the revision, and has been corrected by removing the Property Initialization in Activity pyRollOutToAllAGs.
SR-C40198 · Issue 384917
Non-English characters allowed in MQ message
Resolved in Pega Version 8.1
Connect-MQ was not allowing Russian characters for a message to the IBM MQ because non-English characters were not supported. To allow this use, the code has been updated to set headers first and then fall back to readChars method if an exception occurs.
SR-C40499 · Issue 378119
REST mobile sync updated with exception handling and more flexible page parameter
Resolved in Pega Version 8.1
Invoking REST service to do a mobile sync was failing with null pointer. Investigation showed this was caused by missing exception handling for scenarios where a hardcoded reference to pyworkpage in the function "pzHasOnlyClientPostProcessing" failed during sync. This has been corrected by modifying “pzHasOnlyClientPostProcessing” to add the needed handling as well as read the target page name from the parameter page and run the activity on it instead of using a hardcoded “pyWorkPage”.
SR-C40522 · Issue 378880
Null checks added to avoid spam with bad headers creating multiple duplicate cases
Resolved in Pega Version 8.1
Sporadically a spam email ended up creating hundreds of duplicate cases until it was removed from the inbox. This occurred when Auto Response was configured on the CITEmail listener and a case was created from the email: as the Listener failed to send out an auto response email due to the bad headers of the email, the message was not removed or marked as seen on mailbox and the Listener ended up processing it over and over. This has been resolved by adding null checks in handleStandardRequest method and sendResponseMessage method.
SR-C40574 · Issue 383240
ValidateMaxAge parameter added for MFA OTP expiry
Resolved in Pega Version 8.1
When trying to use the MFA feature via services, the max age was not honored. The Maximum age of a one-time password (OTP) token in seconds was given as '15' under security polices, but the system was allowing login to proceed without showing an expiry error when the OTP was input after the defined expiry time. To address this, the parameter ValidateMaxAge (Boolean) has been exposed as a parameter for sending OTP service to determine whether the token is short lived or long lived.
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".