The HTMLdesktop-template is used to configure the content shown on a desktop on the collaboration platform on the web.
The content on a desktop is composed of HTMLTiles, and it is possible to specify filters for role and configuration.
The HTMLdesktop(s) are published to the web via the HTMLPublisher when they are included on the “Personal Page” tab (see below). It is also in the publisher where it is possible to set filters for role and configuration for the desktops.
The HTMLContextMenu template is for designing context menus for the web.
(relevant from version 10.2, and enhanced in version 10.3)
The symbols available for HTMLContextMenu are:
HTMLContextMenuItem
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.
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.
Context
Role
Condition
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
Active on
Icon on web
Target
The Spreadsheet template allows you to easily to review, edit and aggregate collections of data from across the repository from one window.
With the new dynamic spreadsheet, editing content from the web has never been easier.
Read more about the Spreadsheet functionality here.
The HTMLTile template is used on one or more HTMLDesktop(s) on the collaboration platform.
It is possible to configure the appearance and nature of the tile via the HTMLTile-template.
Among many things you can specify the title, color, size, description text, as well as link it to other content in the repository, e.g. a diagram or a HTMLQueryResultView.
Example of a tile on the web:
The HTML template definition defines the behavior and “look and feel” of a specific template-type.
In QualiWare 10.8 a new Dashboard layout has been introduced. You can create one or multiple dashboard(s) for a diagram template-type. The dashboard(s) are associated on the Dashboard Tab:
The Dashboard are configured using the templates:
The “Left”, “Center” and “Right” tabs specifies the content on the diagram workspace, shown on the example below.
The left window (1) of a diagram workspace is configured on the Left tab:
The Center tabs (2) of a diagram workspace in configured on the Center tab:
The right window (3) of a diagram workspace is configured on the Right tab:
Once you have made changes to the template, you should click “Apply” and “Publish” to implement the changes on the Web.
The HTMLTemplateDefinitions are included in the HTMLPublisher.
The HTMLPublisher Template contains all settings regarding the configuration of the Web. It collects all the settings for the collaboration platform on 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 for the web.
From the HTMLPublisher tab, it is possible to specify:
The Model Generator Settings for the table to model feature in the web-modeler (introduced in QualiWare 10.8) is setup through Smart Capture Settings tab:
Purpose: The purpose of the HTML Mega Menu template is to enable the tailoring of the left menu on the collaboration platform.
Core concerns: The HTML Mega Menu template enables you to build the left menu using HTML Mega Menu Items, which can be layered. The example below shows how a menu looks in our modelling tool:
The screenshots below show how a menu can look on the collaboration platform and how the sub-menus are shown:
The left menu can be configured for differently for diffrent roles. The left menu can be modelled in 3 levels:
The HTMLMegaMenu is composed of HTML Mega Menu Items.
The Mega Menu is published to the Web via the HTML Publisher.
Relation to other templates: The HTML Mega Menu is related to the other HTML templates such as Generic Query, HTML Dialog Layout and Query Design.
Properties and metadata: The HTML Mega Menu template can for example retain the following information:
The above picture shows the properties dialogue window for the HTML Mega Menu template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
Purpose: The purpose of the Query Design template is to enable easy design of Generic Queries.
Core concerns: The Query Design template enables you to model Object Queries and Relation Queries into Generic Queries. When creating a Query Design, a Generic Query will be generated automatically and appear graphically on the diagram as a white triangle in a green circle – see the model below:
Relation to other templates: The Query Design template is used to generate Generic Query templates which can be used in creating Report Definitions, Spreadsheets and HTMLQueryResultViews.
Properties and Metadata: The Query Design Template can for example rentain the following information:
The above pictures show the properties dialogue window for the Query Design Template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager
You can see an example of a Query Design in the QualiTube sections, where there is a video on Composity Query Design.
Purpose: The purpose of the Business Chart template is to create different graphs and charts using information from other diagrams and templates. The Business charts can then either be published on a Dashboard and/or stored.
Core concerns: The Business Chart template is concerned with analyzing other templates and models. Therefore, it is not modelled like a typical template, but created using the Chart Wizard found in the template’s property window:
Below, you can see the Chart Wizard that helps you create your Business Chart:
The Business Chart template can for example be used to generate a chart over how the capabilities or Key Performance Indicators of an enterprise are performing over time or compared to desired values. Additionally, Business Charts can be used to analyze static data entered in a Matrix model. You choose the input to your Business Chart as a ‘Data Source’ in the templates metadata (see figure under Metadata).
Below, you can see two very different examples of business charts:
Relation to other templates: The Business Charts are published using the Dashboard template.
Properties and metadata: The Business Chart template can for example retain the following information:
The above picture shows the properties dialogue window for the Business Chart Template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.