Error saving DocuSign Envelope Status in Salesforce using Apex Toolkit - salesforce

Since September 30th, we started receiving errors while trying to create DocuSign Status records:
All envelopes must be in 'sent' or 'created' state with a valid DocuSign ID to create associated status records
We are using the EnvelopeService Apex Toolkit, and the exception is thrown after invoking the saveSentEnvelopes or sendEnvelope methods.
Sometimes it fails and sometimes it works, so we could not determine any pattern in terms of the envelope we are sending.
Moreover, the users are receiving the email with the envelope correctly.

This is a known issue for which a patch was released yesterday. Please update your DocuSign Apps Launcher to the latest version to resolve this

Related

Source ID is Missing For Embedded Signing in Salesforce

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?

Issue with duplicate Manifest ID in Microsoft AppSource

I received the validation error below in my seller dashboard validation test results:
The Add-in Manifest ID used in your add-in's manifest appears to be a duplicate of a different add-in already submitted to Microsoft AppSource. This ID must be unique.
This is likely due to me accidentally submitting a validation request to Teams App first. Could someone from the Microsoft validation team please help me remove the manifest id from the system so I could re-submit my app package for validation? Or please let me know how I should proceed?
Thanks!
This failure is unrelated to submitting a review request to Teams via email. The manifest ID in the manifest uploaded to SellerDashboard must be unique. The validation team cannot delete manifest ID's for any app or add-in.
If you have previously submitted your add-in via SellerDashboard, then subsequently created a new listing you would encounter this issue. If this is the scenario, then either submit your app on the original listing, or else alter the manifest ID on the second listing.

Attach Signed Documents in to Salesforce

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

Docusign status and Docusign recipient status in salesforce doesn't gets record when we send doc to the user

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

docusign recepient status not getting created

I am using a demo instance of docusign connect for my development on salesforce platform. I noticed that Docusign Recipient Status record is not getting created. Docusing Status record which is the parent object is getting created thought. Any thoughts on why this is happening?
Thanks,

Resources