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.
SR-D81328 · Issue 549992
Kafka Disk Space auto cleanup improvements
Resolved in Pega Version 8.3.3
High disk space consumption was seen when using a custom QueueProcessor and standard retention policies. To resolve this, an enhancement has been added which will allow consumed QueueProcessor messages to be removed from the stream as soon as they are processed to avoid out of space issues. This will ignore partitions with undefined positions.
SR-D70768 · Issue 547016
Handling added for unavailable oWnd
Resolved in Pega Version 8.3.3
After using a Snap Start URL to open an assignment, terminating the requestor and hitting the URL again resulted in a blank screen. This was traced to the pzUnknownSessionAlert script throwing an error when oWnd.pega was not available, and has been resolved by adding the needed handling.
SR-D81651 · Issue 545236
Added check for signed-data in encrypted email
Resolved in Pega Version 8.3.3
Numerous java.lang.UnsupportedOperationException messages were seen in the logs. Investigation showed that signed email which arrived as encapsulated within another email with header content-type = "application/pkcs7-mime; smime-type=signed-data; name="smime.p7m" caused the exception. This was due to a missed check for 'signed-data' while parsing the email and checking for encryption, and has been resolved.
SR-D83329 · Issue 546657
AWS S3 client SDK upgraded
Resolved in Pega Version 8.3.3
The com.amazonaws group has been updated to version 1.11.740 .