A transaction is the experience of a OneSpan Sign user as they review, accept, sign, and potentially download documents. The sender of a transaction generally performs the procedures in the following sections:

Adding Fields to a Document

Fields enable the placement of additional data in a document at the time of signing. Like signature fields, non-signature fields can be placed anywhere inside a document. Nonetheless, each field is linked to a particular signature. Only the signer of that signature can assign or change the field's value. Once the signature is signed, however, the value of the field cannot be changed by anyone.

You cannot add fields to: (1) documents that are Accept Only; (2) the Electronic Consent form; (3) documents in an accessible transaction.

To add fields to an active document:

  1. Click the <Name of Recipient> from the RECIPIENTS section of the Prepare Transaction page.
  2. Drag and drop the desired fields (e.g., Signature) from the FIELDS section onto the document. The Available Fields are described below.

    3. You can duplicate a field by clicking it, and selecting Duplicate from the Field Settings pane. The new field will duplicate the original field's properties (Is required, Is optional, default value, list values, max characters), but its Field Name will be reset to empty.

    You can collectively align multiple fields to the top, bottom, left, or right.

  3. Optional: Configure conditional logic among some or all of the fields you added to the document in the previous step. How to do so is described in the section below called Conditional Fields.
  4. Repeat Steps 1-3 for all other relevant recipients.
  5. Click SEND TO SIGN.
  6. On the confirmation popup, click SEND. A popup now says Transaction created successfully!

    7. An email or SMS notification will be sent to all recipients when it is their turn to sign.

For more information:

Available Fields

The FIELDS section of the Prepare page contains every field that can be added to a document for a given recipient. Those fields are:

  • Signature: This field contains the signer’s signature. Once it has been added to a document, the recipient's name and signature are displayed in this field. The following signature types are available:
    • Click to Sign: The signer's name is stamped on the signature field at the time of signing. This is the default signature type.
    • Capture Signature: The signer draws their signature using their mouse or another input device. The signer can also choose to sign on a mobile device such as a smart phone if the sender has Mobile Capture enabled on their account. The drawing of the signature is stamped on the signature field at the time of signing.
    • Mobile Signature: The signer receives a link via email that redirects them to open the document on their mobile phone. The signer is then required to draw their signature using their finger or a stylus. The drawing of the signature is then stamped on the box. However, Mobile Capture must first be enabled on your account.
    • Optional Signature: Signatures can be specified as "optional" for any of the above three signature types, or for the Signer Initials described in the next bullet. If this flag is set, a signer is not obliged to sign all of their signatures inside a transaction's documents before completing the transaction. However, Optional Signature must first be enabled on your account.
      • An autofield associated with an optional signature will appear only if the latter is signed.

      • A Form Field associated with an optional signature will be retained on a transaction even if the signature is not signed.

      • A signer must "confirm" a transaction before the system will retain the signer's optional signatures or Form Fields within the transaction's documents.

      • Senders on mobile applications (iOS or Android) cannot create optional signatures.

      • Consent documents cannot be optional.

      • If a document contains only unsigned optional signatures (and no other signatures), its header says: Review & optionally sign this document. If a document contains only signed optional signatures: (1) its header says Ready to confirm; (2) its footer says Please Confirm to complete signing. If a document contains only optional signatures AND they are not all signed, its footer says Click Continue to proceed without signing.

      To watch a video on how to create Optional Signatures, click here.

      A default signature type can be configured for the Signature field by contacting our Support Team. The available defaults are Click to Sign, Capture Signature, and Mobile Capture.

  • Signer Initials: At the time of signing, the signer's initials are stamped on the signature field.
  • Signing Date: Displays the date and time when the signature field was signed.
  • Signer Name: Displays the signer's name.
  • Signer Title: If supplied, this field displays the signer's title.
  • Signer Company: If supplied, this field displays the signer's company.

