This documentation supports the 20.02 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

Modifying CMDB classes and synchronizing the data with ITSM applications

When the data model in CMDB is modified, the administrator of the Remedy ITSM suite applications that consume CMDB data, must update the application with the changes in the CMDB data model.

The data model might be modified by creating a new class or an attribute to suit the business needs. These changes are updated in the Remedy ITSM suite application by using Sync Asset UI with CMDB.

Overview of CMDB classes and Remedy ITSM suite application forms

When a new class is created in CMDB, the form layout of the superclass is inherited by the new class. The forms for the CDM classes use panel fields and custom tabs to organize all the attributes, instead of placing all the attributes in the same column or tab. For example, a custom class CBR.CSTM:SubAccount is created under BMC_Account class. By default, the new class uses the form layout of the BMC_Account class. The layout for the new class is modified, as required. The following image shows the new class that uses the form layout of the superclass:

For CMDB forms and extensions, a built-in algorithm in the CMDB organizes the attributes and provides a default layout.

For Remedy ITSM suite applications, the algorithm in SyncUI utility defines the default layout for the application forms.
For example, Asset Management has its own form for a Computer System class. The SyncUI utility updates the Asset Management form to reflect any changes made to the CMDB BMC_ComputerSystem class.

When a custom tab runs out of space to hold more attributes, CMDB and the utility create additional custom tabs as per the algorithm.

For CMDB forms, the maximum number of custom tabs is 20, and the custom tab is visible by default when you add a new attribute.

For Asset Management forms, the maximum number of custom tabs is 50, and the custom tab is hidden. If you change the visibility, the visibility rules are reset to default in the next data model change.

Modification of the form layout

When a Configuration Manager creates a new class or an attribute in the data model, the attribute is added to the custom tab in the Remedy AR System form. 
Attributes represented by Remedy AR System core fields are placed in a single column at the top of the view, and attributes that you create are placed in the panel fields below the single column.

When you modify the view of a form, the new view becomes the default view for the subclasses.


Do not modify the ObjectStoreView view (ID 399999100) of the class form for any class in the BMC.CORE or BMC.CORE.CONFIG namespaces. Your changes could be overwritten by future releases of patches to the BMC CMDB. Instead, copy ObjectStoreView to a new view for that form and modify the new view. There is no risk when you modify the ObjectStoreView view of class forms in other namespaces.

When you create a new attribute for a class, it is added to the Remedy AR System's view as a field by using the following algorithm:

  1. The attribute or a field is placed in the panel field or custom tab named Custom0, immediately following the last existing field on the page.
    If this panel field does not exist, it is created on the page holder field that has field ID 300025400. If no page holder field with this ID exists, the panel field cannot be created.
  2. If there is no space on the Custom0 page for the new field, a Custom1 page is created and the field is placed at the top.
    This automatic creation of panel fields can continue up to a maximum of 50 panel fields or custom tabs.
  3. If 50 panel fields are full and a page holder with field ID 300025400 does not exist, fields are stacked in the upper left corner of the view.
    Stacked fields might be obscured by each other.

Panel fields created by this process are placed in the upper left corner of the view and are hidden, by default. To enable users to see the new attributes, move the attributes out of the panel fields or make the hidden fields visible. If you want to re-arrange the attributes and modify the form view, you must access the Developer Studio, and make the changes in the base-development mode.

For information about modifying the form views in Developer Studio, see  Defining and managing form views Open link .

If you create a new class that has no superclass, the form is arranged according to the default view template. The following image shows the default view template for new base classes:

To update the AST forms with data model changes

  1. Log in to the server where BMC CMDB and Remedy ITSM suite are installed.
  2. Open the AR System Administration Console.
  3. Select Administration Console > Application Administration Console.
  4. Click Custom Configuration.
  5. From Application Settings, select Asset Management.
  6. From Advanced options select Sync Asset UI with CMDB, and then click Open.
    The SHR:SchemaNames form opens in Search mode.
  7. In Schema Name, enter the form name which you want to update and click Search.
    For example, if the BMC_ComputerSytem class is modified and you want to update the Computer System form in Asset Management, you must enter AST:ComputerSystem.
  8. Select the required form, and click Update Asset UI to save the changes.

    CMDB generates a new version of the form that you selected.

