SR-D10855 · Issue 485681
Improved security for DSM Scorecard
Resolved in Pega Version 8.4
Security against remote code execution has been added for the rule Scorecard in DSM.
SR-D11655 · Issue 511426
JMS Listener modified to ensure connections are closed after encountering an exception
Resolved in Pega Version 8.4
JMS listener logs were detailing exceptConnection leaks with the message " J000100: Closing a connection for you. Please close them yourself". Investigation showed that when the JMSListener is configured for JBOSS, it goes via EngineImpl. However, connections opened during engineimpl.ivokeEngine were prevented from closing if they encountered an exception. To resolve this, the execution of the connection close command has been moved to the finally block.
SR-D13886 · Issue 490616
CORS error logging improved
Resolved in Pega Version 8.4
In order to facilitate error resolution, logging has been enhanced for CORS denial errors.
SR-D14159 · Issue 493083
Toggle added for displaying exception stack trace
Resolved in Pega Version 8.4
When text like "%25" was added to the login URL, the full exception stack was displayed on the screen. To resolve this, when the prconfig 'initialization/displayexceptiontraceback' is set to false (default value), the system will render the status.jsp instead of error.jsp and will not populate any sensitive data in the request object. If its set to true, the system will fall back to the old approach which renders error.jsp and emits the stacktrace.
SR-D14601 · Issue 490632
Unique ID generation added for simultaneous multiple text area boxes
Resolved in Pega Version 8.4
In the Interaction portal, adding a task for a interaction using a form with a character-count enabled text area worked as expected when the interaction first opened a task with the character counter text area. However, if a second version of the same task was opened before the first task was completed, the second text area was not responsive or working as expected. This was traced to the system generating the same ID attribute for both instances of the text area character counter span, and has been resolved.
SR-D15910 · Issue 495124
AM/PM time setting corrected for Riyadh timezone
Resolved in Pega Version 8.4
When logged into the Pega mobile application with operator locale as ar_AR and timezone as Asia/Riyadh, selecting time as PM resulted in it being set to AM with Native control. If the native control was unchecked, a blank screen resulted. This has been corrected.
SR-D16624 · Issue 512128
Table layout filter popover position corrected for Pega mashup
Resolved in Pega Version 8.4
When using an exposed harness with table layout using Pega web mash up, the mash up worked but the apply and cancel buttons were not visible when any column was clicked to filter the result. This was traced to the filter popup having a hardcoded position offset set in its div element, and has been resolved by delegating the responsibility of the filter popover height calculation to the popover.
SR-D17973 · Issue 490495
Corected parameter mismatch to allow deletes to be added to history
Resolved in Pega Version 8.4
Pega was not keeping track of a property if it was deleted from the data explorer tab, resulting in not being able to restore the deleted property. This was traced to a parameter mismatch: the Delete API adds the Memo parameter to the history, but while DeleteRecord accepted the Memo parameter, DeleteRecordInner accepted the HistoryMemo parameter. Because the parameters names were different, they were not propagated to the API. This has been corrected by setting the param.memo so that Rule-Delete API adds the history and the rule gets displayed correctly in recently deleted rules.
SR-D18234 · Issue 499028
Updated backwards compatibility for custom date/time wuith extra text
Resolved in Pega Version 8.4
After upgrade, migrated extra text in the custom date format was causing confusion. The previous support of additional text on earlier versions was not intentional, but was allowed by the previous default of non-template mode. In template mode, when custom datetime format includes plain text in single quotes, pega.ui.Formatter.formatDateTime processes the entire format string instead of only the datetime formats. To avoid confusion, updates have been made so if a custom format has plain text in quotes, the system will separate the formats and resolve them.
SR-D18853 · Issue 503276
Visibility on client check removed to enable Pulse on click
Resolved in Pega Version 8.4
When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue.