DocuSign template - multiple recipient roles sign on different sign tabs - docusignapi

I have a DocuSign template template-1 with multiple recipient roles say signerrole-1 and signerrole-2.
Template-1 has multiple signature tabs, viz, signtab-1 & signtab-2.
Using REST API, I am trying to create the envelope so signerrole-1 signs signtab-1 and signerrole-2 signs signtab-2.
I am not clear on how to associate signerrole-1 role and signerrole-2 role to signtab-1 and signtab-2 respectively using api java.

The template associates roles with tabs (fields) in the document(s).
When you create the template, you create signature tabs for the specific roles. It is easiest to do this by using the Web interface to DocuSign but you can also do this using the Create Template API call.
Later, when you submit a new envelope using the template, you associate specific people or signing groups with the roles defined by the template. See this recipe for an example.
When you create the envelope to be sent, you do not create or reference the signing tabs. They are defined by the template.

Related

How can I create a template with fields that is view only? [DocuSignApi]

I have a template that is configured with a recipient that has read only fields and only a signature control. The read only fields/tabs are populated in the view request my API sends to DocuSign to get the signature url. However I'd like to create a new duplicate template that does not have the signature control and is configured to only require the recipient to view the document. This way the only signature event that is set by DocuSign is "viewing_complete" and not "signing_complete" when they're done viewing the template/document.
Edit: The purpose of this is it gives the user a read only view of the template/document so they can catch any errors in the mapped fields/tabs to give them a chance to correct it before signing a final version.
Not sure if you want to create this template from the API or from the web app.
You can easily do this from the web app and if you want to do from the API, you can get a log of the API calls to see how it was done.
When you create a template from the web app, in the first screen, you can pick recipients and there's a drop down with different types of recipients:
Select the "Needs to View" recipient type for your needs.
It's not possible to configure a template to accept populated tabs for a recipient that is set as Needs to View or to preview an envelope recipient view and have the tabs populated, but not show the Signature control.

Get Document id of the template

I have the Docusign template with 3 document in that template. I have three button and on each button click i need to access the different of the template. How it can be accessed.
We consider an envelope a single unit. So we don't provide ways to just see 1 document in the envelope. You can create 3 different envelopes for your scenario if you want buttons in your app that goes to each of them separately.

Docusign for Salesforce template - Show merge fields to all roles

I am trying to setup a template using Docusign for Salesforce. My template is 20 page long and has about 50 merge fields to be populated from Saleforce. These merge fields are read only. We have multiple signer roles - 6 signer roles to be specific. In the template, all 6 signer roles should see all the merge fields.
Problem is when these merge fields are added to template by drag and drop, you have to select a single role and then drag and drop a field on template.
Is there a way to prepare a template so that merge field display on the template can be added for all roles in a single go?
Docusign support was able to resolve the question.
We need to edit the tags after they are added to the template. Click on each tag and go to Collaboration and check the box to "Recipients Can Collaborate.

Can the TemplateID be changed through the REST service - "Modify a Template"

It appears from the REST API documentation that the TemplateID is a modifiable field through the "Modify a Template" call. When we test this we can change other fields using this call however the TemplateID does not change from our tests.
We are currently managing over 150 server templates and want to sync the TemplateIDs across our Demo and Production accounts to streamline the template migration process between our two accounts. Please advise on if/how it's possible to modify the templateID through the API.
Thank you.
The TemplateID is unique to the template upon randomly being generated by the system.
There is no way to assign or re-assign a TemplateId.
They will not match between different environments

Duplicate fields on signing interface

I am building up an envelope using multiple templates through the API using CreateEnvelopeFromTemplates.
Sometimes the server side templates used to build the envelope contain the same logical fields
e.g. two templates used, both have fields of "Account Number"
How do I make it so when the signer enters data in one account number field, it updates the other account number field with the same data immediately in the signing interface?
It is required to prevent the signer from typing one account number on one document then a different account number on the other document in the same template.
The business logic for the document requires this so removing the duplicate account number fields would not be an option either.
There's an account-level setting that you can configure in DocuSign to force this behavior (i.e., ensure that like-named fields throughout all Documents in an Envelope always contain the same values). Simply login to the DocuSign web console (as a user with Administrator rights), navigate to "Preferences >> Features" and on the Features page, set Data Population Scope to "Envelope". (See page 27 of the DocuSign Admin guide: http://www.docusign.com/sites/default/files/Account%20Administration%20Reference%20Guide.pdf)
Because this is controlled via DocuSign account-level setting, there's nothing special you need to do in your CreateEnvelopeFromTemplates API call -- just configure the account setting and you should be good to go.

Resources