Note: This feature is only available with the Enterprise license type.

In order to make compliance simple and natively part of the Tulip platform, the Signature widget offers a way to sign data within Tulip. The signature is immutable and recorded within your application completion data. It can't be reassigned, transferred, or falsified.

The Signature widget is located under the Inputs tab in the App Editor.

Configuration Options

Data to Sign

The Data to Sign option controls what data is included within the e-signature when executed. This widget can be used to sign for variable data and table records.

Signee

The Signee option can be configured to control who has access execute the signature action on the collected data in the Tulip Player. This can be controlled to:

  • Any Operator

  • Operator executing app

  • Any operator besides app executor

  • Specify a list of allowed users

Signature Meaning

Use this field to add an additional description to the signature widget, which is available in the collected information.

Comment Mandatory

A boolean value that can be set to require the signee to add a comment to their signature before submitting.

Triggers

Standard Tulip trigger actions can be built to run off of the "When signature is completed" event.

Using the Signature Widget in the Player

When a user executes the Signature widget in the Player, the following modal appears presenting the data that is being captured as part of the signature, the authentication method for signing (badge ID or SAML user account), as well as a comment field.

Reviewing Signed Data

The information signed during app executions can be found in the completions data for the application. This data will also be available through the Digital History Record widget for any data captured with a table record loaded.

Completions data can be access through the Application Overview page via the Completions tab. This is how the signature widget will look when accessed via the Completions tab:

Did this answer your question?