Tags link a form field with its place within the document
Tags cannot contain special characters or spaces, but they can contain numbers and capital letters. This helps us differentiate one tag from another one and not get lost in the document.
If we pick a standard contract, where the place and date are indicated at the top of the document, a tag that we could use is {place} to indicate the place and {date} to indicate the date. Furthermore, we will easily know what we are referring to.
This could be our original document template:
In ___________, at ____________
And this is how our document template would look like with tags:
In {place}, at {date}
Continuing with the previous example, it is possible that in the same document there are different types of dates (date of the contract, date of birth of one party, etc.).
For this reason, the tags that we use for these dates will have to be different from one concept to another. Thanks to this differentiation, the software is able to distinguish them and we will know what information we are inserting in each case and where in the document.
Original document template:
In ____________, at ____________
[...]
Date of birth: ____________
Document template with tags:
In {contractPlace}, at {contractDate}
[...]
Date of birth: {birthDate}
In short, the names of the tags should help us understand, at a glance, what information is inserted there.
Tags of more than one word
As we have seen in the previous example, there is a high chance that in almost any document we will have to differentiate between similar concepts that do not identify the same variable information. Like the name of the tenant, and the name of the landlord, both are names but they refer to different variable information.
The tags of more than one word are a bit more complex to read, especially if they consist of more than 2 words. Since the tags do not allow spaces, we can use the camelCase method to help your mind to read it.
- Example without camelCase: wordswithoutspaces
- Example with camelCase: wordsWithoutSpaces
Which one is easier to read for you? You see, the camelCase helps your mind read when there is more than one word in a tag.
As we said before, everyone is free to draft the words inside the tags as they like. But our experience tells us that the camelCase makes the automation process easier.
As you automate documents, you will encounter more obstacles when writing the meaning of this field on a tag.
Tags don’t understand languages, you can write them in any language. It is simply writing in a {different} way.
Something to note is that the longer the tag, the more it will cost you to read it, and the more time we will spend writing it, slowing down our work. Tags can contain a maximum of 32 characters.
Here are some examples with which we have come across:
- Mobile phone natural person - {mobilePhoneNaturalPerson}. When this could easily be written with abbreviations {mobPhoneNP}. Going from 24 characters to 10.
- Representative natural person - {representativeNaturalPerson}
- Registration number natural person - {registrationNumberNaturalPerson}