When sending attachments by REST meta data is not populated
User has implemented the SnapStart URL concept in PRPC for external Users and reported that they are facing issue forming different session on click of the URL.
User is explicitly setting values for optional parameters such as pyAttachFileNames and pyAttachTypes in pyResponseAttachmentsPage but those parameters are not taking effect in generated response.
Even though above parameters are set, Content-Disposition: filename defaults to pyAttachNames and not pyAttachFileNames and for Content-Type gets always application/octet-stream, ignoring set pyAttachTypes.
Steps to Reproduce
1. Create four new argument constructor in ClipboardAttachment.java to include attachFileName.
2. Perform a change in ServiceAPI.java to retrieve pyAttachFileNames and set attachFileName in ClipboardAttachment.
3. Perform a change in HttpService.java to take pyAttachFileNames and set as attachFileName in attachmeninfo stringbuffer.
4. Perform a change in HttpUtilities.java to retrieve attachFileName if present and pass to FilePart. Also, in case attachType has value, pass that to FilePart constructor.
A defect in Pegasystems’ code or rules;
There was no support for optional parameters in case of multipart attachments.