QLM Users

HTML Content Blog

The HTMLContentBlog is used to retrieve information about objects related to the current object that is being viewed by the user. The main difference between HTMLContentBlog and other types of presentation is that HTMLContentBlog displays the information in a blog format.

Relation Type: The relation type defines what relation the content blog’s entries should have to the main object.

Options are LinkedBy, Links or Contains.

Attribute: The attribute defines what attribute used to get the relation to the main object.

E.g. for a list of ChangeRequests the relation type would be LinkedBy and the attribute would be Concerns. This will give a list of every linked by object that has the main object at the Concerns attribute.

Filter: Use the filter to provide a list of templates that you want to filter.

Function: Use this to provide a JavaScript function to execute.

Sort Order: Sort Order defines the attributes used to sort the list.

Descending: “true” or “false”. True for descending and false for ascending sort order.

 

Furthermore, the HTMLContentBlog takes a list of parameters for configuring the presentation.

DisableLink: “true” or “false”. This removes the hyperlink in the object title.
TemplateIcon: “true” or “false”. This displays a small template icon next to the object title.
HeaderAttribute: The attribute that should be displayed in the blog header.
HeaderCaption: The string that will be displayed in the caption header.

It is possible to include Audit information in the string by placing the audit keywords in curly brackets.
E.g. “Created {AuditCD} by {AuditCN}”

The complete list of audit keywords: Name, AuditCN, AuditCD, Audit´MN, AuditMD, AuditAR, AuditCG, AuditEN, AuditGC, AuditGS, AuditGD, AuditGA, Name, ObjID, Revision, Template

ShowResponsible: True / false
ResponsiblePrompt: The prompt that will be displayed in the responsible label.
ResponsibleAttribute: The attribute that should be displayed as being the responsible.
ShowUniqueId: true / false (This will display the sequence number.)
UniqueIdAttribute: The attribute that should be displayed as unique id.
ShowStatus: “true” or “false”. This will display the status of the object.
StatusPrompt: The string that will be displayed in the status label.
StatusAttribute: The attribute that should be displayed as the status.
ContentPrompt: The string that will be displayed in the content label.
ContentAttribute: The attribute that should be displayed as content.
ShowProgress: “true” or “false”. This will enable both progressbar and progress header.
ShowProgressBar: “true” or “false”. This will display the progress bar.
ProgressHeaderLabel: The string that should be displayed as progress header.
ProgressOpenPrompt: The string that should be displayed under progress header in red, indicating open state.
ProgressClosedPrompt: The string that should be displayed under progress header in red, indicating closed state.
ProgressClosedAttribute: The string value of the attribute defined in the StatusAttribute-parameter that should be counted as closed. In this case “Closed” for a changerequest.
MaxWidth: The max width of the content blogs.

Below in an example of how it looks on the web frontend.

History State

Description of this template will be available soon.

Help Item

Description of this template will be available soon.

Health Check

Description of this template will be available soon.

Guide

A “guide” refers to a set of instructions or procedures that are used to carry out a specific business process.

For example a restaurant using a recipe to prepare a dish (the business object) as part of their food preparation process (the business process). The recipe serves as a guide for the chefs to follow, ensuring that the dish is prepared consistently and to the desired quality every time it is ordered by a customer.

The “guide” connection links a business object to instructions or procedures that guide the execution of a business process, the “resource” connection links a business object to the specific resources needed to carry out that process.

Grouping : ArchiMate

The grouping element aggregates or composes concepts that belong together based on some common characteristic.

The grouping element is used to aggregate or compose an arbitrary group of concepts, which can be elements and/or relationships of the same or of different types. An aggregation or composition relationship is used to link the grouping element to the grouped concepts. Grouping elements can also have other relationships to and from them.

Group

In a business process diagram, the symbol “Group” is used to represent a grouping of related activities. It is a visual element that can be used to organize a process into smaller components or subprocesses, each with its own set of activities and decisions.

The Group symbol is typically used to improve the readability of a complex process diagram by breaking it down into smaller, more manageable pieces. It can also be used to visually differentiate different parts of the process or to indicate areas of responsibility.

Governance Conditional Message

A GovernanceConditionalMessage is used in a GovernanceWorkflow when you want to do a GovernanceTransition based on some event condition (GovernanceBoolList/Method).

Short description: Here you give a short description of the GovernanceConditionalMessage. This should be able to give the user an overview of the feature.

Level: Level is used to indicate the context where the conditional message is evaluated and executed:

  • Object: Context is object level, i.e. the conditional message should run for each object.
  • State: Context is the state of the object. A manager might want to be notified about all objects in a specific state.
  • Workflow: Context is the entire GovernanceWorkflow. A manager might want a weekly update about their governance tasks related to the GovernanceWorkflow.
  • Global

Event Condition: A condition for if the action(s) should run or not. The condition should return true or false with true meaning the action(s) will run.

Event Renew: This defines how often the GovernanceConditionalMessage should be repeated. The time is defined in minutes.

If Event Renew is set to 0, the GovernanceConditionalMessage will be run once the condition is met. It will be run when EventTracker is set to run.
Otherwise the Event Renew is the number of minutes from the first time the condition is met and the action(s) are executed to the next time the action(s) should be executed according to the setting for EventTracker specified on the HTMLPublisher.

E.g. EventTracker runs daily at 1am and registers that condition is met = the action will be run. If Event Renew is then set to 1440 minutes, the action will run once a day, when the EventTracker is set to run, until the condition is no longer true.

Configuration Filter: When does the condition apply – all configurations (none), base configuration, private workspace(s) or a named configuration

  • None – The configuration will not be considered when evaluating the condition and executing the action(s).
  • Base – Only the base configuration will be considered for evaluating the condition and executing the action(s).
  • PWS – All private workspaces will be considered for evaluating the condition and executing the action(s).
  • Named – Only the named configuration will be considered for evaluating the condition and executing the action(s).

Rule to define Duration: An object is moved from GovernanceState to GovernanceState using different kinds of transitions, e.g. a GovernanceConditionalMessage. When a transition moves an object in to a GovernanceState the object will get a date set that is the limit for how long the object is allowed to be in the GovernanceState. The limit is calculated based on what the duration is set to in the transition leading in to the GovernanceState.

The date limit can be used to handle SLAs on objects. E.g. an email can be send out to the responsible of the object when the SLA is approaching or is already passed.

  • Number of days:
    • Set a specific number of days for the duration. This will be used for all objects handled by this transition.
  • Use the following Attribute
    • Use an attribute on the object to set a specific number of days for the duration. Use this to have different durations for different objects.
    • The attribute on the object will have to contain a number that can be translated into an integer.
  • Use a date attribute
    • Use a date attribute on the object to set a specific date for when the object should no longer be in the next GovernanceState. Use this to have different dates defined for different objects.
    • The date attribute will have to be in a date format.

The number of days defined in this field decides the number of days you have to finish the next state. If you have an SLA it will influence the days to finish like this:

  1. If your days from “Beginning In State” is 5 (this is set on the GovernanceWorkFlow’s attribute “Initial State Duration”), and if your SLA is a positive number 2. Then you will have 7 (5+2) days to finish the transition to next state, and the governance task will be green the first 5 days, then yellow for the next 2 days and then red until handled.
  2. If your days from “Beginning In State” is 5 and if your SLA is a negative number -2. Then you will have 5 days to finish the transition to next state, and the governance task will be green for 3 days, yellow for 2 days and then red until handled.

Action: The action(s) to be executed, if all conditions are met.

Asynchronously: If checked, the action(s) will run asynchronously.