INC-177183 · Issue 656492
Refresh assignment checks updated
Resolved in Pega Version 8.4.5
Additional privilege checks have been added to refresh assignment.
INC-147654 · Issue 642185
Updates to displaying embedded images in cases
Resolved in Pega Version 8.4.5
Sending an email with an embedded image to the email ID associated with the email listener successfully created the interaction case, but the embedded image was not displayed when the case was opened from the work-basket. A rule-not found exception was seen in the tracer for pyGetImageDisplay, the rule responsible for displaying the images in the ET pane. Investigation showed that when URLObfuscation was turned on, the decryption of the URL was not successful because "&" had been encoded to '& amp;'. This has been resolved by calling the activity pyGetImageForDisplay using URLMapping instead. An additional issue was seen with displaying images in the email interaction pane where the additional empty new lines moved the image outside the intended place. This was traced to a customization for the reply area which used the pyHighlightedMessage property and converted newlines to br tags even in HTML mode. To resolve this, pyHighlightedMessage has ben modified to convert newlines to br tags only if the mode is plain text.
INC-152776 · Issue 621242
Check added for HTML and linefeed combined in email
Resolved in Pega Version 8.4.5
In the Interaction right hand pane Email triage widget, additional line breaks were seen when displaying email message data that contained table tags. This was a missed use case for email which contains both HTML and '\n', which resulted in the system replacing '\n' with < / br >. This has been resolved by adding a check whether the content has HTML tags which will avoid the replacement.
INC-157214 · Issue 631598
Mentioned user in Pulse appears correctly
Resolved in Pega Version 8.4.5
When loading user names while using the "@" functionality in a Pulse post, adding or tagging the operator/user in Pulse by entering each letter brought up the list, but when using copy/paste it was not possible to select the desired value from the user.Suggestions list of operators/users. If by chance the user name was selected from the suggested list, the operator ID was added instead of the full name. This has been resolved.
INC-160688 · Issue 632228
Skip topics from the attachments setting honored
Resolved in Pega Version 8.4.5
Topic detection was happening for attachments even when it is disabled in the UI. This issue was traced to pyTopics which were not properly configured by selecting checkboxes in iNLP configuration for Email Channel, and has been resolved.
INC-165188 · Issue 635773
Third-party links allowed to pass target attribute in anchor
Resolved in Pega Version 8.4.5
Attempting to connect to Docusign, a third party application, via Email in an interaction portal was not working, and the error "account.docusign.com refused to connect" appeared. This was caused by the HTML data being sanitized so the attribute 'target' was not allowed to pass and the application could not open in a new tab. To resolve this, an update has been made that will allow the target attribute for an anchor tag.
INC-170135 · Issue 652523
Rich HTML handling added for outbound email
Resolved in Pega Version 8.4.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-174475 · Issue 650110
Removed unnecessary commit in pyGetAttachmentsByCids
Resolved in Pega Version 8.4.5
Attempting to reply to inbound emails generated the error "This action is not allowed as it is outside the current transaction". Investigation showed a commit was occurring for pygetattachmentsbycids even when there was no change in attachment, and this interfered with the subsequent transactions and resulted in the Transaction id mismatch issue. To resolve this, the commit has been removed and the system has been updated to save only when needed for backwards compatibility.
INC-179722 · Issue 659281
Corrected race condition that caused JobScheduler error
Resolved in Pega Version 8.4.5
A race condition between the pzInitializeQueueProcessors and pyPersistNodeState job schedulers that both run at platform's start was causing a null pointer exception with the error "com.pega.platform.executor.jobscheduler.scheduler.JobExecutionException: Activity execution failed with [PRRuntimeException]". This has been resolved by moving the QueueProcessor initialization process from JobScheduler to StartupTask.
INC-143622 · Issue 602981
Improved privacy for email listener alerts
Resolved in Pega Version 8.4.5
To improve privacy, the customer 'from' address will be removed from PEGA0011 alerts for email listener processing.