This documentation supports the 21.3 version of BMC Helix CMDB.To view an earlier version, select the version from the Product version menu.

Qualification conventions for reconciliation activities

The easiest way to build a qualification is to select the fields, keywords, and values from the Qualification Builder. 

Note

The qualification sets always apply to source datasets only and never to a destination or master dataset. For example, it is not possible to limit the number of CIs for a match from the master dataset in an identification activity.

Related topics

Creating-qualification-rules-for-reconciliation-activities

Using-the-Qualification-Builder

You can also create the qualification manually. If you select the manual option, observe the following conventions.

  • The dollar sign ($) indicates the value of the attribute of a CI.
    For example, $Instance_Id$ indicates the value, such as OI-126gft46828dhbcbs00c 
  • The single quotation mark (') indicates the column or the actual attribute name.
    For example, 'Instance_Id' indicates the label InstanceID.
  • Enclose nonnumeric values (including time, selection, and currency values) in double quotation marks. 
    Example: 'VirtualSystemType' = "VMWare"
    In the current (source) dataset, this qualification finds all instances of BMC_ComputerSystem where the VirtualSystemType attribute has a value of VMWare.
  • For currency fields, enclose one of the following items in single quotation marks:
    • The name or ID of the currency field. 
      Example: 'Currency Field' = $NULL$
    • The name of the currency field, followed by a period, followed by a specific portion of the currency field's value. 
      Example: 'Currency Field.VALUE' < 5000

  • Use keywords anywhere that you can enter character values. The most commonly used keywords are $DATE$, $NULL$, $TIME$, $TIMESTAMP$, $USER$, and $WEEKDAY$.

    Note

    Keywords are case sensitive. Use only UPPERCASE characters.

  • Use $AttributeName$ when the Verify in Target Dataset option is not used. It is an in-memory operation and provides quicker response because it checks for the value in the dataset and not in the database.
  • The ‘attribute_name’ is used in a purge activity when the Verify in Target Dataset option is used because the query needs to explicitly check the “values” in the database. Using $AttributeName$ here is a time consuming operation and is not recommended.

  • To restrict a reconciliation activity to a particular CI class, you must include the following qualification rules:

    Namespace

    Class

    Qualification

    If the class is a CI

    BMC.CORE

    BMC_BaseElement

    $ClassId$ = "<CLASSNAME>"

    If the class is a relationship

    BMC.CORE

    BMC_BaseRelationship

    $ClassId$   = "<CLASSNAME>"

    <CLASSNAME> is the class to which you want to restrict the reconciliation activity.

  • After creating a qualification for a field in a given class, the CIs are restricted within that class and all other classes are merged indiscriminately. For example, the following qualification restricts only CIs with the BMC_ComputerSystems class. All other classes are processed as a normal reconciliation job.

    Namespace

    Class

    Qualification

    BMC.CORE

    BMC_ComputerSystems

    $EnvironmentSpecification$ = "ASTAttribute"

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*