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 582472

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.5.1

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.

INC-139018 · Issue 587715

Rules updated to handle Outlook change that displayed multiple/duplicate email responses

Resolved in Pega Version 8.5.1

In Pega Email Triage case, all the replies were displayed along with the original email body, meaning for each and every reply, Pega showed the original email body and duplicated the data. This was traced to an update made by Microsoft in the Selector function of Outlook Windows, and has been resolved by updating the rules 'PyExtractLatestReplyFromHTML' and 'pyRichTextEmailHistorySelector' to work with this change.

INC-137736 · Issue 585510

Timing issue resolved for modal animation

Resolved in Pega Version 8.5.1

A modal dialog configured with Reveal Animation appeared first without the animation and then disappeared, immediately followed by the animated modal dialog. This was traced to a set timeout that caused the modal to render before the animation, and has been resolved by removing the set timeout.

INC-135554 · Issue 584117

Handling added for displaying very long case ID in Cosmos

Resolved in Pega Version 8.5.1

Case ID and case type were overlapping in the user portal when using Cosmos. This was caused by a case ID that was long enough to cause a line break, and was due to a height being set on the Case ID area. To resolve this, updates have been made which will truncate the display of an over-length Case ID and add ellipses when the text is too long.

INC-138886 · Issue 589300

Animated modals correctly trigger refresh conditions

Resolved in Pega Version 8.5.1

In the client application, a list of tasks can be selected by the user to act on. Clicking on any action opens a modal to work on the task. Once that task is complete, the modal is closed automatically, and the task list is updated to show the next task. The task list section has a refresh condition that triggers when D_Reload.pxUpdateDateTime changes (that timestamp is updated when a task is completed inside the modal). However, after upgrade the task list was no longer updating correctly. This was traced to the animation being performed as an asynchronous task: by the time it was executed, the dom element was not present and the refresh section was not getting triggered. This has been resolved.

INC-136793 · Issue 585603

Updates made to display busy indicator correctly in Google Chrome 84

Resolved in Pega Version 8.5.1

The Pega busy indicator was not displaying correctly in Google Chrome 84 due to changes in that browser. The needed updates have been made to adjust for these changes.

INC-135906 · Issue 582901

Harness open handling added for tabs with apostrophes

Resolved in Pega Version 8.5.1

A javascript fail resulted when attempting to open any harness with an apostrophe (') in the name. This was a missed use case, and has been resolved by updating the PegaCompositeGadgetMgr file with a check and appropriate handling.

INC-135594 · Issue 581779

Smart Tip displays correctly with double quotes

Resolved in Pega Version 8.5.1

After configuring a Smart Tip action which used a selected field value as tip source, the double quotes in the tool tip caused it to not be displayed. This has been resolved by escaping double quotes when a field value is configured in Smart Tip.

INC-131774 · Issue 577047

Resolved focus for new s-case

Resolved in Pega Version 8.5.1

After creating an s-case by using the keyboard, the focus jumped to add task instead of newly added s-case page. This was traced to the 'if' condition in focusFirstElement method becoming true for all touchable devices including desktop with touch enabled, causing the focus method on the first element to not be executed. This has been resolved by adding an additional conditional to check whether the device has touch enabled and is a mobile device.

INC-135061 · Issue 579540

Save on modal close works as expected

Resolved in Pega Version 8.5.1

After upgrade, a repeating dynamic layout with a modified modal dialogue template that had an added save button to it was not working as expected. This was traced to a change in the operations order for the modal save and close, and has been resolved.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us