Signature tags
When you pick a PDF in the send screen, Sliick Docs checks it once, automatically. If the document says where its signatures go, the fields are placed for you. There is no button to press, and the document that gets signed is exactly the file you picked.
Three kinds of document can say where signatures go. You never have to choose: Sliick Docs reads whatever the document carries.
- Documents Sliick Docs generated from a template with e-signature turned on and signing fields placed. These remember which template version they came from, so their fields land where the template author put them, even after the file has been downloaded, emailed and uploaded again. There is nothing to type. See Setting up a template for signature.
- Documents from any other system that use the Sliick signature tag described on this page. Use this when your PDFs come from a billing system, a partner portal, a Word mail merge or anything else outside Sliick Docs.
- Documents written for DocuSign or Adobe Acrobat Sign. See Reading DocuSign and Adobe Acrobat Sign tags.
A PDF with none of these is completely normal. You place the fields by hand, and no message is shown. That is the usual path for a counterparty’s contract.
The tag
Section titled “The tag”Type this text in your document, where the field belongs:
{{@Signature:Role:Order:Type}}
| Part | What it means | Rules |
|---|---|---|
@Signature | The keyword. | Not case-sensitive, so {{@signature:…}} works too. |
Role | Who signs here. | Starts with a letter or number, then letters, numbers, spaces, hyphens and underscores, up to 80 characters. Tags with the same role name, ignoring case, belong to the same signer, so Client and client are one person. |
Order | That role’s place in the signing order. | A whole number from 1 to 99. Roles are listed in this order in the send screen. |
Type | What the signer does. | One of the values below. |
Type | Field placed |
|---|---|
Signature or Sign | Signature |
Initials or Initial | Initials |
Date or DateSigned | Date signed, filled in automatically |
SignerPicksDate | A date the signer chooses from a calendar, such as a start date or a date of birth |
Name or FullName | The signer’s full name |
Text | A free-text box |
Checkbox | A checkbox |
Type words are not case-sensitive. Amount fields have no tag: add them in the send screen.
The two dates are different, and the difference is who fills them in. Date is filled in with the date the document was signed, and the signer cannot change it. SignerPicksDate starts empty, and the signer picks a date. Other e-signature products use plain date for the automatic one, so Date means the same here. The signer-picked date has no short form on purpose: type the whole word SignerPicksDate.
Example
Section titled “Example”{{@Signature:Buyer:1:Signature}}
{{@Signature:Buyer:1:Date}}
{{@Signature:Buyer:1:SignerPicksDate}}
{{@Signature:Seller:2:Signature}}
{{@Signature:Guarantor:3:Initials}}
This document arrives in the send screen with a Buyer, a Seller and a Guarantor already listed as signers, and five fields already on the page: one date the Buyer picks and one filled in automatically. Fill in each signer’s name and email, and send.
Where the field lands, and hiding the tag
Section titled “Where the field lands, and hiding the tag”The field’s bottom-left corner sits where the tag starts, so a tag typed on a signature line puts the field on that line. Each field starts at a standard size for its type. You can move or resize it before sending.
Give each tag its own line if you can. A tag on its own line is placed exactly. A tag in the middle of a sentence, such as Sign here: ______ {{@Signature:Buyer:1:Signature}}, lands close to where it sits, but not exactly. A tag on its own line is also the easiest to hide.
The tag is ordinary text, so hide it the way other e-signature products do: make it white (or your page’s background colour), make it tiny (1 to 4 pt), or both. Two things to know:
- White or tiny text can still be selected, copied and read by a screen reader. Do not put anything in a role name you would not want a recipient to see.
- Do not hide a tag off the page or behind an image. If the tag is not part of the PDF’s text, it cannot be found and its field will not be placed.
Writing tags from other sources
Section titled “Writing tags from other sources”The tag is plain text, so anything that can put text into a PDF can produce it. The other system needs no integration or add-on: whatever builds the document just writes the tag where the field belongs.
The one rule is that the tag must still be real, selectable text in the finished PDF. To check, open the PDF, press Ctrl+F (Cmd+F on a Mac) and search for @Signature. If your PDF viewer finds it, Sliick Docs will too.
From a Sliick Docs Word-file template
Section titled “From a Sliick Docs Word-file template”Type the tag straight into the Word document: {{@Signature:Client:1:Signature}} on the client’s signature line, and {{@Signature:Client:1:Date}} next to it. It is the one {{…}} tag that merging leaves as written, so it appears in both the generated Word file and the PDF, and the PDF arrives in the send screen with its fields placed. See Word-file templates.
Format the tag in Word the way you want it hidden, white or 1 to 4 pt, and that carries into both the Word file and the PDF.
Do not use Word’s Hidden font setting. Sliick Docs PDFs still show hidden text, so the tag would print. And a PDF saved from Word itself leaves hidden text out completely, so there would be nothing to find.
From a designed template
Section titled “From a designed template”Do not type tags. Turn on e-signature for the template and place signing fields on its E-sign tab instead. This is the most precise of the three. See Setting up a template for signature.
From Word mail merge, Google Docs or any word processor
Section titled “From Word mail merge, Google Docs or any word processor”Type the tag as ordinary text. Hide it with white or tiny text, not the word processor’s hidden-text setting (which drops it from the PDF). Then export or save as PDF. Do not print to an image, flatten the PDF, or scan a printed copy: each of these turns the text into a picture, and a picture has no text to find.
From a billing system, CPQ, reporting tool, HTML-to-PDF service or your own code
Section titled “From a billing system, CPQ, reporting tool, HTML-to-PDF service or your own code”Put the tag as literal text in the document template, where the field belongs. In an HTML-based generator, for example:
<span style="color:#ffffff;font-size:2pt">{{@Signature:Customer:1:Signature}}</span>
The role, order and type are fixed words you choose when you design the document. They are not looked up from anywhere. Customer, Client or Tenant becomes a signer row in the send screen, and the sender fills in each person’s name and email there. Use the same role name throughout a document, for example Customer everywhere rather than Customer in one tag and Client in another, because two different names mean two different signers.
Before you roll it out, send one real document and check the fields land where you expect.
Tags that are not used
Section titled “Tags that are not used”In each of these cases, the send screen tells you, and you place those fields yourself.
- A
Typeit does not recognise. The tag is reported, never guessed at, and the word is shown back to you so you can spot the typo. If it looks like a date, you are reminded of both date keywords. - A tag written wrongly in some other way, such as punctuation in the role name that is not allowed, an order that is not a number, or a missing part. Anything that starts
{{@Signaturebut cannot be read is reported the same way, so a mistyped tag never disappears without a word. - A document over 250 pages. Sliick Docs does not read it at all, rather than reading part of it and treating that as the whole.
- Fields missing from a document Sliick Docs generated. If the template’s signature setup expects fields the file does not have, nothing is placed, and you are told the document may be older than a change to that template. A half-placed document looks finished, which is worse than an empty one.
Reading DocuSign and Adobe Acrobat Sign tags
Section titled “Reading DocuSign and Adobe Acrobat Sign tags”If you are moving templates across from another product, Sliick Docs reads some of their tags too, so you do not have to rewrite every document at once. This is to help you move across. It is not full support for those products’ tags.
| Product | Tags read | Field placed |
|---|---|---|
| DocuSign | \s1\ | Signature |
| DocuSign | \d1\ | Date signed |
| DocuSign | \n1\ | Full name |
| Adobe Acrobat Sign | {{Sig_es_:signer1:signature}} | Signature |
| Adobe Acrobat Sign | {{Int_es_:signer1:initials}} | Initials |
| Adobe Acrobat Sign | {{Dte_es_:signer1:date}} | Date signed |
| Adobe Acrobat Sign | {{N_es_:signer1:fullname}} | Full name |
The number stands for the signer, from 1 to 99. These tags have no role names, so the send screen adds signers called Signer 1, Signer 2 and so on, one per number used, in number order, each with their own fields. The sender fills in each signer’s name and email as usual.
Exactly what is read:
- DocuSign: only
\s1\,\d1\and\n1\, with any signer number. Other DocuSign tags, including\i1\for initials, text-field tags and custom tags a sender made up, are ignored silently: no field is placed and nothing is reported. Place those fields by hand, or add Sliick tags as well. - One DocuSign tag on its own is ignored.
\s1\is short enough to appear in ordinary text, so a document needs at least two before it is treated as a DocuSign document. One Adobe tag is enough, because Adobe tags are distinctive. - Adobe Acrobat Sign: only the four tags in the table, where the word after
signer1matches the start of the tag:signatureafterSig_es_,initialsafterInt_es_,dateafterDte_es_, andfullnameafterN_es_. Capitals, and spaces around the colons, do not matter. A tag with the right start but a different word is reported as not understood. - Extra tag options are not read. A tag with anything after its third part, such as
:optional, a formatting instruction or a calculation, is skipped and reported. Reading only part of it could create a field with the wrong rules. - Signer-picked dates do not come across. The date tag from each product means the date signed. Neither product has a tag Sliick Docs can read for a date the signer enters, so add a
SignerPicksDatetag, such as{{@Signature:Buyer:1:SignerPicksDate}}, or place those dates by hand.
One kind of tag per document. Each document is read using one kind of tag only, in this order: documents Sliick Docs generated, then Sliick tags, then Adobe Acrobat Sign, then DocuSign. A document with Sliick tags and some leftover DocuSign or Adobe tags is read using the Sliick tags only. The others are ignored, not mixed in.
Moving fully to Sliick tags
Section titled “Moving fully to Sliick tags”Reading other products’ tags is a stopgap. When you next edit a migrated template, replace its tags with Sliick tags. You get real role names in the send screen, and field types the other tags cannot bring across: initials from DocuSign, text, checkboxes and signer-picked dates.
| Was | Write instead |
|---|---|
\s1\ or {{Sig_es_:signer1:signature}} | {{@Signature:Client:1:Signature}}, using a real role name |
DocuSign initials (\i1\) or {{Int_es_:signer1:initials}} | {{@Signature:Client:1:Initials}} |
\d1\ or {{Dte_es_:signer1:date}} | {{@Signature:Client:1:Date}}, the date signed |
\n1\ or {{N_es_:signer1:fullname}} | {{@Signature:Client:1:Name}} |
| A date the signer enters | {{@Signature:Client:1:SignerPicksDate}} |
| A text field | {{@Signature:Client:1:Text}} |
| A checkbox | {{@Signature:Client:1:Checkbox}} |
Use the same role name on every tag for one person, and number the roles in the order they sign, for example Client 1 and Supplier 2.
After the fields are placed
Section titled “After the fields are placed”Fields placed from tags are ordinary fields. Before you send, you can move them, resize them or remove them, just like fields you placed yourself. See Sending a document.