Skip to content

Template Maintenance

The Template Maintenance page is accessed by selecting Template Maintenance from the Admin menu. It is only accessible to System Admin or Admin users.

Doc Assembler uses the term "Template" to refer to "the saved definition of the structure of a document". It is effectively the starting point for the usage of Doc Assembler as all information entered into the system is based around documents that are created from one of the templates established in the Template Maintenance area.

Regardless of User Type (System Admin or Admin), users will only have access to templates for which they have been assigned as an owner.

A template is comprised of the following components or levels:

The Header level is the top level of the template and the operator needs to select this level to configure a number of parameters that apply to the whole template. The operator also needs to select the Header level to assemble the template. Parmeters controlled at this level are discussed in further detail in the Edit Template area under the Complex Structure and Simple Structure articles.

The Section level can be described as containing the headings/titles within a document - the image below shows the sections highlighted in blue from a Council Agenda document that has been assembled. The structure of the section component of the document can be nested to contain many levels, referred to as sub-sections.

The Item level contains the actual content that comprises the assembled document e.g. officers' reports to Council, cover page, table of contents page, meeting notice or order of business. Shown highlighted in green in the image below, the items are the officers' reports that have been included into a Council Agenda document. Items within Doc Assembler can be created in one of two ways:

  1. As part of the template configuration process as static items e.g. cover page, table of contents page, regular officer's report that is required in every agenda, confirmation of minutes etc.
  2. Dynamically by an end user e.g. officer's report