HTML Visualizer Filter

The HTMLVisualizerFilter template is used to create customized filter(s) to use in the 3D Visualizer on the web.

Click “Add Templates” to select the templates to be included in the filter.

Click “Add Relation” to insert the relation to be included in the filter.

Once a HTMLVisualizerFilter is created it becomes available in the Explore and Local Explore menu.

HTML Context Menu

The HTMLContextMenu template is for designing context menus for the web.
(relevant from version 10.2)

The symbols available for HTMLContextMenu are:

The graphical part of HTMLContextMenu is only used to define context menus; it is not used for displaying to the user. The HTMLContextMenuItems on the HTMLContextMenu are defining when and where context menus are available to the user.

Example of HTMLContextMenu:

A default context menu can be defined in the HTMLPublisher. The default context menu will be applied to objects of all templates unless specific context menu is defined on the HTMLTemplateDefinition for the template. If the default context menu is left empty then only templates with a context menu defined will get a context menu.

A default context menu defined on the HTMLPublisher:

A template specific context menu is defined on the template definition for that template:

To activate the changes in context menu setup press publish in the HTMLPublisher.

Context menu and Governance Workflow Engine
Objects governed by a GovernanceWorkflow will get an extra context menu item. The item is called Governance and is added as the last item of the context menu. It contains the possible transitions available for the object.


HTML Context Menu Item

Settings for the HTMLContextMenuItem
(relevant from version 10.2)

HTMLContextMenuItem sample:

Context menu item
List of items to who in the context menu

Menu Image:
Not supported

Role access
General role access for all items in the context menu.

Context menu items

The context menu supports GovernanceStateFeature and HTMLContextMenuItem. Adding a GovernanceStateFeature means adding an action to the context menu. Adding a HTMLContextMenuItem will create a sub menu in the context menu.


  • The context defines where the context menu should be activated from. HyperLink means the menu will be available on objects in the repository explorer. Template means the context menu will be available when a template name is shown in the treeview part of the repository explorer. (Toolbar is not supported)


  • Ability to select role-based access to the menu item.


  • Additional condition for showing the menu item. E.g. Template == RepositoryFolder

Sample list of context menu items containing one sub menu and several items with conditions set:

Settings tab on HTMLContextMenuItem

The settings defined on this tab will apply to the whole context menu. If a HTMLContextMenuItem is used as a sub menu, then only Visual name is used.

Visual name

  • Used to define the display name when used as a sub menu

Active on

  • Currently only Left Click is supported

Icon on web

  • Not used here.


  • Only Dropdown supported.

Interest Group

InterestGroup is a template that can be used to collect a set of organizational objects into a group.

In the standard Metamodel you can include the following templates types into an interest group:

  • Person
  • OrganizationUnit
  • InterestGroup
  • Postion
  • Role

An InterestGroup can be used to in relation to other objects in the repository, in relations to GovernanceWorkFlows or AcknowledgeLists.


HTML Publisher

The HTMLPublisher Template contains all settings regarding the configuration of the Web.

The HTML publisher setting can be accessed in QLM via the HTML icon on the Standard toolbar in QLM.

or by using the shortcut CTRL+H.

The HTMLPublisher collects all settings, including:

  • the HTMLMegaMenu which defines the “Left menu” on the web
  • the Template Definitions with HTML-settings for the selected templates, and thereby the “look and feel” for how the selected templates is presented on the web

  • the Personal Page, defines the structure and role acces to the Desktops on the Web, each desktop is configured in a HTMLDesktop-template

  • Available Navigation Buttons on in the Top right menu


HTML Mega Menu Item

The HTML Mega Menu Items are used to compose a HTMLMegaMenu.

The Mega Menu is composed of 3 levels. Each level is a HTMLMegaMenuItem.


HTMLMegaMenuItems on the top level can be associated with an Image.

It is possible to define role access on each of the HTMLMegaMenuItems.

Right click the role window to add a role:

The available roles are specified in the Repository Administrator.

As can be seen in the selection box above, it is possible to select between two instances for each available role in the repository. The first “:” means that menu item will be visible/accessible in the menu if the user has access to the role. The second “=”  means that the menu item is visible/accessible when the user has selected the role.

Menu Items on the lowest can be associated to all kind of items such as HTMLQueries, Spreadsheets, Diagrams, etc.

It is also possisble to link a HTMLMegaMenuItem to an URL:

Active Directory Sync Setup

The ActiveDirectorySyncSetup template is a system template previously used to synchronize objects between the active directory and QLM. This however is now done in QEF or via the tools menu:

Acknowledge List

The Acknowledge list function enables you to keep track of and document which of your employees have read which relevant documentation.

An acknowledge list is used to select a group of people who must digitally acknowledge that they have read or studied specific sets of documentation. This can for example be a diagram, a document, or a set of regulations. An acknowledge list can be a one to one or a many to many relationships between objects and people. This means that you can have several people, InterestGroups, OrganizationalUnits or several objects listed in the same acknowledge list.

Once a user is assigned to acknowledge an object, an “Acknowledge” action-button is shown in relation to e.g. the Diagram:

The Acknowledge history can be seen on the “Acknowledge History” tab:

Governance Workflow

Purpose: The purpose of the Governance Workflow template is to enable tailored governance solutions for the objects in your repository.

Core concerns: The Governance Workflow template enables you to model Governance Roles and Governance States. The Governance States are placed inside a Governance Role (just like a workflow diagram) and are connected by Governance Transitions, Governance Conditional Messages, and Governance Event Messages.

Below, you can see an example of a Governance Workflow:

The green arrows symbolize a Governance Transition towards the approval of an object while the red arrows symbolize a Governance Transition towards the development state of an object. The blue arrows are Governance Conditional Messages. While the broad, dark green arrows are the preferred Governance Transition, the lighter green colored arrows are alternate routes to the approved state.


Relation to other templates: The Governance Workflow template is a template that can be applied to any of the published objects or diagrams in the repository.


Properties and metadata: The Governance Workflow template can for example retain the following information:

  • A description of the workflow
  • Link to the owner of the Governance Master Role
  • Audits (auto generated information regarding its current state and access rights)

The above picture shows the properties dialogue window for the Governance Workflow template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Further details can be added under the different tabs such as which templates the Governance Workflow pertains to and email settings: