enveloper | Transactional email microservice | Email library

DocuSign doesn't have the ability to do this yet, unless you use the API or PowerForms.

If you use the API or PowerForms to create the envelope, then you can explicitly set the values of the fields. (You'll need to calculate them in your application.)

There is the current capability to automatically set the day. To do so:

1. Add a Date sent field
2. Change the Data label for the field to be dateSigned
3. Change the Formatting options for the field to have a white color so it will be invisible on the page.
4. Add a formula field
5. Edit the formula for the formula field. Set it to Day([dateSigned])
6. Result: the formula field will show just the day of the date that the document was signed. Eg "30" Unfortunately it will not have the "th" suffix that you'd often like for an English reader.

Documentation

There is an enhancement request for this. Ask DocuSign customer service to add your information to TRI-8003

Yes, I believe you can do this, but not via the API. Instead, you set the URLs at the account level via the Brand:

1. Open the eSignature Admin tool
2. Navigate to Account / Brands
3. Click on the brand you want to change.
4. At the bottom of the screen, Click on Destination URLs
5. Set the URL for when the recipient has completed signing.

If some of your account's envelopes should redirect to your application server, and others should not (sent manually?), then you'll need more than one brand for your account. (One brand will have the redirect settings, the other will not.)

Then, when your app sends an envelope via the API, set the brandId and brandLock attributes in the envelopeDefinition object.

Note that the Brand feature is not included with all types of DocuSign accounts. Consult your DocuSign Account Mgr for more info.

If the envelope is in "draft" (created) state - would should be able to do that. If the envelope was already sent - it has to be corrected. That's a legal requirement. It was sent to some recipient and now you modify it (in any way) then it's technically a correction, you can't avoid this.

Answer # 1

I do not believe so. If this workflow is a common occurrence, you might consider creating a third template containing the documents & tabs of the first two templates.

Then, you could simply send an envelope containing just that third template. In this case, you would only have to specify the recipient's information once.

However, we usually advise the composite templates pattern since it's far easier to customize and scale when your use case changes in the future.

Answer # 2

No. You are mixing two different DocuSign design patterns, i.e you should not mix Composite Template and TemplateRole.

Template Role is needed when you have one server template and you want to prepopulate the signer information and/or any DocuSign tab information present in the template from your application.

What you can do (which I'm sure you've realized) is to retrieve the signing authorities for the templates with a GET /template before making your POST /envelopes containing composite templates.

Since you don't see the error in the DocuSign logs, and also from the wording of the error, I suspect that the problem is happening within your machine, before the request is sent to DocuSign.

So the solution is to debug within your application. For more help, please provide your code which causes the error to be raised.

There's a back-end setting for Allow HTML input in the API.

You won't be able to configure this setting yourself - you can either reach out to your Account Manager, or have an administrator on the account open a case with DocuSign Support to request that setting be enabled.

If you open a support case, be sure to include your Sandbox account ID if you would like to have it enabled in the Demo environment as well.

The RecipientView is simply the API method for obtaining an URL to a Signing Ceremony for a particular recipient.

If you don't want a recipient to see a document, then you must use Document Visibility--that includes using the excludedDocuments attribute, but other attributes and tabs need to be set up too.

Once you have an envelope with document visibility set up for some/all of the recipients, you can use RecipientView to obtain the URL for a specific recipient's signing ceremony.

In the DocuSign Developer Center for the REST API family you can go to the Guides -> Features -> Recipients page which has the list of recipient statuses. See the following page:

https://developers.docusign.com/esign-rest-api/guides/features/recipients#recipient-statuses

For reference, here are the statuses listed on the above page:

created: The recipient is in a draft state. This is only associated with draft envelopes (envelopes with a Created status).

sent: The recipient has been sent an email notification that it is their turn to sign an envelope.

delivered: The recipient has viewed the document(s) in an envelope through the DocuSign signing web site. This is not an email delivery of the documents in an envelope.

signed: The recipient has completed (signed) all required tags in an envelope. This is a temporary state during processing, after which the recipient is automatically moved to Completed.

declined: The recipient declined to sign the document(s) in the envelope.

completed: The recipient has completed their actions (signing or other required actions if not a signer) for an envelope.

faxpending: The recipient has finished signing and the system is waiting a fax attachment by the recipient before completing their signing step.

autoresponded: The recipient's email system auto-responded (bounced-back) to the email from DocuSign. This status is used in the web console to inform senders about the bounced-back email.

The name.TabLabel property needs to exactly match the label used in your template. So, for example, if your tag was set up like this:

you would use name.TabLabel = "Text1";. Setting name.Value = "My Name"; would then populate that tag with 'My Name', assuming your template is being referenced and your signer is mapped to the template role.

Code sample for sending from a template with tags populated follows. This assumes the signer role name is "Signer 1" and the tag label is "Text 1"