I need to integrate with Docusign for eSignature. I’m thinking of using Docusign component in Pega market place.
There is a particular requirement that all the traffic has to go through a client specific integration layer for security and monitoring.
Is it possible for Pega to connect with Docusign uing proxy and retrieve the signed copy of the document?
Can I achieve it using this Docusign component in market place. If yes what are the changes I need to make.
Also is embedded signing possible in constellation with OOTB views?
Thanks in advance.
Hello @ABHISEKSAU
The post mentioned by @KiruthikaA has my comments asking for embedding the PDF in pega form assignment.
After couple of weeks of exploration, we have managed to create a custom template component to embed the document for signing in pega. Once user signs the document, we do have callbacks functions provided in DocuSign JS SDK that are to be extended in the custom component and implement any post processing.
There could be one or more documents to be signed for the user and hence we display them in a tabular format. For each entry we have the sign link/button and status of the document. Once user clicks on the sign button, the PDF document is opened up in a modal window where the document is retrieved from docusign and rendered in the modal using DocuSign JS SDK in the custom component. Once the user clicks on sign button, we use the callbacks to update the case with the status and close the modal and table gets refreshed with the latest status. This is just a high level information. May be i will write a post with detailed information soon.
We recently deployed the component to PROD as well and customer is very happy with this change.
You can refer this link for DocuSign embedding using JS SDK Docusign JS for embedded signing reference | Docusign
Regards
JC
Hi @KiruthikaA ,
My question was more on if we want to route the traffic for DocuSign through client specific integration layer(APIM) or a proxy instead of directly calling DocuSign, is it possible to achieve that using OOTB component. Given we want to use same OOTB connect/service REST rules and payload structure.
Thanks for the recommendation. Will try this and in case of issue, will let you know.
Yes, routing through a proxy/integration layer should be possible if the DocuSign base/service URLs can be redirected to the proxy. Retrieving signed documents should continue to work provided callbacks are routed correctly. Embedded signing in Constellation is potentially feasible, but I would validate it with a POC rather than assume full OOTB support.