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.

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-174435 · Issue 659479

Survey Complex Question Definition properly displayed

Resolved in Pega Version 8.4.6

Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab".

INC-175533 · Issue 678911

Improved Page compare for page groups

Resolved in Pega Version 8.4.6

Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.

INC-180603 · Issue 661739

Added protections for GetSiblings

Resolved in Pega Version 8.4.6

Cross-site scripting protections have been updated for the GetSibling activity.

INC-182248 · Issue 665782

Added logic to handle manual validate rule creation

Resolved in Pega Version 8.4.6

Manually creating a Validate rule with conditions and then opening the configure view with conditions caused the validation rule to be removed from the flow action rule along with the validation conditions in the validation rule referred in flowAction rule. This has been resolved by updating the logic in the Condition Builder to handle this use case.

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