INC-183559 · Issue 664813
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.6.2
If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks.
INC-183822 · Issue 667501
Filename with non-ASCII characters normalized for Apple Safari upload
Resolved in Pega Version 8.6.2
When using the Apple Safari browser, attaching a file name that contained Japanese characters resulted in an "attachment doesn't exist" error message when trying to open it again. This was caused by the special characters in the FileName for the Data/Query string not being encoded during the file upload, and has been resolved by updating the UploadFileToADocument activity to normalize the FileName if the Safari Browser is being used.
INC-183864 · Issue 666186
Updated RequestorInitialize to improve performance
Resolved in Pega Version 8.6.2
After updating, initial user logins were taking an excessive amount of time. This was traced to the standard rule "RequestorInitialize", and has been resolved by updating the implementation.
INC-184729 · Issue 669740
Pinning document to space correctly generates thumbnail
Resolved in Pega Version 8.6.2
When pinning a document to a space using the standard document repository tile, the resulting pin did not have an image corresponding to it. The process worked properly when pinning a document directly from the space itself. This was a missed use case and has been resolved by adding an update to set the pyImage of the document while pinning the space.
INC-185950 · Issue 669194
Withdraw task notification uses correct email sender
Resolved in Pega Version 8.6.2
When withdrawing a Task, the withdraw email was sent from the default email box instead of the expected Application default email box. This was traced to the 'pyTaskDeleted' (notification name for withdraw task) value not being present, which meant the system fell back to the task 'pyTaskAssigned' notification name. To resolve this, an update has been made to have pyIsPulseNotificationDefinition return true for a pyTaskDeleted notification.
INC-186489 · Issue 668372
Offline mobile app create work with parameters correctly saves work object
Resolved in Pega Version 8.6.2
The CreateNewWork processor was not saving the work object after merging client and server page. This has been resolved.
INC-152542 · Issue 610947
Support extended for document tags
Resolved in Pega Version 8.7
An enhancement has been added to extend the support for document tags, including showing tags added to a case in a workpool other than the application workpool; showing tags from other operators such as partner sales rep, sales reps, etc; and displaying tags in the "recently added by me" section.
INC-160485 · Issue 655297
Trailing "/" added to public links for SSO use
Resolved in Pega Version 8.7
Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.
INC-161214 · Issue 640893
Push notification of shape-created child case opens correct case
Resolved in Pega Version 8.7
In a scenario with two cases, CaseA and its child case, CaseB, when CaseB was created from CaseA with a standard shape and a push notification was sent right after creation, the "Custom message" notification received on a mobile device opened CaseA instead of CaseB. If CaseB was created as a standalone case, the push notification opened it properly. This was traced to an edge case where the Primary.pzInsKey was empty because the child case was not available in database when the push notification payload was created by push shape, leading to the CaseID retrieved by getInstanceHandleFromPage to fetch the parent Case ID instead. This has been resolved by modifying the process to get the pzInsKey from the step page.
INC-161398 · Issue 639855
DataSync SynchronizationResponseStreamer logging enhancements
Resolved in Pega Version 8.7
The PegaRULES log contained "Response page does not match request, will generate failure response" errors even though no functional impact was observed. In order to enhance troubleshooting, additional DEBUG logs have been to DataSyncHandler, SynchronizationResponseStreamer is now logged on INFO level and contains more detail, and the error message has been modified to "Cannot prepare continuation response because offline package was stale. Will generate reset schedule response." to be more informative.