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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-163292 · Issue 635837

Portlet service deprecated

Resolved in Pega Version 8.4.6

Portlet authentication services have been removed from the standard installation package.

INC-173068 · Issue 654064

HTML tags escaped in Audit History field values

Resolved in Pega Version 8.4.6

The case narrative section was showing case statuses with encoded special characters such as % or ( ), resulting in entries such as "Status changed to Complete &# 40;approved& #41; !@#$ %^& amp;*&# 40;&# 41;_&# 43;.". This has been resolved by updating the PyMemo field from type Text Input to DisplayAsLiteral for case narrative, which matches the setting for case history.

INC-175882 · Issue 658642

Updated bulk action audit history logic and security

Resolved in Pega Version 8.4.6

After update, using the standard bulk action feature did not record an audit history entry for the SLA action on a case. This was traced to changes made around authorization for opening worklists when using pzBulkProcessItem that limited the audit history to reassign, transfer or transfer assignment, and has been resolved by updating the login the Work-pzBulkProcessItem activity. In addition, the Require authentication to run checkbox has been enabled on the Security tab of the activity, and the Allow invocation from browser checkbox has been disabled.

INC-177183 · Issue 660537

Refresh assignment checks updated

Resolved in Pega Version 8.4.6

Additional privilege checks have been added to refresh assignment.

INC-178650 · Issue 673550

Cross-site scripting protections updated

Resolved in Pega Version 8.4.6

Cross-site scripting protections have been updated around the DisplayAttachment function.

INC-183947 · Issue 673735

Query split added to handle Oracle expressions limit

Resolved in Pega Version 8.4.6

The PXCHECKFLOWDEPENDENCIES activity was throwing the Oracle error message "ORA-01795: maximum number of expressions in a list is 1000" when a case had a very large number of sub-cases, causing a failure in trying to submit additional child cases which sent them into the broken process. This has been resolved by updating the pxCheckFlowDependencies rule to break down the query parameter into batches of 999 so they can be handled by Oracle.

INC-184271 · Issue 668414

Portal Header persists appropriately

Resolved in Pega Version 8.4.6

The Portal header was disappearing immediately after case attachments were opened from the right sidebar and did not reappear even after refresh. This was traced to the absence of pd(event), and has been resolved by adding pd(event) to the onclick attribute in the anchor tag in the attachment UIKit rules.

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.

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