SR-D45622 · Issue 521662
Sorting on Grid works with declare expression property
Resolved in Pega Version 8.4
If a property with a declare expression was used in a column, the sorting on that column was not working. This was traced to reference errors when Grid used the engine API pega.sortPageList to sort the page list / data page, and has been corrected.
SR-D47752 · Issue 513752
Resolved Assembly time error for findPage signatures with two arguments
Resolved in Pega Version 8.4
Due to the introduction of IL assembly, an Assembly time error was generated after upgrade when saving a 'when' rule that had a page with the same name defined in both Parameters and Pages & Classes. To resolve this, if the system is generating PegaAPI#findPage or PegaAPI#findPageWithException and passing a null as the second argument, then it will be cast as a String. This will ensure the compiler will not become confused as to the type of null when there are multiple findPage signatures with two arguments.
SR-D48960 · Issue 517880
Exception stack trace will be included as comments in generated assembly code
Resolved in Pega Version 8.4
When there is an exception during assembly time, that original exception message is assembled in the generated code. To improve the process of finding the the root cause by examining the original exception stack, the system has been updated to insert the original exception stack trace into the generated code as comments.
SR-D50016 · Issue 515904
Exception stack trace will be included as comments in generated assembly code
Resolved in Pega Version 8.4
When there is an exception during assembly time, that original exception message is assembled in the generated code. To improve the process of finding the the root cause by examining the original exception stack, the system has been updated to insert the original exception stack trace into the generated code as comments.
SR-D50528 · Issue 514133
Exception stack trace will be included as comments in generated assembly code
Resolved in Pega Version 8.4
When there is an exception during assembly time, that original exception message is assembled in the generated code. To improve the process of finding the the root cause by examining the original exception stack, the system has been updated to insert the original exception stack trace into the generated code as comments.
SR-D51536 · Issue 515067
Holdability flag set on connection for using MS SQL in Designer Studio
Resolved in Pega Version 8.4
Static assembler was not working from Designer Studio, displaying the error "com.microsoft.sqlserver.jdbc.SQLServerException: SQL Server supports holdability at the connection level only. Use the connection.setHoldability() method." Investigation showed that ApplicationAssembly.getResultSetForQuery explicitly sets the holdability flag on the prepared statement, and this issue has been resolved by updating the system to set the holdability flag on connection as well.
SR-D51725 · Issue 516468
DSS added to rpevent logging of sensitive data used as input during async batch task processing
Resolved in Pega Version 8.4
When running Async Batch Task Processing, the whole set of inputs was logged when an error occurred during ADP load. Because this might result in sensitive data such as SSN, DOB, IDs, etc, being included in the debugging output, a DSS has now been added which when set will avoid printing any sensitive information in the log.
SR-D53253 · Issue 515309
Versioning information removed from Universal SMA
Resolved in Pega Version 8.4
To clarify that Universal SMA is compatible with Pega 7.4 and all below versions, the repository name has been changed to remove the versioning number so it is listed as only "Universal SMA".
SR-D53674 · Issue 515625
Stack traces will be logged if debug is enabled
Resolved in Pega Version 8.4
The error logging in com.pega.pegarules.exec.internal.declare.DeclareChangesHelperImpl#onSave was causing an issue with upgrades in MT environments due to excessive logs being thrown from the onSave method in DeclareChangesHelperImpl. These errors are logged when there is a database exception during System declare changes generation during onSave, and in a multiple tenant environment it resulted in Out of Memory exceptions because of logging stack traces. To resolve this, the system has been updated so that stack traces will only be logged when debug logs are enabled.
SR-D57855 · Issue 521126
Context retained during nested automation
Resolved in Pega Version 8.4
Issues were seen with context being passed correctly with automation. When a Data Page that was used to abstract the call to a REST API used a Data Transform which in turn used a Data Page which also used a call to a REST API to retrieve an OAuth Token, an error appeared. The same worked when a URL was provided on the Connect REST. When a service case was launched but a Flow Action wasn't submitted, then another service case was added and submitted, the post-processing robotic automation activity used the run robotic automation activity from the previous service case instead of the current service case targeted for completion. This has been resolved by updating the webwb • pzpega_ui_doc_submit.js file to pass the correct MDIContext based on the event target of FA submission while invoking RDA automation.