Qualification conventions for reconciliation activities
When building qualifications, the easiest way is to select the fields, keywords, and values from the Qualification Builder.
For more information about keyword definitions, relational operators, and advanced search bar conventions, see
Building qualifications and expressions
.
Note
The qualification sets always apply to source dataset(s) only and never to a destination/master dataset. For example, It is not possible to limit the number of CIs for match from the master dataset in identification activity.
You can also create the qualification manually. If you select this option, observe the following conventions.
- The dollar sign ($) indicates the value of the attribute of a CI.
- The single quotation mark (') indicates the column or the actual attribute name.
- 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 ofBMC_ComputerSystem
where theVirtualSystemType
attribute has a value of VMWare. - For currency fields, you must 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
- The name or ID of the currency field.
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.
It is recommended to use $attribute_name$ when the Verify in Target Dataset option is NOT used. It is an in-memory operation and provides quicker response.
The ‘atribute_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 database. Using $attribute_name$ here will be a time consuming operation
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>"
Where
<CLASSNAME>
is the class to which you want to restrict the reconciliation activity to.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"
Comments
Please can you elaborate on differences when using Attribute Name and Attribute Value?
eg.
'VirtualSystemType' = "VMWare"
vs.
$VirtualSystemType$ = "VMWare"
Note this has been already requested in the 8.1 document section, review comments on
https://docs.bmc.com/docs/display/public/ac81/Qualification+conventions+for+reconciliation+activities
Hi Andreas,
Thank you for your patience.
I have included the relevant information in the topic.
Hope this helps.
Regards,
Amol
Hi Amol,
thanks for the update and clarification.
I assume you meant the "Verify in Target DataSET" option correct?
Br,
Andreas
Hi Andreas,
That is correct. It is Verify in Target Dataset.
Sorry about the typo.
Thanks,
Amol