Docusign - Create envelope from PDF form - docusignapi

We have a document, a PDF Form, and we have labelled one of the fields in the PDF form as “prescriber_signature” where we want to place a signature placeholder.
We are sending a document to create the envelope and here is my request body. Attached is the document that we are sending as part of this multipart request.
We are not successful so far in getting the signature placeholder placed per the label name “prescriber_signature”. Can you look into the xml and suggest us what needs to be done please?
XML Body:
?xml version="1.0" encoding="UTF-8"?>
<envelopeDefinition xmlns="http://www.docusign.com/restapi">
<emailSubject>DocuSign API - Signature Request on Document</emailSubject>
<status>sent</status>
<documents>
<document>
<documentId>1</documentId>
<name>Samplefileflattenedfalse.pdf</name>
</document>
</documents>
<recipients>
<signers>
<signer>
<recipientId>1</recipientId>
<clientUserId>1234</clientUserId>
<email>prasanna112#gmail.com</email>
<name>POC Prescriber Name</name>
<tabs>
<signHereTabs>
<signHere>
**
<anchorString>prescriber_signature</anchorString>
**
<anchorXOffset>1</anchorXOffset>
<anchorYOffset>0</anchorYOffset>
<anchorIgnoreIfNotPresent>true</anchorIgnoreIfNotPresent>
<anchorUnits>inches</anchorUnits>
</signHere>
</signHereTabs>
</tabs>
</signer>
</signers>
</recipients>
</envelopeDefinition>

I think you're combining to unique DocuSign features here. The first feature is the ability to transform PDF form fields into DocuSign fields - such as signature fields, data fields, etc.
The second feature, which is completely separate, is the Anchor Tagging feature (also called AutoPlace). With this feature you can tell DocuSign to place any types of fields at certain locations in your documents. Those locations are based on the actual document content itself (i.e. what the viewer sees), not the PDF form field names.
From what I can tell I think you are trying to use the first feature listed above (PDF Form fields transformed into DocuSign fields). As such, please see the following page from the API Guide which explains the transform rules:
DocuSign API Guide - Document Parameters
The following information can be found through this page:
When extrapolating Adobe text fields, the following Adobe names correspond to DocuSign names:
Adobe name contains DocuSignSignHere or eSignSignHere = DocuSign Signature
Adobe name contains DocuSignSignHereOptional or eSignSignHereOptional = DocuSign Optional Signature
Adobe name contains DocuSignInitialHere or eSignInitialHere = DocuSign Initials
Adobe name contains DocuSignInitialHereOptional or eSignInitialHereOptional = DocuSign Optional Initials
Adobe name contains DocuSignEnvelopeID or eSignEnvelopeID = DocuSign EnvelopeID
Adobe name contains DocuSignCompany or eSignCompany = DocuSign Company
*Adobe name contains DocuSignDateSigned or eSignDateSigned = DocuSign DateSigned
Adobe name contains DocuSignTitleor eSignTitle = DocuSign Title
Adobe name contains DocuSignFullNameor eSignFullName = DocuSign FullName
Adobe name contains DocuSignSignerAttachmentOptional or eSignSignerAttachmentOptional = DocuSign Optional Attachment
Any other name will default to a DocuSign data (text) field

Related

Docusign responsive signing text tabs

I have a form that has a few fields that need to be filled in for the last signer after 2+ people have already signed it. They cannot be prefilled as they are not known at the time the document is generated.
I'm sending an HTML document to the Docusign API and have it working great for the first set of signers. The problem is when I try to add text tabs to the document (<input data-ds-type="text" /> following this page) I receive a 400 error back from the Docusign servers with this error message:
Some of the supplied HTML tags, attributes or CSS properties on a guided forms tabs were not allowed. Disallowed: HTML attributes [input:data-ds-type]
How can I do this?
Check that your HTML is valid and all characters in it are correct.
The responsive signing HTML validator is much more strict than the one browsers typically have. a bad HTML will break the whole thing and won't let you create the envelope and the error message unfortunately right now is not as helpful as it can be, but I'll ask to improve this.

Add HTML input field to Advanced PDF of Netsuite

