Thanks, Lalit for sharing this useful video.👍 How to achieve the same requirement between two Pega applications? If I want to create a case from Pega App A to Pega App B and pass the document as an attachment to the case then do we need to create this attachments block payload in Pega-API-CaseManagement class. I don't see this payload by default in Pega-API-CaseManagement class. Also how to trigger Upload API from one pega application to another Pega application. I mean how to pass the base64 string of the document in the connector request payload?
Hi Chandra- it will be like normal api, you have to consume those apis and call with 2nd application endpoint. For sending attachment, we need to set value on some ottb attachment page (have done long back) which I need to check and pass that as request for document as document will go as multipart.
Hi Lalit, thank you for this video on DXAPI. I have a question here, the fourth api "Create Case with an Attachment" is the one you customised by combining both Create case and Attach URL and Upload file to a Case apis right?
is anybody getting the error using pega 23? ,"errors":[ { "ID":"Pega_API_090" ,"message":"Invalid attachment details. type, ID, url etc. are required." ,"pxObjClass":"Pega-API-Error" } I checked that it is caused by this function returning false for the pzDoesAttachmentFieldExist in the 8.3 step of activity pzAttachUploadedFileWrapper
this is an awesome video, it made it clear for me how to use it with postman, now I just need to learn how to use it from pega, thank you!
Please upload more videos on DX API so that we can learn DX API. And tq so much 😊
Sure and there are already 3-4 videos on DXAPI, you can check once.
@@Qtometa Sure 😊
Please make videos on multipart form data, how we can create connectors to pega attachment upload APIs
Ok, I will try to consume upload api from pega.
Thanks, Lalit for sharing this useful video.👍
How to achieve the same requirement between two Pega applications?
If I want to create a case from Pega App A to Pega App B and pass the document as an attachment to the case then do we need to create this attachments block payload in Pega-API-CaseManagement class. I don't see this payload by default in Pega-API-CaseManagement class.
Also how to trigger Upload API from one pega application to another Pega application. I mean how to pass the base64 string of the document in the connector request payload?
Hi Chandra- it will be like normal api, you have to consume those apis and call with 2nd application endpoint. For sending attachment, we need to set value on some ottb attachment page (have done long back) which I need to check and pass that as request for document as document will go as multipart.
@chandrababun8334 : Were you able to implement your requirement? I am also stuck at same position.
@Saanvin Sending Multipart Messages(File) from Pega:Integrating with Pega and Non-Pega Applications via DXAPI
th-cam.com/video/3_sdB3k_ckI/w-d-xo.html
@@QtometaThank you . Let me check the video once
Hi Lalit, thank you for this video on DXAPI. I have a question here, the fourth api "Create Case with an Attachment" is the one you customised by combining both Create case and Attach URL and Upload file to a Case apis right?
Hello, I have not customized just cobmines the two request and it ootb.Pega is excepting both in the request but not mandatory.
can you create a video on how to create the request Multpupart form data for the first call of api/v1/attachments/upload?
Will do this weekend.
is anybody getting the error using pega 23?
,"errors":[
{
"ID":"Pega_API_090"
,"message":"Invalid attachment details. type, ID, url etc. are required."
,"pxObjClass":"Pega-API-Error"
}
I checked that it is caused by this function returning false for the pzDoesAttachmentFieldExist in the 8.3 step of activity pzAttachUploadedFileWrapper