In xential|manager, content is created and formatted in various locations. When the same style (for example Heading 1) is used in multiple locations, xential automatically determines which formatting takes precedence in the generated document. This article describes the hierarchy and the exceptions to it.


Locations where content is formatted

Content can be formatted manually or with defined styles in the following places:

  • The content of question types (selection questions and groups).
  • The content of templates.
  • The content of building block components.
  • The headers and/or footers of header and footer components.
  • Styles defined in the Corporate styles category.


Which formatting takes precedence?

When the same style is used in multiple locations, the following order applies, from highest to lowest precedence:

  1. Style formatting defined in a corporate style from the Corporate styles category.
  2. Content formatted in the header and/or footer of a header and footer component.
  3. Content formatted in the content of a template.
  4. Content formatted in the content of a selection question or group, whether or not used in building block components.

A higher level always takes precedence over lower levels. Whether a corporate style or header/footer component is included in the hierarchy depends on whether the template is linked to it.


Exceptions to the rule

Two situations deviate from the standard hierarchy:

  • A manual formatting change to the Default style is always preserved and takes precedence in all combinations, even over higher-level elements.
  • Additional styles applied to content in question types, components or templates that do not exist at a higher level are preserved and take precedence. In that case, the style is added to the style gallery of the generated document.


Examples of conflicts and outcomes

When the same content is formatted at both the template level and at the question/group/component level, a conflict arises. Below are some common combinations and which formatting takes precedence in the generated document:

Scenario 1: additional style at both levels
The template uses style A, the question/group/component uses style B. Result: style B takes precedence (the content of the question/group/component overrides the template style).

Scenario 2: base style in template, additional style in question/group/component
The template uses Heading 1, the question/group/component uses style B. Result: style B takes precedence.

Scenario 3: additional style in template, base style in question/group/component
The template uses style A, the question/group/component uses Heading 1. Result: the base style Heading 1 takes precedence for text formatted with that style.

Scenario 4: manual formatting in template, additional style in question/group/component
The template has manual formatting on the Default style (e.g. red), the question/group/component uses style B. Result: the manual formatting (red) takes precedence.

Scenario 5: manual formatting at both levels
The template has manual formatting on the Default style (e.g. red), the question/group/component has manual formatting on the Default style (e.g. blue). Result: the blue formatting from the question/group/component takes precedence for that specific text.