The Composer compiles the actual document from different text modules on the basis of a template previously created in the Designer. This type of document template should not be confused with an MS Word-style template. In DES, a template should rather be understood as a structured set of instructions detailing which content should appear with which frequency at which location.
Depending on the application concerned, the Composer controls either the generation or further processing of a given document. For both scenarios, the Composer is loaded with the corresponding document template with the template's content structure being displayed as the document structure. The document structure essentially consists of individual text modules or module bundles.
In this view the future document can be modified by the user who can accept or reject pre-defined text modules and module bundles depending on the input of the administrator. Furthermore, the user has the option of inserting further text modules and bundles into the structure. The latter is especially useful when particular case-specific text modules have not been pre-defined in the document structure by the text administrator.
In the course of compiling the document from text modules, placeholders are populated with corresponding data. This can be staff, company or process data. Indexing of text modules and data fields ensures that placeholders are populated with the correct data fields. The back-end data acquisition is performed exclusively by web services, so that in effect any data source can be connected to your company.
The Composer therefore represents the central application for the manipulation of document instances and the administration of their status. A completed document is transferred to the DES components "Post and Final Processing" which essentially correspond to the Output Management.