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-196961 · Issue 693474

Iteration method updated for SetRequiredSkillsCountColumn

Resolved in Pega Version 8.6.3

After update, database utilization spiked and did not drop. Investigation traced this to the use of Local.totalCount in pzSetRequiredSkillsCountColumn, which caused the iteration loop to run more times than necessary. This has been resolved by replacing Local.totalCount with Local.iterationsCount in the iteration.

INC-198514 · Issue 688851

CheckFlowDependencies query performance improved

Resolved in Pega Version 8.6.3

In order to improve performance on very large tables, the pxCheckFlowDependencies activity has been modified. Previously, checking whether a dependency exists retrieved all columns. The updated query will instead return a count.

INC-198807 · Issue 689770

Bulk Transfer Audit displays correct label

Resolved in Pega Version 8.6.3

After Bulk Transferring an assignment, the audit showed the flow action rule name instead of the label. This has been addressed by creating a field value for the name 'pyTransferAssignment' and updating the param.actionLabel to refer to the localized value.

INC-201410 · Issue 695844

Updated handling for Navigation Breadcrumb DisplayFlag

Resolved in Pega Version 8.6.3

On hitting 'previous' the old breadcrumb was visible instead of the expected flowaction. This was a missed edge case for having 'when' conditions before a subprocess shape, and has been resolved by having the pyDisplayFlag be considered conditionally so that even when the display flag for the top level subprocess is false, if the current flow action / assignment belongs to the subprocess, the system will show the breadcrumb for the same.

INC-201981 · Issue 697634

Added check for StageHistory page

Resolved in Pega Version 8.6.3

After update, the pyDisplayStages section was not visible in pyCaseMainInner due to the 'when' condition pxHasStages not being satisfied. This was traced to a customization for the pyStartCase flow in one of the case types which resulted in a blank pxStageHistory page being set under pyWorkPage, and has been resolved by adding a 'when' condition to check whether pxStageHistory page exists so the step will only execute if the pxStageHistory page is present.

INC-154254 · Issue 674944

Correct Email Bot training text highlighted

Resolved in Pega Version 8.6.3

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-181797 · Issue 679337

FocusSection timeout updated

Resolved in Pega Version 8.6.3

When being redirected from an email notification to a Pulse comment, the case opened but the Pulse post was not highlighted as expected. This was a purely cosmetic issue, and has been resolved.

INC-183960 · Issue 674382

Cases Created through email bots remain searchable

Resolved in Pega Version 8.6.3

When a case was created through Email Bot, the delete attachment link in pzCreateTriageWork activity was triggering a delete event in incremental indexing that removed the main work object. This has been resolved by adding a condition check in the SearchIncrementalIndexNotifier class for the link page, and the work object will be updated instead of deleted.

INC-189819 · Issue 676595

Entity highlight corrected

Resolved in Pega Version 8.6.3

In the email channel, the entity value highlighted under "Training" tab was different from the actual value detected. The location where it was detected was also different. This was traced to an inconsistency of the title shown on the UI of training data tab, and has been resolved by updating the title shown on each entity as well as using exit iteration instead of skip step in pyStructureEntity.

INC-190222 · Issue 675956

Emails load with PegaRULES:User4 access

Resolved in Pega Version 8.6.3

Operators with access groups under PegaRULES:User4 were unable to access emails. This was found to be a side effect of Access Control (BAC): if Production level was set to >=4 then the email body could not be seen in the Email Manager Portal and console reported a 403 Forbidden error. To resolve this, the open work by handle action has been added to the Allow List.

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