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
Related
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.
I want to use DocuSign dll to sign the document but I don't user to redirect to DocuSign portal, is there any way to customize the DocuSign dll.
Well, there is not much to me to go by, so here are some thoughts.
You don't have to redirect, you can instead embed in an iframe. this may solve the issue if your concern is that the URL is visible in the browser as DocuSign vs your URL.
However, if you just don't want to use a cloud provider then you need to use DSA (DocuSign Signature Appliance) which means you'll get a set of servers that you have to maintain by your IT dept and in theory you can have your users sign documents without connecting to the internet.
You can brand the DocuSign signing ceremony to match your site's colors, fonts, add your logo, etc. See the branding docs
The signing always takes place at the DocuSign website. It can be embedded in an iFrame as Inbar mentions, but iFrames introduce their own issues.
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.
Can we navigate signer who is on a Mobile device (Salesforce 1) to a visualforce page when the document is signed and the submit button is clicked?
Yes you can accomplish this. You'll need to use the DocuSign API and more specifically, the Embedding functionality which will allow you to sign through a webview or an iFrame on the mobile device.
With Embedding you can control the redirects URLs based on actions the user takes. For instance, if the user signs you can navigate to the Visual Force page in question. Or, if the user declines to sign then you can navigate them to a different page if you'd like. Same thing for if they hit the X to close the signing window.
To get started with learning DocuSign's APIs check out the DocuSign Developer Center:
http://www.docusign.com/developer-center
And for code samples of Embedded Signing in 6 different language stacks see the bottom 3 API Walkthroughs in the API Tools section:
http://iodocs.docusign.com/apiwalkthroughs
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 :)