Question
Corporation Service Company
US
Last activity: 27 Sep 2018 14:24 EDT
Upload Files from a web mashup - Not working
We have a mashup that exposes case details to another system. As part of it, the external user can view and upload attachments. We have used the OOTB pyCaseAttachments section to achieve this. When the user tried to upload a new attachment, Drag and drop works fine but "Select Files" (browse folders and attach file) is not working. We are getting file not found errors in pyUploadFile activity. I think it is not able to find service export directory. Did anyone face this issue? i believe it is a quite common use case of letting users attach document on the mashup
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
US
Hi,
I just tested a couple of PRPC versions using a simple mashup using createNewWork. The Perform harness I am using has the OTB attachment section. I was able to upload a file. I can see the file from standard portal end user portal and open it.
What version of PRPC are you on?
Corporation Service Company
US
I should have included this in my original post. We have a proxy webserver involved as well. When i drag and drop file, no issues. but with browsing the files, the upload process usually copies the file to ServiceExport directory. This is what causing my issue. It is trying to find the ServiceExport directory on the webserver (apache) instead of app server (weblogic). I think you may have tried using the direct nodes url
Pegasystems Inc.
US
You're correct, tested with direct URL.
With a proxy though the file upload should still get to PRPC as you are proxying based on context root right? The file upload is just a form post using a different content-type.
http://<prpc_system>/prweb/IAC/LhQAgmtcHrr_s-rjKwJru8_ihFUCluPg*/!SRWorkApp/$STANDARD?pyActivity=ReloadSection&pzTransactionId=2ad96d876511ccb3e1fa623b3097f8c9&pzFromFrame=pyWorkPage&pzPrimaryPageName=pyWorkPage&pzKeepPageMessages=false&UITemplatingStatus=Y&StreamName=pzBrowseAttachments&BaseReference=pyAttachmentPage&StreamClass=Rule-HTML-Section&bClientValidation=true&PreActivity=pyUploadFile&HeaderButtonSectionName=&PagesToRemove=&pzHarnessID=HID7F0921041A09228615C5255F16591A15&inStandardsMode=true&AJAXTrackID=2
With the following content-type header:
Content-Type: multipart/form-data; boundary=---------------------------7e2225361108da
Show me the URL that you see the file content being sent with.
Vodafone
IN
Hello Anil,
Have you tried the same without mashup, I believe you should get the same exception. I see there is no difference in processing the attachment to work object from webMashup or directly.
Please re-validate via tracing activity.
Regards,
Naveen
Adaps
IN
Please find below link might help you
https://collaborate.pega.com/question/pega-web-mashup-and-work-attachment-uploaddownload