Examples of Standard Definitions

Standard Valuemation already contains some data check definitions which can be put in direct use or used as examples for customer-specific customizations.

• System Type - Persons

  The definition checks if persons assigned to the examined system correspond to those defined for the system's system type (See 'Configuration Item Relation Definition' for more information on CIRD assignments.) This way it is possible to make sure that all mandatory persons are assigned and that no other persons than those defined by the object type are used assigned to the system. Note that this is the only way to check multiple mandatory referenced objects.

• System Type - Possible Component Classes

  On a system type it is possible to specify 'Possible Component Classes'. This defines the component classes of components which can be used with systems of this system type. Moreover, the used component classes can be specified as main, mandatory and it is also possible to define the minimal and maximal amount of components of this class in a system.
  The 'System Type - Possible Component Classes' definition checks if the examined system complies to these criteria defined for the system's system type.

• System Type - Usage Types

  Similar to the above, definition checks if the examined system complies to the 'Possible Usage Types' criteria defined for the system's system type.

• System Type - Main Component

  The definition checks if the examined system contains a main component according to its system type definition.

Example of a data check workflow

The following workflow is used by data check definition 'Validation rules' which checks All Valuemation validation rules defined for given object type.

Workflow name: DataCheck_BO_validationRules

Workflow Structure:

Workflow Script:

from vm.tools.datacheck import createDataCheckResult

from java.lang import String

#check BO - validation rules

#Check all VM Core validation rules defined for given object type.

#!Don't use in Save action on editor! Validation rules will be run automatically. "On Save" attribute should be "No Check".

#WF return transient BO "DataCheckResult" with indentification of BO, error text and howToFix text, level (warning/error)

listOfMessage = BO.validate()

if listOfMessage!=None and listOfMessage.size()>0:

arrayOfMessage = listOfMessage.toArray()

_output.put("dataCheckResult", createDataCheckResult(BO, "Error" , ", \n".join(arrayOfMessage), VM.localizeMessage("messages/Messages", \

".DataCheck_BO_ValidationRules.howToFix",None), None)