INC-142589 · Issue 595489
Corrected tooltip evaluation for multiselect
Resolved in Pega Version 8.4.3
After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.
INC-142714 · Issue 596554
Recent Cases from different applications available to open
Resolved in Pega Version 8.4.3
An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.
INC-143005 · Issue 596954
Fluid Overlay displays as expected in Firefox
Resolved in Pega Version 8.4.3
After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.
INC-147873 · Issue 610865
Custom header character encoding for Subject added
Resolved in Pega Version 8.5.5
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
INC-161645 · Issue 634639
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.5.5
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.
INC-163292 · Issue 635839
Portlet service deprecated
Resolved in Pega Version 8.5.5
Portlet authentication services have been removed from the standard installation package. The IAC service has been restored.
INC-121435 · Issue 563875
Handling added for null requiredskillcount on assignment
Resolved in Pega Version 8.2.7
If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.
INC-122149 · Issue 562783
Corrected approval step task message
Resolved in Pega Version 8.2.7
When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.
INC-127077 · Issue 564107
Busy indicator appears when uploading via Select
Resolved in Pega Version 8.2.7
After update, the “loading symbol” (busy indicator) was not appearing while uploading large attachments using the Select button. This was a missed use case in recent changes to related to AsyncUpload, and has been resolved.
SR-D76291 · Issue 547840
Updated retry logic for S3 AddAttachmentFromEmail
Resolved in Pega Version 8.2.7
When using the AddAttachmentFromEmail activity with S3 repositories, performing an obj-save on the data-workattach-file page executes a deferred save while also saving the file into the repository. if the data was inserted into S3 successfully but encountered an issue when saving the related data-work-attach-file page, the system was trying to call the save operation again. This tried to insert the duplicate attachment again to S3, causing an error on that side of the process. To resolve this, the duplicate Obj-Save functionality in AddAttachmentFromMail Activity has been removed.