This workflow action is applicable in the context of a state transition.

It is used to enforce regulatory requirements that require an electronic signature for certain workflow steps.

To use this workflow action, you must define a custom tracker text field for the user signature.

For example

In the Label field, enter Signature or Password. If you enter another name, the input field on the user interface will be a plain text field instead of a password field.

If the signature is optional, mark the field as optional. For transition target states for which a signature is required, make the Signature field mandatory.

For example, a signature is mandatory for the Accepted status of the Approvals tracker:

You should give edit permission for the Signature field only to those users that must sign, and are assigned to the task.

As shown below, the Assigned to users must have edit permission for the Signature field in the Accepted status:

In some cases, regulations require two different identification components for an electronic signature, such as username and password. In this case, you should add another custom field of type Members in front of the signature or password field.

For example:

Use the same Mandatory and Permission settings for the signer and the signature fields.

We recommend that you have the signer and signature fields in additional rows as the last fields:

With the signature field (and optionally the signer field) in place, you can then associated the Validate the user signature (password) action with the appropriate state transitions:

This action has two parameters:

Please choose the appropriate fields, that represent the Signer and Signature to validate.