Skip to main content
Skip table of contents

Automatic signature fields

The app offers the option of automatically placing signature fields in the document according to a specific syntax so that they do not have to be created manually by the user.

Syntax and parameters

The syntax is “signFieldKw0” as an abbreviation for “Signfield Keyword,” supplemented with a sequential number starting with 0.

Parameters must also be defined in order to configure the signature field. Refer to the following table for information on these parameters and how to specify them.

The syntax must be included on the first page of the document (e.g. text, white on white).

Parameter

Description

Key

Keyword or search term in the document where the signature field is created.

The keyword should be as unambiguous as possible. If the search term is found more than once, the first one found is used.

Option

Specifies whether the field is a mandatory field.

  • 0 = optional signature field

  • 1 = mandatory field

X-coordinate

Left position in pixels relative to the upper-left corner of the keyword. (Decimal places are permitted)

Y-coordinate

Upper position in pixels relative to the upper-left corner of the keyword. (Decimal places are permitted)

Width

Width of the signature field in pixels. (Decimal places are permitted)

Height

Height of the signature field in pixels. (Decimal places are permitted)

Name

Name of the signature field.

Each signature field must have a unique name.

Display text

Optional parameter. Message displayed during the signing operation.

The parameters should be placed in straight double quotation marks (“"”) and the individual values must be separated by a semicolon (“;”).

Example

The following example creates a signature field in the document:

CODE
signFieldKw0:"Unterschrift Kunde;0;50;-75;100;50;Kunde;Bitte unterschreiben." 
  • Key: Customer signature

  • Option 0

  • X-coordinate: 50

  • Y-coordinate: -75

  • Width: 100

  • Height: 50

  • Name: Customer

  • Display text: Please sign.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.