SR-D48010 · Issue 514983
Unit testing validation relaxed for external input strategy
Resolved in Pega Version 8.4
When trying to test a strategy, the testing transform had to exist in the same ruleset/version as the strategy or it would not resolve. Investigation showed that because the artifacts were in a different ruleset and version build on top of the application that the testing strategy belongs to, validation failed because it was using the platform based ruleset validation. This was a missed use case, and has been resolved by relaxing the validation for external input strategy so it does not take into account the ruleset and version of it. This same change has been applied for referenced data transforms.
SR-D51353 · Issue 516914
Unit testing validation relaxed for external input strategy
Resolved in Pega Version 8.4
When trying to test a strategy, the testing transform had to exist in the same ruleset/version as the strategy or it would not resolve. Investigation showed that because the artifacts were in a different ruleset and version build on top of the application that the testing strategy belongs to, validation failed because it was using the platform based ruleset validation. This was a missed use case, and has been resolved by relaxing the validation for external input strategy so it does not take into account the ruleset and version of it. This same change has been applied for referenced data transforms.
SR-D23881 · Issue 499693
MessageID properly set after exception encountered
Resolved in Pega Version 8.4
When SendEmailNotification was used to send an email to one valid email address and one invalid email address, the email was sent and the code generated a MessageID, but the MessageID was not included in the return parameter. Investigation showed that the MessageID setting was skipped if an exception occurred. This has been resolved by updating the code to ensure the ID is set.
SR-D29034 · Issue 500683
Added support for JSON mapping of deep nested pagelist objects
Resolved in Pega Version 8.4
An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays.
SR-D15395 · Issue 492053
Added DSS to handle BIX extracts under parse delimiter rules
Resolved in Pega Version 8.4
When parse delimiter rules were applied, the File Listener was not parsing the CSV manifest file generated from a BIX extract until the file was resaved. This was traced to a space after a comma in the extracted files, and has been resolved with the addition of a DSS which enables the use-specified delimiter to remove the space after the comma in the manifest files.
SR-D36715 · Issue 507457
Resolved slowness in retrieving case attachment from AWS
Resolved in Pega Version 8.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.
SR-D39606 · Issue 512961
SendEmailMessage Rule-Utility-Function updated so failed Send Corr messages are requeued
Resolved in Pega Version 8.4
When using "send corr" agent for sending email, failed messages were not being re-queued and no error was displayed. Logs had to be consulted to see whether the email was sent or not. To resolve this, changes have been made to the SendEmailMessage Rule-Utility-Function to handle the exceptions properly. Failed messages will go into a broken queue so they are available for retry.
SR-D41229 · Issue 507177
Resolved slowness in retrieving case attachment from AWS
Resolved in Pega Version 8.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.
INC-175595 · Issue 652831
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.7
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.
INC-211977 · Issue 713461
Handling added for large BIX Postgres data sets
Resolved in Pega Version 8.6.5
BIX extracts were causing timeouts or JVM out of memory errors. This was traced to the Postgres JDBC driver ignoring fetch size in auto-commit transaction mode, which led to everything being loaded into memory at once. To resolve this, changes have been added to support fetch size for large results when using PostgreSQL database for BIX Extraction.