I have a template in docusign and can use it to create an envelope using all fields available.
The problem is one of the fields should be a table with a variable length of rows, so I cannot use auto placing because I don't know how many will exists upfront.
The only solution I found till now is to create a brand new word document and upload it to create the envelope, but this is causing problems since this document is taking at lest 10 seconds to be parsed by docusign, probably due to its size.
The best solution will be to have a template and it could be possible to send a "table" field.
Anyone got this before? Any suggestion is welcome.
Perhaps put the table on a second document that you create dynamically? Remember that an envelope can have multiple documents. The signing experience proceeds from one document to the next.
Related
I have a requirement to first create the Docusign envelope in create status and later attach a list of documents and send it out.For this purpose I am first creating envelope with Envelope Rest API,adding documents using the Documents Rest API and finally sending it out.The anchor tabs that I initially added during create do not get picked up on the attached documents.It seems to ignore those tabs.Is there a way to add anchor tabs to get picked up on all documents.
Thanks
Lakshmi
One thing I would suggest checking is the anchor tabs scope - document or envelope. This is something that many people don't know about.
https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/tabs/auto-place/
"anchor population scope"
Also, are you using a composite template by any chance? that may matter
It is hard to say what the issue is without seeing your request. As your use case is complex and there are many variables, I'd advise opening a support case so we can have a look in detail
According to Docusign
Data Population Scope is a great way to speed up the signing process by duplicating their data throughout the document automatically
I want to prevent this replication from happening programmatically.
Is there an argument I can pass to Text that would prevent this? Maybe something like:
Text(data_label="some_unique_label")
I tried doing
Text(name="some_unique_name")
This did not prevent data linking between other Text fields. According to the Docusign documentation I need to set a unique data label for each Field. However, I am not finding a data_label option for Text.
You're looking for the tabLabel parameter.
Data is populated between fields that have the same tabLabel, so if you make those unique, they won't share data.
Using the Docusign API, I am trying to change the fields that exist on a document. When I first create the document, I am able to change field values using "tabs." I get how to do that.
When I am trying to edit, or in Docusign's terms "correct," a document after it has been sent out, but before being signed, I am having trouble figuring out how to access those fields again to change the values.
I have tried using the API avenue described here ( PUT /v2/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId}/fields ), but even after successful calls, the values of the fields aren't changing, and I believe it is because I should be trying to access the tabs, as I did when first changing the tab values as I created the document, instead of targeting the fields, since the two seem to be different. Any thoughts? Thank you in advance for your answers.
To update Tab values you should use the putRecipientTabs api.
Once a signer completes the Signing process, the tab values cannot be updated.
Also not all Tab values can be updated. See this answer for more information.
The putEnvelopeDocumentFields api is for a different purpose. Document fields are different from Tabs. Document fields are an array of name-value custom data strings to be added to a document. Custom document field information is returned in the status, but otherwise is not used by DocuSign.
I figured it out.
The "fields" we are seeing on documents are "tabs," and they are children of the recipients.
The hierarchy goes envelope > recipients > tabs, which tabs we were trying to change. Not envelope > document > fields, which refers to something else--just familiarizing with the language of the api.
Here is a link to the reference for how to change "fields" aka "tabs", and that link includes sample requests.
One thing that helped me target my actual fields, since I kept on getting an error that the field didn't exist for the recipient, is to do a get request of all available tabs and use that response body as the request body for the update call (where we change the field values). Then you know the field information will be accurate, paring the body down to exactly the "fields" aka "tabs" you are interested in targeting.
Is it possible to add extra pages to the middle of the document on envelope created and ready to send from a set template.
Use case:
Using DocuSign UI, Template-Sample saved with 4 pages, signing tab at the end of 4th page
Using API on code, envelope is created with the Template-Sample
Add 1 or more pages (with data contents) after 3rd page on template
Send for signing.
Yes. While the envelope is in the Created status (draft), it is no problem to change the envelope's contents.
Changing a specific document within the envelope is only supported by changing the entire document. That's possible, but the easier way is to have a series of separate documents in the envelope, and then only insert the new document.
Eg, if you still want the signing page at the end of all the pages, you'd have three documents:
The front matter document
The document that you're changing on the fly
The final document, including the signature page
Doing this sort of document manipulation usually involves the use of composite templates. Please ask additional questions if you'd like more help.
I've searched all over to find any information I can about this field. I have some emails that are being generated by one of my applications that crash notes each time you attempt to open them. If I compare the Document properties of one of these emails to a normal email, I find that there are many of these fields: $$$FormScript_0, $$$FormScript, $$FormScript_0, $$FormScript, etc.
Anyone know why these fields are generated and what purpose they serve? Just trying to rule them out as a cause of the crashed Notes.
MJ
I believe those items mean that the form is stored in the document. Some code on that form is crashing the client.