Conversation
BlueRose Technologies
NL
Last activity: 28 Oct 2025 10:22 EDT
Attachment(s) propagation to child case or a different case in constellation application
I need to propagate attachments which is attached at a parent case, to its child cases or a different case which is no where associated with a parent case in constellation application where documents are stored in share point site. Scenario : I have attached some documents using a attachment field to a parent case and once uploaded these documents synchronized to share point site. In the further process we create some child cases where these documents need to be propagated. We can create different cases which are not child cases of the parent case there also we need to propagate these attached documents. How we can achieve this in constellation application.
Pegasystems Inc.
PL
@AshutoshsinghHi, thank you for question. Could you explain particular issue or question you have? Please describe also attempted solution.
If I understand the use case, you want to attach document on parent case but later reasign it to child case. This sounds purely backend solution to change attachment link object. It doesn't look like Constellation plays role here.
BlueRose Technologies
NL
@Kamil Janeczek Thanks for the response Kamil. Yes indeed its a backend logic which we have written and links start creating and document links are getting appeared in Attachments (right hand side utilities) but these document links are of no use because once you click them they are trying to get the document content from a sharepoint site which we have not configured as most of the logic we have written and executing after the attachment field. We are not using attachment utilities provided by Pega. And I was also wondering we need to create attachment field specific categories in different classes so that once you propagate the documents to different child classes or other case types these propagated documents can attached to. Ex: I have 2 type of attachment field
@Kamil Janeczek Thanks for the response Kamil. Yes indeed its a backend logic which we have written and links start creating and document links are getting appeared in Attachments (right hand side utilities) but these document links are of no use because once you click them they are trying to get the document content from a sharepoint site which we have not configured as most of the logic we have written and executing after the attachment field. We are not using attachment utilities provided by Pega. And I was also wondering we need to create attachment field specific categories in different classes so that once you propagate the documents to different child classes or other case types these propagated documents can attached to. Ex: I have 2 type of attachment field
| Field Name | Category Name |
| Upload Document | UploadDocument |
| Supporting Document | SupportingDocument |
Then documents attached to these fields will be attached to categories also and when we want to propagate these attached documents to child cases or diff case types. We need to create these above specified categories also to get the attachment attached to these categories the only these links will be appeared in Attachment Utilities. My point is if we have N number of attachment fields then we need to create N number of attachment categories in different classes. And if we are not using Pega OOTB Attachment utilities view only using attachment fields then where the propagated attachment will be visible.
FusionAIx
NL
As @Kamil Janeczek already mentioned this is a back-end process. The attachment widget uses the /cases/{caseID}/attachments endpoint. Eventually it will go to D_AttachmentList which is based upon Link-Attachment class, so if you generate a new instance there, it should pop-up.
Btw: don't forget security here
Pegasystems Inc.
GB
@Ashutoshsinghon top of what others said, you could also look at using Embedded Data as attachments. Especially in the SharePoint case, where you might be storing and retrieving other metadata, this could be useful. It would also be a little easier to copy the data around (not necessarily the attachments)
https://community.pega.com/conversations/user-experience/data-level-att…