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-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.

INC-191159 · Issue 682363

Validate topics based on all topics in channel instead of default language

Resolved in Pega Version 8.6.3

If a 'When Rule' was used in Email Receiver to provide some conditions, it was not possible to use topics from the dropdown which were trained with training data in prediction studio. This was a missed use case, and was traced to validation being based on the default language topics. To resolve this, the data page has been modified from getting default language topics to getting a union of topics. The datapage for default language topics has also been withdrawn.

INC-192646 · Issue 679066

Correct class for properties set by Chatbot

Resolved in Pega Version 8.6.3

After initiating a service case from legacy webchat and subsequently resolving the case using DX API V1, additional properties with a different applied-to class than that of the workclass were added to the service case workpage while setting answer values to the question structure from the @baseclass.pxSupplyAnswerToQuestion API. Open assignments on the case could be submitted through the portal without any issues but validation errors occurred when the same assignment was completed though DX API, e.g. from a custom React frontend. This has been resolved by moving the properties to baseclass or Work- class as appropriate.

INC-192935 · Issue 688462

Added deferred loading for email cases

Resolved in Pega Version 8.6.3

When there were a significant number of email interactions on an email case, delays were seen when loading the case in the UI. Investigation traced this to a high number of database calls along with the BLOBs also being open. To improve performance, the new rule pyDeferLoadEmails has been added which toggles the UI and loads emails faster. In addition, the button label has been modified to read "View all emails" in place of "Show all" while defer load is enabled.

INC-192935 · Issue 698696

Inline images retrieved for deferred-load email

Resolved in Pega Version 8.6.3

When emails were defer-loaded, inline images with code entered into the non-cache section in pyExtractHtmlFromAttachment were not being displayed. This has been resolved by passing the current page parameter to pyExtractHTMLFromAttachment to convey the pyID.

INC-193727 · Issue 679112

Entity mapping order updated for email bot

Resolved in Pega Version 8.6.3

Issues were seen with the entity mapping functionality in Email bot, especially when mapping email headers like subject, from (email) etc. to case properties. This was an issue with the order in which the entities were mapped ,and has been resolved with an update that will map entities which are configured in the channel first and then mapping the rest.

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