SR-D21569 · Issue 491705
PUT and WHEN support added for REST
Resolved in Pega Version 8.4
Data layer rules in Pega were not getting generated through the Wizard- ‘Create Rest Integration’ when invoking the Rest service though the PUT method. This has been resolved by adding support for PUT and DELETE in pypresentdatapageoptions.
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-D25278 · Issue 499449
Enhanced logging for Clipboard JSON Deserializer
Resolved in Pega Version 8.4
An enhancement has been made to introduce a number of logger events to the Clipboard JSON Deserializer in order to have sufficient data to diagnose any issues encountered.
SR-D26913 · Issue 500208
Decision Table support added to customize MIME types
Resolved in Pega Version 8.4
ExtensionMimeDetector uses the Pega internal libraries property file "mime-types.properties" to return the MIME type. In order to facilitate customization such as a third party filenet system for processing that utilizes different MIME types, an override mechanism has been provided per file extension via a Decision Table for overriding the Pega defaults.
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.