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:

Clustering

Clustering provides users with a new way of interacting with content in their repository. It provides an enhanced analysis capability directly from the 3D Visualizer by logically grouping objects based on their relationships, concepts, and definitions. Filters can be applied to the clusters through the table-based view using existing functionality to focus analysis efforts (for example only clustering objects that are related to a risk with a high impact). The number of clusters can also be defined by the user to provide a broader or more concise result.

API Architecture Metamodel

An Application Programming Interface (API) is a construct that enables communication between systems. Integration between systems in complex environments continues to be a business priority to support automation activities. An API can be purpose-built for a bespoke integration (typical of legacy systems), or alternatively a standard connector can be developed between industry standard systems such as ERP’s and Service Management platforms. Managing these integrations becomes a complex operational task as updates and new releases to the integrated systems (and enabling technologies), can lead to intensive release management and testing activities. Security is also of utmost concern when managing integrations as the API provides a potential entry-point from either system integration direction – the API has become a preferred target for malicious attacks on systems and networks.

Model Gallery

QualiWare 10.8 introduces a new Model Gallery feature. The model gallery is a visualization that enables a group of processes, integrations, or applications to be decomposed or expanded into a single canvas or gallery of models. The gallery view allows a focused view of multiple models without having to open separate tabs or windows.

Related Posts

Clustering

API Architecture Metamodel

Model Gallery

Leave a Comment Cancel reply