Governance | QualiWare Center of Excellence

Governance Action Method

The GovernanceActionList or a single GovernanceActionMethod is used in relation to a GovernanceWorkflow and can be activated when doing a transition (GovernanceTransition/GovernanceConditionalMessage) either before (pre) or after (post).

It can also be activated when an event happens (GovernanceEventMessage).

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

Condition: Contains a GovernanceBoolList or GovernanceBoolMethod (the action will not run if it does not evaluate to true).

Verify: Verifies the Method. If the action is verified, today’s date, OK checkmark, and a “Method OK” will be filled out.

GovernanceActionMethod – Advanced

Is check method: Indicates if the action should check specified conditions on the object or if the action should be run on the object.

Method actual name: The name of the C# function to run. There is a set of predefined methods available.

A list of check methods is available, see section 10.2.2
A list of methods that are not check methods is available, see section 0

It is also possible to define a custom function.

You can click the icon to get some help to the selected Method.

Level: In case an error occurs during action execution, this is the error level to be used to inform the user.

If level is set to Error, the action will stop executing and all following actions (see GovernanceActionList) will not run. An error message is displayed to the user.
- Example: If the action is set to run as pre-action on a transition and the action fails, it will result in the transition not happening. The object will remain in the state it is already in.
If level is set to Warning, the action will stop executing. Any following actions will still run. A warning message is displayed to the user.
- Example: If the action is set to run as pre-action on a transition and the action fails, it will result in the following actions to be run. If these actions do not fail, the transition will be successful.

Parameter: Corresponding parameters – predefined for the current possible methods.

For most of the methods there are some parameters that can be set. Right click in the window and select: “Add Parameters…” to get the list of parameters.

The parameters are predefined for the GovernanceActionMethods in the standard GovernanceWorkFlow, but can be configured/customized.

For some methods Relations and Template filter and/or Attributes to be checked can be added as Parameters.

Predefined methods for when the action is not a check method

Each of the Predefined GovernanceCheckMethods – when the action is not a check method is explained in the following table. Where available the standard parameters are shown for each of the methods. Note that each of the Values needs to be specified, see below.

Method	Description
SetObjectAttributeList	Set one or more attributes on the object.
SetAttributeListByRelation	Set one or more attributes on objects related to the current object. E.g. content of a diagram.
Approve	This will approve the object. Parameters control if content of models should be approved along with the parent model. If content will be approved along with the parent, it is also possible to define if content controlled by GWE will follow the parent or follow its own GovernanceWorkFlow.
Promote	This will promote the object. Parameters control if content of models should be promoted along with the parent model. If content will be promoted along with the parent, it is also possible to define if content controlled by GWE will follow the parent or follow its own GovernanceWorkFlow.
CreateNewRevision	This will create a new revision of the object. Parameters control if object should be published.
FreezeObject	Freezes the object (it will be readonly). (No parameters to be set)
CreateAcknowledgeList	Creates an AcknowledgeList for the object. (No parameters to be set)
CreateLanguageVariants	Creates a LanguageVariant for the object. (No parameters to be set)
ApproveByRelation	Performs approve routine according to the relations
PromoteByRelation	Performs promote routine according to the relations
NewRevisionByRelation	Creates a new revision for all objects according to the relations
FreezeByRelation	Freeze all objects in accordance to the relations
AcknowledgeListByRelation	Create acknowledge list or all objects according to the relations
PublishContent	Publish current content.
PostByRelation	Post for all objects according to the relations.
EventActionByRelation	Send an Event Action for all objects following relation.
ResetCanApprove	Reset CanApprove for the current object. (No parameters to be set)
ResetCanApproveByRelation	Reset CanApprove for all objects following relation.
EmailAllParticipants	Send an email to all participants.
GlobalUpdateParticipantList	Update the participants list
GlobalAcknowledgeListChange	Execute a global acknowledge list change
GlobalCheckAcknowledgementSLA	Perform a SLA check on acknowledgement

Predefined methods for when the action is a check method

When the check box ‘Is check method’ is enabled the predefined methods for a check are shown. See in the image below.

