How the Category, Type, and Item attributes extend the data model
To further categorize a configuration item (CI) class that has the specific attributes that you need, consider using the existing
Item attributes instead of creating attributes or subclasses. These attributes are part of the
BMC_BaseElement class and are thus inherited by all other CI classes. You can use them to provide levels of categorization for instances of a class without the performance cost of a subclass.
For example, the class
BMC_PointingDevice does not distinguish between a wired mouse and a wireless mouse. To make this distinction in your data, you do not need to create subclasses called
YourModel_WirelessPointingDevice. Just populate the Item attribute with
Wireless when creating instances of
Because this categorization strategy uses a single class, the different categories, types, and items cannot have relationships to different classes. To have different relationships for each
Item, create subclasses for them instead of using this strategy.