Template Type: System template

Spreadsheet

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.

Repository Folder

Folders offer access to specific groupings of objects, making objects easily accessible to the relevant stakeholders. The template name for folders in QualiWare is “RepositoryFolder”.

RepositoryFolders can be created in QLM and in the Repository Explorer from the web:

On the RepositoryFolder tab you can add a short description and create a hierarchy by including additional repository folder(s) in the folder.

If “Folder is a root folder” is selected the folder becomes available in the folder selection in QLM.

On the Advanced tab you can specify which tag(s) should be included/excluded, and set additional search conditions:

On the Objects tab you can include all objects of one of more template(s) as well as include specific object(s):

On the Visibility tab you can specify who can access the repository folder from the web.

A repository folder can also be available from the web in the repository explorer.

The Repository Explorer is configured in the HTMLPublisher in QLM, where folders can be added:

Read more about folders and hashtags here

Report Definition

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.

  1. In the design phase it is necessary to structure the data for the report. This is done via SQL. To remove the need of learning SQL QualiWare has introduced a Query Designer that helps users build SQL scripts and tables automatically based on a graphical diagram.
  2. The queries are then used as input for the ReportDefinition where the individual attributes can be re-arranged graphically.
  3. When designing a Query that needs to read the attributes of objects that are referenced in a multi-link field it is necessary to create sub-queries and sub-reports. Sub-reports gather and organize the attributes for the underlying objects and then are themselves inserted into the main report, just like the other attributes.
  4. When the data has been defined, organized and arranged in the report it is necessary to apply advanced formatting to the report for aesthetic reasons.

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.

Notification Template

A notification template is used for sending standard emails and notifications on the QualiWare app. – and with GovernanceGetMethods the data can be dynamically taken from the relevant object.

Type: Check if the notification is an email of notification in mobile App

Priority: Priority set on the email

Condition: It is possible to add a condition (or a list of conditions) that needs to evaluate to true before the notification is send.

To: Who is the receiver of the notification – it can be a static written email or use a GovernanceGetMethod

Subject: What is the subject header of the email notification – GovernanceGetMethod can be used again to retrieve data dynamic from the object

Message: Text of the email notification– GovernanceGetMethod can be used again to retrieve data dynamic from the object

Signature: Signature on the email

Insert a Dynamic Value (governance get method) in the text

There is a whole set of Governance Get Methods included in the available standard governance workflows.

Right click to insert a governance get method in the text in an email field.

Once you have selected “Insert Dynamic Value” a list of GovernanceGetMetods come up, and you can select the method.

If you have expanded the text editor (F8), you can right-click and select “Insert Link” to choose the GovernanceGetMethod.

Notification Templates – Mail Setup

Mail Setup: You setup the mail in the QEF Admin Console and insert it into this field.

Email Domain Filter: If you want to filter which emails it is allowed to send to, select the Domains here.

Delivery Options:

  • “Do not wait to send (fast)”: which means that emails (notifications) will be sent immediately. If something goes wrong in sending the email, and you haven’t set up the QCL Engine service “EmailSender” in the HTMLPublisher, then the email will never be sent.
  • “Use ‘HTTP Sender Service’”: will only send emails if the EmailSender QCL service has been added to the HTMLPublisher.

 

News Item

The News Item template is used to post and share News on the collaboration platform.

When you create a NewsItem you can add a short description, a full description as well as information about when it should be released and archived.

The relevant news will be shown as standard on the News Tile on the Desktop.

A list of available News items can be found in the leftmenu.

Model Presentation

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:

  • Relevant for:
    • Here you map the model that is subject to the presentation
  • Content Selection:
    • Here you select the content of the presentation (All revisions, Revisions across configurations, All language variants, Custom selection, Walkthrough)

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.

Interest Group

InterestGroup is a template that can be used to collect a set of organizational objects into a group.

In the standard Metamodel you can include the following templates types into an interest group:

  • Person
  • OrganizationUnit
  • InterestGroup
  • Postion
  • Role

An InterestGroup can be used to in relation to other objects in the repository, in relations to GovernanceWorkFlows or AcknowledgeLists.

 

HTML Tile

The HTMLTile template is used on one or more HTMLDesktop(s) on the collaboration platform.

It is possible to configure the appearance and nature of the tile via the HTMLTile-template.

Among many things you can specify the title, color, size, description text, as well as link it to other content in the repository, e.g. a diagram or a HTMLQueryResultView.

Example of a tile on the web:

HTML Template Definition

The HTML template definition defines how and what information is displayed on the web for each template-type.

