Trending Topics: Latest from our forums (July 2024)

Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of July 2024. To make sure we see your questions on Stack Overflow, use the tag docusignapi.

Thread: How do I pre-populate fields in a document before sending it from the eSignature Rest API?

https://community.docusign.com/esignature-api-63/how-do-i-prepopulate-field-in-a-document-before-sending-it-from-the-esignature-rest-api-5792

Summary: This developer is sending envelopes through the eSignature REST API and they want to dynamically pre-populate fields (also known as tabs) in their documents.

Answer: You can pre-populate a field by setting the value property for that field when you create the envelope definition. You can find an example of this in How to set tab values in a template.

Alternatively, you can also use pre-filled tabs to create EnvelopeDocumentTabs that are visible to all recipients but can’t be edited.

Thread: Adding a hyperlink on PDF to sign

https://community.docusign.com/sdks-71/adding-a-hyperlink-on-pdf-to-sign-5746

Summary: This developer is sending an envelope containing a PDF through the Node.js SDK and they want to use that SDK to add a tab with a hyperlink to their document.

Answer: This can be done by creating a new custom tab. When creating the new tab, the tabLabel property needs to include the string #HREF_. The tooltip should be set to the URL that the hyperlink will direct to. The code snippet below shows how to do this with Node.js.

let hyperlinkTab  = docusign.Text.constructFromObject({
    documentId: "1",  
    locked: "true",  
    name: "https://www.google.com",  
    pageNumber: "1",  
    recipientId: "1",  
    required: "true",  
    tabLabel: "#HREF_Google",  
    tabType: "text",  
    tooltip: "https://www.google.com",  
    value: "Go to Google",  
    xPosition: "100",  
    yPosition: "100" 
    });

You can find examples for this using other SDKs in this blog post.

Thread: How to resolve a Cors error when trying to get an authentication token using authorisation code grant in Next.js

https://stackoverflow.com/questions/78723119/how-to-resolve-a-cors-error-when-trying-to-get-an-authentication-token-using-aut

Summary: This developer is trying to authenticate using Authorization Code Grant for their single-page application using CORS. They are receiving the following error:

Access to fetch at 'https://account-d.docusign.com/oauth/token' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Answer: At this time, it isn’t possible to use Authorization Code Grant with CORS for Docusign. Instead you need to authenticate using Implicit Grant, which means that you won’t need to make the API call that is returning this error. Because you cannot store a secret on the client with CORS, you also need to update the settings in your integration key, as shown in the screenshot below.

Additional resources

• Docusign Developer Center

• Docusign Developers Community

• @DocusignDevs on X

• Docusign for Developers on LinkedIn

• Docusign for Developers on YouTube

• Docusign Developer Newsletter