Producer: QualiWare Developers

HTML Dialog Layout

Purpose: The purpose of the HTML Dialog Layout template is to enable the organization to tailor the objects Dialog Layout on the collaboration platform.

Core concerns: The HTML Dialog Layout template enables you to model HTML Dialog Layout, HTML Dialog Fields, HTML Dialog Groups and HTML Dialog Text. Using these elements, you can design the content of your dialogs. Below you can see an example of a Dialog Layout for a Business Process Network:

Relation to other templates: The HTML Dialog Layout template is, like the other HTML templates, a tool for creating a fully tailored collaboration platform that meet the needs of the specific organization. As such it is related to HTML Mega Menu, Generic Query and Query Design.

Properties and metadata: The HTML Dialog Layout template can for example retain the following information:

  • A description
  • Audits (auto generated information regarding its current state)
  • Access rights (such as linking to roles with read/write rights)
  • Layout (such as dialog title and colors)
  • Sub-dialogs (shown as additional tabs in the dialog)

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

The access tab is used to specify which dialog description to use for any situation.

  • Roles with Read-Write: Role is used in the calculations of which HTMLDialogLayout is used when user triggers an action requiring a webform.
  • Customizations: Customization is used in the calculations of which HTMLDialogLayout is used when user triggers an action requiring a webform.

It is possible to set up multiple customization if needed.

From QualiWare 10.5 it is possible to have two versions of a form to edit objects from the web, a Simple and an Advanced form. If you specify the simple form, the advanced form will automatically be generated. The “advanced” form that has the full metamodel for our object (all tabs and all attributes). (see more details in the release note for QualiWare 10.5).

Query Design

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:

  • A description
  • Audits (auto generated information regarding its current state and access rights)
  • Query filter (with wizard for filter options)

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.

User Role Configurator

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:

  • A description of the User Role
  • Audits (auto generated information regarding its current state and access rights)
  • Repository View Definition, detailing the standard views the User Role should make available
  • Property View Definition, detailing which relations should be visible

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:

Repository Desktop

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:

RepositoryDesktop_2

RepositoryDesktop_1

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:

  • A description of the template
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

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.

Generic Query

Purpose: The Purpose of the Generic Query template is to provide datasets for QualiWare System templates.

Core concerns: The Generic Query template is an auxiliary template. The Generic Query can be created using a Query Design template which enables you to easily structure the query for creating reports. When creating a Report for a diagram, the Generic Query created using the Query Design should be used as a Data Set in the Report Definition.

A Generic Query can also be generated using its Property Dialog, where you can link to Data Source and filter the data selection using a wizard – see example of the property dialog below:

The Generic Query can, for example, take the form of data sheets:

GenericQuery_2

The Generic Query template can also execute a command using the Advanced Query tab:

Relation to other templates: Generic Queries are automatically created when creating a Query Design. Generic Queries are used in the following templates: HTML Template Definitions, HTML Embedded content, HTML Publisher and HTML Content tab.

Properties and Metadata: The Generic Query can for example rentain the following information:

  • A description
  • Audits (auto generated information regarding its current state and access rights)
  • Query Filter, including a wizard for filter options
  • Attribute Definition
  • Advanced Query
  • Matrix Behavior

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

 

 

Dashboard

Purpose: The purpose of the Dashboard template is to publish selections of Business Charts targeting different stakeholders. It should be used to gather a series of relevant or connected Business Charts to provide a dashboard-like overview.

Core concerns: The Dashboard template enables you to gather Business Charts, Key Performance Indicators, Performance Indicators and General Concepts to create stakeholder specific views of analyzed data. For example, an Enterprise Architect could find a Dashboard containing Business Charts relevant to the usage and governance of the Enterprise Architecture useful.

Below, you can see examples of different Dashboards presenting an array of Business Charts:

Dashboard_1

 

Dashboard_2

Relation to other templates: The Dashboard template is closely connected to the Business Chart template, as the Dashboard publishes the charts the Business Chart template generates.

Properties and metadata: The Dashboard can for example retain the following information:

  • A description of the Dashboard
  • Link to the owner of the Dashboard
  • Link to the one responsible for the Dashboard
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

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

Configuration Diagram

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:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

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.

 

Browser Diagram

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:

BrowserDiagram_1

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:

  • A description of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

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.