Sneak Peek 31.0
This article, part of a series, describes upcoming features that will be part of the next version of TX Text Control. A release date is not known yet and will be announced separately.
TX Text Control .NET Server for ASP.NET provides all required components to request electronic signatures from users. This article describes a complete typical workflow including document preparation, signature acquisition and the digital signing of the resulting document.
Preparing the Document
The TX Text Control document editor - available for ASP.NET (Core), Windows Forms and WPF - can be used to prepare a document to request signatures. The TXTextControl.SignatureField class represents a signature field in a document. It is a frame object with additional data such as the SignerData (address, contact info, name, reason, title) and a name property that is used by the document viewer for the signature acquisition.
To insert a new signature field, use the Signature Field button in the Insert ribbon tab.
Select the signature field and open the Frame Formatting contextual ribbon tab. Find the Name input field and type in a name for the signature field. For this sample workflow, type in the name txsign.
Insert a second signature field into the document and name this field txsign_init.
Save this document using the internal TX Text Control format (StreamType.InternalUnicodeFormat) and name this document signature.tx.
Deploying the Document
To deploy the document, the TX Text Control document viewer can be used.
This article describes the workflow using the different components.
Refer to the documentation or the Getting Started tutorials to learn how to setup an application using the document viewer.
Create an ASP.NET (Core) application that uses the document viewer and use the following settings in the MVC Html helper:
The following table lists the used SignatureSettings in the above MVC Html helper code.
Setting Value description ShowSignatureBar Specifies whether to show the blue signature bar on opening the document. OwnerName The name of the signature requester that is displayed in the signature bar. SignerName The name of the signer that is displayed in the "Setup your Signature" dialog. SignerInitials The initials of the signer that is displayed in the "Setup your Signature" dialog. UniqueId A unique ID that is included in the graphical representation of the electronic signature. RedirectUrlAfterSignature An Url that provides an endpoint to accept the signed document and signature data. SignatureBoxes An array of SignatureBoxes to define which signature fields should be used based on the given name. Additionally, the style of the signature box can be provided.
After starting your application, you can setup a signature and sign the signature fields. Pay attention to the second field that has been created as an Initials field using the given SignatureBoxes array in the SignatureSettings.
Processing and Signing the Document
The document viewer is forwarding an electronically signed document to the given endpoint (provided by the RedirectUrlAfterSignature property in the SignatureSettings). All signature images are merged into the selected signed signature fields (using the SignatureBoxes array in the SignatureSettings). This document is forwarded to the given endpoint including a complete SignatureData object that holds the document, the signature images and additional data such as completed form fields.
In case, you only need an electronically signed document, you don't have to implement the following step. The returned document already contains all merged signature images. But if you want to assign a digital signature to the signature fields, the following controller method must be implemented.
Create an HttpPost endpoint that handles the signature document.
In line 24, the signed document is loaded into an instance of Server
╰ TXTextControl Namespace
╰ ServerTextControl Class
The ServerTextControl class implements a component that provide high-level text processing features for server-based applications. . An X509Certificate2 is created from a PFX file that is then assigned to the signature fields txsign and txsign_init. Eventually, the document is exported and returned as a PDF/A document. At this point, you can store the document server-side, return it to the client or whatever is required in your specific workflow.
Checking the Signatures
When opening the resulting document in Adobe Acrobat Reader, you can see the visual representations of the signature fields and the signature details in the Signatures sidebar: