S-Sign offers the capability to collect more than just signatures in e-signature requests. This document will explain the different S-Sign field types that you can insert into your documents to collect signer information. There are currently five different field types available: Signature, Text, Checkbox, Initials, and Date.

Signature Fields

The signature field comprises the core functionality of S-Sign: it will create a link that opens the S-Sign signature pad when clicked. In the template editor for templates that are S-Sign enabled, the signature field menu looks like this.

As you can see, [1] the field type is set to Signature. If there are multiple signers, you have the option to [2] choose which signer this signature field is for by selecting a signer profile. This will make it so that only that specified signer can interact with that field (you can edit aspects of each signer's profile by clicking over to the "Signer Profiles" tab in the S-Sign menu). Once you have set these options, you can [3] paste the field tag into the document.

Signature fields look like this to the signer:

Text Fields

A text field will appear as a blank box that the signer can type into. The text field menu looks like this in the template editor:

The field type [1] has been changed to text at the top, meaning different options have appeared for this particular field type. You can [2] specify whether a text field is required by checking this checkbox. You can also opt to [3] write the data entered into this box back to a Salesforce field. To learn more about this feature, please click here. Additionally, you have the option to [4] provide a default value to appear if the signer chooses not to interact with this field.

You can also [5] edit the width and height of the text input field, as well as add additional styling. The width and height fields accept any CSS length unit without semicolons. The Additional Style field accepts CSS syntax (including semicolons). Note that you can use the letter-spacing property, which isn't normally supported by Salesforce.

Text fields look like this to the signer:

Checkbox Fields

Checkbox fields are fairly self-explanatory: a checkbox will appear where this field tag is placed. The checkbox field menu looks like this in the template editor:

Checkbox fields allow you to set most of the same requirements as text fields. You can make the field required, specify which signer can interact with it, specify the default value (checked or unchecked), and even write the data back to a checkbox field in Salesforce.

The main difference is that checkbox fields can also be assigned an Input Field Group. Input field groups allow you to group checkbox fields together and set requirements for the group as a whole. Input field group settings are found in the S-Sign Template Settings menu.

Checkbox fields look like this to the signer:

Initials Fields

The initials field type creates a link similar to the signature field type. Clicking the link brings up a variation of the signature pad that is made for initials. Signers can either draw their initials, or use the Text to Signature feature and type them. The initials menu looks like this in the template editor:

The options for initials are the same as those for the signature field type.

Initials fields look like this to the signer:

Date Fields

Date fields allow the signer to input a date. They look like this in the template editor:

You can [1] opt to have this field automatically populate with the date the document is submitted, or you can leave this unchecked to allow the signer to input their own date. You also have the option to [2] format how the date will appear in the final document.

Date fields look like this to the signer:

When clicked, a calendar will appear for the signer to choose a date from.

Picklist Fields

Picklist field types allow the signer to choose from a list of options. There are two types of picklist fields available: picklists from text, and picklists from fields.

Picklists From Text

Picklists from text are comprised of options that you input manually. The picklist from text menu looks like this in the template editor:

You can [1] enter a new line-delimited list of options for your picklist to begin.

Note: The semicolon character ( ; ) and the character chosen for the multi-picklist delimiter cannot be used within your picklist options.

To make your picklist a multi-select picklist, you can [2] check the box underneath the List Options field. If you enable multi-select for your picklist, you can also [3] set a delimiter for the output data (by default, the data will be displayed as a comma-delimited list).

You can also [4] control how many options are shown on screen at once by inputting a number into the Size of Multi-Picklist field. A scrollbar will appear within the picklist to view all options. By default, all picklist options will be shown on screen at once.

In addition, picklist fields can be [5] written back to Salesforce fields, and you can [6] set a default option to be selected.

Picklist (from text) fields look like this to the signer:

Picklists From Field

Picklists from field are comprised of options from an existing Salesforce picklist field. The picklist from field menu looks like this in the template editor:

To use the picklist from field feature, you need to specify an existing picklist field from your base record to be displayed within your S-Sign document. Use the Insert Field button to find a picklist field, then copy the merge field syntax into the Salesforce base record picklist field box. In this example, we used a merge field that points toward a custom field on our opportunity record that we'd like to use in our S-Sign document.
If the picklist is multi-select, S-Sign will detect this and reflect that in the document.

Picklists (from field) look like this to the signer:

With these seven field types, you are ready to optimize your e-signature workflow and start gaining more value from your S-Sign requests.