I'm trying to create a webhook that updates the envelope on my system, but I'm having this issue:
Docusign Issue
Has anyone ever had something similar?
I took a look about this error and I found a bug with connect from last year where there was a special character in the document causing the error. In one of the examples, there was a newline character in the name of the document which caused the error. I would suggest creating a case on the DocuSign support site for further investigation (support.docusign.com).
An internal issue ticket has been opened on this matter. When you do contact DocuSign Support, please reference issue number EC-4887.
Related
My website has been using DocuSign Connect API (SOAP) for years without issue. Part of my website utilizes the brand creation functionality of the DS API (CreateAccountBrands). This has worked flawlessly until very recently.
I now notice in the DocuSign Demo environment that the CreateAccountBrands calls return an InternalServerError with the message "Brands could not be created" but no other information is present in the trace log file. All other DocuSign API calls still seem to be working fine.
Nothing with my payload has changed at all. Has something recently changed with the payload requirements of the CreateAccountBrands call?
I thought it could be that you reached the limits for brands but it seems to be 1900+
You can check Docusign's release notes to see if there are any relevant changes here: https://support.docusign.com/s/releasenotes?language=en_US&page=1
If you don't find anything then you can reach out to DocuSign's support by opening a ticket here: https://support.docusign.com/
I saw similar post previously but there was no solution provided, resubmitting the same issue here asking for help please.
When signing in DocuSign, most of the time it just times out (spinning circle) or I will get the error below:
dsPrepare is not defined.
This happens when I connect to corporate network but seems ok when i switch to my own hotspot.
Any idea what might be causing the error above?
thanks
Your corporate network may have a filter applied that blocks traffic from certain unknown IP Addresses. This would usually cause regular DocuSign processes from completing successfully. You can ask your IT Team to allowlist DocuSign's domains which are listed here and see if that helps.
We are using docusign for more than 3 years, We have several demo accounts as well as we have paid account too.
we are using the following docusign rest service
https://demo.docusign.net/restapi/v2/accounts/*****/envelopes
In our local environment we are using the above demo rest service, Till last month (August) we were able to post the document into docusign without any issues. The Problem now is that we are not able to post a document to docusign.
we getting the exception like
"errorCode": "UNABLE_TO_LOAD_DOCUMENT", "message": "Unable to load the document. Unable to load Document(1;CONSENT FORM). Error: Cannot add the widget (connected to field: ColombiaCurrentlyresideYes) to page -1, because it's already added to page -1. If you want to re-use this widget, please remove it from the current page first
Same data worked till last month (August) and it's working fine now in docusign production account(paid). we are not sure what went wrong in demo accounts. Any release are done in demo accounts?
I tired using the same template in web console too, same error throws in browser console
Please help me to resolve this issues.
We require your guidance regarding this issue!
I suggest first trying to load the documents into an envelope by using the DocuSign Web tool (NDSE). If that doesn't work then the document is the issue.
Has the document changed?
Re changes: Yes, the demo system is changed each month. Then the changes are applied to the production systems. While we do have thousands of automatic regression tests, problem can creep through the system.
I suggest you contact DocuSign customer support to give them the document which is failing to load.
I'm using Docusign's C# client as the basis for my API app and I am sporadically getting USER_LACKS_PERMISSIONS when calling the ListTabs function for a document Signer.
Docusign support thought this was because I was trying to pull Tabs for a CC recipient but I have verified that I was only trying to get the Tabs for the Signer.
I have successfully downloaded approximately 700 envelopes with the exact same app and no changes whatsoever to the code but there are about 20 envelopes that throw this error. This makes me believe that this is something internal to Docusign but they have been unable to come up with a root cause.
Has anyone come across a similar issue and been able to resolve it?
I'm currently trying to automate the process of creating a docusign document and sending it by putting it into an apex trigger. I have managed to get the docusign api (via WSDL) into my org, and now I'm trying to add the code into the trigger to send out the document. Without pasting the entire code here, I've been following this tutorial and have gotten all of the required code into my trigger. Unfortunatly, when I run it, I get this error:
11:40:49.965 (12965647595)|FATAL_ERROR|System.VisualforceException: Getting content from within triggers is currently not supported.
Trigger.OpportunityTrigger: line 109, column 1
Does this mean that it's not possible to send a document in a trigger? The tutorial sends it through a controller, is that the only currently supported method?
Thank you for any help you can give me!
EDIT:
So I've gotten past that error (using a different tutorial), and am now getting this error.
System.CalloutException: Web service callout failed: WebService returned a SOAP Fault: This User lacks sufficient permissions. User does not have the permision to the CreateEnvelopeFromTemplates method faultcode=soap:Client faultactor=https://demo.docusign.net/api/3.0/dsapi.asmx
This appears to be a problem with the Docusign user I am using for sending this document. I am currently using CreateEnvelopeFromTemplates to try and send a templated document out to up to 5 recipients.
I ended up phoning into Docusign Support, and asking them about the issue. Turns out that the last error was caused by me trying to authenticate and sign into docusign with my userID not the AccountID (switched those around and the permission error went away).
Another error showed up related to not having roles setup properly in my template (fixed that by setting up the role), and now everything is working fine. I'm answering my own question to leave it as a reference to future searchers.
Create a call out from trigger
Then get the request from a rest method
Then continue to get the pagereference conten
You can find an example here