SR-D50584 · Issue 518450
Security added to retrieving operator list by URL extension
Resolved in Pega Version 8.4
It was possible to append information to the application URL which allowed an unauthenticated user to find a list of operators. This has been corrected, and will now result in the message "There has been an issue; please consult your system administrator."
SR-D50725 · Issue 516515
Page cleanup processes updated to facilitate Pulse Task creation
Resolved in Pega Version 8.4
Attempting to create a Pulse Task in an assignment resulted in a "The Operation completed successfully, but returned no content" screen after clicking submit. This was traced to an incorrect usage of createworkpage. To resolve this, the system has been updated so that before calling createworkpage, a page-remove will be done so createworkpage will not clean the assignment page.
SR-D53266 · Issue 516397
Synchronization continuation updated so mobile attachments properly preview
Resolved in Pega Version 8.4
Clicking on attachments in mobile would open them if the attachment had just happened, but otherwise would not open them at all. This was traced to an issue with Synchronization continuation: the page was properly loaded from database but its content was not used to fill the named OfflinePackage page (which contains only the search keys). This has been corrected by replacing the empty page with the one loaded from the database.
SR-D55559 · Issue 520973
Setting added to allow commas in bulk upload survey questions
Resolved in Pega Version 8.4
Questions uploaded in bulk to Survey Designer were delimited by comma, potentially causing an issue when an option itself contains a comma. Because this is a hard-coded Excel template value, this has been addressed with the addition of an extension where delimiter values can be configured and overridden.
SR-D7323 · Issue 493178
Pin Case to Board updated to use unique IDs for different workpools
Resolved in Pega Version 8.4
When using the Pin Case to Board functionality, it was only possible to find and pin cases in the default/current work pool of the working access group and not any other cases in any other work pools which allowed access to open/search/process. This was due to pyLabel being used to compare if a value entered was valid, which was not a unique key. To resolve this, the pyValidatePinDetails activity in Pega-Ext-Mentions-Documents, Pega-Ext-Mentions-Cases, and Pega-Ext-Mentions-Groups classes have been updated to compare pzInsKey instead of pyLabel to check for validate pin.
SR-D18814 · Issue 493325
Enhancement added to fetch HTML attachment from CMS
Resolved in Pega Version 8.4
When email containing HTML was sent to the Listener, some of the characters were not getting decoded properly when viewing. In this case, HTML email content was saved as an attachment in CMS , and this error was traced to the system being unable to fetch the attachment. To resolve this, an enhancement has been added to fetch non-Pega database attachments using pxGetFileAttachmentContent.
SR-D23360 · Issue 493465
Email reply with same attachment name correctly processed
Resolved in Pega Version 8.4
When an email reply was received with an attachment using the same name as one received earlier, the new attachment was not getting processed and the message 'The Specified file/folder already exists in the target repository. Please specify a different file/folder' appeared. This was traced to an incomplete check for the object class that did not qualify the attachment name for a reply, and as been corrected.
SR-D27695 · Issue 500839
Email Discussion Thread retains Formatting
Resolved in Pega Version 8.4
CSS styles were not being retained in the discussion thread when replying to InboundCorrespondence cases. This was traced to a missing value in Param.latestReply activity pzCreateExternalPostFromMail, and has been resolved by setting an initial plain text value to the param.latestReply before it is set with the HTML value. This prevents having a blank parameter value if the incoming HTML value is empty.
SR-D29832 · Issue 503226
Corrected image alignment for email case creation
Resolved in Pega Version 8.4
An issue with missing image styling when an email was sent to create a case was traced to the Owasp library stripping align attributes from the img tag. This has been fixed.
SR-D47795 · Issue 524675
Fallback to Pulse notification added for empty incoming account in CallEmailAutomation
Resolved in Pega Version 8.4
After upgrade, issues were seen with the sender receiving email notifications for sent messages when alias addresses were used for incoming emails. To resolve this, a fallback mechanism to use a Pulse notification has been added in cases where an incoming email account is not found in the pyCallEmailAutomation activity.