E-Signature Connector (DocuSign/Adobe)

Temel Özellikler

"Send for Signature" action added via page extensions on Sales Quote, Sales Order and contract documents

DocuSign eSignature REST API and Adobe Acrobat Sign API support (one or both, your choice)

Real-time signature status tracking (Sent, Delivered, Signed, Declined, Voided) on each BC document

Table extension stamps envelope/agreement ID and status field directly on the source record

Auto-download of the completed certificate-bearing PDF and attachment back to the BC document

Template-driven signing flows mapping BC document types to DocuSign templates or Adobe library documents

Job queue entry that polls the provider on a schedule for status updates

Optional webhook relay (API page or Azure Function) for instant status push

Per-company setup page for OAuth credentials, signer roles and routing order

Dedicated permission set so only authorized users can send and void envelopes

Signer routing and field mapping (signature, date, initials) defined per document type

Activity logging of every send, status change and void for audit trails

Siparişe özel, sizin için baştan sona

Kendiniz kurmanıza gerek yok — ECOSIRE tarafından geliştirilen, kurulan ve desteklenen çalışır bir uygulama.

Sipariş verirsiniz

Tek seferlik geliştirme fiyatıyla başlayın. Kapsamı başlangıçta sizinle birlikte belirleriz.

Geliştirir ve kurarız

ECOSIRE, Dynamics 365 Business Central ortamınızda geliştirir, yapılandırır ve kurar.

Yayına alma + destek

Yaklaşık 2–4 haftada yayına alırsınız; lansman sonrası bir destek süresi de dahildir.

Bu Ürün Hakkında

The E-Signature Connector closes the gap between Business Central and your e-signature platform so sales and legal teams never leave the ERP to get a document signed. It is delivered as a per-tenant AL extension that ECOSIRE builds, installs and supports directly on your Business Central environment (cloud SaaS or on-prem) — not a generic AppSource download you self-install.

We add page extensions to the Sales Quote, Sales Order and your contract documents with a "Send for Signature" action. Behind it, an AL codeunit calls the DocuSign eSignature REST API or Adobe Acrobat Sign API (your choice, or both), uploading the report-generated PDF and your defined signer roles. A table extension stamps each document with an envelope/agreement ID and a signature status field, and a setup page stores OAuth credentials, template mappings and signer-routing rules per company.

Status flows back two ways: a job queue entry polls the provider on a schedule, and an optional HTTP webhook (via an exposed API page or Azure Function relay) updates status the moment a signer acts — Sent, Delivered, Signed, Declined, Voided. When all parties sign, the connector auto-downloads the completed, certificate-bearing PDF and attaches it to the document's Incoming Document / record attachments so the signed copy lives where auditors expect it.

Template-driven flows let you map a BC document type to a DocuSign template or Adobe library document with predefined fields and routing order, so reps send a compliant packet in one click. Everything respects a dedicated permission set and writes to a change/activity log.

This is honest, scoped work: we confirm your exact document types, signer roles and provider account during a short discovery, build against your sandbox, then deploy to production with a walkthrough. Stated lead time applies — this is built to order, not instant.

Ne elde edeceksin

Per-tenant AL extension (.app) built for your Business Central version, deployed to sandbox then production

Page extensions on Sales Quote, Sales Order and your contract document(s) with the Send for Signature action

Table extension and setup page for envelope IDs, status, OAuth credentials and template mappings

Job queue setup plus optional webhook/Azure Function relay for status sync

Dedicated permission set and role-center cue for pending signatures

Configured DocuSign and/or Adobe Sign connection wired to your provider account

Source code, install walkthrough and a short admin handover document

Post-deployment support window with bug fixes and a Business Central version-compatibility check

Bu kimin için

Sales Manager

Wants reps to send a quote or order for signature in one click from within BC and see the moment a prospect signs, without chasing email threads or copying PDFs between systems.

Legal / Contracts Officer

Needs legally-binding e-signature with the completed certificate PDF auto-filed against the source document, plus an audit log of who sent, signed, declined or voided each contract.

Business Central Administrator

Wants a clean per-tenant extension with its own permission set, setup page and job queue rather than ad-hoc scripts, and a supported upgrade path across BC releases.

E-Signature Connector (DocuSign/Adobe) Nasıl Karşılaştırılır

Kriter	ECOSIRE	Özel Yapı	Rakip
Send BC quotes/orders/contracts for e-signature from inside Business Central	Dahil	Dahil	Kısmi destek
Both DocuSign and Adobe Sign supported	Dahil	Kısmi destek	Kısmi destek
Auto-download and attach the signed PDF back to the source document	Dahil	Kısmi destek	Kısmi destek
Real-time status tracking via job queue and webhook	Dahil	Kısmi destek	Kısmi destek
Built, installed and supported on your tenant by the vendor	Dahil	Dahil değil	Kısmi destek
Tailored to your exact custom document types and signer routing	Dahil	Dahil	Dahil değil
No in-house AL developer required to build or maintain	Dahil	Dahil değil	Dahil
One-time price with source code handed over	Dahil	Kısmi destek	Dahil değil

E-Signature Connector (DocuSign/Adobe) hakkında Sıkça Sorulan Sorular

How long until the extension is live, since this is built to order?

This is a custom-built per-tenant extension, not an instant AppSource download. After a short discovery to confirm your document types, signer roles and provider (DocuSign and/or Adobe Sign), we build against your sandbox and deploy to production. Typical delivery is about 1 to 2 weeks depending on how many document types and routing rules are in scope; we give you a firm date once scope is confirmed.

Do I need my own DocuSign or Adobe Sign account?

Yes. You keep your own DocuSign eSignature or Adobe Acrobat Sign subscription and account — the connector authenticates to it via OAuth using your API credentials. We configure the connection, templates and routing; the signature transactions and any envelope/transaction costs run through your provider plan.

Will this break when Microsoft updates Business Central?

The extension is written in AL using supported extension points (page/table extensions, event subscribers, the BC REST/OData API), so it survives standard updates. Our support window includes a compatibility check and any required adjustments for the BC release you are on; major-version upgrade work beyond the window is quoted separately.

Can it handle our own custom contract documents, not just quotes and orders?

Yes. We can add the Send for Signature action to custom or third-party document pages and map each to its own template, signer roles and field layout. Just include those document types in the discovery so we scope the page extensions and routing correctly.

Where does the signed copy end up, and is it the legally complete version?

When all parties sign, the connector downloads the provider's completed PDF — including the signature certificate / audit trail — and attaches it to the source document's record attachments or Incoming Document in Business Central. That is the legally-binding final copy, stored where your finance and audit teams already look.