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.
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
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 User Role Configurator template is for the QLM user to create his or her personalized workspace featuring only chosen repository views.
Core concerns: The User Role Configurator template is a system template in QLM. It enables you to create and attach Repository View Definitions, Property View Definitions and Sub Tab View Definitions to the User Role Configurator. Where the information in the User Role Configurator decides which filters will be shown in QLM, the different view definitions define what the filters should contain. Below, you can see a screenshot of the QLM workspace. The repository view, which this template can configure, is marked with a red arrow and framed by a red square:
‘Relation to other templates: To run, the User Role Configurator template must have a corresponding QualiWare Setup template to execute its code. Where the HTML templates pertain to the setup of the collaboration platform, the User Role Configurator template is solely concerned with the workspace in QLM.
Properties and metadata: The User Role Configurator template can for example retain the following information:
The above picture shows the properties dialogue window for the User Role Configurator template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager. Below you can see the tabs for Repository View Definition and Property View Definition:
Purpose: The primary purpose of The Repository Desktop template is to design toolbars in QLM.
Core concerns: The Repository Desktop enables you to use Button Panels and Icons to design additional toolbars that can be added to the desired diagram template types in the actions tab in QLM. The toolbars can, when assigned to a template type, be used to analyze the data shown in diagrams.
Below, you can see some examples of different toolbars:
The repository has several toolbars available when installed that you, through the repository template can assign to the desired template types.
Other functionalities: The Repository Desktop template can also be used as an overview page that links out to other diagrams relevant for certain stakeholders. Below, you can see an example of a strategy desktop where each icon links to the model illustrated:
Relation to other templates: The Repository Desktop is, like the Matrix template, an auxiliary diagram. As such it is not directly connected to other templates but can be used to enable certain analytical functions in all types of diagrams.
Properties and metadata: The Repository Desktop template can, for example, retain the following information:
The above picture shows the properties dialogue window for the Repository Desktop template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
Purpose: The purpose of the Configuration Diagram template is to document a well-defined combination of documents and files to enable an explorer functionality.
Core concerns: The Configuration Diagram template enables you to model Document Categories, External Documents, and Document Revisions (which store references to files containing a revision of an External Document).
The Configuration Diagram should be used to link external documents like CAD-files, word processor documents, spreadsheets etc. including the applications that must be used to view or modify the documents, to the repository.
Other functionalities: Controlling paper documents and their distribution is also possible with this diagram type.
The diagram contains embedded revision control of the external documents. This functionality is based on the following placement of the repository related documents:
Directory structure example:
c:\qwc\
. db\…
. demos\…
. guides\…
. models\…
. Projects\
. . repdb1\…
. . repdb2\…
. . …
. . repdbx\
. . . in\…
. . . out\…
. . . Docs\< here are all related documents placed >
Relation to other templates: The Configuration Diagram can be contained in a Workflow Diagram, be linked as ‘Relevant Documentation’ for a Project Activity and be a decomposition of a Business Scope.
Properties and metadata: The Configuration Diagram template can for example retain the following information:
The above picture shows the properties dialogue window for the Configuration Diagram template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.
Purpose: The purpose of the Browser Diagram template is to build a structure for reports in QualiWare.
Core concerns: The Browser Diagram template allows you to build a graphical representation of a reports structure, from which it will then generate a code for the system to execute. The symbols available in the Browser Diagram template are: Browser Filter, Browser Action, Browser All and Browser Source. They can be connected by Browser Relation, Browser Back Relations and Browser Graphic Relations.
Several Browser Diagrams are included in the installation of QualiWare. Below, you can see an example of a Browser Diagram for a Business Process Network:
The Following is a Browser Diagram for Audit Planning:
Relation to other templates: The Browser Diagram template is used for QualiWare platform customization and is as such related to templates such as the Generic Query, Query Design.
Properties and metadata: The Browser Diagram template can for example retain the following information:
The above picture shows the properties dialogue window for the Browser Diagram template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.