Allow the field length to be set when using Text Tags in MS Word documents.
The inability to set the field length when using Text Tags in MS Word documents greatly detracts from their usefulness. For example, {{essigner2_title}} does not provide enough space for entry of any but the shortest job titles, even when the text tag is given an entire line in MS Word to work with.
At this point, I often don't both with text tags, instead leaving sufficient blank space and creating, positioning, and sizing the field within Echosign. This is a cumbersome process. There have been times where I've just emailed a document and asked the other party to sign, scan, and send back, because I didn't have the time or patience for playing around with form fields in Echosign.
Paul C. Easton
shared this idea
Adobe Sign text tags base their size on two factors.
The height of the field is predicated on the font size of the opening brace {
The width is based on the distance between the opening brace pair, and the closing base pair. The tag within the braces must be contiguous, but white space is permitted before or after the text tag string:
{{FeildName_es_:signer1:title }}
For tags that are too long for the desired field width, text tag shortening can be used. Shortening is essentially defining a variable, and attaching the explicit tag to that variable.
For more on tag shortening: https://helpx.adobe.com/sign/help/adobesign_text_tag_guide.html#short
-
Anonymous
commented
Aaron, If you haven't found your solution yet, tags can be shortened using the reference method Chrizzy mentioned. To use your example, where you wish the field to appear you would enter:
"{{$dob}}" then elsewhere in the document you would define $dob with:
"{{#dob=*DOB_es_:signer:date(format=mm/dd/yy)}}"You can enter all of your reference definitions on a blank page and enter the tag {{REMOVE_PAGE_FROM_OUTPUT}} to have the page omitted from the finalized document. I find it makes sizing fields easier, and you can also enter comments on that page, as it will not be included.
-
Aaron
commented
Chrissy, your 2nd point is what I'm looking for as well. Consider this example of using the following text tag: {{*DOB_es_signer.date(format=mm/dd/yy)}} All this field is asking is for someone to submit their date of birth in the mm/dd/yy format, which should be a short field. However, the length of the text tag itself makes the field huge and pushes the next field down onto the next line, wasting space and making a sloppy appearance. Echosign should be able to shorten the length of a field as it's displayed, even if the text itself is large.
-
Chrissy
commented
The reference and definition tag method for text tags implemented in the Spring 2012 EchoSign release greatly progresses the flexibility of text tags and pretty much resolves this issue, I believe. I will remove my vote here to use for other outstanding items.
-
Chrissy
commented
This is useful information to know about the text width properties of text tags. However, what if we want to make the field *smaller* than the text tag itself, such as with a State abbreviation or if we use data validation, which further increases the length of the text tag beyond what may be desirable? Ideally, text tags would accept a text width value so that we can specify in exact numbers how wide we wish for the text field to ultimately be. +1 vote here.
-
Ben Barnes
commented
When Will line Wrapping (Multiple Lines) Be available - This really is a neccesity is it not?
-
Paul C. Easton
commented
Okay, so this is possible already. I received a response from tech support, which instructs:
The width of a field is predicated on the distance between the opening pair of brackets and the closing pair of brackets. So you can just add spaces between the tag and the last brackets to give width to the field. At this time text tags do not support line wrapping or multiple lines, so make sure the full bracket to bracket tag is on one line.
{{*samplefield_es_signer1 }}