How can I add signatures to documents I generate with Fluent?
Fluent does not include signing tools, however signatures can easily be added to a document generated with Fluent by using Xodo Sign. Below are instructions for including XodoSign hidden signature tags, so your documents can be seemlessly signed once they're generated.
Fluent Reports and XodoSign Hidden Tags
This article describes Fluent’s out-of-the-box support for XodoSign signatures. No extra coding, Tags or queries are needed to add XodoSign signatures to your Report Template output.
You can enter XodoSign Hidden Tags into your Report Template, generate output, then send your output to XodoSign for signatures.
Just follow the formatting from the XodoSign documentation (or reference the table below) to enter a Hidden Tag into your template, then send your output to XodoSign for signature(s)- that’s all there is to it!
XodoSign Hidden Tag Details
A hidden tag is a text element wrapped in square brackets [ ] containing a series of options in a specific order, all divided by | symbols. You can specify a total of 9 options, such as field type, signer ID, required/non-required, field label, field identifier, and more.
Example:
[text|req|signer1|Name|name_1|Paul McSign|125|50|letters_only]
Options: Below you will find all 9 available options explained:
| Order | Name | Description |
|---|---|---|
| 1 | Field Type | Enter your preferred field type. See a list of available field types here. [Example: sig for Signature] |
| 2 | Required / Non-Required | Enter req for required or nonreq for a non-required field. |
| 3 | Signer Number | Enter signerX with X being the number/ID of the signer this field is for. [Example: signer1] |
| 4 | Field Label | Enter your field label. This will be displayed as the placeholder for text fields. [Example: Name] |
| 5 | Field Identifier | Enter your field identifier. [Example: signature_2] |
| 6 | Prefill Field Value | Enter a value to prefill your field with. Different field types come with different prefill options, which are explained here. |
| 7 | Field Width Override | By default, your field will come with the same width as your hidden tag. You can override this width by entering a pixel width here. [Example: 125] |
| 8 | Field Height Override | By default, your field will come with the same height as your hidden tag. You can override this height by entering a pixel height here. [Example: 50] |
| 9 | Field Validation | Enter your preferred field validation type, if any. |
Supported Field Types: The following field types can be created using hidden tags. "Prefill Value" refers to the type of value your field can be prefilled with.
| Field Type | Context | Prefill Value |
|---|---|---|
sig | Signature field | |
init | Initials field | |
text | Text field | String |
date | Date Signed field | |
check | Checkbox field |
*Example: XodoSign Hidden Tags can be combined with Fluent Tags to create dynamic signature fields in your output document.
For Example, here is a table containing ForEach tag [Employee] that outputs a list of Employee Names. Each employee also has a Signature column that is a XodoSign Hidden Tag. By including the ForEach “count” status in the XodoSign hidden tag for signature identifiers (via an out tag), XodoSign will create a unique signature for each employee.
To make these XodoSign Hidden Tags actually “hidden” simply make the font color of the text the same as the background color of your document (white typically).