Background: Generating the pdf document via third party system and adding a place holder on document to sign it via DocuSign function. This pdf document is used in Docusign Integration enabling client to sign electronically.  

Note: This use case is not using DocuSign template to generate and sign the document.

Solution option

Configure DocuSign as per Pega documentation. It is suggested to go through this document before configuring your application with DocuSign. Find below Pega & DocuSign Documentation link. https://docs.pega.com/bundle/platform-88/page/platform/data-integration/configuring-oauth-authentication-docusign-integration.html

What Configurations are needed from DocuSign?

1. Create developer profile in DocuSign https://account-d.docusign.com’
2. Create service account profile with DS Admin role that will be used to send DocuSign email on behalf of this account. This account should have a valid email box access so that docusign can verify this email for further use. Mail box name should be user friendly as mail box name will appear on DocuSign email i.e. xxxx Proprietary information hidden. If mailbox is not available then check with IT support team and get the email box created and configured you should have access to this account so that you can receive DocuSign related, password, OTP emails.
3. Login with this service profile using https://account-d.docusign.com.  (for dev environment)
4. Get the user id of this service account.
5. Note down the Integration Key and setup authentication to ‘Authorization code grant’ and redirect URI to http://localhost if not defined for your application. Generate RSA file & pfx file as per pega documentation.
6.  

7.  
8. Copy paste this link in browser  https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=<<Integration Key>>&redirect_uri=http://localhost .
9. Application is using JWT token to authenticate the service request hence you need to provide consent for the first time, use  ‘service account configured for this integration, loginto DocuSign and provide consent. You would see an option to provide consent and then login. A blank screen will appear.

10. Update regional setting and update the date format and time zone.

11. If you don’t want to receive any DocuSign notification, then stop receiving such notifications by clicking on Profile-->Preferences--> Notifications and uncheck notification

12. If you would like to receive signed document as an attachment after signing the document then check below signing setting.

Signing and Sending -->  Signing setting -->Envelope Delivery --> check ‘Attach documents to completion email’

13. Don’t wait for SIT/UAT Completion, promote your DocuSign Dev application for Production review. When integration with Pega is successful, Initiate at least 20 successful services calls and submit a request for production review from ‘Action’ menu.( production review option is not available as app is already in prod)

14. Login with your production Service account to access DocuSign Production environment.
15. Additionally, you can monitor envelopes analytics via DocuSign portal.

What is wrong with Pega Documentation?

1. Pega provided DocuSign documentation is not accurate. You need to update One of the applications setting instance ‘pyDocuSignAuthenticationBaseURL’ was wrongly configured.

Values should be changed from ‘https://account-d.docusign.com’ to ‘account-d.docusign.com’.

2. Application setting was missed for API version.  Created new Application setting for ‘pyDocuSignAPIversion’

How to test Token generation via POSTMAN

1. Open DocuSign Token profile and get assertion value available under encoded section.
2. Use Postman to generate token,
3. If you are getting ‘consent_error’ then it means that User id used for this integration hasn’t provided any consent yet. You must use below link to provide the consent

https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=<<Integration Key>>&redirect_uri=http://localhost