Have a requirement to upload the documents attached to a case to filenet in constellation. The upload is via Rest API where a unique ID is returned in response and that ID needs to be used for further actions like retrieval, deletion.
Have gone through the below article which talks about achieving this by creating a custom repository
When the upload api gets called, the pzSaveToRepository activity invokes the D_pxNewFile. The pyNewFile extension activity can be used to achieve this but when the save data page is called the data page gets flushed out in constellation(got info after I raised an SR). The ID returned in the response of the API is lost and not able to store it for further actions. The pega SR says that this is product limitation currently. Is there any alternative solution to this?
Did you get any answer to your use case from teh Pega Community? or Could you find any alternative solution? We have a similar use case, we need to configure our Pega Constellation Applications to store content in an external repository via Rest API, case attachments must be stored externally and all attachments management such as create file, delete file, get file, etc. must be performed by invoking REST APIs.
I’ve used Azure as my Custom repository to store/retrieve the attachments. We’re leveraging the OOTB data pages to store/ retrieve the files and delete the file from Repo if required.
Create the Azure Custom repository
Configure the OAuth for Azure Custom Repo
Configure the Custom repo in Application Definition-> Integration tab
For a different application in UI Kit, I’ve used FileNet to store/retrieve attachment. However, we tried to invoke the direct API calls for the attachments.