Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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 .

SR-D74376 · Issue 552257

Check added for string vs boolean for pzscan JSON

Resolved in Pega Version 8.3.3

When calling the CloudRemoteMaintenance/Work-/pzscan API, the response JSON had boolean values in the form of String which caused the JSON parsing to fail. The system was using ClipboardProperty.toStringValue() while generating outbound JSON from the clipboard page, which did not correctly interpret a boolean value. To resolve this, a check has been added that will assess the value and invoke ClipboardPage.toBoolean() when needed so that the value is converted as per type before generating the JSON.

SR-D81673 · Issue 546395

ClipboardToJSON Serializer enhanced

Resolved in Pega Version 8.3.3

After creating a JSON data transform with the top level structure set to Object and a step that mapped a Pagelist in clipboard to an Array of Objects in JSON, calling the data transform in Serialize mode resulted in a JSON mapping exception. This was a missed usecase for using the JSON serializer with nested pagelists in page, and has been resolved by adding pagegroup support for data transform serialization and skipping pagegroup serialization when automapped.

SR-D85699 · Issue 548662

DASS given for overriding boolean transformation to true/false

Resolved in Pega Version 8.3.3

In order to ensure greater backwards compatibility, support has been added for not converting boolean values in the DOM-based Parse XML assembler based on the DASS as below :Pega-IntegrationEngine • ParseXML/DOM/DoNotConvertBooleanValues This will maintain values as 0/1 and override the default of transforming them to true/false which was enabled as of v8.3.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us