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-176138 · Issue 723084
Performance improvements for save-as
Resolved in Pega Version 8.8
Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.
INC-187857 · Issue 700855
Added debug logging and exception recovery for unexpected data object
Resolved in Pega Version 8.8
When rules were complied in lower environment and deployed into production, they later became corrupted and system behavior changed. The error "Java generation failed: caught exception while expanding property pyGetCasePredictionsByClassName on page CurrentRecord" was generated. Investigation showed the auto-populate property pyGetCasePredictionsByClassName was attempting to get the metadata property "pzDataObjectParams": this was a string value in this scenario instead of the expected java object, and caused the exception. To resolve this, a debugger has been added which will check if the property is a java object or not. If it is not, the system will skip the processing and then display an error message with a stack trace.