I am suing Docusign Tool Kit to send the Documents for getting the esignature from Salesforce Oppurtunity Object. The documents are sent and are getting signed and goes to completed state in DocuSign but it is not getting attached back to Salesforce after the signing is done/Docusign status is completed.
Below is the settings for Salesforce connect object
I dont see anything getting attached
The Document shows completed status in DocuSign
Am I missing something why it doesnt attach the signed document to Salesforce Object
You'll likely want to open a case with DocuSign Support for troubleshooting. If you do, be sure to include an Envelope ID of a test send.
Things to check:
Is the DocuSign Status record being updated in Salesforce? If not, you'll first want to check the link from DS back to SF. Log in to DocuSign > Go to Admin > Connect > Reconfigure Login
are you sending from the same Opportunity the attachment should be writing back to?
Do you have Use Content Files checked in your DocuSign Connect configuration page? If so, check the Reconfigure Login panel and confirm that Salesforce SOAP Web Services API Version is 39
Related
I have embedded signing configured in a Salesforce community. The whole signing process works(i.e. envelope is sent and signed), but there are some field updates that I configured within the Envelope Template that are not working. I noticed new DocuSign log entries with the following error message - Cannot perform data updates because source ID is undefined for envelope
I'm not sure how the source ID is missing because my envelope gets sent to the right SF contact and the signed document is attached to the contact record.
I followed the instructions here to create a Lightning Component to launch the embedded signing session - https://developers.docusign.com/docs/salesforce/how-to/embedded-sending-signing/
I thought the problem might due to this line of code because mySourceId is not being set anywhere.
new dfsle.Entity(mySourceId)
I modified the code so that mySourceId is set to the Id of the contact. Unfortunately that did not solve the problem. What am I missing here?
In Salesforce, we are initiating an outbound DocuSign envelope from the Opportunity object. On that Opportunity object, I've got some files that I've already uploaded (example: Signed Proposal), that I want to include as an addendum to the DocuSign envelope that I'm getting ready to send out.
When I initiate the DocuSign from the Opportunity record, and attempt to attach my Salesforce File (see screenshot below), I am unable to find my documents...keep in mind, these are documents that I've uploaded myself, so I DO have access to view and modify them.
Any idea what I'm doing wrong? How to resolve this?
Yes, I'm a System Admin in Salesforce and DocuSign Admin in DocuSign.
Thanks in advance!
Screenshot showing where to search for existing Salesforce files within DocuSign
I runned into an issue when trying to connect docusign to SFDC, here are the steps followed :
Went on my docusign admin portal in Salesforce
Into Account, clicked modify account configuration
Logged in with my docusign account and then salesforce user account (both admin on respective platforms)
I've added Docusign IP addresses in network access in Salesforce
Tried to connect and received the following error message : Web service callout failed: Unable to parse callout response. Apex type not found for element isTLSv12Required
Does anyone know how to solve this ? Thanks
It looks like this might be an error related to an older version of the DocuSign eSignature for Salesforce managed package. Do you have version 7.8.1 installed? If not, try updating and try again.
If you're on a version that's 7.x.x or above, you should be able to update straight to 7.8.1 without issues. If you're on 6.9.x or below, there are some changes in Custom Button format you'll need to be aware of (Documented Here: https://support.docusign.com/en/articles/DFS-URL-buttons-for-Lightning-basic-setup-limitations). In either case, I'd recommend updating in a Sandbox first to confirm everything is compatible.
As a temporary workaround, you should be able to configure Connect from the DocuSign side. Log in to the DocuSign web console and navigate to Settings > Connect > Salesforce > Reconfigure Login to attempt to connect DS to SF from the DS side. This may allow you to bypass the error.
I have integrated Conga with Docusign in Salesforce. I ran the process of generating and sending the document to the user for signing. This has worked very well without using the background mode Conga parameter(&DS7=17) with docusign status updated in salesforce(with signed date and time) but, when I use background mode enabled, docusign status of that object(Contact or Opportunity) in salesforce doesn’t gets updated(no record gets added).I'm very much new to all these tools. Sorry, if i'm asking a silly question over here. Button url used:
https://composer.congamerge.com
?sessionId={!API.Session_ID}
&serverUrl={!API.Partner_Server_URL_290}
&id={!Contact.Id}
&TemplateId=a3X6F000000R4ue
&DocuSignVisible=1
&DocuSignR1ID={!Contact.Id}
&DocuSignR1Type=Signer
&DocuSignR1Role=Signer+1
&DocuSignEndpoint=demo
&DS7=17
Sign into DocuSign admin
Click connect
Click salesforce
Scroll to the connected objects section
Edit dsfs_DocuSign_status
Add a new field
If it is the Account object use the Account reference Id and map it to the Envelope External Source Id
Try that the rest of the settings are located there. It took me forever to figure it out too!
Here is my example of setting it up to the Order object
enter image description here
I had a SF userid go expired and I've got a bunch of envelopes that need to be updated with the appropriate status. I send out envelopes via the api. Then I programmatically create the dsfs__DocuSign_Status__c including the evelope id and AccountID/Company. As soon as Docusign gets sends the envelope it updates the dsfs__DocuSign_Status__c record and creates the dsfs__DocuSign_Recipient_Status__c records. All this works great. My issue is my SF ID's password expired and I have 100s of missing dsfs__DocuSign_Recipient_Status__c records. How can I force an update from DS?
Yes you can force DocuSign Connect (webhook) updates to be re-sent, however you can only do it if you are a member of the sending account. For instance, if a given account member has DocuSign Connect configured, and they send a signature request through Salesforce using their DocuSign account, then they can re-publish those updates through their account settings.
To re-send DocuSign Connect updates:
Login to your sandbox or DocuSign account and in the top right profile drop down select "Go to the Admin".
Under the Integrations section on left select "Connect".
Click the LOGS button at the top of the connect configuration screen.
On a given connect log click the REPUBLISH button to re-send the update.