In QualiWare 10.8 a new Dashboard layout has been introduced. You can create one or multiple dashboard(s) for a diagram template-type. The dashboard(s) are associated on the Dashboard Tab:

The Dashboard are configured using the templates:

The “Left”, “Center” and “Right” tabs specifies the content on the classic diagram workspace, shown on the example below.

The left window (1) of a diagram workspace is configured on the Left tab, using HTMLContentBox and other HTML-templates:

The Center tabs (2) of a diagram workspace in configured on the Center tab, using HTMLContentTab and other HTML-templates :

It is also possible to insert analytic content (BusinessGauge) in the Center Top content.

Example of a BusinessProcessNetwork with Business Gauges displayed at the Top Center (as configured in the example above).

The right window (3) of a diagram workspace is configured on the Right tab, using HTMLContentBox and other HTML-templates :

On the Analytics tab, you can configure which “Social Behavior Warehouse” tabs should be available on the model.

The Behavior tab, specifies the behavior of a template, e.g. how should a link to an object of the template behave when clicked.

Target: This is how the link will open when clicked.

  • Self: This will open the object page in the same browser window.
  • New Window: This will open the object page in a new browser window or tab depending on the browser setup.
  • IFrame: This will open the object in an iFrame pop-up window using the Popup Settings configuration.
  • FancyBox: This will open the object in a Fancybox pop-up window using the Popup Settings configuration.

Title: This specifies what should be shown as the title of the object being shown.

  • Page header: The header of the page or popup window of the object. This can be static or dynamic text. Dynamic text is indicated by curly braces and will be evaluated client side in JavaScript.

Popup settings:

  • Width: The width of the popup window.
  • Height: The height of the popup window.
  • Popup content: A list of HTMLContentTables or HTMLContentTabs contains information about what is shown in the popup window. If nothing is specified here, the HTMLPublisher will use the information specified in the Center tab of the template definition.

JumpOnLink: JumpOnLink functionality can be used to forward the user if certain criteria are met. This is typically used when e.g. a BusinessProcess can be broken down in to subprocesses. It allows the user to jump directly to one of the subprocesses without having to open the properties of the BusinessProcess first.

  • Attribute(s): This is an attribute that is part of the object that this template definition is for. When the user clicks on the object, this attribute will be used to calculate where the user is taken to on click.
    • If the attribute contains exactly one link then the user will be taken to the target of that link when clicking the object.
    • If the attribute contains more than one link, then jumping is disabled.
    • If more than one jump attribute is defined, then the whole set of resulting links are evaluated. If only one link is available in the set, then jumping happens. If more than one link is available in the set, then jumping is disabled.
    • E.g. BusinessProcess can be set up to jump on BreaksDownTo. When the user clicks a BusinessProcess the user will be redirected to the link in the BreaksDownTo attribute (if only one link is available).
  • And attribute(s) is empty:
    • If the specified attribute is not empty the JumpOnLink functionality will be ignored. The attribute specified here should be different than the attribute for JumpOnLink.
    • E.g. BusinessProcess can be set up to jump on BreaksDownTo when ShortDescription is empty. If ShortDescription has content then the BusinessProcess will follow the behavior specified in Target settings.

Tooltip settings: The tooltip is used to display information about the object when a user hovers the object link.

Example of a BusinessProcessNetwork tooltip appearing when a BusinessProcessNetwork is hovered on the web.

  • Enable: Enable or disable the tooltip feature.
  • Title (attribute): The attribute that should displayed at the top of the tooltip.
  • Width: The width of the tooltip window.
  • Tooltip content: A list of attributes to be displayed in the tooltip window.

 

 

 

 

 

 

 

App settings:

  • App content: This specified what should be shown in the app. It links to a HTMLContentTable.
    • If nothing is specified for the template then the app will look for the settings for DefaultDiagram/DefaultObject template definitions and use those.
    • If nothing is specified on the template definition for the template or for DefaultDiagram/DefaultObject the all attributes are shown.

OnClick

  • Execute javascript: This can be used to execute a JavaScript function when the object is clicked.

On the Smart Capture tab, you can link Model Generator Settings to the template definition. The settings are used for the table to model feature in the web-modeler (introduced in QualiWare 10.8).

Table-to-model

  • Inherit default settings: Tick the box to inherit the settings from the Smart Capture Settings on the HTMLPublisher
  • Model generator settings: Insert specific HTMLModelGeneratorSettings to the template definition

Once you have made changes to the template, you should click “Apply” and “Publish” to implement the changes on the Web.

The HTMLTemplateDefinitions are included in the HTMLPublisher.