INC-144387 · Issue 605339
Support added for allow list for LaxRedirectStrategy
Resolved in Pega Version 8.5.2
When using Connect REST with POST to access a third-party service deployed on multiple nodes, the load balancer sometimes replied 302 with Location header. The ability to allow the REST connector to automatically follow these redirects even in the case of POST messages is supported by Apache http client via LaxRedirectStrategy, but REST Connectors need both rule and engine enhancements to allow for this. To support this use, an allow list has been implemted for hostnames. This will allow the connector to be configured to follow the LaxRedirectStrategy only when the hostname of the redirect location is in the allow list. The default will continue to block the redirect.
INC-144601 · Issue 602422
Empty addresses removed from email
Resolved in Pega Version 8.5.2
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.
INC-144917 · Issue 598200
Healthcheck will only initialize after successful node startup
Resolved in Pega Version 8.5.2
Nodes were not starting up, but because the Healthcheck service was initialized even though the node was not started properly, errors related to that were overriding the actual exception causing the node startup to fail and it was not possible to diagnose the startup issue. To resolve this, an update has been made that will ensure the Healthcheck service is only initialized when the node is initialized successfully.
INC-144978 · Issue 600590
Updated JSON DT nested page property handling
Resolved in Pega Version 8.5.2
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists.
INC-145540 · Issue 601590
Added handling for email folder close exception
Resolved in Pega Version 8.5.2
EmailListeners were marking messages as ERROR when it encountered a FolderClosedException when retrieving message detail from the inbox. This has been resolved by adding handling for the folder closed exception in getMessagebyMessageId method so that the message will be marked as initial and retried.
INC-146030 · Issue 602603
Added queue process tracer cleanup on node restart
Resolved in Pega Version 8.5.2
If a node restart occurred while a queue process trace was in progress, some entries in the tracer distributed map were not cleared properly and a subsequent tracer failure was encountered indicating a current trace by a requestor on same operator Id was already running. This has been resolved by clearing the tracer distributed map on node startup for stale entries associated with this node.
INC-146057 · Issue 599807
Secure access for Activities
Resolved in Pega Version 8.5.2
Authentication requirements have been added to Standard activities.
INC-146752 · Issue 602933
File Listener made more resilient
Resolved in Pega Version 8.5.2
When file listener encountered a FileNotFoundException as a consequence of sporadic AmazonS3Exceptions, the listener was disabled and no retries were made. In order to make the file listener more resilient, FileMatchConcentrator has been updated. While file listener is running and trying to get the next set of files, if the isDirectory() method returns false due to a non-existent directory or some other intermittent issues, instead of throwing an exception and shutting down the file listener, the system will now log the exception and continue.
INC-147140 · Issue 604369
Email listener update for Microsoft Exchange server
Resolved in Pega Version 8.5.2
After upgrade, TooManyObjectsOpenedException/MapiExceptionSessionLimit errors were seen when starting the email listener. Investigation showed that when the listener was started, two sessions were getting opened and then not closed properly. This was a method originally intended to allow the system to re-use the session to minimize performance overhead, but it is not well-suited for use with Microsoft Exchange server as the Exchange server is unable to cleanup idle sessions. As a result, too many MAPI sessions were opened and led to an authentication exception while opening additional sessions. To resolve this, an update has been made so the system will close the session while the listener sleeps. This stop, restart and graceful shutdown scenario for single threaded email listener scenarios will create a new session every time and close it properly.
INC-147716 · Issue 603238
Warning added to indicate if QP/JS have been disabled via DASS
Resolved in Pega Version 8.5.2
Search was not working, and the error “The Flow Action pre-processing activity pzLPSearchManagerMainActivityWrapper failed: java.lang.NullPointerException” appeared in the search landing page. Investigation showed that the environment was configured with disabled BackgroundProcessing, which prevented the QueueProcessor framework from working. There was no notice in the UI of this condition. This has been resolved by adding a warning that will appear if background processing is disabled.