In the default signing process, users sign a document and click the Submit button to submit signature data such as the signature image and form field data. The server-side DocumentViewer controller is processing the signature and creates a document with the patched electronic signature images.

But the DocumentViewer can be also utilized to implement custom workflows. In this sample, the DocumentViewer is essentially used to acquire the signature images from multiple signers. At the end, when all signatures are captured, the document is finalized by merging signature images into the signature fields and by signing them using a certificate.

Server-Side Processing

The acquired signature data can be forwarded to a custom HTTP endpoint given through the RedirectUrlAfterSignature TX Text Control .NET Server for ASP.NET
Web.MVC.DocumentViewer Namespace
SignatureSettings Class
SignatureSettings.RedirectUrlAfterSignature Property
Specifies an Url that is used for a controller-side redirection after a successful signature acquisition process.
property.

Loading...

Custom HTTP Endpoint

The custom controller HttpPost method Sign is called by the DocumentViewer after a document has been signed successfully and should implement the SignatureData object:

Loading...

The forwarded SignatureData object contains meta data about the signature and the signed document:

Signature Workflow

After the user signed the document, the electronic signature is stored server-side until all signatures are acquired. After that, all signature images are patched to the document and finally, the document is signed digitally. The following sequence diagram shows the general workflow::

Signature Workflow

The Sample Application

After starting the sample application, an overview of all signature requests ("flows") is shown:

Signature Workflow

To create a new flow, click the button New Flow. This page is asking the user to upload a document that is used for the document signing process. For this demo, the document must be in the internal Text Control format.

Signature Workflow

The document is analyzed server-side for contained SignatureField TX Text Control .NET Server for ASP.NET
TXTextControl Namespace
SignatureField Class
An instance of the SignatureField class represents a signature field in a Text Control document.
objects with unique Names TX Text Control .NET Server for ASP.NET
TXTextControl Namespace
FrameBase Class
Name Property
Gets or sets a name for the frame.
.

Signature Workflow

As the document owner, you can complete the form data for each signature field and create the document flow by clicking the button Create:

Signature Workflow

The overview list contains the created signature flow including links for the signers to request the signatures. In real-world applications, this link would be shared by e-mail or other ways. For demo purposes, you can now click on this link to complete the signatures:

Signature Workflow

After all parties have signed the document, the document is finalized and will be available for download in the overview:

Signature Workflow

You can clone the sample and test this workflow on your own. This sample is meant to be as a framework for your own workflows. The major advantage of the electronic signatures created with TX Text Control is the flexibility and the customization options.