I have an envelope which utilizes a template with read only text tabs. Using the Java API, I am able to initialize these tabs with dynamic values for each envelope created. These text tabs include information such as customer first name, customer last name, etc.
I have one recipient with signing order 1 and role 'Receives a Copy' (the agent) and another recipient with signing order 2 and role 'Needs to Sign' (the customer).
The issue I am having is that, upon initial CC to the agent, all of the dynamic read-only text tabs are empty. Is it possible for the CC recipient to receive these fields with data upon initial send of the document? Otherwise, is there an alternative way to fill in dynamic data within a document so that CC recipients can see the data?
The option you are looking for is under Settings > Sending Settings > When an envelope is sent, write the initial value of the field for all recipients.
With that checked, the pre-populated fields will appear even if the role they are assigned to has not taken action.
Just a suggestion. What about if you reverse the signing order for the 2 recipients. In my opinion "Receives a Copy" role should receive completed document. If the agent need to approve it first, then perhaps you should use different role for the agent. The dynamic read-only fields are related only to the customer and will be visible to the CC only when signed by the customer
Related
How can I add hidden text fields or values into a document?
I have to receive documents and update a database with certain values. I want to add hidden fields into a document so that I could access the values when I get the envelope. How can I do that? The hidden fields I found in the documentation were focused on hiding sensitive data from a receiver. I want the field to be completely hidden.
You can use custom fields.
Custom fields are meta-data, hidden values that are associated with an envelope and you can use API to get/set them.
They are text fields limited to 100 characters, but you can have as many of them as you need.
Meta-data can be added at the envelope, document, and/or recipient (signer) levels.
Envelope-level meta-data can be optionally shown on the certificate of completion.
Here's a live API example that demonstrates use of the different types of meta-data while creating an envelope
I am using docusign to have contracts signed by various parties.
I am looking for a way to populate my contracts with an effective date field, I don't know a priori the order in which the parties will sign (i.e. I don't know who will sign last), but I couldn't find a placeholder to populate such field.
has anyone got a workaround for it?
Thanks,
If the sender of the document used the routing order feature to control who will be the last signer, then just use the dateSigned tab (field) type with the last signer.
If the signers are at the same routing level, then see my prior answer: https://stackoverflow.com/a/63651154/64904
Currently using the Docusign API to create an envelope request.
Is there a way to set the Name field as NULL or BLANK and configure my docusign template to prompt the user to enter that field when its blank but to allow them to edit that data if its pre-populated ?
In some cases we know this value and in other cases its not known and the user would have to type that data in at the time they sign (e.g. if they are Company Signatory).
Is there a way to configure Docusign to support this type of logic ?
When you use a name or email tab in DocuSign, the system automatically populates those tabs with the recipient's name and email. If you want an editable name field do not use the name tab, use a text tab instead.
I have SharePoint 2007 and SharePoint Designer 2007. I have a workflow that sends out an e-mail to admins when certain conditions are met. What I am struggling with is getting the Assigned To data in the TO part of the e-mail. I can do a lookup to get the Assigned To value in the body of the e-mail, but not in the actual To field (as Assigned To just isn't one of the options to select in this field, and any attempt to add this just doesn't translate at all into any sort of readable e-mail address).
So, my question is, how do I, using a workflow generated e-mail, send e-mail notifications utilizing the Assigned To field.
Thanks in advance.
I believe you'll need to have an action (preceding the "send email" action in the workflow) in which you set a variable equal to the value of the "Assigned To" field, retrieving the field value as an email address. Then use that variable as the recipient in your send email action.
I am using the docusign API on my website to allow users to sign documents. For this I have used tags such as [#<COMPANY>#] in my document before uploading it, so that it is visible to end user in the form of docusign tags of signing, entering text data, etc.
There is a certain document where I require user to enter multiple text fields. these are different text fields and hence he will be entering different values in them. For this I use [#<CUSTOMREQUIRED>#] and [#<CUSTOMTEXT>#] tags in document. However, whatever value user enters in one field is duplicated in the others. How do i distinguish between the tags?
If whatever value the user enters in one field is duplicated in the others, it's because the fields are "named" the same (i.e., have the same tab Label). If you want DocuSign to treat them as entirely separate fields, make sure that tabLabel (in REST API) [or TabLabel in the SOAP API] is set to a distinct value for each field.