SR-B89567 · Issue 340261
Logic reworked for case advancement
Resolved in Pega Version 7.4
The logic in function pega.process.engine.canAdvance was incorrectly calling pega.process.caseType.getNextTask before running the execPostProcessHook or the subFlowPostProcessHook functions, leading to missing properties needed by the decision shapes in the flow. This has been fixed.
SR-B89621 · Issue 336849
Abstract Push Engine logic fixed for passing portalname
Resolved in Pega Version 7.4
The error "AbstractPushEngine ERROR - Portal Name could not be retrieved from request" was being logged every 15 seconds. The JS layer was passing the request parameter, but the logic in AbstractPushEngine.validateRequest() was mistakenly reading it using the getHeader() method rather than getParameter() method. This has been corrected.
SR-B89621 · Issue 328119
Abstract Push Engine logic fixed for passing portal name
Resolved in Pega Version 7.4
The error "AbstractPushEngine ERROR - Portal Name could not be retrieved from request" was being logged every 15 seconds. The JS layer was passing the request parameter, but the logic in AbstractPushEngine.validateRequest() was mistakenly reading it using the getHeader() method rather than getParameter() method. This has been corrected.
SR-B89625 · Issue 342129
Clipboard clears on form submit, plus performance improvements
Resolved in Pega Version 7.4
Progressing through an application questionnaire was causing clipboard size to increase without being cleaned. This was due to a page clearing request not being triggered, and the harnessonbeforeunload method has updated to trigger pyDeleteDocumentPg on submission of the form in topnavigation portal. In addition, performance improvements have been made to this process.
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.