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 HTML Model Generator Settings template is used to configure the table to model feature introduced in the web-modeler in QualiWare 10.8.
In the HTML Model Generator Settings you can configure the table-to-model settings and make them available for selected diagrams in the web-modeler.
Below is an example of where Box in a Box is selected as Diagram type:
Below is an example of how the “Box in a box” settings works in the web-modeler for the Business Capability Model diagram:
In order to be able to access and generate models in the WebModeler, the HTMLModelGeneratorSettings objects needs to added to the HTMLPublisher and/or to the HTMLTemplateDefinition for the specific diagram Template.
The Model Generator Settings is setup through the HTMLPublisher’s Smart Capture Settings tab:
You can insert the HTMLModelGeneratorSettings in the HTMLTemplateDefinition for the specific diagram on the Smart Capture tab (or select the “Inherit default settings” to inherit from the HTMLPublisher.
The HTML Dashboard template is used to configure the dashboards introduced in QualiWare 10.8.
The Dashboard is setup up through a HTMLTemplateDefinition’s Dashboard tab:
It is possible to have multiple Dashboards. In this case they will appear in the selection in the web:
The Dashboard-template contains a collection of DashBoardItems-templates.
Furthermore, the Dashboard contains a Settings tab where the Dashboard can be adjusted.
Each DashBoardItems contain 2 tabs relevant for configuring their behaviour.
HTMLDashboard tab:
… And Custom Configuration
The Dashboard Setting tab contains the setting following table:
Background: You can insert any HTML color, HEX or RGB. This field behaves like color in CSS.
Examples: rgb(204, 255, 229) #E5FFCC PaleGreen
minWidth and maxWidth: The dimensions of the dashboard.
minRow and column: minimum rows amount and columns
cellHeight and CellHeightThrottle: cellHeight- one cell height (default?: ‘auto’). Can be:
CellHeightThrottle: throttle time delay (in ms) used when cellHeight=’auto’ to improve performance vs usability (default?: 100).
marginTop, marginBottom, marginLeft, marginRight and marginUnit:
The margins can be set with integers or strings. Use marginUnit to define the unit. Example of units: “px” and “em”.
float: enable “floating” items (default: false). Enabling this allow items to be anywhere on the page.
When true:
When false, items “fall upwards” and stack:
animate: turns animation on to smooth transitions (default: true). This is used when editing the layout when items swap places.
placeholderText: placeholder default content (default: ‘MOVE HERE’). This is shown when user is in edit mode and dragging the items:
rtl: “Right To Left”, Possible values are true, false, ‘auto’. This value has no effect.
In QualiTube, you can find videos about how to configure the Dashboards
The HTML Dashboard Item template is used in the HTML Dashboard template to configure the dashboards introduced in QualiWare 10.8.
The DashboardItems can show many types of data in different ways which makes them a flexible tool.
The icon source attribute allows you to select from a predefined list of symbols that are available for use.
Please refer to the DashboardItem Icon Source Cheat Sheet in the Appendix (below) for the keyword mapping list. The Method attribute (combined with the Parameters and Reference Link(s) attributes) determine the behaviour of the DashboardItem.
It is possible to use a custom icon on a DashboardItem. The URL can be any image file supported by browsers and it must be fetched through HTTP/s protocol.
Put the image file in the GeneratedHTML folder in your IIS-application. In this example I have put the image into the Images-folder.
Using the ContexInfo-method will display information about the object.
It is set up in the following way:
Alternatively, it is possible to display the content of an already existing HTMLContentTable:
Using the ObjectLink will open the object directly.
Example of using the ObjectLink-method to open a report:
RASCI is not configurable.
Example of RASCI:
The TableOverView – Context-method is used to display a list of objects based on a GenericQuery.
Examples:
It is set up in the following way:
The reference Link(s)-object is a generic query showing data about a collection of objects.
The parameter is HTMLParameter containing a mapping string. The mapping will only change the label shown on the web page.
If the HTMLParameter is empty the count of different templates will be hidden:
Example of empty parameter:
The HierarchyView-method will show the Hierarchy based on the HierarchyView-object in the Reference Link(s).
Example:
It is not possible to configure the HierarchyViews presentation on the DashboardItem.
| (Empty) |  |
Ability |  |
Approve |  |
| Capability |  |
Change |  |
Chart |  |
| Collaboration |  |
Comment |  |
Context |  |
| Cost |  |
Cycle |  |
Dashboard |  |
| Deleted |  |
Edit |  |
Feedback |  |
| Heatmap |  |
Highlight |  |
Image |  |
| Improvement |  |
Information |  |
Items |  |
| Link |  |
List |  |
People |  |
| Plan |  |
Process |  |
Query |  |
| Rating |  |
Report |  |
Risk |  |
| Score |  |
Spreadsheet |  |
Visualization |  |
In QualiTube, you can find videos about how to configure the Dashboards
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.
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.
Report definition is used to generate reports for e.g. a diagram type, and make them available on the web.
There is a set of standard reports included in the standard configuration, click here to see more about the standard reports.
Reports are designed via the template ReportDefinition.
Reports are always generated dynamically based on the content where they are executed. For example, if you click on the report button on a diagram, it will use the objects and their information contained on the diagram. To make this possible it is necessary to define what variables the ReportDefinition should gather and where it should place them in the report.
Designing a report consists of four stages: Designing the queries, arranging the attributes in the main report, designing sub-reports and finally applying advanced formatting.
See this detailed guide for more.
Once created the report can be added to the relevant template in the Template Definition, to make them available on the web, via the “Print icon” in the Toolbar.
The ModelPresentation is an attempt to make it easier for the end-user to understand the meaning of the model when viewing it on the Web.
The ModelPresentation consists of a series of models or model parts shown in a sequence on the web. The sequence may include pictures, sound, video or text to explain the view of the model.
From the main settings, you can configure the scope of the presentation:
Once the ModelPresentation is created and associated with e.g. a diagram in the “Relevant for”, the presentation becomes available on the web, as a tab in the classic view.
The presentation gives the user a standard set of “video control buttons”, so it is possible to jump forward, backward, stop the automatic sequencing of pictures and so on.
This example shows a definition of a ModelPresentation that fades through the all revisions of the BusinessProcessNetwork.
The custom selection is a selection of diffrent models, which can be shown in the model presententer in relation to content selected in the “Relevant for”:
Another example of a ModelPresentation is the illustrated walkthrough of a diagram. Here it is a CustomerJourneyMap that shows the journey of a persona interacting with our enterprise. Each interaction is illustrated by a TouchPoint, and the ModelPresentation includes real life explanation, photos, etc. to illustrate the journey.
As illustrated in the example above with the customer journey, it is possible to show pictures and video associated to the object.
You can specify what attributes should be shown where in the “Attributes” tab.
You specify the layout of the presenter on the “Layout” tab.
