I am using iframe to get document signed by clients on ipad. There are attachments as well for each signer, but before attaching the captured image, I want to resize it. Is there a way to resize an image before attaching it with document.
Currently there is no functionality built in to the DocuSign platform that would allow the re-sizing of an attached image, DocuSign is an eSignature company and when they allow attachments on top of the documents that are about to be signed they should not be modified in any way as it could alter important aspects about the legally binding agreement that is being signed.
However I think you might still have a few options here to solve your issue. The two obvious ones that come to mind are:
Get the captured image from your recipients BEFORE they start the signing process.
Use a conditional tab to not allow the recipient to add an attachment unless it's within a certain size.
For the first solution you could use the Embedding feature to design whatever UI around the signing experience you'd like and in that case you can control the order of operations (i.e. have them upload the image first before clicking a button to sign) and you can then resize the image and add it to the envelope.
For the second solution, you could use the radioGroupTabs to add 2 grouped radio buttons to the envelope (so that only one can be checked) and say something like "Check this box if your image is within NxM size" and then the signer attachment tab only shows if they check that box. To do this you can make use of the ConditionalTabs feature.
For more information on Embedding DocuSign please see this page from the DocuSign Developer Center:
Embedding Feature
For more information on Conditional Fields refer to the User Guide (non-api use) and the documentation:
Conditional Fields User Guide
REST API Guide (search for term "conditional")
Related
Hi #all DOCUSIGN users,
Instead of reviewing the document and sign in every pages of the envelop document, i need to make the process simple. We will show the documents as like Terms & Conditions with agree option. Thus required to get the customer signature, only once in a form (basically within the application) and automatically signed off on every template document, in respective places, with that eSignature. Please suggest me the possibility to do with Docusign in a better way.
Thanks.
One option for single-click is to use the DocuSign Click product with clickwraps.
Here is an example of using it for Terms and Conditions just like you asked.
See if this does what you want.
I have been trying merge DocuSign in my application to make the user sign the documents I upload. Currently DocuSign allows us to add the signature tag at a static location, where we can provide the co-ordinates programmatically.
I would like to have a functionality where the signer can move the Signature tag anywhere over the page and insert the signature at the selected location.
Is there any good way to do this using DocuSign API's. Are there any DocuSign API's currently which do this?
Can anyone help me with this?
You want the signer to have the ability to dynamically position where the signature will go? Just send the document with no tabs at all and the signer will be asked to select the type of signing field (signature, initials, date, etc) and then choose its placement.
However, this is typically not a good UI. Instead, it is better for the sender to pick where the signer should sign. This can also be done dynamically using the "Sender View."
Not entirely sure about the part where the signer can move the tabs. But Anchor-Tabs sound like something that might help. I have asked a question on it a few minutes ago with sample code.
DocusignApi - Attachment with SignHere tab on the third page
The following link might also help.
DocusignAPI - Sign here tabs
Few questions about PowerForms
What is the real advantage of using PowerForms? In which case(s) it is most useful?
In Docusign Classic View >> PowerForms, there is an option to download Form Data as XML and CSV. Can we download this data using APIs?
For this question, I referred this thread "Can We get a report for the values filled in radio button in DocuSign Envelope".
PowerForms are an easy way of referencing a DocuSign Template through the API without writing any code. They are intended for less technical end-users who want to quickly access a Template through either email delivery or through a direct link (URL) but don't know / want to code it up. Instead they manually initiate such requests through a created PowerForm.
With regards to the form data question- yes, you can programmatically retrieve the form data through the API. You need to keep in mind that DocuSign tabs (aka fields) are always with respect to recipients and not the document itself.
Therefore, you can make the Get Tab Information For Recipient API call (REST version linked).
I just wanted to understand certain terms such as
1) what is a template in context of docusign
2) What is an envelope an when do we use it ?
3) What is embedding signature ?
Basically my client wants to populate a pdf contract form with certain data got from a form. Would liek to send the pdf form to get it signed by the client...
Although the form maybe same the data fields in it may change ..
so what approach should be taken
a) template or b) embedded ?
assuming a blank form needs ot be sent for signing how does that work ? does the form goto the client phsycially ? or do they come on your site to sign it ...
i am sorry if i am all over i just wanted to understand the process frolm a developers stand point.
I suggest you read up on the DocuSign Developer Center. In particular the Explore -> Features section has pages dedicated to Templates and Embedding (among other topics) that have much of this info.
what is a template in context of docusign
Templates help streamline the sending process by allowing you to - at design-time - save document(s), recipients (or placeholder roles for recipients), tab locations and types for those recipients, routing and workflow, and more. Then at real-time when you want to request a signature you simply match a recipient to a role on your template and they automatically inherit all that previously configured workflow. The data they enter into their fields will still be specific to them, but things like the location of the signature tabs you've placed for them will always be the same, any conditional or dynamic workflows will be the same, etc. Templates are very flexible and have many features and options so I suggest you read up on them both through the Features -> Templates page but also through the API docs.
An alternative to requesting a signature from a Template is to request a signature on a Document. This is a similar call except that you need to define the tab locations, recipients, routing, etc every time before sending. With a template you just define all of that stuff once, at design time.
What is an envelope an when do we use it?
Definition from Explore page overview: "An envelope is basically a "container" used to send documents to recipients. The envelope carries information about the sender and timestamps to indicate the progress of the delivery procedure. It can contain collections of Documents, Tabs and Recipients and is analogous to a physical envelope you would send through the mail".
An envelope can have as many documents as you want in it (I think there's a total size limitation but that it's set high) and can be addressed to 1 or more recipients (actually up to 1,000 if using Bulk Send feature). And once the last person is done signing the docs in the envelope a Certificate of Completion (CoC) PDF doc is automatically generated and placed inside the envelope as part of an audit trail for your review.
What is embedding signature ?
Embedding allows you Embed the signing workflow directly into your website or app or whatever you are building. The signing still takes place through a DocuSign endpoint but you can generate the unique signing URLs yourself and open in an iFrame or Webview. You can control the branding around the signing experience and you also have control over where the user is re-directed to after they sign. See the Features -> Embedding page.
Regarding your questions about form fields, yes DocuSign also supports that- you want to use Data Fields (called textFields in the API), see the Features -> Stick-eTabs page.
Lastly, in terms of what approach should be taken (Template or Embedded) - hopefully my first answer cleared this up but those are not mutually exclusive. You can create an envelope from a Template or from a Local Document(s), and you can either Embed the signing experience or have it remote (i.e. recipient receives an email to start signing). To make a recipient an Embedded one, you have to set their clientUserId property. See the links I've referenced.
DocuSign also has sample code in 6 different languages for 9 common API scenarios, including Embedding, Requesting a signature from a Template, on a Document, and more. See the API Walkthroughs:
http://iodocs.docusign.com/apiwalkthroughs
DocuSign has free code samples in 6 different languages
I would like send an envelope with below two options.
Here we go,
User should sign in SignTab if it is first page of document.
User can sign anywhere if it is other that first page.
Is it possible to have this option using docusign API.
If Yes, Please let me know what are the parameters should I send?
Unfortunately you can only have it one way or the other currently- either you make the signing experience a Free Form signing experience (meaning the recipients can place tabs anywhere they want on any page of the envelope), OR you set 1 or more tabs in the envelope document(s) and the recipient will only be able to take action on those tabs and they will not be able to place tabs wherever they want.
The DocuSign Developer Center has a page devoted to Stick-eTabs under the Features section, they also talk about Free Form signing further down:
https://www.docusign.com/developer-center/explore/features/stick-etabs