Pathagoras On Cloud

Document Assembly

Hide Navigation Pane

Document Assembly

Previous topic Next topic No directory for this topic  

Document Assembly

Previous topic Next topic Topic directory requires JavaScript JavaScript is required for the print function Mail us feedback on this topic!  

Document Assembly


Definition: There is no standard definition for the term 'document assembly.' We have defined it as the process of bringing together various text components (boilerplate text, conditional text and variables) into a cohesive document, and then personalizing that text to meet the needs of the client or customer. Included within the scope of Document Assembly is document automation, replacement of variable text, and document dis-assembly -- creating the clause snippets and bespoke text from existing documents.


  There are two distinct types of document assembly processes, and then a continuum of types between the two extremes.


Template assembly:


A template is an overbuilt document that contains every possible variation that the author can conceive as appropriate for the document. Conditional text in Pathagoras are denoted by <Options>>, <<Optional>> or {Optional} blocks.  The document is assembled (actually 'processed' in our ling by calling that document to the screen (or a copy of it by clicking the Assembly button) and then clicking "Process Document". That will trigger Pathagoras to look for conditional text block, ask the proper question leading to the keep or delete action.


Paragraph assembly:


Pathagoras handles templates very nicely, but it was conceived as a clause assembler. Imagine that you have 100 clauses that represent the variety of clauses that you might need to compose a wide variety of documents. For this particular client, you need clauses 1,4,5,14, 22 and 56. (While we are using numbers, that is for example purposes. All documents would have real and meaningful names.) With Pathagoras, you can easily select these multiple documents, using your mouse or your finger, and cobble them together into a single document.


Mixed assembly:


This is where Pathagoras shines. You can seamlessly and fluidly mix and match assembly techniques. Individual clauses that you assembly using clause assembly might have <<Options>>, <<Optional>> or {Optional} blocks that can be processed after the base document is assembled. You can also start with a single template, and then pour in additional clauses from the boilerplate or elsewhere. (The method for adding additional clauses is varied as well. They are discussed under the topic 'Boilerplate.")


After Assembly:


You will have two choices as to what to do with your assembled document.


1. Keep it in the cloud for further processing. (If you have conditional text to process or variable to complete, you will want to choose the Process in the Cloud option.

2. You can download the assembled document to your desktop or table for further eding. (If you have Pathagoras (On Earth), you can download an unprocessed document to your desktop or tables and perform processing functions 'locally,' if you wish).


     After the document is processed, personalized and edited to your satisfaction, you then decide what happens next. Click the File tab to see your choices. (Print, create PDF, email.) See Post-Processing Actionsfor more information.