TechnicalDebt

The TechnicalDept template is used to document technical dept related to e.g. software development and IT-systems.

Technical debt refers to the long-term cost or extra work incurred when software development shortcuts are taken, prioritizing speed over code quality or maintainability.

Technical Dept is a part of the Application Management Desktop as part of the “Evaluate application portfolio”.

CustomerJourneyMap:EDGY

The Customer Journey Map in used to create a visual representation of the end-to-end journey that a customer experiences when interacting with a product(s) or service(s) of an enterprise. It
outlines the customer’s interactions across various touchpoints, channels, and stages, capturing their emotions, pain points, and expectations at each step.

Data Store Node

Represents persistent storage of data that can be read or written during the activity.

Service Function

The ServiceFunction is part of the DORA reporting (see DORA Desktop) used to describe the Service Functions as part of the reporting.

Business Entity

The Business Entity is part of the DORA reporting (see DORA Desktop) used to manage the different business entities part of the reporting.

HTML Feature

The HTMLFeature is used to configure different settings in the Web-front end.

The template can be used to pre-defined features (such as the Smart Importer or PowerPoint Generator) and other advanced customized features (JSScripts).

A subset of the Features can be configured.

The following (configurable) feature types are available:

In addition there is a Custom type that can be used to insert customised features.

Feature type – AskList (Create/Edit/View) (QualiWare 10.10)

There are 3 different types of AskLists features available, (used in the Getting Started Tile in the Desktop):

  • Create
  • Edit
  • View

All of them have the same configuration and behavior. When clicked on the web front end, an ask list will be shown

 

When a template is selected each of the types will have a different behavior:

  • Create will prompt a “Create New” dialog where the user can name the object

    • When create is clicked the new object will open in the Web-Modeler (if it is a diagram) or in the editable Web-Dialog.

 

  • Edit, will open the selected object in “edit-mode”, i.e. the Web-Modeler (if it is a diagram) or in the Web-Dialog.

 

  • View, will open the selected object in the Web Front End (as configured in the HTMLTemplateDefinition), e.g. the corresponding Dashboard associated to the selected diagram.

The content (List of templates) in the Ask List is defined by the referene parameter in the Feature, using a HTMLParameter object.

The Ask List will contain the templates listed in Value field, and contain the title as defined in the string.

Feature type – Hashtag

This type enables the hashtag feature in the ContextMenu in the Repository Explorer, to work with hashtags related to the object.

Feature type – WebForm

The WebForm is used to create new object, e.g. as a part of a ContextMenu in the Repository Explorer.

The example above creates a new object (ChangeRequest) and link it to the existing object with the link “Concern”.

The WebForm can also be used as a part of a HTMLContentBox in a HTMLDashboardItem on a Dashboard.

The HTMLContentBox contains a HTMLFeature (WebForm) and a link to a HTMLQueryResultView.

The content box shown on the web front-end as a part of a DashboardItem (example from the EDGY Enterprise Desktop).

Feature type – WebModeler

This type is used in the Repository Explorer in the ContextMenu to open the diagram in the webmodeler.

HTML Parameter

The HTMLParameter is used to specify parameters in relations to various HTML settings:

In the example below the style of the objects (in the underlying highlight query) is specified, a long with the opacity of the complentery object, i.e. the objects not included in the underlying query.

In the example below the style of the objects (in the underlying highlight query) is specified, a long with the legend and position of the legend. The parameter {} are refering to parameters in the underlying query.

The parameter shown above is related to the Multiple highlight functionality that was introduced in QualiWare 10.9.

In the example above “*” has been inserted as search criteria for the templates, it is possible to configure the template list by inserting Template names, seperated with ‘,’ to focus the search, e.g.

templates: ‘BusinessProcessNetwork,BusinessProcess,Activity,ExternalDocument,WorkflowDiagram’,
The parameter shown above is related to the QuickSearch Method that was introduced in QualiWare 10.10.
  • In relation HTMLFeature, e.g. when configuring the content of an AskLists, containing the available templates in an “Create”, “Edit” or “View” list as a part of the Getting Started tiles.