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-175994 · Issue 667481

Removed redundant Microsoft Outlook email interaction chain

Resolved in Pega Version 8.6.2

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-176881 · Issue 669701

Resource added to extract email threading code from message body

Resolved in Pega Version 8.6.2

In some scenarios the case ID was not being sent in the subject of email replies as expected, and the secure tracking code was part of the email body instead. That caused replies back to the email thread to create a new email interaction case instead of properly threading the new message into the conversation. Investigation traced this to some email clients removing space after the tracking code. To resolve this, an update has been made which will extract the tracking code from email-content html if it is found and otherwise fallback to the email body.

INC-178990 · Issue 664613

Added handling for reloading portal while ChatBot is active

Resolved in Pega Version 8.6.2

An issue was seen with UI rendering when a customer tried to reload the portal where the chatbot is deployed. Investigation showed that this was caused by the screen going to pyCreate harness instead of ChatPerform harness due tot he unexpected refresh, and has been resolved by updating the handling for the Chat Work page and the business case so that pyWorkPage is always Work-Channel-Chat.

INC-179888 · Issue 663845

Training data correctly added to model

Resolved in Pega Version 8.6.2

Negative training data was not getting added to the entity model. This was traced to logic used to remove consecutive spaces which was incorrectly removing new lines and leading to entity detection of entities such as address line. This logic has now been removed.

INC-184155 · Issue 673074

Entity Detection prefers first detected entity

Resolved in Pega Version 8.6.2

Entity detection shown in the "Training data" tab of the email channel did not match with the results of running the corresponding text analyzer rule. This occurred when a single piece of text was detected as multiple entity values, which led to the last entity detected being picked for case mapping because of the unclear scenario of duplicate entities. To resolve this, pxmapresponseentities has been updated to prefer the first detected entity.

INC-184834 · Issue 669457

Channel copy text analyzer detection updated

Resolved in Pega Version 8.6.2

The error message "No unlocked Ruleset versions are available. Please add or unlock a ruleset to create a new channel." was displayed when trying to save a new interface. This was traced to the system copying the channel to incorrect classes/names due to detecting an incorrect type of text analyzer and copying the wrong rules. To resolve this, the method of detecting the text analyzer type on channel copy has been updated.

INC-184902 · Issue 669452

Corrected portal image display for authenticated request

Resolved in Pega Version 8.6.2

Email images for the user portal were not displayed in the browser but were showing correctly in the manager portal. The URL to the image was the same in both cases, however for the user portal the URL request was requiring authentication. This has been resolved by updating the API to use currentsessionURL.

INC-185455 · Issue 671976

Email widget auto-refreshes for incoming email

Resolved in Pega Version 8.6.2

The email thread was not updated automatically for incoming email in an email interaction case with Outlook, but did refresh when the work object was closed and opened in perform mode. This was traced to a Jump statement after pyMapEmailToEmailTriage which interfered with threading, which has now been removed.

INC-176542 · Issue 668477

Removed unused function to improve Class rule save performance

Resolved in Pega Version 8.6.2

Clicking save on the Policy Class rule was not working correctly or was taking an excessive amount of time to respond. Adding property mapping in the External Mapping tab of the Class rule exhibited the same behavior. Investigation showed there was an infinite loop being invoked in the class ruleform, which was traced to the disableKeyEntries() function. As this function is no longer used, this has been resolved by updating the RF_RuleObjClassScript.js to remove disableKeyEntries and any function calls to it.

INC-179111 · Issue 666017

Toolbar delete handling modified

Resolved in Pega Version 8.6.2

After upgrade from Pega 7.4 to 8.5, the toolbar delete button behavior was different. Previously, the pzRuleFormToolbarDeleteRule section rule invoked RuleFormMain on refresh, but the updated version was calling RuleFormHeader, preventing the deletion of the assignment from the class instance. This was an unanticipated edge case and has been resolved by updating the action in the button to refresh the section RuleformMain instead of header.

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