INC-145425 · Issue 600774
New email template added to include full message history
Resolved in Pega Version 8.4.4
Whenever a reply was sent from the email triage case, the outbound email sent only the actual reply along with the original email and latest reply only, skipping all remaining replies from email. For example, if there were 5 replies from case, replying 5th time generated an outbound email that contained only 5th reply (actual / current), original reply (which created the service case) and the latest reply (reply 4 in this case) and skipped reply 1 and reply 2. To resolve this, a new Outlook-style template has been added for use in replies that will include all of the previous exchanges.
INC-146544 · Issue 604495
Updated handling for unexpected character set in non-UTF-8 email
Resolved in Pega Version 8.4.4
After upgrade, the listener properly created a case from an email, but the space character was being replaced by ? in the inbound emails. Investigation showed the messages did not appear properly in the UI if the email was sent using any encoding other than Unicode (UTF-8) and it had a special character set. To resolve this, the system will remove the attachment type which includes the charset.
INC-149667 · Issue 610053
Email Triage properly maps attachments to case
Resolved in Pega Version 8.4.4
Attachments from emails coming in via the Email channel were not being attached as expected to both the Email Triage case and the case generated from that. Instead, attachments were only being added to the triage case. This was traced to the pyAttachments property not being properly updated for attachment to the generated case, and has been resolved.
INC-150367 · Issue 606030
Double quotes escaped in entity mapping
Resolved in Pega Version 8.4.4
A usecase where the BOTS created the triage cases from the emails and pushed it to the Workgroup had an intermittent problem where the screen would freeze and no actions could be performed. perform any action on the same. Investigation showed this occurred when the entity text contained double quotes which is caused JSON to break on the client side. This generated an exception during rendering, and other onload scripts failed on load and blocked the entire thread. To resolve this, the system will now avoid the JSON break by escaping double quotes in entity mapping.
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.