Method	Description
CheckAttributeList	Performs a list of check in some attributes for the object.
CheckAttributeListByRelation	Performs a list of check in some attributes for all object following a relation for a specific template
CheckUnableToUpdateObject	Will give a message to the user, when the object cannot be updated (No parameters to be set)
CheckChangesOnAttrList	Returns error message if attribute is not changed with a change event.
CheckUnableToUpdateContent	Will give a message to the user, when some of the content on a diagram cannot be updated (No parameters to be set)
IsStateByRelation	Checks if object is in a target state and returns error if not. (TemplateFilter can be removed if not required.)
DoCompareDate	Returns an error message if the dates do not respect the condition.

Add attributes to be checked

Some of the Method have parameters that can be specified.

Right click in the window to “Add Parameters…”

Once a parameter is added, you can click on the three dots in the Value column to choose from the menu.

The value can be a custom input or one of the predefined. Generic Content gives the choice of checking if the attribute is empty or not empty. Object Attribute gives you a list of attributes on the chosen object. Governance Attributes are governance specific values. explained in the table below.

Note the list of available Governance Attributes depends on the method.

GovernanceAttribute	Description
GovernanceCurrentState	Check the current State-object that the object is in (returns the State object)
GovernanceStatus	Check the current status of the object (returns a string with the status)
GovernanceMessageComment	The message written when a user does the transition is returned
GovernanceNextApprover	Check the approver of the next governance state
GovernanceOnStatusSince	The date for when the object got into its current state (used for calculating how long it takes to changes states for analytics and governance history)
GovernanceDateLimitOnState	The limit on state is calculated from the set SLA and time limit set for each state
GovernanceCycleOwner	Checks the cycle owner of the object
GovernanceCycleCount	The cycle count of the governance flow
GovernanceRecyclingCount	The workflow can be setup to count the number of rewinds is being done (requires a configuration of the standard workflows)
GovernanceWarningDate	Checks the warning date
GovernanceLimitDate	Checks the limit date
GovernanceSLA	Checks the SLA value
GovernanceSignatureDone	Checks the number of signatures
GovernanceSignatureMissing	Checks the missing signatures
GovernanceSignal	Check the governance signal

Governance Action List

It can also be activated when an event happens (GovernanceEventMessage).

A GovernanceActionList can be composed of one or more GovernanceActionMethod(s) and NoticationTemplate(s).

Governance Workflow

Purpose: The purpose of the Governance Workflow template is to enable tailored governance solutions for the objects in your repository.

Core concerns: The Governance Workflow template enables you to model Governance Roles and Governance States. The Governance States are placed inside a Governance Role (just like a workflow diagram) and are connected by Governance Transitions, Governance Conditional Messages, and Governance Event Messages.

Below, you can see an example of a Governance Workflow:

The green arrows symbolize a Governance Transition towards the approval of an object while the red arrows symbolize a Governance Transition towards the development state of an object. The blue arrows are Governance Conditional Messages. While the broad, dark green arrows are the preferred Governance Transition, the lighter green colored arrows are alternate routes to the approved state.

Relation to other templates: The Governance Workflow template is a template that can be applied to any of the published objects or diagrams in the repository.

Properties and metadata: The Governance Workflow template can for example retain the following information:

A description of the workflow
Link to the owner of the Governance Master Role (the master role gives “governance-access” to all objects in scope for the governance flow)

Further details can be added under the different tabs such as email settings (needs to be set up i the QEF console in order to available)

Under “Detail” you select the templates that should be governed by the flow (highlighted below):

Once you have made any changes to a flow, you need to execute maintenance to make the changes take effect to existing objects in the repository, and update participants

Click the 3 buttons one at a time to synchronize

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:

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.

Matrix

Purpose: The Matrix template is used as an auxiliary diagram type for other diagrams. It can either show the properties or links of and between existing objects.

Concerns: There can be generated three types of Matrix diagrams: Link Matrices, Property Matrices and Text Matrices.

