SR-C40740 · Issue 408513
Improved error handling added for sync issue with malformed JSON action
Resolved in Pega Version 8.2
A sync issue with a timesheet record was preventing mileage submission. This appears to be caused by a malformed JSON action being inserted into the actions queue sent to the server, and enhanced error handling has been inserted to avoid this issue.
SR-C34802 · Issue 388490
DomainId Column size increased in Pegadata.Address table
Resolved in Pega Version 8.2
Previously, domainId (in table pegadata.p_Address ) had a column length maximum of 16 characters. This has been increased to 256.
SR-C32383 · Issue 404383
Pegacall Longpoll now supports rerty after network drop
Resolved in Pega Version 8.2
Previously, Pegacall Longpoll would not auto-connect after a network drop, although polling could be restarted by refreshing the browser. Retry support has now been added to Longpoll.
SR-C61477 · Issue 418265
HTML conversion added to email IVA
Resolved in Pega Version 8.2
When sending through emails that are in HTML format, HTML tags were visible within the Analysis of the email under Entities. These tags also potentially had an impact on topic detection, as the same email sent through in HTML would be classified under a different topic from one sent through as Plain Text.This issue originated because Email IVA received text as HTML while it expected plain text without HTML tags, and was traced to the use of an IMAP setting which sends only HTML to the listener. This has now been fixed such that If any HTML is received by email IVA, it will be converted to plain text via JSoup APIs in the service method as the first step.
SR-C79142 · Issue 417678
HTML conversion added to email IVA
Resolved in Pega Version 8.2
When sending through emails that are in HTML format, HTML tags were visible within the Analysis of the email under Entities. These tags also potentially had an impact on topic detection, as the same email sent through in HTML would be classified under a different topic from one sent through as Plain Text.This issue originated because Email IVA received text as HTML while it expected plain text without HTML tags, and was traced to the use of an IMAP setting which sends only HTML to the listener. This has now been fixed such that If any HTML is received by email IVA, it will be converted to plain text via JSoup APIs in the service method as the first step.
SR-C44297 · Issue 397534
XSS filtering added to RTE control
Resolved in Pega Version 8.2
The system has been updated to close a vulnerability with RTE where an authenticated application user could potentially inject an XSS payload into the Case Notes section for later execution.
SR-C65032 · Issue 407952
XSS filtering added to RTE control
Resolved in Pega Version 8.2
The system has been updated to close a vunerbility with RTE where an authenticated application user could potentially inject an XSS payload into the Case Notes section for later execution.
SR-C55574 · Issue 407191
Mashups reload properly after authentication timeout
Resolved in Pega Version 8.2
When using a Mashup and a Pega AuthService that uses Pega Timeouts, the mashup did not reload properly if there was a Pega Timeout. This was traced to the system not honoring auth timeout for activities that don't need authentication, and has been fixed.
SR-C34235 · Issue 392563
Clarifications added for PDF rendering when using default values
Resolved in Pega Version 8.2
A visibility condition has been added in pzGeneralTab_ControlProps to hide the default value when .pyEditOptions value is "Read-only-always". In addition, the documentation has been updated to reflect that when default value is configured, it will be applicable only if the control renders in editable mode. If the control is editable and the property value is empty on the clipboard, the default value will be set on clipboard.
SR-C64783 · Issue 407087
Corrected handling for SAML logoff
Resolved in Pega Version 8.2
On SAML logoff, the error "There has been an issue; please consult your system administrator; Status:fail ... No certificate found in truststore" appeared. Investigation showed this was an issue with the aliasing of certificates and signing that led to the requestor not being terminated for that logoff response. To correct this, when Pega receives a logout request which is invalid, it will terminate the session instead of throwing a PRRunTimeException.