Text Tags are used in document creation. When documents with tags are uploaded, those tags will generate fields.
These field will have the properties set in the tag. These properties include roles, validations and calculations.
There are specific rules that needs to be followed when using Text Tags. As long as you abide by these rules, your tags should generate all of your fields just fine.
Only certain fonts can be used to create Tags. The EchoSign system will only pick up Arial, Helvetica and Times New Roman fonts consistently (first three fonts listed below). Custom fonts will not be picked up by EchoSign and no fields will be generated.
Generally, Arial is the best option to use.
There are two rules for spacing when using Text Tags.
1. A Text tag cannot contain spaces, unless they are before the tag and after the opening curly braces or after the tag and before the closing curly braces.
2. Text Tags cannot line break. If the tag continues from one line to the next, EchoSign will not pick up and field and no field will be generated.
If the tag you're creating is too long to stay on one line, you'll want to utilize Text Tag Shortening.
The following approach will go through the process of creating a tag from start to finish. As properties and arguments are added, an definition and explanation will given.
All Text Tags are contained in two opening and two closing curly braces, as shown below. These should be treated as the container for the tag itself. By just using the opening and closing sets of curly braces, a basic field with no properties can be made.
Placing blank spaces between the curly braces increases the width of the field, allowing for more information from the signer.
The font size of the curly braces define the height of the field. This also scales the font size of the data entered to fit appropriately. Of the two fields below, it first would be a smaller because of the font size. The second field would be taller and longer and data entered would show in a larger font.
Naming the fields you're creating is very important. By naming each field you can either take advantage of or avoid field pollination. This is a feature that allows information to copy from one field to the next. Field pollination works within doucments and across multiple documents.
Cross document pollination can be disabled by contacting email@example.com
Identically named fields will replicate the data entered in one field to all others with the same name. Both of the fields below would contain the same information entered into either.
Using field pollination can simplify the signing process for your recipients. For example the signer would only need to enter their address once and it can be populated into other fields across the document.
The EchoSign Identifier instructs our system to look for the name and properties of the field. Without this the EchoSign system does not know how to parse out the different pieces of the tag.
Roles are the most important part of a Text Tag. Roles define which signer the fields are assigned to. When creating a document with Text Tags you don't set who specifically will interact with the document, but more so which signer.
The signers are defined by the order the email addresses are entered into the "To:" field on the Send page. These different numerical signer roles need to be used for all signers, including yourself as the sender (depending on when you sign; first or last).
With this understanding the roles can be set in the document creation as long as you have an understanding of how you will be sending out your documents and who will get them in what order.
The Prefill role is used for fields you need to fill in prior to sending out the document. This is the opportunity to enter signer specific information before it's sent off to them.
The Preview, position signatures or add form fields option needs to be checked in order to reach the Prefill stage.
Validations are used to either create EchoSign specific fields or require the data entered be in a specific format. These are used to ensure you get the intended information from your signers. These are also used to make the EchoSign fields found in the Drag and Drop environment.
For our example tag, the :phone validation will require the signer enter their phone number in the (XXX) XXX-XXXX format or just as a string of ten numbers.
Setting conditions for a field will allow you to change it's visibility based on the state of another field. This can create dynamically changing documents depending on the information provided by the signer.
In the example below our phone number field will show for the signer if they check the box above it. In this instance it's like asking for an alternate phone number.
When the box is not checked, there are no fields for the signer to interact with. When the signer checks the box the phone field appears and the signer can enter their alternative phone number.
Additional information on Conditions.
A default value for a text field can be specified through the tag. This is text that will appear in the field before the signer interacts with it. Default text can be used to guide the signer by letting them know what information you want entered.
When the signer accesses the document, they will see the text in the field and they can overwrite it to enter their information.
If the signer does not replace the information in the field, the document can be completed with the default text intact. This will also fulfill a required field flag, allowing the signer to leave the default text.
Tooltips are smimilar to default text, in they can help inform the signer of what information you're looking for, if it's not obvious on the form itself.
The difference is tooltips will pop up when the signer hovers their mouse over the field.
Now when the signer hovers their cursor over this field they will see the tooltip you've set in the tag.
For fields that gather sensitive information like credit card or account numbers, we highly suggest using the mask property.
This replaces all data entered into the field with asterisks.
As the signer fills in the requested information, the content will still be visible to mitigate the chances for mistakes.
When the signer clicks out of the field, the information is replaced. These asterisks will also be visible on the resulting, completed document.
To retrieve the masked data, the send of the document will need to export the form data from either the Manage page or my running a Report.
Aside from text fields, you can make other objects using text tags. All fields available through the drag and drop environment can be made using text tags.
Checkboxes are used in "check all that apply" situations. Checkboxes can be made standard, required or checked by default.
Checkboxes can make use of field pollination, so be sure to uniquely name each checkbox.
Radio buttons should be used for "choose only one" situations. Radio buttons need to include at least two options and are grouped by giving them the same name. The actual option is set in the parenthesis after ":radio".
Dropdown menus provide a list of options for the signer to pick from. A dropdown will only allow them to choose one option.
Attachment fields are for Enterprise and Global level of service only.
Attachment fields allow the signer to attach a file to the transaction. This file will be appended to the end of the completed document. The ":label" property of the tag allows you to enter informative text into the field, like default text.