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/
Related
I use the version 9.0 of the Grapph API. The leads retrieval was wroking ok, but the last 3 weeks I am not able to retrieve lead form information, using the endpoint :
https://graph.facebook.com/v9.0/${leadId}/?access_token=${process.env.FACEBOOK_PAGE_ACCESS_TOKEN}
The page access token as well as the facebook app has all the permissions like leads_retrieval, pages_manage_ads, pages_manage_metadata, pages_read_engagement, business_management, public_profile, pages_show_list.
When I create a lead form id from the page that is connected to the app, and then use the testing tool (https://developers.facebook.com/tools/lead-ads-testing) to check if the webhook works, everything works ok !!
The facebook and the connected page that are connected and were used for testing purposes, do belong in different businesses.
The problem is that when someone submits a lead from paid campaigs, then the following error message shows:
An invalid response was received from the Facebook API: {"error":{"message":"Unsupported get request. Object with ID '1223289864932223' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api","type":"GraphMethodException","code":100,"error_subcode":33,"fbtrace_id":"AIQ5Q-yJo249IZwdn10dfhi"}}
Is there an error in the set up of the whole system? Something that needs to be changed? Why suddenly did it stop working ?
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 sandbox environment and also API Explorer.
I need some help to create envelopes by API for request attachments for signers. I've seen in this page it might not be enabled in some accounts. But I'm not sure if this is the case once I can request attachments by sending envelops from user's portal.
Also on API Explorer I'm not being able to include attachment tabs, as you can see in this print:
By API calls, I'm trying to include signerAttachmentTabs as I've seen on their documents.
No errors, it seem my signer_attachment_tabs are just ignored. Hope some one can help me to find out why it is not working by API calls.
Thanks,
Etore
SignerAttachementTabs are fully supported but are not yet included in the API Explorer. The next version of the Explorer will let you use them from the Explorer.
Accounts on the Demo/Sandbox platform enable you to include SignerAttachmentTabs.
Please use the documentation to try creating an Envelopes::Create call that includes a SignerAttachmentTab. If you have problems, ask another question here and include your code that is not working.
Can anyone help.
I’m using the rest api to create an envelope, and then configure it using the api sender view call (/restapi/v2/accounts//envelopes//views/sender) to get the DocuSign UI.
Creating the envelope and viewing it the first time using sender view to bring up the docusign api works fine.
The problem occurs if instead of sending the envelope I click ‘save as draft’. When I try to go back to the envelope and view it again using sender view I get the following error with http status of 400:
{
"errorCode": "EDIT_LOCK_ENVELOPE_LOCKED",
"message": "The envelope is locked. The lock must be released before requesting the sender token for envelope, id = xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx."
}
The lock seems to wear off after time (apprx 20 mins). However after it wears off I can only view the item once, and then the lock is reapplied.
I can’t find anything in DocuSign api documentation that relates to this behaviour. Any help would be appreciated.
UPDATE (12/Feb/15): This error only happens on my demo account but not on production, so it seems like it's an account setting, but I can't figure out what/where the setting is.
Thanks,
Nick
Yes - there is new documentation about this envelope locking feature and behavior in the February service pack (PDF) available here: https://www.docusign.com/support/releases.
We have a bug logged on our side where Save Draft isn't correctly releasing the lock on the envelope. We should have a fix for this issue in our DEMO environment soon. The locking feature is currently only "ON" in our DEMO environment but not in our Production environments while we find and fix potential issues such as the one identified here. More information about locking is in our February service pack (PDF) release notes available here: https://www.docusign.com/support/releases.
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