#Docusign3 personnes en discutent

Hi, I’m interested in this opportunity. I’m an India-based Salesforce Developer with 5.5+ years of experience working extensively with Apex, LWC, Flows, and integrations. 

One relevant use case I’ve worked on involved integrating Salesforce with DocuSign for contract and document signing. The solution allowed users to initiate a DocuSign envelope directly from Salesforce, dynamically populate documents and recipient details, send documents for eSignature, and capture the signing status back in Salesforce. We used Salesforce automation and APIs to manage the end-to-end signing process and update the related Salesforce records once the document was completed. 

I’d be happy to connect and discuss the requirement in more detail. Please feel free to DM me.

Try re-authorizing the DocuSign System Transfer User. 

When we upgrade from a trial to a paid subscription, DocuSign often provisions a new Account ID. If our Salesforce organization is still trying to listen for updates from our old trial Account ID, or if the background integration user wasn't re-authenticated against the new paid production account, writebacks will silently fail.

1. In Salesforce, open the App Launcher (nine dots) and select DocuSign Apps Launcher.
2. Go to the Settings tab.
3. Look for the DocuSign System User or Connection section.
4. Click Disconnect or Log Out, and then choose Connect.
5. Crucial: Ensure you log in using the credentials for your new paid production DocuSign account, not the old trial credentials.
6. Grant permissions when prompted. This refreshes the OAuth tokens and updates the background webhook listener.

@Harsha Shashikanth I'm no longer actively responsible for our DocuSign integration, but I never did find any tools to help or improved recommendations.  What I ended up doing was manually creating a template stub in the UI so IDs and all the right relationships were created natively.  Then surgically updating hard parts like all the configured fields via SOQL on the Salesforce objects directly for the new template records (either copy\paste in dev console or bulk upload).  Improved the time spent and uncertainty in the release but you better believe I thoroughly worked out my process between 2 sandboxes first before trying between sandbox and prod!  Good luck.

Hello Anna, 

You can definitely handle this without changing global settings. In DocuSign, each template can have its own recipient routing, so for those 6 sensitive credit app templates, you can set them up to send the completed documents to a specific user (like someone from the credit or compliance team) instead of the sender. Just go into each template and adjust the recipient and routing settings accordingly. That way, your Sales Team can still send the envelopes, but they won’t have access to the completed ones, and everything else will keep following the normal path. It keeps things secure without disrupting other workflows.

@Logan Boardman

Thanks Logan for your response. I have created a ticket with DocuSign Support and confirmed the following :  

DocuSign retrieves data from child records based on the Salesforce row number specified in the field's property panel. 

When adding merge fields for child objects, you need to add the merge fields to the document multiple times, each time specifying a different Salesforce row number. This allows DocuSign to retrieve the data from the corresponding child record based on the selected row number. 

For example, if you want to display two lines of the child object, add the merge fields to the document twice, with the corresponding Salesforce row numbers 1 and 2. 

Based on the above Docusign response, the retrieved child record is based on the value of that setting,  the Salesforce row number,  under the merging field.