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-214294 · Issue 710828

PopulateEmailClientWorkFilter correctly resolves field value

Resolved in Pega Version 8.8

The first item in the Email manager queue selection dropdown was 'DefaultWorklist', instead of 'Default worklist' or other formatted text. Investigation showed the New Page was not created for the temp results in pzPopulateEmailClientWorkFilter Activity, preventing it from resolving the customized/available field values, and this has been resolved.

INC-218361 · Issue 737014

AttachmentEmbededInHtml flag works with Microsoft Graph

Resolved in Pega Version 8.8

When an email was received with inline attachments such as images in the signature or an attached file like a Word or Excel document, the attachments were saved into Data-WorkAttach-File but the flag "pyAttachmentEmbededInHtml" used to differentiate whether these attachments were inline attachments or not was not being set consistently when the email was sent from an external domain. This was was missed use case related to Microsoft Graph where pyAttachContentDisposition was not being set to inline for inline images, and has been resolved by updating pzCreateInteractionReply.

INC-228963 · Issue 740547

Null check added for blank CSS style

Resolved in Pega Version 8.8

After a case was created from email, opening the case did not display the email body. This was traced to the styles found in the content of the email body, specifically to a style starting with ":root" that was causing the issue. In pyGetHTMLMessage, the email processing does not happen if the CSS selector is blank, which happened due to a null check not being performed when changing the internal CSS styles to inline CSS styles. To resolve this a null check has been added on the selector.

INC-229423 · Issue 729987

forcemigratetriagecases added to allow check migration status query skip

Resolved in Pega Version 8.8

The IsMigrationDone query was taking around 20 seconds to run on a very large amount of data in pc_work table. To address this, a new 'when' rule pyforcemigratetriagecases has been added to allow skipping checking migration status for on-demand migration.

INC-230368 · Issue 735187

Handling added to prevent empty interaction identifier

Resolved in Pega Version 8.8

The pxInteractionAggregator queue processor was trying to aggregate data periodically but failed with the error "Unable to open an instance using the given inputs: pxObjClass = "Data-Conversation-Summary", pyInteractionId = "". Investigation showed the interaction aggregator could not find the interaction or could not get an ID from the interaction, causing the number of broken records to grow because Obj-Open failed each time it could not find a record in the database. To address this, the pxInteractionAggregator has been updated to better handle the Obj-Open step and empty interaction IDs.

INC-232672 · Issue 742205

PreChatQuestions correctly captured in history

Resolved in Pega Version 8.8

When a chat was escalated to the agent, an internal error message was shown after the queue position and wait time message. The PreChatQuestions flow was executed, but the questions were not captured in the pyHistory of BotCase. This was traced to an incorrect reference relating to inbound and outbound messages and has been corrected.

INC-234503 · Issue 745906

Corrected PrimaryTopic detection

Resolved in Pega Version 8.8

Using natural language processing (NLP) to detect a topic worked as expected, but the list in the clipboard was unordered and an incorrect value was set as the primary topic. This was traced to the system not sorting pyTopics after aggregating the topics from the body and attachments, and has been corrected.

INC-239086 · Issue 746010

Menu titles allow HTML formatting

Resolved in Pega Version 8.8

Attempting to format line breaks and hyperlinks within the menu titles was not taking effect. This was due to the system only accepting a string and stripping out HTML tags in menu titles. To support this formatting use, an update has been made which will not strip the tags on the platform side but will instead send the formatted text all the way to the messaging layer for the menu title inside a menu message type.

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.

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