The Security Fields section of the toolbox holds the fields used for sensitive entry and for signing. All of them share the settings described in Common Field Settings, and their conditions work as described in Field Conditions.


Password

A text box whose characters are masked as they are typed, so the value cannot be read over the user's shoulder.


Max Length - The greatest number of characters that can be entered.


Field Placeholder - Prompt text shown in the empty box.


Masking hides the value on screen; it is not encryption. Think about whether the value needs to reach the record at all before turning Save to Record on, and on a public form turn Allow Save for Later off so the value is not held on the user's device.


reCAPTCHA

Uses Google reCAPTCHA to check that a real person is filling the form in rather than a bot. The field only appears in the toolbox once the reCAPTCHA keys have been entered in the site's settings.


Dropping it on a form makes it required automatically, so the form cannot be saved until the check is passed. It belongs on public forms that accept submissions from anyone. Because a returning user has already proved themselves, set the field to be hidden when the document exists, so people editing a form they have already submitted are not challenged again - the Field Conditions topic covers the -Document- source that does this.


Signature Check

A check box with wording attached, used for agreeing to terms rather than for signing. Setting it as required is the usual way to stop the form being saved until the user has agreed.


Text - The wording beside the box, normally the agreement or the legal line the user is accepting. Variables and {field} references are replaced when the form loads.


Checked Value and Unchecked Value - What is saved in each state. Set these where the record needs particular wording rather than the defaults.


Signature Pad

A box the user signs in directly, with a mouse, a stylus or a finger.


Text - The wording shown below the pad, normally a short instruction or the legal line being signed.


Allow Personal Signature - If the user has a personal signature saved, adds a button that applies it to the field for them, so staff do not re-draw their signature on every form.


Allow Record Signature - Adds a button that applies a signature already stored on the current record. This is the setting for a process where someone - often a customer - signs once and then confirms on later forms with a single click.


Record Signature Field - Which field the stored signature is loaded from. It has to be filled in for Allow Record Signature to work, and the designer marks it in red until it is.


Topaz Signature Pad

Signs using an attached Topaz signature pad rather than the screen. It needs the Topaz client drivers installed on the machine, and the designer links to the installation instructions beside the setting - a form that relies on it will not work on a device without them.


Text - The wording shown below the pad.


Combined Signature Pad

A single field that can sign either way, on screen or on a Topaz pad, so one form serves both the front desk with a pad attached and everyone else. It needs the Topaz drivers on machines that will use the pad.


Text - The wording shown below the pad.


Default Style - Which way the field starts: Mouse / Touch Screen or Topaz Signature Pad. The user can switch.


Allow Personal Signature - As on the Signature Pad, offers the user's saved signature as a one-click option.


A note on required signatures

None of the signature fields stop a form being saved on their own. Set Field Required on the signature or the Signature Check to make the form insist on it, and give it a Required Message that says what is missing - "Sign here to confirm you have read the terms" reads better than a generic error.