Templates allow you to create configuration fragments that you can re-use in all instances. All templates require a unique name. Most template types are lists that you can reference in the configuration of action trees. This enables you to complete the configuration faster and also provides a form of processing instructions for categorizing the instance. For example, you could specify to only process certain message classes, which is why you create the list of selectable classes centrally as a configuration template. You could also use an instruction to exclude specific folders, regardless of whether they appear in the mailbox structure or not. You would use a folder filter template for this. You can create list templates for action trees for catalogs, entry points, folder filters, and classes.

To use message stubbing, you need to define a stubbing template using the corresponding action ("StubbingDef"). This template defines the content that is created when the message is stubbed. It is created in the template directly. It is necessary to distinguish between HTML and text format, as this will affect how the message is displayed after stubbing.

The most important template is for the keywording in the ELO repository. When configuring a new instance, there are two default templates, one for archived messages, and one for components of the filing paths. This template defines how the relevant keywording information is generated, such as the keywording form that is assigned, and the index field entries.

If you click the Templates node, you will find the templates that have already been created. You can create new templates by clicking the star icon and selecting the desired template type from the submenu.

A drop-down menu with available configuration templates appears.

The following configuration templates are available:

• Entry point template
• Class template
• Folder filter template
• Mailbox template
• Stubbing template
• Keywording template

Information: Refer to the