For embedded signing , when a user starts the signing session for the first time, there is a disclaimer that can be shown to him, I know that this can be customized in the preferences.
But where do i show/hide/change the actual buttons that are shown to the user , for example there is a Review, Decline, Finish Later and Sign on paper buttons shown to him. I need to hide last two of those four buttons, How and where can i do this ?
The code i am using is from the api code walkthough for java and there is a template setup for our demo account that we are showing to the user.
Also is there a way to customize the way the button looks or can we upload a button that we already have within our site? .
Thanks in advance...
Generally speaking, there are several mechanisms for controlling things like which buttons (functions/features) are available to Signers:
Account-level settings (controlled by the DocuSign account admin via the web console: Preferences >> Features)
Brand-level settings (controlled by the DocuSign account admin, via customization of "Resource file(s)")
Template-level settings (controlled by anyone with access to edit the Template's settings in the web console)
Envelope-level settings (controlled by the sender of an envelope either via parameters set with the API call, or when manually sending an envelope via the web console)
The visibility of the Decline button can be controlled via the following means:
Brand-level setting (in the Signing Resource File): DocuSign_DeclineAllow boolean setting
The visibility of the Finish Later button can be controlled via the following means:
Brand-level setting (in the Signing Resource File): DocuSign_FinishLaterAllow boolean setting
The visibility of the Sign on Paper button can be controlled via the following means:
account-level setting (Preferences >> Features): Sign on paper checkbox
template-level setting: Allow recipient(s) to sign on paper. checkbox
envelope-level setting (via API): enableWetSign boolean flag
The visibility of the Change Signer button can be controlled via the following means:
account-level setting (preferences >> features): signers can reassign envelopes checkbox
template-level setting: Allow recipient(s) to change signing responsibility.
envelope-level setting (via API): allowReassign boolean flag
The following guides may be helpful to you:
Branding guide:
REST API guide:
Administrator guide:
To hide the Finish Later button, you'll need to edit the Signing Resource file(s) for the Brand you plan to use with your envelopes to set the DocuSign_FinishLaterAllow element value to false -- including especially the "Captive" resource file for the "embedded signer" scenario. See the Branding Guide I've linked to above for information about accessing/modifying the Signing Resource file(s). Then, simply associate that Brand when sending the envelope via API by specifying the brandId property as part of the API request.
To hide the Sign On Paper button, you can use the Account-level setting, or the Template setting (if accessible/visible), or Envelope-level setting (set enableWetSign = false in the API call).
Regarding the question about button style -- while it's technically feasible for you to modify the CSS used for various elements of the DocuSign UI (if the "allow css upload" feature is enabled for your DocuSign account) -- I'd highly recommend against it. Modifying the CSS file can have very unpredicible results, and there's no easy way to "undo" your changes and get back to square one. Save yourself a lot of time and frustration, and live with the existing/default button style :)
Related
How to hide "Decline to Sign" feature from other actions in DocuSign envelope?
I'm using Java esign package. Also I couldn't find any option to turn it off in the web console.
Looks like there isn't a setting that allows you to remove the Decline to Sign Button in the DocuSign Web Application. However, You can hide its visibility.
To do that you need to set the DocuSign_DeclineAllow to False in the Signing Resource File, you can check how to do so, in this article:
https://support.docusign.com/s/document-item?language=en_US&rsc_301&bundleId=docusign-signing-resource-file-guide&topicId=docusign-signing-resource-file-guide.pdf&_LANG=enus
I am sending embedded request using rest api. I can get recipient view url by setting authentication method as 'email'. In this view there are other actions like void, delete, view history, view certificate. But I want to hide this options for some user and show it for some user. Also I want to hide some actions and not all in some cases. Is there any way using api or some setting to achieve this?
In the "Other Actions" dropdown:
View History: Account wide setting, either enabled or disabled. You will need to reach out to DocuSign support to enable/disable this option.
View Certificate: Account wide setting, either enabled or disabled. You will need to reach out to DocuSign support to enable/disable this option.
Void: This should only appear if the Sender=Recipient case.
Decline: Option to decline can be controlled in the signing branding file.
I am working on SOAP UI to test Docusign methods. I am getting emails and attachement with signature(anchor tab). But I am getting only signatures to be selected but not able to
allow user to sign using mouse. How to enable this feature?
Thanks.
I believe what you're talking about is how DocuSign gives signers the ability to adopt one of the default signature styles or you can draw your signature using the mouse. This is an account level setting that needs to be enabled in your account.
When your signers are signing if they do not have the ability to draw in their signature using the mouse, then most likely they have "Disable Draw Signature" checked in your account settings.
To resolve try the following:
1. Login to the Console.
2. Go to Preferences -> Features page.
3. There should be a "Signature Adoption Configuration" hyperlink. (if not contact your Account Manager to have that enabled)
4. Open the Signature Adoption Config screen by clicking the link.
5. Un-check the "Disable Draw Signature" option.
Then send another signature request and your recipients should have the ability to adopt their signature or draw their own.
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