Trending Topics: Latest From Our Forums (Nov 2019)
Here are some of the latest popular questions that the DocuSign developers community asked on Stack Overflow in the month of November 2019. You too can ask questions by using the tag docusignapi in Stack Overflow.
Thread: C# DocuSign API: How to prefill form field data
Summary: The developer created an integration using the DocuSign eSignature C# SDK that is sending an envelope using a template. The developer wants to be able to fill data in some of the tabs that are in the template using the integration and is not sure how to do that.
Answer: The TemplatesRole object that the developer is already using in their code has a Tabs object that can be used to modify tabs when sending an envelope from a template. This is the C# code snippet to do that:
var tabs = new Tabs(); var textTab1 = new Text(); textTab1.Value = "test"; tabs.TextTabs = new List<Text>(); tabs.TextTabs.Add(textTab1); trole1.Tabs = tabs;
Thread: DocuSign remote signing vs Echosign
Summary: The developer is asking if it’s possible to use remote signing to obtain a URL that can then be used to send in an email to the recipient. The developer is trying to send the emails for signature themselves, but embedded signing URLs expire very quickly, and the developer is not sure how to do that using DocuSign.
Answer: Embedded signing and remote signing are different concepts. In remote signing, the DocuSign system sends the email to the recipients that are specified in the envelope. In embedded signing, a URL is produced by DocuSign using eSignature API calls to enable the app developer to embed this URL inside their application for real-time signing. This URL should not be used via an email as it expires very quickly (about two minutes) for security reasons. The developer is interested in sending their own emails. If the reason is that they want them to look different, they should consider using the DocuSign branding templates to modify the appearance of the emails sent by the system.
If there’s another requirement to send the emails from a different system, the developer can build a mechanism wherein the URL in the email goes to their own application. The application, in turn, would generate an embedded signing URL to be used only when the recipient is ready to sign, and redirect the recipient to that URL immediately. This approach would enable the developer to have URLs that they can send in emails that in theory do not expire and can be used to send invitations to sign using DocuSign.
Thread: docusign how to receive the signature in the header
Summary: The developer is building an application and is using Connect webhooks to get event notifications from DocuSign. The developer is trying to make his app more secure by using HMAC values that should be included in the header of the HTTP call made by DocuSign Connect. These values are not showing and the developer is not sure why.Answer: The DocuSign system enables two types of Connect configurations. One type is a global account configuration that applies to every envelope in the account and has to be set up by an account administrator. The second type is a unique per-envelope request to add Connect to a specific envelope. The latter can only be applied using the eSignature API. The developer in this case was using the second, envelope-specific Connect configuration, and it did not include the HMAC value in the header because it was set in the global Connect configuration. By removing the request for a custom Connect configuration, the envelope that the developer was sending from their app was using the global (account-wide) Connect configuration, and at that point it included the HMAC value in the header.
Additional Developer Resources