How can I copy Pega Attachments from one case to another case, when the case types are different.
If in both case you need to have same attachment copy then you can use pxCreateAssociation activity. User can add document in 1st case and to the needed 2nd case just by using the above mentioned activity you can establish the link (even though case type is different this approach will work), no need to have duplicate document copy inside system. After establishing the link, from both case you will be able download (or) view the document.
@GunaSekaran_B Thanks for your response, The activity pxCreateAssociation links “Link-Association” rule with a work object. In my scenario, it is Link-Attachment associating to work object, I tried pxLinkAttachmentToCase, it did not help.
@GunaSekaran_B
created a custom activity, did the following in it.
Used the following OOTB Data Page, to get Stream in “pyContents” property from case A. Setting the stream to “.pyAttachStream” in Data-WorkAttach-File page of Case B.
D_pxGetFile[repositoryName:FilePage.pyStoredInRepository,filePath:FilePage.pyContentLocation,responseType:“STRING”]
Following are the properties I am setting in Data-WorkAttach-File page, once I apply Obj-Save to Data-WorkAttach-File page, it will upload the stream using pzSaveToRepository OOTB activity, which in turn uses another OOTB Data Page D_pxNewFile.
.pxInsName
.pxRefObjectClass
.pzInsKey
.pxRefObjectKey
.pyIsStreamBasedUpload = false
.pyContentLocation
.pyAttachStream = pyContents from D_pxGetFile
@SudheerC6830 Send me if any attachment you have
Pega has changed the architecture design in case attachment process in later versions.. Whenever user uploading a document inside case, a new case will be getting created in back-end (PegaSocial-Document) and document related information will be maintained in that case.. So we can link the pegasocial-document case and needed work-object to which the document needs to be shared.. This will help users to access the same document from different cases…
The problem with the design which you have mentioned is, inside system we are trying to hold duplicate document data which would not be recommended approach. For avoiding this kind of process only pega is recommending us to use Link-Association features..
Hope this helps you..