Trending Topics: Latest From Our Forums (Jan 2020)

Here are some of the latest popular questions that the DocuSign developers community  asked on Stack Overflow in the month of January 2020. You too can ask questions by using the tag docusignapi in Stack Overflow.

Thread: How can I correctly send an envelope using DocuSign that includes two copies of the document, to two recipients, one for each to sign?

https://stackoverflow.com/questions/59776746

Summary: The developer is using the C# SDK and is trying to send an envelope that includes two documents that use tab anchoring. The documents are the same and are using the same value for their anchorString property, but the developer wants each document to only have a single tab for a single recipient and finds that, using the API, the tabs are populated on both documents for both recipients.

Answer: When using anchor tabs in DocuSign, there’s an implicit scope that the DocuSign system is using to search for the anchorStrings. By default, for your account, the scope is set to the envelope level. That means that the entire envelope and every document inside it will be searched for the matching string. You can change that scope to a document, in which case, only the specified document will be searched. Making this change requires that you contact DocuSign Support, as it cannot be done by the user directly.

Thread: Implementing sign a document option without send notification email to signer

https://stackoverflow.com/questions/59642697

Summary: The developer is implementing embedded signing for a “sign and return” scenario where there’s a single signer who is also the sender of the envelope. The developer wants no email to be sent to the signer when the application generates the embedded signing view, as well as to show the user the “sign and return” dialog that enables them to email a copy of the signed document back to someone.

Answer: Typically, the way to suppress the DocuSign system email notification is by using the clientUserId field. That indicates to DocuSign that the signer will be signing embedded, and no email is sent to the signer for this purpose. However, that also suppresses the “sign and return” dialog, as it may not be applicable for embedded signing situations. To that effect, there’s another way to suppress the email message by using a special custom text field. The developer is using the C# SDK, so the code needed looks like this:

var textCustomFields = new List<TextCustomField>(); 
var textCustomField = new TextCustomField { Name = "AppName", Value = "DocuSignIt" }; 
textCustomFields.Add(textCustomField); 
envDef.CustomFields.TextCustomFields = textCustomFields;

Thread: DocuSign Rest API returning blank response after moving into production environment (same code works fine in Sandbox)

https://stackoverflow.com/questions/59738679

Summary: The developer is using JWT Authentication and has built a successful integration in the developer sandbox (demo) environment. When trying the same integration in the production environment, they are getting a blank response from the same endpoint used to create a new envelope.

Answer: When going live, a new integration key is created in the production environment. The process does not copy over all the settings associated with your integration key in the developer sandbox. The developer had to confirm all the settings were copied correctly from one environment to the other, and that resolved the issue.

Additional resources

Author

Inbar Gazit

Published
Share this post