I want to add a HTML input field to Advanced PDF of Netsuite. We have a requirement from client where we need to add an editable field to the Advanced PDF. If anyone has tried doing this previously please help. I want to add a textarea to the Advanced PDF.
The BFO Report Generator documentation has details on how to create PDF form fields.
http://bfo.com/products/report/docs/tags/tags/input.html
http://bfo.com/products/report/docs/userguide.pdf (page 57)
The code would look something like
<input type="text" name="address" lines="4" scrollable="no" />
However, take note that this functionality is only available in the "Extended Edition" of the Report Generator. I am not sure what version NetSuite licenses.

Can we get URL details of a HotSpot Link inside a richtext content

Is it possible to get the URL details of a Hotspot link inside a RichText content.
Like we can get the DocLink details inside richtext with the help of NotesRichTextDocLink class
Access to Rich text using the native classes of Domino is relly limited. Thus, I'd suggest to export the Rich Text to HTML and parse it to get the url of the link.
See: How to export Rich Text fields as HTML from Notes with LotusScript?
My prefered way is ConvertToMIME.

Docusign REST v2 API : Populating Tab text data when creating an envelope via template

First time that I've used the Docusign API and it seems great.. but am having issues...
I've tried a number of various changes to my XML format and just cannot get any tabs to populate with data via my API call. I created a simple template & a single Signer, called "Checker". I added a label to the template called lblTest. I've verified that the "Checker" is a signer and can see the tabs that I add.
All that I'm trying to do is pass through a value that I want to display on a single template in an envelope.. that's it.. should be very simple!
I'm following the code here --> http://iodocs.docusign.com/APIWalkthrough/requestSignatureFromTemplate
The document is being sent, but the tab data is not being populated.
The XML I'm POSTing to ~/envelopes is as follows
<envelopeDefinition xmlns=\http://www.docusign.com/restapi\>
<status>sent</status>
<emailSubject>DocuSign API - Signature Request from Template</emailSubject>
<templateId><<redacted>></templateId>
<templateRoles>
<templateRole>
<name>Some Fake Person</name>
<email><<redacted>></email>
<roleName>Checker</roleName>
<tabs>
<textTabs>
<textTab>
<tabLabel>lblTest</tabLabel>
<value>12345678</value>
</textTab>
</textTabs>
</tabs>
</templateRole>
</templateRoles>
</envelopeDefinition>;
I've posted my API call, to show envelope recipients, as suggested in other posts.
API call result for
https://demo.docusign.net/restapi/v2/accounts/749390/envelopes/08C591B3-F6A4-4A9B-80DA-F7B542E58FE2/recipients?include_tabs=true&include_extended=false
API Call Result: 1 1 789ccf19-7dea-4e1a-bb50-9d273d128105 false Checker 1 created false 1 1 1 56cbbdfd-4f97-492f-9612-015f5ab19843 42 6 false false lblTest false false false false 8 false 60 false false 11
Thank you -- I've spent way too much time on this and am pulling my hair out in frustration!!!
Try changing <textTab> to <text> -- like this:
<textTabs>
<text>
<tabLabel>lblTest</tabLabel>
<value>12345678</value>
</text>
</textTabs>
Since you're using XML format with the REST API, this page will be helpful >> https://www.docusign.net/restapi/help -- it lists the format of all API requests and responses, in both JSON and XML.

SharePoint - Custom Dataview - Link Rendering Issues

I have a custom SharePoint page with several dataviews. The dataviews essentially filter documents matching a certain criteria from a document library and display a link to the document along with some other meta data.
The problem I have is that when a document has a single quote in it's title, the character is being rendered as ' and invalidating the link. This is the code within my custom page that is displaying the invalid link.
<A onfocus="OnLink(this)" HREF="{#FileRef}" onclick="return DispEx(this,event,'','','','','{ddwrt:ListProperty("DefaultItemOpen")}','{ddwrt:MapToControl("", string())}','{#HTML_x0020_File_x0020_Type}','','{ddwrt:GetUserID('CheckoutUser')}','{$Userid}','{ddwrt:ListProperty("ForceCheckout")}','{$FieldIDA5KNTB}','{ddwrt:CurrentRights()}')"><xsl:value-of select="ddwrt:UrlBaseName(string(#LinkFilename))" /></A>
Does anyone have any thoughts on how I can ensure the #FileRef variable is encoded correctly before being rendered?
Many thanks in advance :)
you need to use the ServerURL or EncodedAbsUrl properties, this guys written it out already:
Itay Shakury's blog

Resources