The fields below are collapsed by default. To toggle the list, click Show /Hide.

  • Text Field: This field accepts any text entered by the signer prior to signing.
    • You can specify a Name, a Default Value, and the Maximum Length of the field. You can also enable Is Required to ensure that the signer fills out this field.
  • Text Area: This is a multiline area that accepts any text entered by the signer prior to signing.
    • You can specify a Name, a Default Value, and the Maximum Length of the area. You can also enable Is Required to ensure that the signer fills out this field.
  • Checkbox: This is a simple check box that the signer can either select or clear.
    • You can specify a Name and a Default Value. You can also enable Is Required to ensure the signer selects the box.
  • Radio: Radio buttons enable signers to select one of many predefined options.
    • You can specify a Name and a Default Value. You can also enable Is Required to ensure the signer selects a radio button. Radio buttons can be grouped by associating them with a Radio Group, and you can identify one button in the group as the Default (ensuring that it will be pre-selected).
  • List: This is a drop-down list that offers multiple predefined options. The signer can choose one option from the list. Once that option is selected, only that option is displayed, thus minimizing the amount of space this element occupies on the screen.
    • You can specify a Name and a Default Value. You can also specify the options that appear in the list, and enable Is Required to ensure the signer selects one item from the list.
  • Label: This is a READ-ONLY label that will be stamped on the PDF.
    • You can specify a Name and Default Value for this field.
  • Custom Fields: These fields are populated at the time of signing with data. Custom Fields are created for an entire account, and an account can have any number of Custom Fields. If the sender has defined a value for their custom fields, as described in the Custom Fields section of the My Account page, then that value will be used in the Signing Ceremony. If the sender has not defined a value for their custom field, a default value can be defined by your administrator, which will be used in the transaction.

For all the above fields except Capture Signature, Mobile Signature, Radio and Checkbox, the Field Settings pane has a Field Formatting section that specifies a font size for the field (i.e., the font size that will be used for text in the field when the parent document is printed). The options are: (1) a specific font size; (2) Auto-fit (which will scale the text to fill its input box); (3) Inherit from parent (this is the default, and will use the font size defined at the transaction/template level).

Conditional Fields

The feature called Conditional Fields enables Senders to configure IF-THEN conditional logic among two or more fields in a document. For example:

  • You can specify that IF a highlighted Text Field is not empty, THEN a particular Signature Field will be enabled — i.e., the signer must add text to the Text Field before they can sign the Signature Field.
  • You can specify that IF a highlighted Checkbox is checked, THEN all other fields in the document will be enabled — i.e., the signer must check the Checkbox before they can interact with any of the document's other fields.

  • Conditions cannot be applied to Custom Fields, Notary Fields, Auto-populated Fields (e.g., Name, Title, Date), Labels, or attachments.
  • Conditional logic cannot be applied across documents or across signers.
  • This feature is also available via the REST API and SDKs, but not via the Classic User Experience.

The following procedure describes how to configure conditional logic among a document's fields.

Prerequisites

Action

To configure conditional logic among fields added to a document:

  1. Add fields to your document. Conditional logic requires that: (1) you add more than one field; (2) at least one of the added fields be of type Text Field, Text Area, Checkbox, Radio, or List.

    2. Conditional logic can act on all five of the above types, as well as on Signatures and Signer Initials types.

  2. Click an added Text Field, Text Area, Checkbox, Radio, or List field that you want to use as the IF part of your desired conditional logic. A FIELD SETTINGS pane appears on the right of your screen.

    3. If you have a narrow screen, getting the FIELD SETTINGS pane to appear may require clicking three vertically aligned dots on the upper right of your screen.

  3. In that pane, expand the Conditional Logic tab.
  4. Configure the conditional logic you want between the field chosen in Step 2 and the document's other fields. The following table indicates which conditions are available for the various field types.
    5. Available Conditions Field Type Description

    IF ...

    		   
    Empty/Not empty Text Field, Text Area Determines if a Text Field or Text Area must be empty or not empty (in the IF part of your conditional logic)
    Checked/Unchecked Checkbox, Radio Determines if a Checkbox or Radio Button must be checked or unchecked (in the IF part of your conditional logic)
    <Any Item in a List> List This is a specified item from the list of items in your highlighted List field. The signer must select this value to satisfy the IF part of your conditional logic.

    THEN ...

    		   
    Enable/Disable All

    Determines if the selected field will be enabled or disabled (in the THEN part of your conditional logic). This therefore determines if the signer will be able to interact with that field.
    Make required All

    Determines if the selected field will be required (in the THEN part of your conditional logic). This therefore determines if the signer will be required to interact with that field.
    Make optional All Determines if the selected field will be optional (in the THEN part of your conditional logic). This therefore determines if the signer may optionally interact with that field.
  5. Click Save. Small icons appear on the right edge of all the fields that have been configured with conditional logic.

The 11.35 release of OneSpan Sign deprecated the part of the Classic User Experience for Senders and Admins. Thus the features described on this page are no longer available. If you try to access them, you will be redirected to the corresponding part of the New User Experience. Note: The Classic Signing Ceremony — i.e., the part of the Classic User Experience for Signers — is still supported.

Once you have created a package and added at least one document to it, you can prepare all of its documents for signing. This is done using the New.

If a package is accessible, the Designer page will be read-only. That is, no one can: (1) add, modify or remove signatures or fields; (2) specify the documents as Accept Only; (3) apply layouts to the documents.

