Touch Signature Pad

Audience: Low-code Engineers

Skill Prerequisites: Forms, Tokens

The Touch Signature Pad add-on lets users sign a form. It adds two form fields:

• The Touch Signature field shows a box the user signs in with a finger, a pen or the mouse.
• The Topaz Signature field takes the signature from a Topaz electronic signature pad connected to the user's computer.

Both fields save the signature as a PNG image in a portal folder when the form is submitted, and give you its file name, URLs, path and Base64 content as tokens.

note

This add-on is the ActionForm.TouchSignaturePad package. It's installed separately and needs the ESIGN feature package in your license. If it isn't licensed, submitting a form that has one of these fields fails with a not-licensed error. If you don't see the fields in the Security category of the form builder, the add-on isn't installed.

The fields are for Forms. They aren't available in Forms 2.0.

Touch Signature field

The Touch Signature field is in the Security category of the form builder. It shows a drawing box as wide as its container, with a Clear Signature link under it. The user draws the signature with the mouse, or with a finger or pen on a touch screen. Clear Signature empties the box.

It works with all form templates.

Topaz Signature field

The Topaz Signature field is also in the Security category. It shows a box that mirrors what the user writes on a Topaz signature pad, with a Clear button. The signature is read from the pad when the form is submitted.

The user's computer needs:

• A Topaz signature pad, connected and working.
• The Topaz pad driver (SigPlusPro).
• SigWeb, Topaz's local service that lets the browser talk to the pad.

The browser reaches SigWeb through the tablet.sigwebtablet.com address, on port 47289 for http pages and 47290 for https pages. Firewalls and security software on the user's computer must allow it. The field doesn't work on phones or tablets without the pad and SigWeb.

To check from JavaScript whether a pad is connected, call TabletConnectQuery(). For example, save the result in a hidden field from the form's initialization script: [HiddenField] = TabletConnectQuery();.

caution

The Topaz Signature field only works with the obsolete Bootstrap 3 Legacy Engine and Material form templates. A form with the Bootstrap 5 or Bootstrap 3 (Razor) template can't show it and fails to load. Use only one Topaz Signature field per page.

Settings

Both fields have the same settings:

Setting	What it does
Signature Name	The file name, without the extension. .png is added. Supports tokens, for example signature-[OrderId]. If it's empty, a random name (a GUID) is used.
Upload to Folder	The portal folder to save the image in. It's created if it doesn't exist. Default: the portal's root folder. If no folder is set, the image is saved in Temp.
Save to Report (Obsolete)	Saves the value in the form's reports. Use the form's report settings instead.

Use the Required validation setting to make the user sign. A required Touch Signature field fails validation if the user didn't draw anything. A required Topaz Signature field fails if the pad has no signature, but only when the form's client-side validation is on. Otherwise a blank image is saved.

Tokens

When the form is submitted, the field saves the image and creates these tokens, where <FieldName> is the field's name without spaces:

Token	Contains
[<FieldName>]	The file name with the extension, for example signature-1024.png.
[<FieldName>:FileName]	The file name with the extension.
[<FieldName>:RelativeUrl]	The URL of the image, relative to the site.
[<FieldName>:AbsoluteUrl]	The full URL of the image.
[<FieldName>:PortalPath]	The folder and file name inside the portal.
[<FieldName>:FilePath]	The physical path on the server.
[<FieldName>:Base64]	The PNG image, Base64 encoded, without a data: prefix.

If the field is empty, all the tokens are empty. Use the URL tokens to show the signature in an email or a document, and [<FieldName>:Base64] to embed it or send it to another system.

Considerations

• It's an image. The field saves a picture of the signature. It isn't a digital signature and doesn't prove who signed or that the document wasn't changed. To sign PDF files, see the PDF AutoSigner add-on.
• Saved on every submit. The image is saved when the form data is read on submit, before validation and before your actions run. If validation fails, the file is already in the folder, and each new submit saves another file unless Signature Name is fixed.
• Existing files are replaced. A file with the same name in the folder is overwritten. Include something unique, such as an ID, in Signature Name.
• Slashes, spaces and colons in Signature Name become dashes (-).
• Blank signatures. If the field isn't required and the user doesn't sign, a blank image is still saved. Make the field required, or check it with a condition, if you need a signature.
• Who can see it. Anyone with the URL can open an image in a public portal folder. Save signatures in a folder with restricted permissions if they're sensitive.

For other fields that create images, see the Barcode Generator add-on. To use the image in documents, see the PDF Generator and Word add-ons.

Revised 10/02/2026