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

Dialog Layout

Purpose: The purpose of the Dialog Layout template is to provide a representation of a dialog design for the system developed in the Dialog Model.

Core concerns: The Dialog Layout template enables you to model Windows, Fields, Menu Layouts and General Concepts.

Relation to other templates: The Dialog Layout is a QualiWare system template and is related to the Dialog Model, Menu Layout, Report Layout and Help Model.

Properties and metadata: The Dialog Layout template ­­­­can for example retain the following information:

  • A description of the diagram
  • A link to Epilog and Prolog
  • 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 model and who has been involved in the approval of the layout

The above picture shows the properties dialogue window for the Dialog Layout template where you can view and edit the model’s properties in QualiWare Lifecycle Manager.

Dialog Model

Purpose: The purpose of the Dialog Model is to enable the creation of customized applications for your QualiWare solution that, for example, can generate codes for the Data Model Diagram.

Core concerns: The Dialog Model template enables you to model Dialog Layout, Menu Layout, Report Layout, Help Model and Application Specifiers. These elements can be associated through Connections.

Relation to other templates: The Dialog Model is a QualiWare system template and is related to the Dialog Layout, Menu Layout, Report Layout and Help Model.

Properties and metadata: The Dialog Model 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 model and who has been involved in the approval of it.

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

Help Model

Purpose: The purpose of the Help Model is to provide the structure of a help system for the system developed in the Dialog Model.

Core concerns: The Help Model template enables you to model Help Items and attach them to each other using connections.

Relation to other templates: The Help Model is a QualiWare system template and is related to the Dialog Model, Dialog Layout, Menu Layout and Report Layout.

Properties and metadata: The Help Model 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 model and who has been involved in the approval of it.

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

HTML Mega Menu

Purpose: The purpose of the HTML Mega Menu template is to enable the tailoring of the left menu on the collaboration platform.

Core concerns: The HTML Mega Menu template enables you to build the left menu using HTML Mega Menu Items, which can be layered. The example below shows how a menu looks in our modelling tool:

The screenshots below show how a menu can look on the collaboration platform and how the sub-menus are shown:

The left menu can be configured for differently for diffrent roles. The left menu can be modelled in 3 levels:

The HTMLMegaMenu is composed of HTML Mega Menu Items.

The Mega Menu is published to the Web via the HTML Publisher.

Relation to other templates: The HTML Mega Menu is related to the other HTML templates such as Generic Query, HTML Dialog Layout and Query Design.

 

Properties and metadata: The HTML Mega Menu template can for example retain the following information:

  • A description of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Menu settings
  • Text settings

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

Menu Layout

Purpose: The Purpose of the Menu Layout template is to provide the menu structure for the system developed in the Dialog Model.

Core concerns: The Menu Layout template enables you to model Menu Items which can be connected by containing each other – as is the case with the HTML Mega Menu template.

Relation to other templates: The Menu Layout is a QualiWare system template and is related to the Dialog Model, Dialog Layout, Report Layout and Help Model.

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

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

Query Design

Purpose: The purpose of the Query Design template is to enable easy design of Generic Queries.

Core concerns: The Query Design template enables you to model Object Queries and Relation Queries into Generic Queries. When creating a Query Design, a Generic Query will be generated automatically and appear graphically on the diagram as a white triangle in a green circle – see the model below:

Relation to other templates: The Query Design template is used to generate Generic Query templates which can be used in creating Report Definitions, Spreadsheets and HTMLQueryResultViews.

Properties and Metadata: The Query Design Template can for example rentain the following information:

  • A description
  • Audits (auto generated information regarding its current state and access rights)
  • Query filter (with wizard for filter options)

The above pictures show the properties dialogue window for the Query Design Template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager

You can see an example of a Query Design in the QualiTube sections, where there is a video on Composity Query Design.

Report Layout

Purpose: The purpose of the Report Layout is to provide the layout of a report for the system developed in the Dialog Model.

Core concerns: The Report Layout template enables you to model Report Pages and Report Fields which can be related by connections.

Relation to other templates: The Report Layout is a QualiWare system template and is related to the Dialog Model, Dialog Layout, Menu Layout and Help Model.

Properties and metadata: The Report Layout 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 Report Layout template

The above picture shows the properties dialogue window for the Report Layout template where you can view and edit its properties in QualiWare Lifecycle Manager.

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:

RepositoryDesktop_2

RepositoryDesktop_1

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.