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.
SR-C68219 · Issue 406591
Customizable extension points added to Work-.CorrAttach
Resolved in Pega Version 8.2
In order to support the use of custom properties on Link-Attachment instances when correspondence is sent and attached to the case, extension points have been provided for pyDefault data transform in the activities Work-.CorrAttach.
SR-C68901 · Issue 411286
Multiple fixes made to handleXThreadChanges to resolve IE11 latency for opening cases/assignments
Resolved in Pega Version 8.2
After upgrade there was a performance issue with IE11 when opening a case from the search box or opening the assignments, and alerts were triggered from PDC indicating "ClientPageLoad has exceeded the elapsed time". This was caused by IE stopping the triggering of requests until a client processes was done, causing increased latency when compared to using Chrome. To resolve this, multiple fixes have been made to the handling for handleXThreadChanges in setTimeout.
SR-C65690 · Issue 405920
Currency Code updated for new Venezuela VES designation
Resolved in Pega Version 8.2
The currencycodes.xml file has been updated to reflect the recent decision by the Central Bank of Venezuela to change the Venezuela Currency code from 937(VEF) to 928(VES).
SR-C74954 · Issue 413139
Fixed column search function for Report Browser Data Explorer
Resolved in Pega Version 8.2
Searching/filtering for columns in the Data Explorer in the Report Browser was not filtering the tabs by the search string. This was an error caused by the unique ID changes for controls, and has been fixed by updating the getSearchTextElement() function in pega_report_events.js to use the name attribute rather than the ID attribute to identify the search bar. The tabClickCallback() has also been updated to not rely on window.event as it was causing discrepancies in Safari.
SR-C65748 · Issue 411169
Multiple fixes made to handleXThreadChanges to resolve IE11 latency for opening cases/assignments
Resolved in Pega Version 8.2
After upgrade there was a performance issue with IE11 when opening a case from the search box or opening the assignments, and alerts were triggered from PDC indicating "ClientPageLoad has exceeded the elapsed time". This was caused by IE stopping the triggering of requests until a client processes was done, causing increased latency when compared to using Chrome. To resolve this, multiple fixes have been made to the handling for handleXThreadChanges in setTimeout.
SR-C75099 · Issue 413432
Improvements made for the stability and reliability of the stream tier
Resolved in Pega Version 8.2
Several enhancements and fixes have been made to improve the stability and reliability of the stream tier with a focus on rolling restart. Issue 410567: When a stream node shuts down, it takes up to a minute for all client nodes to recognize the event and failover to other nodes due to large default timeouts. Timeouts have now been reduced to allow nodes to failover much earlier. Issue 413375: When a stream node shuts down, other stream nodes are notified and attempt to discover the new cluster topology. Since the cluster is still in flux, this operation may take a long time blocking all producers until a new topology is determined. This procedure has been changed to be less heavy and make the discovery only if required. Issue 401326: Kafka (running as a separate process as part of the Stream services) generates log files, but does not use log rotation with a maximum amount of log files. This means that the log files will eventually fill up the disk, leading to failures of the service and PRPC instance running on the same disk. To resolve this, the system will now limit number of generated log files to prevent high disk usage by using the parameters of file size = 2 MB and a max nr of size = 10. Issue 410280: A large number of "Processing override for entityPath" entries were seen in the Kafka logs. This has been addressed by ensuring message.timestamp.difference.max.ms is set to equal to retention.ms. In addition, the system will properly compare the Kafka Configuration created for the entire topic and the configuration retrieved for Partitions so the configuration is not unnecessarily updated. Issue 414765: During stream node restart, decision hub nodes may block for 15-30 seconds when writing to a stream data under certain conditions. This can cause high response times for a small period. This has been addressed by updating stream dataset logic to handle stream tier restarts properly and not cause response time degradation. Issue 401093: HttpMessageDecoder was throwing an exception regarding “TooLongFrameException” causing a 502 on HTTP stream tier requests going over 8192. The default max header size used by stream data set REST service was 8KB. In this particular case, the HTTP header contains a lot of cookies and other meta-info and exceeds 8KB. To resolve this, the default max header size has been increased to 16KB. A new prconfig setting to control max header size has also been introduced.
SR-C55452 · Issue 399480
oLog.infoForced has been replaced with oLog.debug in GetAssignmentDetailsInternal to reduce excessive logging
Resolved in Pega Version 8.2
The Rest API used by Robotics was generating excessive logging on the application server due toPzGetAssignmentDetailsInternal generating several lines of logs with each REST call. In a high volume system, this can make the logs difficult to utilize. To resolve this, oLog.infoForced has been replaced with oLog.debug.