SR-D38144 · Issue 509380
MQ listeners will not start before the node is ready
Resolved in Pega Version 8.4
If there were messages in an MQ queue during a JVM recycle, the MQ listeners would start and pull the messages from the queue prior to the application being fully available. This resulted in an error message in the logs and the MQ messages were lost. This was due to the requestor context being stale because the Listener was started but the node was not, and has been resolved by adding a check to ensure the MQ Listener will not start to process until the node has started.
SR-D39060 · Issue 526982
Rest connector supports extended chars in attachments
Resolved in Pega Version 8.4
When the pyRequestAttachmentPage clipboard page was populated with a file name that contained Latin supplemental 1 unicode characters (decimal values 160 to 255 - for example an umlaut), any extended characters were being converted to question marks (?) before the call was sent, causing the web service call initiated by Pega to fail. To better support this use, an enhancement has been added to support a multipart request with extended characters in the file name. This allows the pyRequestAttachmentPage to specify pyFileNameExtendedChars, allowing RFC 6532 mode to be toggled for multipart requests with attachments. This mode allows for UTF-8 encoding in the attachment file name header, rather than the default ASCII encoding.
SR-D39491 · Issue 506020
Logic trimmed for better Listener performance
Resolved in Pega Version 8.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-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-D40883 · Issue 511124
Updated SendEmail shape to remove newline code from the subject line
Resolved in Pega Version 8.4
When using the SendEmail shape to send outgoing email, the message contained HTML tags on the subject line that caused it to be split and copied into the email body. This has been resolved by updating PegaEmailClientImpl.prepareMessage() to replace new line characters with spaces in the subject.
SR-D41228 · Issue 512108
DSS added to Request Only Connect SOAP for Robust
Resolved in Pega Version 8.4
After upgrade, creating a new SOAP integration set to "Request only" in the Service tab and then running the activity showed requests coming with no response, then failure after three tries. This was traced to previous changes made to support Robust behavior and log failed asynchronous calls, and has been resolved by modifying the Robust support and moving it to a DSS. If “EnableRequestOnlyFaultMapping” is set to “true”, then the ANON_ROBUST_OUT_ONLY_OP option will be used; otherwise, the default behavior will be ANON_OUT_ONLY_OP.
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.
SR-D41229 · Issue 513590
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.4
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D42380 · Issue 515002
Draft mode switched off for pzCreateNew flow
Resolved in Pega Version 8.4
After upgrade, the Connect SOAP wizard (Configure -> Integration -> Connectors -> Create SOAP Integration) would not open. Analysis found that pzCreateNew flow [Class: Pega-DataModel-DataSources-SOAP and Ruleset: Pega-IntegrationArchitect:08-01-01] had draft mode on, causing the issue. There was a workaround of doing a private edit of pzCreateNew flow, but this issue has now been corrected by switching off the Draft mode.
SR-D42406 · Issue 510670
Support added for UTF-8 charset in Connect-REST pyRequestAttachmentPage
Resolved in Pega Version 8.4
When using Connect-REST with pyRequestAttachmentPage, Polish characters like "ó" or "ł" were converted to "?". This did not happen when pyRequestAttachmentPage was not used. This was due to the post request body using a multipart handler that ignored the charset being passed in and considered it a respective enum type for Application/json internally instead. This has been resolved by adding support for charset UTF-8.