Trending Topics: Latest from our forums (November 2022)

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

Thread: How to avoid placing fields everytime a contract is generated with Docusign Gen and Docusign Envelope in Salesforce?

Summary: The developer is using Docusign Gen and wants to have a repeatable process where they have tabs (singing fields) placed in the document once and can reuse this template repeatedly similar to how you would do with Docusign eSignature.

Answer: It is possible to set up an eSignature envelope template configuration that works with anchor-tag/auto-placement, either with or without a static document pre-uploaded into the template. We offer default anchor fields out of the box that are listed in this support article. But it’s also possible to create your own custom merge fields with defined anchor text with the {r} wildcard placeholder. The trick is to also ensure your recipients use the standard role naming conventions of “Signer 1”, “Signer 2", etc. Example: If you have \s1\ on the document, then that will get assigned to the recipient you’ve defined with the role name of “Signer 1”; \s2\ for “Signer 2”, and so on. If you create a custom field with the defined anchor text of something like \ObjectName_FieldName_{r}\, then on the document you place the text as \ObjectName_FieldName_1\, that field would be assigned to “Signer 1”; \ObjectName_FieldName_2\ would be assigned to “Signer 2", and so on.

More information can be found in this Docusign eSignature for Salesforce Admin Guide article.

Thread: Do envelopes in Docusign developer accounts disappear?

Summary: This developer is wondering why envelopes disappear from their developer account. 

Answer: The developer account is meant to be used for developers to build and test their integration. It gives developers unlimited access to almost every Docusign feature free of charge. However, there are a few limitations to using the Docusign developer account. One of them is that the data (envelopes and documents) is only stored for 30 days and is later removed from the developer account. In addition, transactions made using the developer account are not legally binding. If you want your information to be stored permanently, you need to use a production account.

Thread: Docusign eSignature REST API v2.1 Java : Document in html format with non English language

Summary: The developer is building an integration using the Java eSignature SDK that sends documents in a variety of foreign languages. They are seeing an issue where certain Unicode characters are not formatted properly on the resulting Docusign envelope.

Answer: Unicode characters have to be properly encoded into the Base64 string that is sent via the Docusign eSignature API when you make a request to send a document to be included in an envelope. Here is the proper Java code to do this (including the sample string provided by the developer):

String htmlDoc = ".... .... <p>Signera arbetsorderavtal för anställningsnummer</p> ......";
Document document = new Document();

Additional resources

Inbar Gazit
Inbar Gazit
Sr. Manager, Developer Content