To configure form generation for another application

If you have developed an application that uses its own forms as an interface for BMC CMDB data, BMC CMDB can update those forms with any changes made to the data model. CMDB updates the custom application by generating a new form for every modified class. You must set the configurations in the form generation utility in advance to specify how you want the forms to be created. After modifying the data model, launch the form generation utility as described in the following steps:

  1. Open Remedy Developer Studio and create a companion form for each class that is modified in the data model.
    The form must have the following character fields with a maximum input length of 80 characters:

    Class Keyword

    The class ID of the class for which a form is generated. The class ID is case sensitive, and might not be the same as the class name. For example, the class with a name of BMC_ComputerSystem has a class ID of BMC_COMPUTERSYSTEM. For more information about the class ID of a specific class, see BMC CMDB Data Model Help inPDFs and videos.

    Form NameThe name of the companion form that your application uses for the class. If this form exists, it is modified. If not, a new form is created.
    Primary Join FormIf you specify a form name here, the form generated is a join of this form as the primary join form and the CMDB form as the secondary join form. This field is an optional field and must be blank if a secondary join form is specified.
    Secondary Join Form

    If you specify a form name here, the form generated is a join of the CMDB form as the primary join form and this form as the secondary join form. This field is an optional field and must be blank if a primary join form is specified.


    If you do not specify a primary join form or secondary join form, the form generated is a self-join of the CMDB form as both the primary and secondary join forms. Unless you have other data you want to display with CMDB data, leave the Primary Join Form and Secondary Join Form fields blank.

  2. Open an Application Pending form. 
    On a new tab in the browser, enter the URL with the form name: http://<arServer>:<port>/arsys/forms/<arServer>/<FormName>
    For example, http://lon-vm-abc:1010/arsys/forms/lon-vm-abc/Application Pending
  3. In the Application Pending form, enter the following information:
    • CategoryCMDB
    • CommandSync-UI
    • Other Short

      -f -g -c -C -R -p -s -D

      -f<configFormName>The companion Form Name that was created.
      -g <formNameFieldID>The field ID of the Form Name field.
      -c <classKeywordFieldID>The field ID of the Class Keyword field.

      The class ID of the class for which a form is generated. You must provide either this parameter or -t, but not both.

      Important: Class ID is case-sensitive.

      -t<timeStamp>A UNIX epoch time value. Forms are generated only for classes modified after this time and all of their subclasses. You must provide either this parameter or -C, but not both.
      -R(Optional) Specifies that forms are also generated for all subclasses of the class specified with -C.
      -p <primaryJoinFormNameFieldID>(Optional) The field ID of the Primary Join Form field on the form. If you populated the Primary Join Form field, you must specify this parameter.
      -s <secondaryJoinFormNameFieldID>(Optional) The field ID of the Secondary Join Form field on the form. If you populated the Secondary Join Form field, you must specify this parameter.
      -D(Optional) Enables debugging for this operation. Debugging increases the details that are written to the log file.

      If you have started any synchronization process with the changes made to the data model, wait till the synchronization process is complete. If any classes do not complete synchronization, the form generation utility stops with an error.

The CMDBSynchronizeUI.log file is generated in ARSystem/ARServer/db folder. View the log file to track the status of the synchronization. 

The CMDBSynchronizeUI.log file saves the following information:

  • Errors and Warnings for Active Link, Filter, Escalation associations and missing Attributes or Classes.
  • If the line Synchronization completion status is missing from the last line of the log, then the synchronization has not yet completed.


You can use a workflow to create the Application Pending entries, but make sure there are no classes with errors.

Was this page helpful? Yes No Submitting... Thank you