My company has one program that creates a pdf from a template pdf and another that sends that pdf through DocuSign. It has worked all along for I don't know how long (it predates me working here). But lately when I try to send the pdf through DocuSign, I get a PDF Validation Error. This just started happening in the last week or two. I can open the file in Adobe Acrobat Reader and print it with CutePDF Writer and then it works fine. Just don't know why DocuSign all of a sudden doesn't like the pdf's. Any ideas would be greatly appreciated.
You have a potential regression bug.
Confirming a regression bug
Isolate: does the PDF work via the DocuSign web app? If it does then the problem is with your API integration and you'll need to determine the problem there.
If you have an older pdf that was used to successfully create an envelope, test it to see if it still works (via the DocuSign web app). If it does then your PDF software changed. Not a regression bug.
The best test is that a PDF that previously worked no longer does.
If you've confirmed a regression bug
Please contact DocuSign developer support
You'll either give them the PDF to analyze or, if it contains private data, you should create a test pdf that also doesn't work via the DocuSign we app.
Catching regression issues sooner
DocuSign strongly recommends that all software developers build automated tests for their software to exercise the DocuSign integration/APIs.
Then set up the tests to automatically run daily against the test platform (demo.docusign.net). Accounts on that system are no charge.
If your automated test detects a regression problem then you should immediately contact DocuSign Developer Support.
Regression bugs are rare
DocuSign uses thousands of automated regression tests to ensure that new releases don't cause regression problems. But issues do slip through.
By testing against the test platform, you have the opportunity to discover an issue (and alert DocuSign) a week or more before the scheduled production release.
Thank you all for your suggestions. They were very good suggestions. However, it turned out that it was my pdf template that was being used to create the pdf. It had Adobe signature fields in it and it appears that Docusign has decided they don't like Adobe signature fields. I removed those fields from the pdf form and it worked fine.
Related
I have a problem with a DocuSign flow on staging environment. After signing a document and clicking on continue button I have an error:
This authentication mode is not supported: NONE
It's a little bit strange because on production I have the same code and everything is working fine. I'm using different docusign account but both accounts (demo and production) have same settings.
Besides this, there are also a small differences in docusign flow buttons (staging vs production).
After signing the document, instead of "continue" button there is a "finish" button.
Staging used to work fine and looks like production for a long time but few days ago that changed. Do you know why there are differences between these two environments and how to fix staging?
The error you are seeing is mentioned in this article with the solution, please have a look
https://support.docusign.com/s/articles/000043153?language=en_US
As discussed in the support article, Standards Based Signing often requires signer authentication. Your signing request did not included a needed authentication step, that's an error.
Regarding:
Do you know why there are differences between these two environments
Yes, DocuSign works to improve its products. The demo ("staging") environment is used as a final test for new releases before they're installed on the production systems.
The UX changes you noticed will soon be implemented on the production systems too. In some cases, UX changes are only made for selected account plans (eg web purchased accounts vs enterprise accounts).
I have an iframe with an embedded DocuSign. When I try to navigate to this page using cypress tests, the document won't open. I couldn't find much information on google. Is it a drawback in cypress that won't support docusign inside iframe?
Cypress has hard time working with iFrames; however, there are ways around it in most situations, which you can read about here.
The problem with DocuSign, from what I remember, is the document originates from a different domain than your test application. If that's the case, Cypress isn't able to test elements within a different domain, as it is bound to a single origin.
If that is the case, I would see about using Cypress to interact with the DocuSign API directly and testing its integration with your application that way, if possible.
We've implemented DocuSign in our e-Builder instance. It works okay on normal documents with the normal signing actions. We would now like to sign our CAD plans in a similar fashion. Some plans sets have over 100 pages. Each page needs to be initialed, signed, and stamped. So, placing all the signature "Tabs" is a bit time consuming. When the signer receives the plans, all of these should be positioned already right where we want them. Same x,y on each sheet.
What would be the best approach to placing these? Python?
Any suggestions would be appreciated. Thanks!
You can use either Python or C# (with VS 2017) to use the REST API and it has the functionality you want.
Here is some code example to help you:
https://developers.docusign.com/esign-rest-api/code-examples/set-envelope-tab-values
GitHub Python code can be found here:
https://github.com/docusign/eg-03-python-auth-code-grant/blob/master/app/eg016_set_tab_values.py
GitHub C# code can be found here:
https://github.com/docusign/eg-03-csharp-auth-code-grant-core/blob/master/eg-03-csharp-auth-code-grant-core/Controllers/Eg016SetTabValues.cs
You will need to get a sandbox/demo account and get an integration key to make API calls.
I'm working on a project that involves the development of an add-in for outlook the web for the purpose of sending secure email.
I have a few requirements for this add-in:
It must be able to have access to smart card reader and read certificates from it.
It must be able to sign and encrypt mail using S/MIME
Ideally, should also work on mobile (e.g. iPhone, Andriod).
From my current research, I understand that there are some restrictions regarding add-ins for Outlook. The main one being it won't be activated for encrypted mail... But I have noticed that some people are able to work around this limitation.
Hoping to get some promising leads from the experts here.
Thanks!
Currently add-ins are not supported on S/MIME encrypted messages and are not available for mobile compose scenarios. We track Outlook add-in feature requests on our user-voice page. Please add your request there. Feature requests on user-voice are considered when we go through our planning process.
Is there any way I can write an Excel VBA program to interface with Quickbooks online? I work for a company that uses quickbooks for accounting, and I'd like to write a simple program that I can run from one of our common excel files to take data from that file and dump into in a Quickbooks bill.
The problem Im running in to is that I dont know where to start. The quickbooks online API online seems suitable for other web apps, and any integration with Excel is online with quickbooks desktop. Are there any good resources? Is this even possible?
You can definitely use the QuickBooks Online API to do what you're looking to do.
The API is usable to both web apps and desktop apps.
If you follow the linked text above there's tons of documentation.
The basic process if you're building a desktop app would be to:
get your OAuth tokens from Intuit's OAuth playground
find an OAuth library for your language of choice
parse the Excel sheet
send OAuth signed REST requests to Intuit's API to send the data to QBO
If you're building a web app instead, you'd be better off implementing the entire OAuth signup process instead of using the playground tool.
You probably don't want to do this from directly within Excel because there's a lot of OAuth signing and other crazy stuff that likely won't be easy/available within Excel directly. But you should be able to use Intuit's .NET DevKit to do what you're trying to do.
I researched this last month. From what I can tell the API is only for creating apps for their app store. The apps have to comply with their standards for navigation, security etc... so the answer to your question from what I can tell is that it's not possible. (I could be wrong but I was asking myself the same question a few weeks ago.)
Probably not the answer you were hoping for but I came to accept it. After talking with my business partner who is a Pro Adviser he said that it was easy enough for him to just upload a csv file if the information was correct and the file was documented.
QuickBooks Online API Diagnostics.php ERROR However, from the looks of this post one might have a reason to believe otherwise.
EDIT The API has been updated. Keith Palmer's answer is correct.
Last week this sample was posted:
OAuthHangoutSamples
I have been using a modified oAuth part of this. I found it was easier to build out the transaction than use the SDK for the API. I have a wrapper class, exposed to com that is working in VBA.
Attending the Intuit's Friday Developer Google Hangout was very helpful in my Intuit Magical Mystery Tour.