SharePoint Connector Documentation
Index

E-Signing Overview

The SharePoint Connector integrates with electronic signature services, allowing you to send documents for signature directly from Business Central. This page provides an overview of the e-signing capabilities.

E-Signing Features

What is E-Signing?

Electronic signature integration allows you to:

  • Send documents for digital signature
  • Track signature status
  • Retrieve signed documents
  • Store signed documents in SharePoint

Supported Services

Service Support
Adobe Sign Full integration
DocuSign Full integration

End-to-End Workflow

Typical E-Signing Process

1. Document in SharePoint
       ↓
2. Select for signature
       ↓
3. Configure signers
       ↓
4. Send for signature
       ↓
5. Signers receive request
       ↓
6. Signers sign document
       ↓
7. Status updates in BC
       ↓
8. Signed document retrieved
       ↓
9. Stored in SharePoint

Step-by-Step

  1. Prepare document - Upload or generate document
  2. Initiate signing - Select document, choose e-sign action
  3. Configure - Add signers, message, settings
  4. Send - Document sent to signing service
  5. Track - Monitor status in BC
  6. Complete - Receive signed document
  7. Store - Signed copy saved to SharePoint

When to Use E-Signing

Common Use Cases

Document Type Scenario
Sales contracts Customer agreement required
Purchase orders Vendor acknowledgment
Employment docs HR document signing
NDAs Confidentiality agreements
Approvals Internal approvals

Benefits

Benefit Description
Speed Faster than mail
Tracking Know when signed
Legal validity Legally binding signatures
Convenience Sign from anywhere
Automation Integrated workflow

Prerequisites

E-Signing Service Account

You need an account with Adobe Sign or DocuSign:

Service Requirement
Adobe Sign Adobe Sign subscription
DocuSign DocuSign subscription

Business Central Configuration

Requirement Purpose
SharePoint configured Document storage
Table mapping Documents accessible
E-sign setup Service credentials

Integration Architecture

How It Works

Business Central
      ↓
SharePoint (document)
      ↓
E-Signing Service (Adobe/DocuSign)
      ↓
Signers (email)
      ↓
Signed document
      ↓
SharePoint (stored)

Data Flow

  1. Document retrieved from SharePoint
  2. Sent to signing service API
  3. Service sends to signers
  4. Signers interact with service
  5. Status reported back to BC
  6. Signed document returned
  7. Stored in SharePoint

Feature Comparison

Adobe Sign vs DocuSign

Feature Adobe Sign DocuSign
Send for signature Yes Yes
Track status Yes Yes
Download signed Yes Yes
Multiple signers Yes Yes
Custom messages Yes Yes

Choosing a Service

Consider Adobe Sign DocuSign
Existing subscription Use what you have Use what you have
Features needed Compare features Compare features
Integration requirements Both supported Both supported

E-Signing Status Tracking

Status Lifecycle

The Adobe Status and DocuSign Status fields on the e-Signature Overview page are Text[30] free-text fields populated directly from the signing service's response. They are not a BC-defined option set.

Typical values you will see (exact casing matters -- the connector uses exact-string matching when auto-downloading signed documents):

Service Typical values
Adobe Sign Sent to Adobe (initial, set by the connector), OUT_FOR_SIGNATURE, SIGNED, CANCELLED, EXPIRED
DocuSign sent, delivered, completed, declined, voided

Status values returned by the Adobe Sign service are uppercase (for example SIGNED), but the initial value written by the connector itself is mixed case (Sent to Adobe). DocuSign status values are lowercase. If you build custom logic with exact-match comparisons, match the exact casing of each individual value -- do not assume all Adobe-related values are uppercase.

Tracking in BC

The e-Signature Overview EFQ page (page 70319488) shows:

  • All documents sent for signing
  • Current status of each (Adobe Status and DocuSign Status)
  • Sent date
  • Signed date (when complete)
  • Signed document name
  • Actions to check Adobe Sign status and DocuSign status

Automated Status Checking

The e-Signature Checker EFQ (report 70319477) is a processing-only report that checks the status of all pending e-signatures. It can be scheduled as a Job Queue entry to automatically monitor signature progress. It checks:

  • DocuSign documents that are not yet "completed"
  • Adobe Sign documents that are not yet "SIGNED"

Getting Started

Setup Steps

  1. Subscribe to Adobe Sign or DocuSign
  2. Configure the service in BC (see service-specific guides)
  3. Test with a sample document
  4. Train users on the workflow

Quick Start Checklist

Step Action
1 Obtain e-signing service account
2 Configure service in BC
3 Connect and authenticate
4 Send test document
5 Verify workflow

Security Considerations

Data Security

Aspect Handling
Document transfer Encrypted API calls
Signer authentication Service-managed
Storage SharePoint security

Compliance

E-signing services provide:

  • Audit trails
  • Tamper-evident sealing
  • Compliance certifications

Limitations

Current Limitations

Limitation Description
External dependency Requires service subscription
Network required Internet connectivity needed