This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Configuring Version Rollup normalization rules

Use Version Rollup rules to define a value to assign to the MarketVersion attribute and a qualification to select the instances that are assigned the new value. The purpose is to normalize multiple VersionNumber strings to a particular MarketVersion value.

By default, the Version Rollup feature is enabled for datasets and all active Version Rollup rules are checked. You cannot disable the Version Rollup feature, and you cannot select particular rules to apply to individual datasets.

Also by default, the MarketVersion value in the Version Rollup rules takes precedence over a Product Catalog entry. You can change this configuration, as explained in Priority of Version Rollup rules and Product Catalog entries.

The Normalization Engine includes Version Rollup rules for a number of products from manufacturers such as Microsoft Corporation, Oracle Corporation, and Adobe Systems. You must create rules for other products.

When you create new rules for the products, you can check if the Version Rollup rules already exist for a product or a manufacturer using the search field available on the Version Rollup tab.


  • Although you can edit or delete the Version Rollup rules that are shipped with the product, BMC recommends that you do not edit or delete these rules.
  • Instead of editing a rule, create a new rule and copy the desired qualification and other values to it. You can then modify this new rule.
  • BMC recommends that the Version Rollup rule should be based on Normalized product names.
  • When you search for existing version Rollup rules, the search results depend on the case sensitivity of the underlying database. For example, for a case sensitive database, if you enter a search string as "adobe", it treats "adobe" and "Adobe" differently. Hence, the search result does not list the rules for "Adobe". However, if the underlying database is case insensitive the search string "adobe" lists the rules for "adobe" as well as "Adobe".

Version Rollup rules apply to CIs in the BMC_Product class. You can add more classes, as explained in Adding CMDB classes to Version Rollup normalization.

If the Normalization Engine does not find a specific rule for a product, and if the CI does not have a value for MarketVersion, the Normalization Engine uses a default rule to set MarketVersion to the VersionNumber value. If the CI does have a value for MarketVersion, then the Normalization Engine retains this value.

For more information about the Version Normalization feature, see Normalization and software license management.


  • You can use manufacturer aliases to reduce the number of Version Rollup rules needed to match the ManufacturerName attribute within a CI. This is because the Normalization Engine uses manufacturer aliases to look up matching Version Rollup rules, as explained in Normalization process.

To create a Version Rollup normalization rule

  1. In the Normalization console, click Normalization Features.
  2. On the Version Rollup tab, in the Search by Manufacturer Name/Product Name field enter the Manufacturer Name or Product Name for which you want to create or edit a Version Rollup rule.
    This field allows you to search for existing Version Rollup Normalization rules for that Manufacturer or Product. You can use % for wildcard search.
  3. Click the Create New Rule icon to create a new rule.
  4. In the New Rule for Version Rollup dialog box, configure the following parameters.
    • Active — Select Yes to activate the rule so that the Normalization Engine applies the rule on datasets.
    • Rule Name — Define a descriptive name for the rule.
    • Class Name — Select the name of the class for which the qualification returns instances.
    • Precedence — Enter a value to determine the rule's execution order. The value can be 0 to 9999999, inclusive, with higher numbers determining a higher priority. If more than one rule applies to an instance, the Normalization Engine applies the rules sequentially from the highest precedence value to the lowest, until a match is found.
    • Qualifier — Type the qualification or click

      Use BMC Remedy AR System qualifications to define the CIs or relationships to which the custom rule applies. For information about using the Qualification Builder, see Building a qualification for a reconciliation activity.

      The qualification can also be written using an alias name instead of using the manufacturer or product name.
    • Manufacturer Name — Specify a string to apply to the ManufacturerName attribute.

      If you are using manufacturer aliases, make sure that the value in this field is the same as the value in the ActualName field in the Normalization Alias form. The value in the ActualName field should in turn match the Manufacturer Name field in the corresponding Product Catalog entry.
    • Product Name — Specify a string to apply to the Model attribute.
    • Market Version — Specify a value to apply to the MarketVersion attribute of the instances that match your qualification. You can specify either an exact value, such as 2003, or an expression that generates the MarketVersion value. If you are are specifying plain text with special characters, you must put the text in double quotes.

      The following are examples of expressions that you can specify in the Market Version field:

      MAJOR($VersionNumber$) — This expression extracts the major version from the VersionNumber attribute of the qualified instances and applies that value to the MarketVersion attribute. For example, if the VersionNumber attribute value is 11.5 or 11.7, this expression populates 11 as the value of the MarketVersion attribute.

      MAJORMINOR($VersionNumber$) — This expression extracts the major and minor version numbers from the VersionNumber attribute. For example, if VersionNumber contains 5.1.2, this expression populates 5.1 as the value of the MarketVersion attribute.

      $VersionNumber$ — This expression applies the VersionNumber attribute value of the qualified instances to the MarketVersion attribute. For example, if the VersionNumber attribute value is 10.20.01, this expression populates 10.20.01 as the value of the MarketVersion attribute.
  5. Click OK.
Was this page helpful? Yes No Submitting... Thank you


  1. Brian Gillock

    Is it possible to get a link to a comprehensive list of functions available for expressions; e.g. MAJOR, MAJORMINOR? Thanks!

    Aug 06, 2019 05:02
    1. Maithili Deshpande

      Hi Brian, 

      Thank you for you comment. Please refer to Building an attribute expression for relationship and custom normalization rules topic for Attribute Expression Builder functions.

      Please let me know if this does not help. 




      Aug 27, 2019 07:18