Classes on Catalog Item

[Community Alums]

Why do we have different classes (OOTB 14 classes)   on sc_cat_item. I can see it's not mandatory while creating a catalog item and it takes Catalog Item as the default one. I understand the difference of Record Producer & Order guide but not sure about rest all.

Hardware Catalog

Software Catalog

AWS Security Token Catalog Item

Catalog Item

Content Item

Order guide

Record Producer

Wizard Launcher

Cloud Provisioning Catalog Item

Cloud Management Provider Catalog Item

EC2 Catalog Item

EC2 Key Pair Catalog Item

Virtual Provisioning Catalog Item

Standard Change Template

[darius_koohmare]

Classes on catalog items are similar to 'task types' on Tasks, or 'Classes' in the CMDB.

Essentially they are all separate tables in the database, but are extended from the same root 'catalog item' table. (just like how incident, problem, change, etc. extends from task).

As a result, when you apply business logic or create a field at the catalog item level, it applies to all child tables (classes). In the same regard, this is why when you look at a catalog item list view, it will include child table table rolled up (e.g. record producers, standard change definitions, etc.)

Granular classes like above lets you edit a form or business logic just for a specific type of record. It also means that the behavior can be unique.

ERM4SN - Table - sc_cat_item «Catalog Item »