Hot topics: latest news from our forums (February 2022)
Here are some of the latest popular questions the DocuSign developer community asked on Stack Overflow in February 2022. You can also ask questions using the tag docusignapi in StackOverflow.
Subject: Envelope JSON request with single document, two signers, pre-filled fields?
Summary: The developer is trying to use the pre-fill fields feature and send a template-based envelope that includes pre-fill tabs. They get an error that says
To respond: You can use prefill tabs when creating a template-based envelope that includes such fields. However, there is a difference in how you provide the values for these fields. With regular tabs (which are part of a specific recipient), you only need to specify each tab’s property and value to set the value of the tabs. With pre-populated tabs, you must also provide the , which is a unique identifier (GUID) identifying each tab in the DocuSign system. The developer did not provide it and therefore received an error.
If you want to use prefill tabs using our eSignature SDKs, check out Inbar’s blog post on this topic.
Subject: SOBO using JWT functionality
Summary: This developer is trying to implement SOBO (Send on Behalf Of) with JWT authentication. They don’t know how to do this. They want their app to impersonate different users and be submitted as if it was submitted by that specific user.
To respond: When you use JWT authentication, you provide the for a user in the DocuSign system. The access token you get after successful authentication allows you to make API calls impersonating that user. However, the user must give consent (or it must be given by an admin for the entire organization) before an API call can be made on their behalf for a specific application (represented by a dongle). integration). To get a user’s name, you can use the Users:list API method to find the list of users for the given account. This API call will need to be called by an admin in a configuration section of your app and the results stored somewhere so that you can later make JWT authentication calls for all those users if needed.
Subject: Why aren’t DocuSign custom fields populated in the embedded ceremony?
Summary: The developer uses the C# SDK to create an integration that sends envelopes based on a DocuSign template. Envelopes must include text fields for recipients populated with C# code. The developer does not see the filled fields.
To respond: Here is the relevant C# code the developer was using:
The problem this developer had was that the one he provided in this code was not the same as the one on the envelope. It was a case sensitivity issue. The must be the same as the one used in the template for the fields to be assigned correctly.