A configuration template can itself include a setting for [FDK]ConfigTemplate, specifying yet another template file. This allows you to create a chain of templates for Mif2Go to search for settings. The chain can be any length. All files in the chain must have distinct names; the chain stops if Mif2Go finds a repeated template name. The settings in all templates in a chain are applied to your project configuration in a cascade at run time.
In a chain of templates, if the same setting appears in more than one template file but has a different value in each file, the value for that setting in a template closer in the chain to the project configuration file overrides the value in any template farther away in the chain from the project configuration file; and a value for that same setting in the project configuration file overrides the final template value. See §31.1.2 .
You can use the chaining effect to specialize templates for different types of settings; for example, you could have a graphics template, a style template, and a table template. Or, you could maintain separate templates for different HTML-based Help formats, and have them all inherit settings from a generic HTML template, and thus avoid a lot of duplication.
> 32 Automating Mif2Go conversions > 32.2 Importing settings from configuration templates > 32.2.3 Chaining configuration templates