SR-D27307 · Issue 503758
Jcraft libraries updated
Resolved in Pega Version 8.4
The JCraft libraries have been updated to resolve an intermittent FTP connection issue.
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-D30505 · Issue 501896
Revalidate and save works for Service Packages using OAuth2.0
Resolved in Pega Version 8.4
Revalidate and Save was failing for service packages of type Data-Admin-ServicePackage which used authentication type as OAuth2.0 . If this was modified to basic authentication / unchecking authentication, revalidate and save was successful. Historically, the implementation of pzOnlyRestServiceType always assumed the primary page was the Service Package rule itself. To support this alternate use, the logic has been updated and a check of the Service Type has been added for the pxResults of the data page.
SR-D34532 · Issue 506353
SMTPUserID derivation logic updated to handle O365 format
Resolved in Pega Version 8.4
After email accounts were changed to point to Office365, the SendEmailNotification activity threw an exception with the error "javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful". Running the SendSimpleEmail activity with the same details worked as expected. This was due to how SmtpUserID is derived from FromUsername parameter: if FromUsername is empty, the system will try to derive SMTPUserID using the 'From' address by trimming it up to the '@' character and using that. This worked well with Gmail or Outlook accounts which have '@' followed by the domain name, but in O365 the format is generally along the lines of "[email protected]". This led to the authentication error. To resolve this, the logic used to assign the SMTPUserID from the email address has been updated in the EmailAccountUtility.java .
SR-D36704 · Issue 504809
Repaired Pega validation report
Resolved in Pega Version 8.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-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-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.