Setting fonts for different brands using Style list functionality in EngageOne Designer

Style list functionality within EngageOne® Designer was introduced to enable users to switch fonts, typefaces, colours and encoding based on a single style for different brands.

A Style List would usually be set up in a piece of Active Content, so it could be deployed in either Active Content or Documents as required.

The user would initially create a piece of Active Content for their styles, with a parameter for the brand, and use this parameter in a case test:

User-added image

A series of case tests would then be set up to check for the brand, and in each of the case tests, the style list would change the font associated with the style.  A style list is entered from the Control Objects menu:

User-added image

The font, typefaces or colours are then applied for each style in the least dependent on the brand selected:

User-added image

In this example, 3 different styles have been set up, body_regular, header_bold and footer_bold and the font has been set by selecting the "font" tab, where the user accesses the standard Windows font list, and all available fonts and typefaces can be selected, and a colour and language applied if required.

For one brand, the "header_bold" style is set to Arial 14pt Bold in Black using the English language option:

User-added image

For another brand, the "header_bold" style is set to Times New Roman 14pt Bold red using the English language:

User-added image

All that is then required is a variable or data field to drive the brand in either the document logic, or Active Content.  Please note that the style list must be present in the logic of either the document or Active Content before the text where the style needs to be applied.

In the document or Active Content logic, the user would then select the Style, rather than the font:

User-added image

When the user selects the style, it automatically switches the font to that set for that brand.

Once a style has been created, it is available anywhere in the repository in which is was created, be aware though, that if a style is selected, and the style list is not present in the item before the text where the style has been applied, the results can be unpredictable.
  • A style contains text formatting instructions. It always specifies a font and point size and can also include font decoration settings such as color, bold, italic, underline and so on.
  • A style can be applied to most text elements including data fields, address blocks and charts. 
Before a style list is encountered no styles are used and all text elements are presented using their regular settings. Once a style list is encountered any text that follows the object within the logic will adopt the settings of the styles it contains wherever a style name from the list has been applied. Subsequent style lists within the logic may amend some or all of the named styles. If a style name does not appear in a style list in a given object, its settings remained unchanged from the previous time a style list included it.  

Styles can only be used for setting fonts, there is currently no inbuilt mechanism to affect the appearances of tables (coloured border or table shading), but this could be achieved using a condition or a case test.

If the user imports a snapshot from a different environment where different styles have been deployed, these styles will all be imported in the current repository.

If there is a need to remove a specific style, this is done through the style list functionality, bring up a style list, select one of the current styles from the drop down list, and select "remove", this gives two options, "remove from the list" or "remove from the repository and list".  If the latter is selected, it should be done with care in case some item in the repository is using it.
UPDATED:  July 20, 2020