INC-129982 · Issue 574393
Temporary case creation from Cosmos resolved
Resolved in Pega Version 8.4.2
Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.
INC-130326 · Issue 571522
Added handling for apostrophe in Pulse username
Resolved in Pega Version 8.4.2
The User Name in Pulse notifications was displayed with symbols if the username has special characters in it, for example the apostrophe in "O'Hara" was showing as ' in any notification. This was a side effect of work done to improve security, and has been resolved by using org.apache.commons.lang.StringEscapeUtils.unescapeHtml to unescape HTML characters in the pzDisplayGadgetMessage control.
INC-131025 · Issue 573113
CheckStorageForDuplicateFiles validation added
Resolved in Pega Version 8.4.2
When two files were attached to case, attempting to delete one file and download the other one resulted in the error "Unable to get file from repository. There was a problem setting/connecting the file path or repository”, and an exception related to "There was an issue creating stream for the file.: Cannot find S3 object at Container" was generated. As repositories are not allowing file versioning, validation was not happening when multiple files with the same file name were uploaded. To resolve this, an enhancement has been made to perform validation in the pzCheckStorageForDuplicateFiles activity.
INC-131151 · Issue 572834
Resolved empty body for Reject email
Resolved in Pega Version 8.4.2
When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.
INC-131296 · Issue 569578
Updated duplicate file name handling for drag and drop
Resolved in Pega Version 8.4.2
When files with the same name were attached with drag and drop, the files were being overridden and became visible to non-authorized users. This has been resolved by using the AppendUniqueIdToFileName parameter when using the pzMultiFilePath control which will append a unique ID to the fileName and pass it in the request along with the file data.
INC-131385 · Issue 573456
Swagger APIs updated
Resolved in Pega Version 8.4.2
The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .
SR-D72456 · Issue 561119
Added duplicate page handling for Bulk actions
Resolved in Pega Version 8.4.2
Trying to resolve cases using Bulk Actions and Bulk Resolve resulted in the exception "Trying to save an invalid page. The cover open count is incorrect; it is -1". This was traced to duplicate pages available on the clipboard with same the insHandle. To resolve this, the pzUpdateAndDeleteAssignments activity has been updated to check for duplicate pages, then pick the right page which is not being served by the findPageByHandle engine API.
SR-D85664 · Issue 559012
Added handling for flow Status values over 32 characters
Resolved in Pega Version 8.4.2
After upgrade, flows were throwing exceptions due to the 32 character limit for the Status field, causing issues for flows where the status on the case is determined dynamically based on value from expression builder. To resolve this, the limit has been removed on the property and a validate rule has been added that will only use the 32 character limit to check static plain text.
SR-D87898 · Issue 552590
SaveAttachment Activity in Data-WorkAttach-URL updated
Resolved in Pega Version 8.4.2
A 'when' condition was not properly evaluated for Activity SaveAttachment (CL:Data-WorkAttach-URL ), causing the Next assignment screen to not be displayed. This has been resolved by modifying the handling of Page Names used as activity parameters to remove the use of the specific PageName "pyAttachmentPage" in the operation and make it generic to Primary in the SaveAttachment Activity of CL: Data-WorkAttach-URL.
SR-D92352 · Issue 553618
Completed onChange will reset FileInput value to null
Resolved in Pega Version 8.4.2
When attaching a file using the "Select File" button, it was not possible to attach the same file after deleting it. Re-attaching the file worked as expected when using Drag and Drop. Investigation showed that the onchange event occurred only when the value of an element was changed, so in this case trying to attach the same file did not change the value of the element and did not fire the onchange. To resolve this, the value of FileInput in pzMultiFilePath Control will be set to null at the end of the onChange event so that an onChange event will be triggered next time even if the same file is added.