Link Matrices are typically used to summarize the links of two different template types. For example, a Link Matrix can be created using Business Process as the rows and Information Systems as the columns to quickly get an overview over which Information Systems are linked to which Business Processes under IT -Support.
Property Matrices can be used to summarize the contents of many objects, for example, of a single template type in a single diagram. For example, a Property Matrix can be created for Information Systems to obtain an overview over the details describing all the relevant Information Systems and identify any gaps in the information. You could also choose to filter the items in the template, so only the Information Systems used in a specified process are shown.
Text Matrices function as a regular spreadsheet. This type of matrix can for example be used to store data used for KPIs

Below is an example of a property matrix detailing the risks and control processes related to the process called ‘Inventory’:

Below is an example of a link matrix detailing the relation between three identified risks and several controls (from the diagram, you can see that only two of three risks are addressed by the control processes):

Relation to other templates: Where the Matrix can be used as a backend tool, Query Result Views (QRV’s) are created to give an overview of specific objects and their attributes on the collaboration platform.

Properties and metadata: The Matrix 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

In the picture below you can see the Matrix template’s properties dialogue window, where the properties can be viewed and edited:

You can also edit the properties of the Matrix in the properties dialogue window by changing the Matrix behavior, Row filter or Column filter.

Hierarchy View

Purpose: The purpose of the Hierarchy View template is to show the hierarchy of objects related to a chosen root object.

Core concerns: The root object in the hierarchy View can for example be a Capability or a Business Process. The view is not modeled as a diagram, but generated based on information specified in the template’s property dialog, making the scope of the view flexible. Below, you can see an examples of a Hierarchy View for the Capability “Market Objects”:

Relation to other templates: The Hierarchy View is not directly connected to any single template but is not unlike a Context View. The Hierarchy View is, compared to a Context View, usually filtered to only show certain types of relations amongst certain types of objects and not as a default connected to diagram templates:

Properties and metadata: The Hierarchy View template can for example retain the following information:

A description of the diagram
Link to the owner of the Hierarchy View
Link to the one responsible for the Hierarchy View
Audits (auto generated information regarding its current state and access rights)
Specifications (definition of root object and other inclusion criteria)
Adjust (specification of templates that should be removed from the view)
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 Hierarchy View template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

The HierachyView can be used in relation to the Standard Tree View in the HTMLPublisher, to establish a hierarchy for the network of process models in a repository.

Heatmap

Purpose: The purpose of the Heat Map template is to document a representation of values from other QualiWare templates in the form of a Heat Map.

Core concerns: The Heat Map template is created using the Risk Management and Application Portfolio Management toolbars in a diagrams action tab in QLM. It can afterwards be found under the Heat Map template in the repository explorer window.

The Heat Map template can, for example be used to document risks, identify the most pressing ones. Additionally, Heat Maps can be used to identify systems that don’t live up to business or technical criteria.

Below, you can see two examples of Heat Maps for risks. The first shows two risks and how they compare to each other with regards to significance and likelihood:

The second Heat Map shows four risks as well as their residual risks, and how they compare to each other regarding likelihood and significance:

Relation to other templates: The Heat Map can for example be generated from data gathered from a Business Process Network, Workflow Diagram, Business Process Diagram, Application Architecture Diagram or a Strategy Model.

Properties and metadata: The Heat Map template can for example retain the following information:

A description of the diagram
Link to the owner
Link to the responsible
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 model

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

To learn how to build Heat Maps in QualiWare click here

Graphical Matrix

Purpose: The purpose of the Graphical Matrix template is to compare the states or scores of objects, such as for example Capabilities or Information Systems.

Core concerns: The Graphical Matrix is generated based on information inserted into its property dialog where input, x-axis and y-axis are defined. Below, you can see an example of a Graphical Matrix for capabilities, scoring their quality and timeliness:

Relation to other templates: When scoring risks and visualizing residual risks, you can use a Heatmap.

Properties and metadata: The Graphical Matrix template can for example retain the following information:

A description
Link to the source of the input
Coordinate definitions of the Graphical Matrix
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects

The above picture shows the properties dialogue window for the Graphical Matrix, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager. Below, you can see the tab for Coordinate Definition:

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:

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.