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.

INC-154254 · Issue 632638

Correct Email Bot training text highlighted

Resolved in Pega Version 8.4.6

When a piece of text was selected and tagged against an entity while training the Email Bot, the entity selection was misplaced and partially covered the actual text selected. The incorrect selection was then carried forward to the training data spreadsheet. To resolve this, rule changes have been made that will update HTML entities to HTML encoded forms.

INC-175994 · Issue 667483

Removed redundant Microsoft Outlook email interaction chain

Resolved in Pega Version 8.4.6

When opening an email interaction case, the email editor user interface area showed the complete email chain of the email for every new message that came in related to the case. This was traced to the difference in the selectors that various email clients use to construct a response to an email with email history in it, and has been resolved by updating the selectors for Microsoft Outlook in pyRichTextEmailHistorySelector so no conversation is repeated when using that client.

INC-187031 · Issue 676245

Topic handling updated for behavior tab

Resolved in Pega Version 8.4.6

While submitting topics configured on the behavior tab of the chat channel, duplicate records were created and a null pointer exception was generated. Investigation showed this was due to a difference in Topic handling between the email channel and the chat channel in a modal window, and has been resolved.

INC-174321 · Issue 664240

SSLContext created using protocol from REST connector rule form

Resolved in Pega Version 8.4.6

After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead.

INC-184756 · Issue 667323

Static assembler correctly creates temp directory

Resolved in Pega Version 8.4.6

Static Assembly CLI was failing while creating a temp directory. This was traced to an issue with staticAssembler.xml, and has been resolved. In addition, security improvements have been added to the XML transformer.

INC-190722 · Issue 676403

Ruleset Restoration Utility repaired

Resolved in Pega Version 8.4.6

Attempting to use the standard Ruleset Restoration utility after update was resulting in a "Status:fail Operator:Unauthenticated or not available Node:No ID available" error message. This was a missed use case for the refactoring done around importing rules, and was caused by the utility calling the deprecated Importable.isValidImport() method. This has been resolved by updating the import activity to restore its functionality.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us