SR-B89698 · Issue 336758
Timeline control shows in Microsoft Internet Explorer 11
Resolved in Pega Version 7.4
The Timeline Control was not showing in Microsoft Internet Explorer 11, instead displaying an error message in the console saying 'tzdetect is undefined'. This was due to some unsupported syntax in Microsoft Internet Explorer that has now been fixed.
SR-B90954 · Issue 339632
Assembly errors sent to PDC and AES
Resolved in Pega Version 7.4
A large number of com.pega.pegarules.pub.generator.UnresolvedAssemblyError exceptions were found in the PegaRULES logs with no corresponding data in PDC-Central. LogHelper methods take a Throwable as an argument to trigger an alert, and Pega7 exceptions are supposed to generate EXCP0001 alerts which are sent to PDC. However, a review of EXCP0001's show that there were no messages for com.pega.pegarules.pub.generator.UnresolvedAssemblyError -- thus the exceptions were never sent to PDC and there was no visibility to system managers. This issue also occurred with AES. To correct this, a Throwable argument has been added in oLog.error() at all the places where this alert was needed.
SR-B91057 · Issue 347833
Improved handling for static content filename errors
Resolved in Pega Version 7.4
Changes have been made to better handle FileNotFound exceptions during static content requests and send a generic error message to the client when a filename has a dot but no extension.
SR-B91077 · Issue 338569
Added locking default for PegaFS-Data-ProductType-IRA data instance
Resolved in Pega Version 7.4
When running the prpcServiceUtils script to perform a rollback action, a lockGoneException was generated on a particular PegaFS-Data-ProductType-IRA data instance. Acquiring a lock is not required for all classes: it is required only for classes which should be locked before opening. As it may not be obvious that this instance requires such a lock, the importinstancedeleter class code has been modified to open this instance with a lock.
SR-B91143 · Issue 341708
Support added for customizing appender names
Resolved in Pega Version 7.4
In order to support more customization, the method used to check for default appenders has been modified in some rules. Previously, there was explicit code to check for the appender type instead of the appender names. To make those rules more robust, the system will now check on the appender names instead of the types in the following 3 rules: @baseclass.LogFileDownload @baseclass.MyAlerts @baseclass.LogViewer Within these rules, appender names will be checked instead of appender type.
SR-B91355 · Issue 342172
Enhanced Ajax recovery code
Resolved in Pega Version 7.4
The code leading up to the (optional) call to AjaxRequestFail has been updated as follows: 1. The "responseObject" created in the method pega.util.Connect.handleTransactionResponse will also contain the value of httpStatus. 2. An "if" clause has been added to targetAsyncRequest that will reset the counter which controls how many retries occur before giving up if the call experiences yet another error before refreshing the entire screen.
SR-B91390 · Issue 340706
SOAP decimal values retain expected format
Resolved in Pega Version 7.4
After upgrade, the integers returned by SOAP Service were mapped as scientific notation instead of decimal properties on Clipboard. For example, the number 1000000001 that was previously mapped as 1000000001 became 1.000000001E9. This was an unexpected behavior change related to a mapping modification that considered the property type and converted the value based on the property type: in this case, the system conversion caused a doubling of value which was then expressed as exponential value because of its length. This has been corrected.
SR-B91390 · Issue 342708
SOAP decimal values retain expected format
Resolved in Pega Version 7.4
After upgrade, the integers returned by SOAP Service were mapped as scientific notation instead of decimal properties on Clipboard. For example, the number 1000000001 that was previously mapped as 1000000001 became 1.000000001E9. This was an unexpected behavior change related to a mapping modification that considered the property type and converted the value based on the property type: in this case, the system conversion caused a doubling of value which was then expressed as exponential value because of its length. This has been corrected.
SR-B92216 · Issue 346332
Unable to resolve source property error level now set to WARN
Resolved in Pega Version 7.4
The log message 'Cannot resolve source property for..' indicates that the system is unable to resolve the source property and needs attention to investigate the reason why. Previously, this had the log level as ERROR. The log level has now been changed to WARN.
SR-B92456 · Issue 342339
Dynamic setting added for setting ElasticSearch backup path
Resolved in Pega Version 7.4
ElasticSearch has a built-in 'snapshot and restore' mechanism which allows for the backup of ElasticSearch. In order write backups to a shared filesystem, it is necessary to first to set the ElasticSearch setting "path.repo" to the path (or parent path). In order to facilitate this, a new dynamic system setting has been added for setting "path.repo" during initialization of elastic search node.