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-136264 · Issue 582469

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.2.8

In order to present an improved interface for customers interfacing with chatbots, the code has been updated so that the recipient's chat scroll will remain at the top of an answer that would scroll off the screen.

SR-D87188 · Issue 551349

Mentioned user in Pulse correctly converted to hyperlink

Resolved in Pega Version 8.3.3

In the Interaction portal, mentioning a user in Pulse using @ was not converting the name to the user name with hyperlink for Email Interactions. @ mentions were working as as expected in Phone Interactions. This problem was introduced as part of using OWASP to sanitize HTML user input in Rich Text support, and was due to OWASP converting @ to an HTML entity. To resolve this, the @ will be excepted from HTML conversion.

SR-D92688 · Issue 551339

Optional feature to improve pxETReport performance

Resolved in Pega Version 8.3.3

Poor performance was seen when using pxETReport. This was caused by the system loading the recent cases widget by looking up all the ET cases within last 30 days, opening each ET case to check if it is from the same pyFrom email address, and then if yes, opening its related service case. On a complex system, this was potentially a slow process. To improve performance, the "Related cases" feature can now be disabled through an overridable 'when' rule.

SR-D63638 · Issue 544015

Performance improvements for opening cases with embedded images

Resolved in Pega Version 8.3.3

Opening cases containing email interactions was taking an excessive amount of time. This was traced to the use of embedded images, icons, etc, in the message body and signature, and was caused by the pyGetAttachmentsbyCID activity running multiple times due to discussion threads that were duplicated over and over. In some cases, more than 360 calls to the database were seen. This has been resolved by shifting some case opening processes to executing when the listener thread gets the mail, and storing the results in a .pynote property, and a URL will be used to get images instead of embedding them directly to the HTML. If preferred, this can be reverted to the previous behavior by changing the when rule (pyUseCachedHtmlForDisplay) to false.

SR-D81707 · Issue 544671

Webchat bot interaction box cleared on submit

Resolved in Pega Version 8.3.3

After upgrade, when using Google Chrome responses to webchat bot questions were not getting cleared from the chat input window after the enter/send button was clicked. This has been resolved by changing the order of refresh section and set value and disabling submit on refresh when refreshing pzSubmitArea.

SR-D86837 · Issue 547992

Webchat interaction timeout updated

Resolved in Pega Version 8.3.3

Interaction timeout was not working as expected in Webchat channels. This was traced to the system looking for total interaction timeout instead of user inactive timeout, along with the Web chat interaction case clipboard page being stale. To resolve this, timestamp propagation has been updated for pxProcess in Work-Channel-Interaction.pxAcquireInteraction.

INC-169824 · Issue 655331

Handling added for response command beginning with "call"

Resolved in Pega Version 8.5.5

There was an issue if a response command in a web chatbot channel started with the word "call". This was due to the storage and handling of the commands in the decision table. There was a workaround of avoiding the use of "call" to start a command, but the issue has been resolved by adding quotes around the decision table result to support this response command structure.

INC-170135 · Issue 652522

Rich HTML handling added for outbound email

Resolved in Pega Version 8.5.5

The HTML content was visible in the received email when replying from the email pane in the existing email interaction. This has been resolved by adding logic to handle rich HTML for outbound email.

INC-173193 · Issue 660938

Resolved exception from isArchived

Resolved in Pega Version 8.5.5

After update, the message "ERROR - Could not retrieve the database time" was seen. This was traced to the interactions of the isArchived API with a version of Oracle, and has been resolved by adding code to skip the isArchived() API call if pzIsPegaCloud is set to false.

INC-178990 · Issue 663786

Added handling for reloading portal while ChatBot is active

Resolved in Pega Version 8.5.5

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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