SR-D74921 · Issue 551786
Error condition will close WebSocket connection
Resolved in Pega Version 8.3.3
An async listener has been added that will close the WebSocket connection when an error condition is encountered.
SR-D53835 · Issue 524212
Handling added for custom authentication in embedded mashup
Resolved in Pega Version 8.3.3
After embedding the Mashup gadget in an external application, at browser refresh a Cross-Origin Read Blocking (CORB) warning appeared and the gadget did not load as expected. A second refresh cleared the error. Investigation showed that when custom authentication is configured, 'use SSL' is checked in Authentication service. That meant that when the user was authenticated, the redirection was not considering the query string entered before authentication and the CORB warning was issued due to a change in response. Because there is special handling for the above use case and post-authentication redirection does not happen through the normal flow (HttpAPI), this issue has been resolved by honoring the query string stored in requestor (entered by user) while redirecting.
SR-D87605 · Issue 547295
Indexes and tables updated to improve purge query performance
Resolved in Pega Version 8.3.3
Due to work done previously, purge queries to clean up the application ruleset index and application hierarchy_flat tables were running slowly or not returning the expected results. This has been resolved.
SR-D60830 · Issue 533027
Logic update for classloading synchronization
Resolved in Pega Version 8.3.3
The synchronization logic for classloading has been updated to resolve intermittent deadlocking seen when two DataFlow threads are executing a distribution test.
SR-D61747 · Issue 526196
Null check added for MutationKeepert dataProvider
Resolved in Pega Version 8.3.3
Trying to open the shape "NBA Designer Setting" from Strategy "RealTimeControls" resulted in an null-pointer exception thrown from the MutationKeeper code during PageCopy. This was traced to the dataProvider for the MutationKeeper object being null due to a node in the runtimetree which was marked as removed, and has been resolved by adding a check for a null dataProvider before trying to copy it in the constructor of MutationKeeper.
SR-D84880 · Issue 546888
Null check added to resolve addmapcasetomap error
Resolved in Pega Version 8.3.3
Using a createcase flow shape to create child cases by looping on a page list on the parent case resulted in pzaddmapcasetomap throwing an exception related to the activity pzLoadCaseHierarchyWrapper in step 5. This was traced to a page being removed after the list of pages was received in findPageByHandle, and has been resolved by adding a null check.
SR-D71145 · Issue 536368
PropertySet will iterate over changeList map copy to resolve CME
Resolved in Pega Version 8.3.3
An empty menu was seen intermittently when handling incoming email, and a ConcurrentModificationException error was logged. Investigation showed that a step scope changeList map used in the handleChaining method was sometimes modified by another process while the first one was iterating over it. To resolve this, PropertySet will receive copies of the change list map from clipboard pages instead of the original map.
SR-D81911 · Issue 553093
Reference property copying updated
Resolved in Pega Version 8.3.3
An error appeared on screen when performing the local action "NonProceed case" after upgrading. This was traced to the way copying reference properties was handled as part of pxDeleteAssignmentsForWork, and has been corrected.
SR-D85653 · Issue 548599
Repaired Tracer use with Google Chrome
Resolved in Pega Version 8.3.3
After running Tracer while using Google Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Google Chrome Versions greater than 70 and was caused by Google Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.
SR-D90051 · Issue 549492
Repaired Tracer use with Google Chrome
Resolved in Pega Version 8.3.3
After running Tracer while using Google Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Google Chrome Versions greater than 70 and was caused by Google Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.8.4.1: 546596