function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Lindsay JohnsonLindsay Johnson 

Docusign Error

Hi all - I'm hoping someone can help me out here.  We recently started getting the below error on Leads in Lightning (we do not get the error in Classic or on the APP).

Does anyone know what this means...? Any help is appreciated!
User-added image

Thank you!
NagendraNagendra (Salesforce Developers) 
Hi Lindsay,

Sorry for this issue you are encountering.

May I request you please elaborate your issue when exactly are you getting this error so that we can look into it and can help you accordingly.

Assuming that you are facing this issue when you are using DocuSign managed buttons, if yes, the DocuSign Managed Buttons all use Javascript and Java is NOT supported in Lightning.  You will need to use the Classic Mode. At least at the present time until DocuSign comes up with another way or you do some custom programming and connect to DocuSign via their API.  

Happy to help further.

Kindly mark this as solved if the reply was helpful.

Thanks,
Nagendra
Lokesh KumarLokesh Kumar
It sounds like a step may have been missed Please refer to the DocuSign for Salesforce Lightning Experience User Guide (https://www.docusign.com/supportdocs/pdf/dfs-lightning-guide.pdf). On page 6, you can review what needs be happen (particularly step number 6).

https://support.docusign.com/en/guides/using-the-send-with-docusign-lightning-component-htm 
https://support.docusign.com/en/answers/00083685
 
Lindsay JohnsonLindsay Johnson

Hi all-- Thank you for the responses.  Let me clarify further what the situation is.  We had it set up and working correctly (Lightning / Classic / App), and then one Thursday afternoon that error started popping up for users who did not have the Docusign permission set, where the day before were able to view the lead without any issue.

I'm not sure what could have caused this error, as I went through the audit trail and nothing appeared to be out of order.

Hopefully this gives a bit more background :)