Automating field placement in dynamic contracts has never been easier. In this webinar, developer Harini Chellappa demonstrated how BoldSign text tags eliminate the need for manual coordinate mapping and streamline eSignature workflows in .NET.
If you missed the webinar, or would like to watch it again, the recording is uploaded to our YouTube channel and embedded here.
What you’ll learn
- What text tags are: Learn how placeholders within a document can automatically create signature, date, and text fields.
- How to use definition tags: See how checkboxes, radio buttons, and dropdowns can be defined programmatically using definition IDs.
- Integrating with the BoldSign .NET SDK: Understand how to send documents for signatures and enable text tag detection.
- API setup: Generate and use API keys to securely connect with BoldSign services.
- Practical demo: Watch as a dynamic service agreement is prepared, tagged, and sent for signature, all without manually positioning fields.
Time stamps
[00:00] Welcome and Introduction
[00:26] Understanding Dynamic Field Placement Challenges
[01:27] Introducing BoldSign Text Tags
[02:00] Session Agenda
[03:08] What Are Text Tags?
[03:52] Demo—Adding and Sending Text Tags for Signing
[05:44] Hiding Text Tags in Documents
[05:47] Text Tag Syntax and Field Types
[07:23] What Are Definition Tags?
[08:14] Demo—Using Text Tags in .NET SDK
[09:14] API Authentication and Key Generation
[10:04] Demo—Adding Fields and Tags in a Contract
[13:02] Sending a Document for Signing
[16:33] Enabling Text Tags in the .NET SDK
[17:00] Defining Radio Buttons and Checkboxes
[19:03] Final Demo—Automated Form Field Placement
[19:38] Wrap-Up and Next Steps
Q&A
1. What is the advantage of using this method compared to the current one?
Text tags allow you to add field definitions directly into the document content. This eliminates the need to manually define coordinates or page numbers for each field.
2. Does the final document always have to be converted to PDF? In the video I saw, the Word document was being uploaded directly.
Yes, you can upload all standard formats like Word, PDF, an image, or Excel. The signed document will be in PDF format, though.
3. Should the template document be a Word file? Does the person who signs receive a PDF file?
The template document can be any standard file. If you upload a Word document, we will convert that to PDF.
4. Is this new feature included in the existing plan we have or is there an additional cost?
It comes with our Enterprise API plan
5. Can this method be a substitute for setting up templates in the web app? Can I just add text tags to any document and then send it to others?
Yes, you can add text tags to any document and send it via API.
6. OK, so we just need to use the API to activate the text tag function?
Yes, correct.
7. Can I automate word content creation using Syncfusion components and then send it for signature using BoldSign, all from the application?
Yes, you can do that.
Why it matters
Developers can save time by using text tags instead of manually placing fields in every document variation. This approach reduces human error, improves consistency, and allows for scalable automation in enterprise workflows.
