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
SR-D90505 · Issue 550989
Repaired Tracer use with Google Chrome
Resolved in Pega Version 8.3.3
After running Tracer while using 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 Chrome Versions greater than 70 and was caused by 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-D64570 · Issue 546713
Resolved Thread deadlocks during RAP imports and MT rule loading
Resolved in Pega Version 8.3.3
When using a time-intensive large query to build a cache to hold complex property references, multiple threads on a single tenant executed this query in a sequential manner and thread locking problems were seen. To resolve this, an update has been made so that for the same tenant, only one thread will run the query. All other threads waiting to acquire the lock will not execute the same db query but will instead make use of the result fetched by the first thread. In addition, a prconfig has been added to control the loading of tenant-specific declarative rules: by default, declaratives/ignoretenantspecificdeclaratives will be set to false and all declarative rules will be loaded. When the config is enabled in a multi-tenant environment, the loading of the tenant-specific declarative rules will not happen and only the declarative rules which are shared will be loaded. In Non-MT environments, this configuration will not have any effect.
SR-D88490 · Issue 548185
SQL query performance improvement
Resolved in Pega Version 8.3.3
An SQL query was running sequential table scans with UPPER keyword while also doing an index scan without UPPER, causing performance issues. The query was used when there was a conflict of a Page property pointing to different Page in the hierarchy of class while creating a dedicated Index, and used the Upper function for a filter condition on pyClassName and pyPropertyMode. In the Database the value will be in MixedCase and the code will pass it as mixed case, so the Upper function has been removed from the query to utilize the index scan for filter condition and improve the query performance.