I am working on a DocuSign integration and want to allow the sender of the envelope to view the control panel to drag and drop signature tabs onto the document.
I already have a successful implementation that sends an embedded envelope to the signers. However, for this specific requirement, I do not know a) the X/Y coordinates of the signing tabs, or b) any anchor string for the signature tabs.
I have looked at the DocuSign api and I cannot see a way outside of java, which isn't really what im going for.
I am hoping to use this in an iframe, similar to how the embedded signing panel is done.
I believe the EnvelopeViews::CreateSenderView method is what you're looking for.
You can create a draft, then do the CreateSenderView call to request a url to a session of the DocuSign tagging screen. Since you're wanting to go straight to the tagger, you can leave the send=1 parameter as-is. If you wanted the URL to go to the Documents/Recipients screen instead of the tagger, you could change the url you recive from DocuSign to end with send=0 instead.
Do heed the Information Security warning on that API call: The Sender View URL will provide full access to the Web Console for whoever the authenticated user is. This is not a concern if you have one membership per user, but if you are using a shared membership everyone will have access to all envelopes on that membership.
Related
We want to open sender view of draft/created envelope in our application using REST API and allow sender/user to add signature fields/tags in documents. This sender view currently shows and allow all the options where sender can add new recipient or modify, can change the document and etc. But we want to restrict sender to only can add/edit signature fields/tags, we do not want to allow user to modify any other envelope information or even can send from there.
In short words: Want to open sender view of envelope only for edit signatory fields/tags using REST API.
Could anyone help how we can achieve this.
You can start the view on the tagging page by adding send=1 to the API call. Eg:
https://demo.docusign.net/restapi/v2/accounts/{account_id}/envelopes/{envelope_id}/views/sender?send=1
However the user can still go back to the recipients page if they want to by using the "Other Actions" menu item.
An alternative is for you to figure out what your users need to do on the tagging page and do it for them programmatically. That way you're both providing a better user experience for them and you don't have to worry about them changing the recipients or documents.
What are they doing on the tagging pages? It is not hard for you to programmatically place the tags by using anchor field locating. See the recipe.
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
We have implemented the embedded signing process and at last step we get the embedded url. So, what we want is when I click on the embedded url I want to see the document in another language for eg. Norwegian.
Is it possible that using DocuSign API we can view documents in another language like Norwegian.
Thanks and Regards
Sandeep
DocuSign will always present the documents in the same exact state as the sender supplies them in -- having DocuSign translate the documents to another language, or make any other changes to the documents is not possible. The ability to configure "language" in DocuSign applies only to the DocuSign web console UI and other instructions that DocuSign displays to the Signer during the signing process -- not to the documents themselves.