Signature

Collecting a signature from the responder.

This question type is used in cases where the responder needs to sign a document.

If you would like the responder to check a confirmation box instead of a signing, use confirm type instead.

Universal Signature

The universal signature component allows responders to either type their name and adopt a generated signature or draw their signature directly within the form.

Type (adopted signature): The responder enters their name and clicks Adopt and sign. This creates a valid electronic signature and submits signature metadata to your answers endpoints and Formsort Data Storage. This method does not generate an image file for file upload integrations.

Draw: The responder draws their signature using their mouse or touch input. This method behaves like the default signature component and will generate an image file that can be sent to your configured file storage integration.

Both methods capture key signature data, including the signer’s name, timestamp, and signature method, which are included in webhook submissions and stored response data.

Managing File Storage

By default, Formsort securely stores uploaded files and images with our data storage service — no setup required. If you prefer to manage your own storage, you can optionally configure an S3 or GCS bucket as a custom file destination.

To set up a custom integration, follow our detailed guides for:

• Amazon S3 setup

• Google Cloud Storage setup

Creating a filename pattern

You can opt to define a naming pattern for the signature images that your responders upload by enabling Filename pattern in the question settings.

You can template any relevant variable you would like to be included in the name of the file into the field. For example, if you type in {{first_name}} into the field, the value of the first_name variable will be used as the filename at upload.

Formsort offers three custom variables for these types of file upload components, built right into the settings of the component itself: sessionUuid, randomUuid, and currentTimeUTC. These variables can be templated into the Filename pattern field to create dynamic filenames.

• sessionUuid: a uuid that is created once, when the form is loaded.

• randomUuid: a uuid that is created at and re-run at each upload instance.

• currentTimeUTC: a timestamp that is created at and re-run at each upload instance.

You can use several of these variables at once, if required, and one pattern we suggest is {{currentTimeUTC}}_{{responder_uuid}}. This ensures uniqueness via the timestamp, while still tying the file to a particular user via the responder_uuid System Library variable.

Visit the System Library variables section for details on built-in variables that provide information about the responder's environment and context.

Note that these extensions will be added automatically. You should also set a fallback naming convention in case the variable is not defined by typing it into the Filename pattern fallback field. Values here cannot use templated variables.