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-163292 · Issue 635837
Portlet service deprecated
Resolved in Pega Version 8.4.6
Portlet authentication services have been removed from the standard installation package.
INC-167606 · Issue 665868
Updated ConfirmHarness handling for case type creation
Resolved in Pega Version 8.5.5
If a new case type was created with the initialization stage and there were no assignments in the case type, the /cases API did not return a NextPageID in response. This has been resolved by setting the pyConfirmHarness parameter before calling addworkobject.
INC-168368 · Issue 651080
Correct flow actions loaded in multi-thread portal refresh
Resolved in Pega Version 8.5.5
The member authentication screen was displaying an incorrect flow action on doing browser refresh after creating a new interaction. Refresh is a special case where the parameter retention is different across single-threaded & multi-threaded portals alongside the execution order of activities. In this case, this inconsistency occurred in a multi-threaded portal when newAssignPage had the information to load the proper assignment but the parameter indicated an old index. This has been resolved by adding 'when' conditions to to populate and pass the correct references and labels and to honor the Param.TaskIndex set and sent by UI activities so it's retained in case of multi-thread portals.
INC-169636 · Issue 649730
WorkObjects security update
Resolved in Pega Version 8.5.5
Cross-site scripting protections have been updated for WorkObjects.
INC-170514 · Issue 653761
Lock conflict resolved for AssignmentCheck
Resolved in Pega Version 8.5.5
The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.
INC-171842 · Issue 664385
Visible element populated for field value controls
Resolved in Pega Version 8.5.5
When implementing a section which had several labels with visible when conditions, this is not reflected in the DX API Get Assignment View. This has been resolved by adding a visible element.
INC-172584 · Issue 654923
Deprecated NewWorkGadget registered for BAC
Resolved in Pega Version 8.5.5
Logging in through the Administrator portal and launching a new project resulted in a blank screen. Investigation traced this to the Create New Work action called in the NewWorkGadget control; because the NewWorkGadget is no longer used by Pega, it was not registered for use with BAC. To resolve this, validations have been added for Control: NewWorkGadget, and the control has been marked as deprecated.