Does anyone know the difference between using the Data Field in Standard set of fields versus defining a Custom field ?
JK
If you are talking about envelope custom fields - those are invisible during signing and should be used for meta-data only.
Here is a good reason to use envelope custom fields:
A loan origination system might have a loan ID and would put the loan ID as a meta data on all the DocuSign envelopes that pertain to that loan. This makes searching and cross linking easy.
Here is a good use case for regular "Secure Fields" or "Form Fields" or "Data Fields":
A system has address for a particular signer and wants to pre-populate that data for signing, but maybe give the signer an option to correct it. You put the data field on and then the user can fill it out or update it.
Hope this helps.
Related
If I have a TextField that is editable and the signer changes their Title while e-signing, is there a manner in which to monitor TextField edits? Currently I am using the EnvelopesApi.list_audit_events to monitor events. In this case, all I can view is that the signer either 'opened', 'viewed', or 'signed' the envelope. Although that is valuable information, I would also like to know which TextFields the signer edited and what the new values are? Did the signer change their email, title, name, etc? In this particular case I am using TextFields to display email, title, name, etc...
Does the Docusign API provide an avenue for fetching this information? If so, would you please provide a snippet demonstrating how to fetch this info?
You will have to do this by comparing the value that was in these fields before signing to the value you obtain from the envelope after singing.
There's no built-in event that will give you these changes as far as I'm aware, but it can be done using code.
I'm assuming here that what you're doing is setting the values of some text tabs and then want to know if the signer modified them or not. So, yes, you can do that.
When sending a document to be signed, with DocuSign, I can choose a Document Label for the document with a dropdown list which I can manage administrative access. I don't, however, see the purpose of the Document Labels since I don't see any obvious way of using them to e.g. filter documents and create statistical reports. More information on the subject can be found here.
Can somebody describe to me the actual purpose of having these labels?
Here is screenshot of the Document Labels section:
Hmm, I agree the documentation you linked is missing some detailed information on what they are for. In Classic (and soon again to be in the New UI) they were called Envelope Custom Fields, from the old documentation they are classified as "fields that can be used to record information about the envelope, help search for envelopes and track information. The custom fields are shown in the Message window when a user is creating an envelope. The custom fields are not seen by the envelope recipients."
Think of it as an invisible label that you can than use to report on later. In the Reporting section of DocuSign it's actually called "Custom Field" and can be added to reports:
Envelope custom fields (Document Labels) are labels used to classify, record, and track information about envelopes sent by a user. These labels are shown to a sender when an envelope is being created; they are not seen by recipients.
The values for an envelope custom field can be free-text entries, or selected from a list of possible values. Envelope custom fields can be required or optional.
It is a metadata over envelopes. For instance, if you want to associate a case number or Invoice Number present in your system with an envelope but you do not want recipient to see it then you use Envelope custom fields (Document Labels) for this purpose. Then you can search envelope based on this label value in the Manage tab in your DocuSign Account. So Document Label helps in mapping data in your system with the envelopeId plus it helps you send extra data on an envelope which you do not want recipient to see.
Scenario: Single document should be sent to two recipients, the 1'st recipient can only edit the fields and the 2'nd recipient has all the access.
Can anyone let me know, is there any possibilities that 1'st recipient can have only edit field access ( should not have sign access ) and other recipient should be able to edit fields and add sign in a single document in DocuSign.
There are currently seven different types of recipients you can use in your DocuSign transactions. See more information here
The DocuSign platform supports many different tab types and features. You can add signature, initial and information tabs to help your signers know precisely what actions you want them to take, where in the document you want them to sign, initial or add information, and in what order. You can also do things like pre-populate tabs with data, use calculated or conditional fields, and much more.
See more information here
If you do not add any tabs to an envelope then it becomes what's known as a Free-Form signing experience. During free-form signing the recipients decide where to place tabs on the documents as well as the location of those tabs, instead of the sender controlling those aspects.
In this case a menu list occurs on the screen listing multiple options (FirstName, LastName, Date, Signature, etc).
Now the question-
I am looking for one of the following behaviors-
1) Is there any way we can disable/ hide all options (FirstName, LastName, etc) in the above list except for the Signature field. In short I want to see just 'Signature field' in the menu. Is this possible?
2) Considering 'Free form signing' is the default behavior, is there any way to customize this default behavior?
I am actually signing the document using 'Anchor string' and if the anchor string is not present in the document I need to add a default 'Signature tab' at some default position. Is this possible?
Don't think of Free Form Signing as the default. Think of it as the fallback that your senders should not use.
Your senders should always add fields to their documents. To help ease the burden, you can use templates, your API program can place the fields on the document, etc.
At a high level, your senders want to get their documents signed by the signers. Making the signers figure out the Free Form Signing experience is a big mistake. Your senders are putting an unnecessary burden on your signers. The only thing that can accomplish is to delay or stop your signers from signing. And that's not in your senders' best interest.
1) There is no way to disable those various tabs during free form signing (FFS), or only display the 'signature tab'
2) If you enable 'document visibility', then FFS is not allowed and the envelope will not be allowed to be created in this case, if you want to consider this approach as a way to prevent FFS.
This is continuation to the following post
insert a page into document while sending envelope using DOCUSIGN
I have rephrased my question due to poor explanation before.
Any help is greatly appreciated.
I am not successful in finding a documentation about the following scenario.
I am trying to find whether is it possible to "dynamically" insert table in a PDF while creating an envelope out of Template. Assume that you have created a template with one signature and you want to give an option to insert other rows for multiple sinature.
No information found so far. Thats why i am trying to see if there is a way which i am not aware of.
Any reference to online material is greatly appreciated!!!
One option to facilitate your use case might be to create multiple Templates in DocuSign -- one for each possible number of signers, and then have your application logic determine which Template to use during Envelope creation based upon some logic within your application. For example, let's assume the following scenario:
Your application is an online loan processing application that collects information from the borrower, and then uses DocuSign to present the loan documents for signature.
If there IS NOT a co-borrower, then you only need signature from one person (the borrower).
If there IS a co-borrower, then you need signatures from two people (the borrower AND the co-borrower).
In DocuSign, you create two (nearly identical) templates:
Loan Docs - 1 signer : This template defines a single recipient role (Borrower) and the document(s) in the template only contain space for the Borrower's signature.
Loan Docs - 2 signers : This template defines two recipient roles (Borrower and Co-borrower) and the document(s) in the template contain spaces for both the Borrower's signature and the Co-borrower's signature.
If your application determines there is no co-borrower, then it creates the Envelope using the first template (Loan Docs - 1 signer). If your application determines there IS a co-borrower, then it creates the Envelope using the second template (Loan Docs - 2 signers).
So, that's one way of handling it. Another way of handling things would be the following:
Create a single template that defines Recipient Roles (and corresponding tags in the document(s)) for the maximum number of Signers you'd ever have.
When you make the "Create Envelope" API call using that template, only supply recipient information for the number of signers that are required for that specific Envelope.
For example, let's say that your template defines 2 recipient roles (Borrower and Co-borrower), and contains signature tags for each recipient.
If your application determines that there are 2 signers, you supply information for both signers in the "Create Envelope" API call.
If your application determines that there is just 1 signer, you supply information for only the Borrower in the "Create Envelope" API call.
DocuSign will simply drop/ignore any tags belonging to recipient roles that you did not supply information for in the "Create Envelope" API call. So, in the latter case (info supplied for only one signer), the space(s) in the document(s) where the second signer's signature would have appeared still exists -- it'll just be empty/blank (because there is no second signer for the Envelope).