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.
SR-D40785 · Issue 515098
WorkPageName preserved during passivation so attachments are correctly tracked
Resolved in Pega Version 8.3.3
When a work object was left open but inactive for a period, using the delete button in the pyAttachFieldRequired section caused the deletion of the Attachment Links for the 500 most recent attachments in the system with the same value for the AttachmentFieldName, regardless of which work object they were attached to. This was due to the delete attachments activity being executed with missing parameters: since data page loading was disabled and read-only data pages are not passivated, the value for the autopopulate property 'WorkPageName' was passed as empty. This has been resolved.
SR-D81496 · Issue 547168
Data Social tag class FTS index query improvements
Resolved in Pega Version 8.3.3
A query intended to select from the link tag table to see if any cases were linked to the tag in question and then index the tag change was causing performance issues. Investigation showed that checking tag associations during FTS indexing fetched all matching rows from the table even though one was sufficient. To resolve this, the query will be created with max result count = 1, fetching up to 2 rows from the table.
SR-D83023 · Issue 549687
Apache Commons Compress library upgraded
Resolved in Pega Version 8.3.3
The Apache Commons Compress library has been upgraded to v1.19.
SR-D82695 · Issue 546538
Correct tenant ID set in execution of SLA Agent
Resolved in Pega Version 8.3.3
An incorrect tenant ID was set in the execution of service level agent, causing the SLA Queue item to fail with the error "You are not authorized to open instance SYSTEM-QUEUE-SERVICELEVEL." This was traced to an incorrect access group which was set in QueueProcessor for a processed item and not restored correctly, and has been resolved by populating the access group on the security tab of the relevant standard agent with the value “PRPC:Agents”.
SR-D85410 · Issue 549568
Improved queue processor tracing
Resolved in Pega Version 8.3.3
After starting to trace the queue processor, the message "waiting up to 1 minute for queue processor, <<Name>> to start processing an item" was displayed as expected, but if the tracer was closed and then there was another attempt to trace the queue processor, the message "Trace request with the current requestor is already registered. Multiple trace requests from same requestor are not allowed." appeared. Research showed that this was related to the implementation around canceling a background task, and has been resolved by adding code to handle the scenario of terminating an on-going trace request on window close and then beginning another trace request with the same requestor.
SR-D76861 · Issue 544605
Job Scheduler will be stopped by node shutdown detection
Resolved in Pega Version 8.3.3
LifeCycle Job Scheduler was trying to start already stopped background services during node shutdown, causing exceptions to be logged. This has been resolved by stopping Job Scheduler execution when node shutdown is detected.