To prepare a package for signing:

  1. Perform the procedure Adding Signature Blocks to Documents.
  2. Optional: Perform the procedure Adding Fields to Documents.
  3. From the Signers and Documents page, click Prepare.

This section also discusses Creating and Using Templates, which is related to preparing documents for signing.

Adding Signature Blocks to Documents

Signature Blocks define: (1) where each signer must sign a document; (2) fields that contain information about the signer.

In a given document, you can insert multiple Signature Blocks for a given signer.

However, you are not obliged to add a Signature Block for a signer. For example, a package may include several documents, one of which requires signatures from only two of three signers.

To add Signature Blocks to the documents in a package:

  1. Click Prepare to Sign in the document toolbar. The Preview window appears for the package' first document.
  2. Using the drop-down arrow in the Signers list, select the signer whose signature you want to add.
  3. Click Add Signature.
  4. Drag the Signature Block to where you want it to appear in the document.
  5. If you want to change certain settings: (1) hover your cursor over the Signature Block; (2) click the gear icon.
  6. For each Signature Block you want to add to the document, repeat Steps 2 to 5.
  7. If the package has multiple documents: (1) open the next document by clicking the navigation arrow in the Preview window's toolbar; (2) repeat Steps 2 to 6 to add Signature Blocks to that document.

Adding Fields to Documents

Fields are associated with a specific signer, and are optional. You can include any number of each type of field. If the signer has a OneSpan Sign account, fields such as the signer's name and title will be filled in automatically, even if that information is not provided by the sender.

A field does not appear if the document that contains it is displayed to a signer other than the user for whom the field was created. For example, if you add Signer Name, Date, and Checkbox fields for a specific signer, those fields will never appear to the package owner.

Field Types

You can add any of the following field types:

  • Signing Date: At the time of signing, the system automatically populates this field with the current date.
  • Signer Name: At the time of signing, the system automatically populates this field with the signer's first and last names. These names are provided when the signer is added to the package.
  • Signer Title: If the signer's title is available, the system automatically populates this field with that title at the time of signing. Otherwise, the field is left blank. The signer's title is usually provided when the signer is added. However, if the signer is a Contact, Lead, or User in Salesforce, this field is automatically populated with the information stored in Salesforce.
  • Signer Company: If the name of the signer's company is available, the system automatically populates this field with that name at the time of signing. Otherwise, the field is left blank. The company name is usually provided when the signer is added. However, if the signer is a Contact, Lead, or User in Salesforce, this field is automatically populated with the information stored in Salesforce.
  • Date: This field enables the signer to add a date of their own choosing. The Name, Format, Is Required, and Type values can all be specified in the field's settings.
  • Text Field: This field provides a box where the signer can enter additional information at the time of signing.
  • Text Area: This is similar to the Text Field type, in that it provides an area where free-form text can be entered by signers. However, unlike Text Fields, it provides automatic wraparound. Each Text Area can accept up to 4000 characters. The Name, Default Value, whether the text area Is Required, and the Maximum Length of the text area can all be specified in the field's settings.
  • Checkbox: Prior to signing, the signer can either select or clear this simple check box. It can be useful to indicate that the signer has completed a particular action. The Name, Default Value, and whether the box Is Required can all be specified in the field's settings.
  • Radio: Radio buttons provide the ability to select one of many options. Multiple radio buttons can be grouped together by associating each with a common Group Name. The Required field, if enabled, indicates that at least one button in the group must be selected. Identifying one button in the group as the Default will pre-select that option. The Name, Default Value, whether the radio button Is Required, and the Radio Group can all be specified in the field's settings.
  • List: A drop-down menu list also provides the ability to select one of many options. Once an option has been selected, only that value is displayed (this reduces the amount of space taken by this UI element on the screen). The Name, Default Value, and List Items can all be specified in the field's settings.
  • Label: The package sender can add a label field to embed text in a document. This is a read-only field with a value that will be simply stamped on the PDF. During the Signing Ceremony, the label is displayed as non-editable text.

If you don't see some of the above field types when you perform the next procedure, it's because they have been disabled for your account. For help, see your System Administrator.

To add a field to a document:

  1. Hover your mouse over a relevant Signature Block, click the Gear icon, and then click Add Field.
  2. Choose the field type you want to add (see Field Types).
  3. Drag the field to where you want it to appear in the document.
  4. Repeat Steps 1-3 for each field you want to add.
  5. If your package has multiple documents, and you want to add fields to other documents, use the navigation arrows to open the next relevant document, and repeat Steps 1-4.

Application Administrators can configure default values for the field-type settings Is Required and Format. These settings can be edited by users.