SR-D27527 · Issue 504283
Corrected schema import permissions
Resolved in Pega Version 8.2.4
When a product rule contained schema changes to add columns for properties that already existed, such as properties that were exposed since the previous ruleset, it incorrectly indicated that there were no changes to be applied. This was traced to the operator lacking the SchemaImport permission, and has been corrected.
SR-D28719 · Issue 505967
Null archive check added to set import process status
Resolved in Pega Version 8.2.4
After running a 'prpcServiceUtils.sh import' which failed due to a low-level null pointer error, the job "IMPORTREQUEST-2" then incorrectly showed the status as 'IN PROGRESS' instead of 'FAILED'. In this case, the null pointer exception occurred because two imports were unintentionally happening at the same time: the process copied up the same set of archives to the service export directory, but the first import processed an archive and deleted it so that the second process failed to find it. When it exited with the null pointer exception, the status was not set to 'failed'. To resolve this, a null archive check has been added which will set the status to 'failed' if the archive is unsupported, corrupt, or not there at all.
SR-D20439 · Issue 496404
Hotfix hashmap cleanup improved
Resolved in Pega Version 8.2.4
A DL installation failed with an out-of-memory error. It was observed that many CacheEntry(VersionedJdbcJarRwader.java) hashmaps were being created to store the details for each hotfix but that were then never cleared. This has been resolved by adding the finally block in CodeImportProcessImpl.java class to call the shutdown method for proper cleanup. In addition, the default command line utility (prpcUtils) has been updated to use JVM settings of Xmx 4GB and capture a heap dump if an out-of-memory error is encountered. The auto-generated prconfig.xml has also been updated to leverage its minimal startup setting which will avoid loading the conclusion cache into memory.
SR-D39491 · Issue 506025
Logic trimmed for better Listener performance
Resolved in Pega Version 8.2.4
After multiple email listeners with Data indexing were enabled, the FTSIndexer queue was filling with Email Listener instances. Investigation showed that although Listener Management has logic for updating the last access time of all listeners by using APIs, the Email Listener was explicitly opening the email listener rule to update the last access time every time it was run. This has been corrected.
SR-D41229 · Issue 507176
Resolved slowness in retrieving case attachment from AWS
Resolved in Pega Version 8.2.4
Attempting to open a case attachment caused the application to slow over time and eventually became unresponsive. Restarting the Tomcat nodes improved the response time. This was traced to a null Buffered Input Stream not being closed correctly when using AWS, and has been resolved by adding the needed logic to PegaGadget-Pulse.pzStorageAttachSelectedFile. In addition, enhanced logging has been added to Embed-Repository-S3.pyGetFile. Additional enhancements for this issue will be included in a future release.
SR-D36715 · Issue 507456
Resolved slowness in retrieving case attachment from AWS
Resolved in Pega Version 8.2.4
Attempting to open a case attachment caused the application to slow over time and eventually became unresponsive. Restarting the Tomcat nodes improved the response time. This was traced to a null Buffered Input Stream not being closed correctly when using AWS, and has been resolved by adding the needed logic to PegaGadget-Pulse.pzStorageAttachSelectedFile. In addition, enhanced logging has been added to Embed-Repository-S3.pyGetFile. Additional enhancements for this issue will be included in a future release.
SR-D36704 · Issue 504808
Repaired Pega validation report
Resolved in Pega Version 8.2.4
The Pega Usage validation report was not working. This was traced to the UVO O/P file having a null value and not containing any data regarding the environment daily usage. This has been corrected by updating the java used in getElementsByTagName.
SR-D40523 · Issue 505926
Corrected Pega-Perf cookie adding double quotes
Resolved in Pega Version 8.2.4
After upgrade, issues were seen with mashup not loading properly. In addition, a region in the environment was not able to access the developer portal. This was traced to an issue with pzPega_ui_statetracking.js, which handles adding the Pega-Perf cookie, adding a cookie with double quotes to HTTP requests. The double quotes have been removed to resolve this issue.
SR-D36335 · Issue 504333
Post Value action properly displayed in upper case after validation
Resolved in Pega Version 8.2.4
After upgrade, if a property with Edit Input toUppercase was created and placed it on a section where the text input has Post Value on Change, validating the uppercased property on the clipboard resulted in the non-uppercase value displaying on the screen. This was traced to the target element with the response value not being updated with the server response for the post value action. Only the attribute value was updated, which is not shown to the user. In order to properly display the value, logic has been added to update the target element value with the response value.
SR-D20423 · Issue 503444
Improved upgrade handling for tables using classes with property references
Resolved in Pega Version 8.2.4
After upgrade, some page property values were blank and exposed database columns did not contain the values. Investigation showed that the reference properties did not have context and hence column population was not able to determine their value. To resolve this, instead of doing column population for all the columns, the system will identify classes that have property references and that are being optimized as part of upgrade process and maintain a list of specific columns to update.