Documentation

clearString neatComponents

Application Development

Reference

How-to Resources

Installing

Application Development 

External {{signing}} 

Legal Document Preparation

clearString makes it straightforward to automatically create documents that are assembled through a series of process-steps, each clause or paragraph being determined by how a question is answered. Contracts, agreements, medical authorizations, share distribution and company formation documentation, and insurance agreements are common examples.

In these scenarios while the document is constructed from the database the app wants to be able to present the end-user with the ability to insert qualified information into the 'finished' document before rendering it as a completed PDF suitable for signing by an external authority. This is achieved in a similar way to old-style 'mailmerge'.

Named Parameter Expansion for 'mailmerge' 

There are situations where you need to provide 'mailmerge' functionality, where a text document with embedded codes is combined with data from a separate source, so that it substitutes the codes with appropriate data.

Primary Use Case

This is useful for completing template documents and contracts.

Unlike conventional 'mailmerge' both  the 'template' text (that is user generated) and the 'mailmerge' content is drawn from a database that can be fully integrated with a company's work flow.

Automatic template generation can be fully conditional as well as the 'mailmerge' content, built on layers of queries drawing from multiple sources.

Documents and Contracts generated by the system are rendered as PDF documents for signing by external signing authorities - such as SignNow, etc.


Create the Template table

Create a Table, and include a Rich Text field.

In this each record represents a separate template document. (There may only be one record needed if there is just one template)

Edit the rich text field, entering the boilerplate text.

Where some content will needed to be inserted, enter a shorthand code.

This has the format:

{code}

ie a curly open-bracket, followed by some lowercase text, and a curly close-bracket.

The code should not contain any spaces or punctuation.

Read detailed information here...

Copyright © 2026 Enstar Systems Inc.    All rights reserved