A good rule of thumb would be that if you need to add more than 5 attributes then use a regular class.
Categorisation subclasses don't have new regular forms created for them so the database impact is reduced. If, however, you need any of your new attributes to be required fields in a categorisation sub class then you'll need to give these a default value otherwise you won't be able to create new CI's in other sibling classes. There won't be any impact on new relationship classes but you might want to create these as categorisation subclasses (I don't know why BMC created the Component and Dependency classes as regular classes) -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Sathish Kumar Sent: 19 September 2013 17:50 To: arslist@ARSLIST.ORG Subject: A.CMDB 7.6.04 SP2 - Categorization vs Regular Class benefits Hello, We have few custom attributes were we need to create a custom class. But the question is which one to use regular or categorization? Can you please share your experience on how to decide on creating a regular vs categorization class. Any rules? Especially pros and cons of going for a regular class versus Categorization class from performance, extension of sub class, adding new relationship classes etc., -Sathish _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
