SR-D41228 · Issue 512107
DSS added to Request Only Connect SOAP for Robust
Resolved in Pega Version 8.2.5
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-D42406 · Issue 510669
Support added for UTF-8 charset in Connect-REST pyRequestAttachmentPage
Resolved in Pega Version 8.2.5
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.
SR-D42824 · Issue 517010
Warning logged for encrypted email with missing local keystore
Resolved in Pega Version 8.2.5
The Email Listener was becoming stuck while processing encrypted email if the related keystore was not configured within the Pega application. Encrypted mail was not marked as read/deleted, causing the system to attempt to process it again and then repeat the attempt. To address this, a check has been added that will mark the mail as completed for system purposes under this condition, and will log a message to clearly state that the mail was marked as read/deleted but not actually processed due to invalid keystore details.
SR-D43918 · Issue 511182
Resolved duplicate task urgency
Resolved in Pega Version 8.2.5
Duplicate task urgency was displayed when using dynamic layout in non-template mode. Investigation showed that there were three 'when' rules used to display the task urgency based on an urgency value, and two of the 'when' rules were being returned as true, one of which was incorrect. This was due to an incorrect PropertyReferenceImpl object being passed when retrieving the value from the failSafe page because of an incomplete reference, and has been fixed.
SR-D44184 · Issue 511444
ValueList/Group correctly appears on clipboard
Resolved in Pega Version 8.2.5
After upgrade the property of type ValueList/Group was missing from the clipboard. This was traced to an extra 'when' rule applied on the visibility of Layout-2 in final section pzProperty (Pega-Desktop:08-02-01), and has been corrected.
SR-D44215 · Issue 512191
Navigation Breadcrumb honors pyDisplay in navigation link subflows
Resolved in Pega Version 8.2.5
After configuring a sub process (screen flow) inside a screen flow connected by a decision shape having a fork condition, the Navigation breadcrumb for this subprocess was always visible irrespective of the connector when condition. This was traced to pyDisplay not being considered for subflows while building navigation links, and has been resolved.
SR-D44809 · Issue 511806
Allowed Property Exceptions will be logged as DEBUG
Resolved in Pega Version 8.2.5
The Logger was printing an ERROR message when evaluating a declarative expression. By design, declarative expressions throw a MissingProperty exception if fetched without the source value present, but this can cause excessive logging on a system where this condition is allowed and expected. In order to support flexible use for this scenario, the system has been updated so that the log level will be switched from ERROR to DEBUG when MissingPropertyExceptions are allowed. Logging will remain as ERROR if exceptions are not allowed.
SR-D46159 · Issue 510971
Reinitializing Full Text Search will shut down Elastic Search regardless of search initialization status
Resolved in Pega Version 8.2.5
Pega search was only sporadically working after converting from standard sandbox-marketing to largesandbox-marketing. This was traced to the Full-Text Search initialization having failed on the app-tier node during re-initialization. As part of re-initialization, the existing node is shut down and the Elastic Search node is started. The shutdown process relied on a boolean flag which indicated if the current status of full-text search initialization was successful. In this case, ES was trying to validate all the cluster level settings, for every save of one of the cluster level settings, but could not due to topology changes in the Util Tier node. The boolean flag indicated initialization had failed so the shutdown process was not invoked, yet the system was attempting to start the second instance of an ES node on the same machine. To resolve this, the shutdown FTS code has been modified to shutdown ES regardless of the search initialization status.
SR-D47752 · Issue 513751
Resolved Assembly time error for findPage signatures with two arguments
Resolved in Pega Version 8.2.5
Due to the introduction of IL assembly, an Assembly time error was generated after upgrade when saving a 'when' rule that had a page with the same name defined in both Parameters and Pages & Classes. To resolve this, if the system is generating PegaAPI#findPage or PegaAPI#findPageWithException and passing a null as the second argument, then it will be cast as a String. This will ensure the compiler will not become confused as to the type of null when there are multiple findPage signatures with two arguments.
SR-D48248 · Issue 517238
Cross-site scripting filtering added to URLs
Resolved in Pega Version 8.2.5
Cross-site scripting filtering has been added to prevent the injection of a script into a URL using ViewXML.