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.
Related
I have a requirement where i want to validate a template using Access Code, but i want to bypass the access code validation by passing the Access code programatically(similar to how we can bypass the Initiator landing page https://docs.docusign.com/supportdocs/ndse-help/Content/populate-custom-fields.htm#pnz1578456644088).
There is a value you can enter to bypass the access code validation. If you append the parameter ActivateOnly=1 at the end of your Email PowerForm URL, the recipient will not have to enter an Access Code
A Sample PowerForm URL would look like this:
https://www.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=ad01e352-158a-4380-96c9-9cbc4366028t&ActivateOnly=1
It is explained in more detail here:
https://support.docusign.com/en/articles/Email-PowerForms-How-to-remove-system-generated-Access-Code-requirement
The problem with this option is that it requires users to access the powerform from their email
If you need the template to be both available to your internal sending users as well as your Powerform, then split them up.
Duplicate your template by using "Create a Copy" from the drop-down menu. Rename the one being used by your PowerForm and unshare it with your users. Remove the Access Code requirement from the template role.
Edit the duplicate template. Ensure this one is shared with your users.
If a person has previously filled out a contact us form on our website, the next time they visit that form I would like their information pre-populated. Using Kentico EMS and the form builder, how can I make that happen?
you can access the contact informant via macros or custom macro methods and place it in the contact form default values (I would use an alternative form), but often you do not know if the user already exists unless they are logged in or enter the same email (which you would then need to add a client side trigger to Ajax an api once the email field is filled out, check for that contact in the api, return json of their info and populate the form).
to build the api you can either use the Kentico rest service or if you need more flexibility use the web part to api coupled with a repeater with custom query, adding the right where condition through macros.
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.
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.
Is it possible in the dev environment (or production for that matter) to brand the page that a user is redirected to for embedded signing?
Yes you absolutely can brand/configure the Embedded Signing iFrame window. The way you do is, you configure your branding through the DocuSign Console, then you provide a brandId in your API request to chose which branding profile to use (you can save multiple).
Try logging into the DocuSign Console at demo.docusign.net and then click your profile icon in the top right and go to
Preferences -> Branding
From there you'll see that you can create and save multiple branding profiles. Within each profile you'll see the various screens you can configure, including the signing window. Then, in your signature API request, at the envelope level you add the property
brandId
to your JSON or XML formatted request body and make sure you provide a valid brandId for it's value. To get a list of brand Ids programmatically, you can make the following call:
Get Brand Profile Information