LogoLogo
Getting StartedDevelopersDeployment GuideGet Help
  • Quick Links
  • Welcome to Form.io
    • Getting Started With Form.io
    • Launch a Form
    • Overview of Form.io
  • Developer Tool Ecosystem
    • PDF Solution
    • Enterprise Form Builder
    • Form View Pro
    • The Security Module
    • Accessibility Compliance Module
    • Developer License
    • SQL Connector - Deprecated
    • Integration Libraries
    • Form.io CLI Tool
  • User Guide
    • Introduction
    • Form.io Developer Portal
    • Teams
    • Projects
      • Project UI
      • Project Settings
      • Stages
      • Multi-Tenancy
    • Resources
      • ResourceJS
    • Forms
      • Form Creation
      • Form Types
      • PDF Forms
      • Embedding a Form
      • Form Revisions
      • Form Settings
    • Form Building
      • Form Builder UI
      • Form Components
        • Component Settings
        • Basic Components
          • Resource as Select Component Data Source
        • Advanced Components
        • Layout Components
        • Data Components
        • Premium Components
          • Nested Forms
        • Custom Components
      • Logic & Conditions
      • Existing Resource Fields
      • Actions
    • Submissions
      • Accessing Submissions
      • Importing Submissions
    • Form.io eSignature - Coming Soon
    • Form.io Reporting Module
    • PDF Template Designer
    • Form View Pro
    • Form Manager
    • Enterprise Form Builder Module
  • Developer Guide
    • Introduction
      • Application Development
      • API Documentation
    • Form Development
      • Form Renderer
      • Form Builder
      • Form Embedding
      • Form Evaluations
      • Form Templates
      • Custom Components
      • Translations
    • JavaScript Development
      • JavaScript SDK
      • JavaScript Frameworks
      • JavaScript Utilities
    • Authentication and Authorization
      • SAML
      • OAuth
      • LDAP
      • Resource Based Authentication
      • Email Authentication
      • Two-Factor Authentication
    • Roles and Permissions
      • Field Match-Based Access
      • Field-Based Resource Access
      • Group Permissions
    • Integrations
      • Email Integrations
      • File Storage
      • Google Developer Console
      • eSign Integrations
      • Relational Databases
    • Modules
    • Fetch Plugin API
    • CSS Frameworks
    • Offline Mode
    • Audit Logging
  • Deployments
    • Self-Hosted Deployment
      • Local Deployment
        • Local File Storage
      • Kubernetes
      • Cloud Deployment
        • AWS Deployment
          • AWS Lambda
          • Form.io/AWS Elastic Beanstalk End-To-End Encrypted Deployment
        • Azure Deployment
          • Azure App Service
            • Azure MSSQL Connector - Deprecated
          • Azure Virtual Machine
          • Azure Kubernetes Service
          • Set up the DB
        • GCP Deployment
          • GCP Cloud Run
      • On-Premise Deployment
      • Enterprise Server
      • PDF Server
    • Deployment Configurations
      • DNS Configuration
      • Load Balancer Configuration
    • Licenses
      • License Management
      • Library Licenses
    • Portal Base Project
      • Portal SSO
      • Portal Translations
    • Maintenance and Migration
      • Changes to Premium Libraries
  • FAQ
    • FAQ
    • Tutorials & Workflows
      • Password Reset
      • Dynamic Select Filtering
      • Approval Workflow
      • SSO Email Token
      • Embedding A Video
      • Data Source Validation
      • Select Data Source Options
      • Nested Form Workflows
        • Nested Wizard Forms
      • Save as Draft
      • Role-Based Conditions
      • Custom Component
      • Dynamic Radio and Select Box Values
      • Override CKEDITOR
    • Errors
    • Examples
    • License Utilization Checks
  • Contact Us
Powered by GitBook
On this page
  • Overview
  • How to use
  • Signature Component
  • eSign Action
  • eSign Integration Settings

Was this helpful?

  1. Developer Guide
  2. Integrations

eSign Integrations

Form.io contains eSign integrations that allow forms to request an eSignature from a form user on submitted forms.

PreviousGoogle Developer ConsoleNextRelational Databases

Last updated 7 months ago

Was this helpful?

Overview

Form.io allows integration with eSignature providers to capture an eSignature, a digital signature, from one or multiple signers. This process is customizable and works for both PDF and API forms.

The Form.io Box Sign Integration will soon be deprecated

How to use

Signature Component

To add an eSignature component, drag and drop a Signature component onto a form as seen below:

Once placed, the Signature component edit modal opens. Click on the "Providers" tab to select a supported eSignature provider. The available options are:

  • Default - This is a standard digital signature that should be signed upon form submission

  • Box Sign

The Form.io Box Sign Integration will soon be deprecated

When selecting a provider other than Default, additional fields are available:

  • Signer Email - The email address of the person needing to provide a signature. This can be a string email address or an interpolated value. For example, in the above screenshot, the value is {{data.emailAddress}}. This assumes there is another component on the form whose display and API value is "Email Address". The value of this component will be substituted for {{data.emailAddress}}.

  • Signer Order - The order in which this recipient should receive an email request for signature. Example: any value between 1 and integer max value.

eSign Action

Add the eSign action under the Form's "Actions" tab by selecting "eSign (Premium)" from the drop-down on the Actions page as seen below:

The eSign action screen contains several options.

The available options include:

  • Approvers - Recipients who need to approve a document sent for eSignature, but do not need to provide a signature. The values here can be a string email address or an interpolated value. Example values: approver@example.com or {{data.approverEmailAddress}}

  • Final Signed Copy Recipients - Recipients who need to be sent a copy of the signed document once signing has been completed. The values here can be a string email address or an interpolated value. Example values: final_copy_recipient@example.com or {{data.finalCopyRecipientEmail}}

  • Automatically redirect to E-Sign provider on Form Submit - By checking this box, the form will automatically redirect to the eSignature provider website upon form submission to allow the person submitting the form to provide a signature. Note that there is no redirect back to Form.io upon signature completion. You will have to navigate back to Form.io.

  • Email Subject - A custom email subject to be included in the signature request email. Valid values are string values. Example: Please eSign this form

  • Email Message - A custom email message to be included in the signature request email. Valid values are string values. Example: This is my test email message

  • Name of upload PDF File - The name you wish to customize for the file when uploaded to eSignature provider. Valid values are string values. By default, if you leave this field blank, the name of the file when uploaded to the box will be the submission id. Example: My request form

eSign Integration Settings

Before eSign can be use, set the appropriate eSign integration settings on the project's settings:

Drag and drop the Signature component onto a form
Fill out the eSign integration settings here