Trending Topics: Latest from our forums (October 2022)
See how our most popular recent threads on Stack Overflow can help you solve your own development issues.
Table of contents
Here are some of the latest popular questions that the Docusign developers community asked on Stack Overflow in the month of October 2022. You too can ask questions by using the tag docusignapi in Stack Overflow.
Thread: Error saving Docusign Envelope Status in Salesforce using Apex Toolkit
https://stackoverflow.com/questions/73949783/
Summary: The developer is using the Apex toolkit for Docusign eSignature for Salesforce.They are getting an exception thrown when using the saveSentEnvelopes or sendEnvelope methods.
Answer: At the time this developer attempted to use the Apex Toolkit, there was an issue that was fixed a couple of days later. The fix was included in the most recent version of the Docusign App launcher. Installing the latest version immediately resolved the issue.
Thread: Docusign | Radiobuttons and Checkboxes
https://stackoverflow.com/questions/73932281/
Summary: This developer is trying to create linkage between two sets of tabs on the envelope. In the example, the recipient will first choose yes/no on a radio button (presumably asking if they would like to provide contact information). If they say “yes”, another set of checkboxes will allow them to select Email/Phone/Address.
Answer: The developer can do this with conditional fields. They would need to set the conditionalParentLabel and conditionalParentValue fields on the checkbox tabs so that the value for conditionalParentLabel matches the value for tabLabel in the parent tab. In this case the parent tab is the radio button. They would also need to set conditionalParentValue to "on". There is an example of what this JSON would look like on the Conditional Fields page in the Developer Center.
Thread: PHP: Docusign - NO_DOCUMENT_RECEIVED
https://stackoverflow.com/questions/73952679/
Summary: The developer is using the C# eSignature SDK and is attempting to create an envelope, but is getting an error: “The document element did not contain the encoded document, or there is a problem with the encoding. No documents were found in the request.”
Answer: The easiest way to send a document for the purpose of including it in an envelope is to use Base64 encoding. If a valid document is encoded with Base64, the content of the document is provided as a string to the eSignature API in the request to create an envelope. You can find an example of this C# code by using Quickstart or by going directly to GitHub.
Additional resources
Inbar Gazit has been with Docusign since 2013 in various engineering roles. Since 2019 he has focused on developer content and advocacy. Inbar works on code examples including the launchers, available on GitHub in eight languages, and helps build sample apps showcasing the various Docusign APIs. He is also active on Docusign Community and StackOverflow, answering your questions. Inbar can be reached at inbar.gazit@docusign.com.
Related posts
Discover what's new with Docusign IAM or start with eSignature for free
