We have Salesforce prod/live account, where we needed to add DocuSign.
While clicking the DocuSign tab under Saleforce tab "DocuSign Admin",
we are getting error message like this: "Sorry you do not have access to this page".
Also in the Layout Tab, adding Remote URL is not working.
If i add "Send with DocuSign" with any object like Account and click that button, it giving authentication error message like this:
Can anyone help/guide me to find out the issue and resolve.
Got response from DocuSign Support team about this issue.
Hi Yousuf,
Welcome to the DocuSign Support Community!
It sounds like you have a trial DocuSign account. If that's the case, DocuSign Services that are available for a Free Trial may not include or allow access to all features or functions.
If you have further questions, please let us know.
Thank you.
Donna
DocuSign Support Community Moderator
https://docusigncommunity.force.com/CSP_Answers?question=9061W000000boYb
Related
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 am receiving this error 'The envelope specified either does not exist or you have no rights to it.' when I click to sign a Document that was sent to a gmail account. This only happens when I first click on 'Review Document'. If I close the tab and click again on 'Review Document' I am able to sign the Document. This is happening in my Salesforce Sandbox with gmail accounts. If I use the company email I have no issues.
I have tried with another corporate account and it doesn't throw an error but tried with 1 other public email and still have the same error.
I'm sorry you're having this difficulty with the DocuSign system.
For help on this type of problem, please contact our support department: https://support.docusign.com/contactSupport
StackOverflow is for developers' questions.
Many thanks.
I am using IN PERSON feature. I am using docusign for salesforce.
When I select user as Host in person - sign now recipient type and select other user as signer and send the envelop.
Then email is sent to me and all the user which I have selected. When I open my email review document. I can add only my signature not the other user that I have added.
Any idea?
Here is the guide for in-person signing with DocuSign for Salesforce. If it doesn't help then please contact the support group for DocuSign.
StackOverflow is aimed at developers using the API. Thank you.
Ive been advised by Docusign to post here.
I have 4 clients who I've installed the Docusign for Salesforce App for. I've followed the installation instructions and every time I end up with the same error. When it comes to entering my Salesforce credentials it says they are wrong or I have not added the trusted network. I know the credentials are correct and I have entered the trusted network. I've tried various things like using security token in the password, configuring at the docusign end. Nothing works, Docusign don't know what the issue is, I've also raised a case with Salesforce and they can't help. I can't understand why an App on the app exchange can't get passed configuration and noone can help! Hopefully someone here can help. Thanks
The DocuSignAPI tag on Stack Overflow is used for api development and integration questions normally, however I will try to address your issue...
First off, if you could update your question with a screenshot of the error and screen you are on when you receive the error that would help isolate the issue.
With that in mind, what screen are you on? Are you on the screen that's titled "Connect DocuSign to Salesforce"? Even though you've mentioned I just want to double check that you are entering your Salesforce user credentials and not your DocuSign credentials.
Next, what environment are you selecting? And what type of DocuSign account do you have? You need to make sure that you are pointing to an environment where you have an existing account. For instance, if you have a DocuSign demo account but you are pointing to Production during the install, you might get that error.