Integration with DocuSign (need help initiating a template in DocuSign)
Hi there,
We have gone through extensive documentation provided by DocuSign and Pega to send documentation to DocuSign. In all the examples and screenshots, it talks about sending a PDF /document from Pega (as an attachment) to DocuSign establishing the tags, prefilling the information.
Our business requirement is to trigger a preloaded DocuSign template and populate information into that template and then trigger the signature process.
What kind of changes have to be made to the 3 data-transforms to meet this need?
prepareNewEnvelope Data Transform allows you to set a pyTemplateID which we tried but we are not sure of how to structure the data-transform in that case.
Any help initiating templates would be of great help.
***Moderator Edit: Vidyaranjan | Tagged thread as SR Exists***
Accepted Solution
Pegasystems Inc.
IN
Hi,
For sending a template based signing request, all you got to do is
1. have a template defined on your Docusign portal.
2. Use the templateId and Roles (If defined any on the template.. Like 'Recipient' in above screenshot) inside pyPreparetNewenvelope DataTransfrom.
You can ignore all other fields in this DT except for call to SetEnvelopeCredentials DT.
3. you should then bypass the validation activity(If the smart shape is being used for template based signing requests) that gets triggered in the flow (pxSendViaDocusign --> pxValidateEnvelope --> pyValidateEnvelope) for sending new Envelope request.
You can simply override 'pyValidateEnvelope' activity into your app RS to exit from the first step.
4. Drop the smartshape into your case and run to see desired behavior.
Hi,
For sending a template based signing request, all you got to do is
1. have a template defined on your Docusign portal.
2. Use the templateId and Roles (If defined any on the template.. Like 'Recipient' in above screenshot) inside pyPreparetNewenvelope DataTransfrom.
You can ignore all other fields in this DT except for call to SetEnvelopeCredentials DT.
3. you should then bypass the validation activity(If the smart shape is being used for template based signing requests) that gets triggered in the flow (pxSendViaDocusign --> pxValidateEnvelope --> pyValidateEnvelope) for sending new Envelope request.
You can simply override 'pyValidateEnvelope' activity into your app RS to exit from the first step.
4. Drop the smartshape into your case and run to see desired behavior.
TATA Consultancy Services Ltd
GB
For Example if there are two sets of approvals in the application using docusign.
1)One which has PDF 1 sent to docusign to get signed by two approvers [not using OOTB docusign mails for signing]
2)Second PDF sent to docusign to get signed by two more approvers in the same case Type.
In the above scenario is it good to use one smartshape and one envelope or is it good to use two smart shapes and two envelopes and all two sets.[Since pyassignrecipientsDT palys a major roleinsending the correct recipients to the appropriate template/PDF]