HelloSign
Send generated documents automatically for Signing.
To start with a HelloSign delivery, choose the
Hello Sign option from the list of deliveries available in the Configure New Delivery view. | |
Title | The title you want to assign to the Signature Request. |
Subject | The subject in the email that will be sent to the signers.
|
Message | The custom message in the email that will be sent to the signers. |
Signers Name | The name of the signer. |
Signers Email | The email address of the signer |
CC | The email addresses that should be CCed. |
Use Text Tags | |
Hide Text Tags | Enable this if you wish to enable automatic Text Tag removal. It is preferred that you don't enable this, hide your tags with white text or something similar because the automatic removal system can cause unwanted clipping. See the Text Tags walkthrough for more details. |
Sequenced Signing | Enable this if you wish to enable Sequenced Signing. |
To enable Text Tags and make sure you enable Use Text Tags. Your Text Tags will be converted into UI components for the user to interact with. Keep in mind that by default the tags themselves will remain on the page. To hide the tags from the end user you can change the text color to match the background (such as white on white). Alternatively you can set Hide Text Tags although we don't recommend this because auto-removal can lead to unwanted clipping.
To begin and end a tag, use square brackets [ ] in your document. Within the square brackets, use the pipe character | to divide the parts of the tag. The first part of the tag is the type. The second part indicates if it is required or not. The third part indicates which signer in the list of signers needs to complete the field. The last two parts are optional and are for setting a label and unique ID.
For example: [text|noreq|signer1|Label|UniqueId]
HelloSign Text Tags
Text Tags let you specify which signer the field is for, what type of field it is, and if the field is required or not in addition to the relative size of the field. The types of fields available are the same as when you create a template:
TEXT TAG VALUE | FIELD TYPE |
text | Text field |
check | Checkbox field |
date | Date field |
initial | Signer's initials field |
sig | Signer's signature field |
text-merge | A text field that has default text set by the api |
checkbox-merge | A checkbox field that has default value set by the api |
The only valid values for field requirement are "req" and "noreq". The value defaults to "req" if the entry is not understood.
When you write a Text Tag you must assign it to somebody. The number N in "signerN" represents the signer index, For example with these two text tags:
- [sig|req|signer1|OptionalLabel|OptionalID]
- [initial|req|signer2|OptionalLabel|OptionalID]
You have specified that signer[1] is required to sign and signer[2] is required to initial.
If you text tags, you will need to configure the signers fields in the delivery configuration. The number of signers configured in the document using text tags must match the number of signers configured in the delivery.
Enabling optional recipients in the HelloSign delivery will skip invalid signers and carbon copy (cc) entries.
Last modified 8mo ago