General Catalog "Add Catalog Class" vs "Add Catalog Item"

[Giulio Soleni]

Hi, sorry for my naive question but I cannot find a real answer in the manual...
I tried to add a new CI, as a test and NOW I see that the correct procedure would have been:
- Admin > General Catalog > ITSM::ConfigItem::Class > [Add Catalog Item]
- Admin > Config Items ... to edit the new CI class specified.

Instead, on my first attempt, I started directly from:
- Admin > General Catalog > [Add Catalog Class]
and I added a Catalog Class with the following specifics:
* Catalog Class: ITSM::ConfigItem::MyClass::MyType
* Name: MyItem1
Valid: valid
Comment: test new class definition in General Catalog

My questions:
1. what did I do?
2. is there a way to remove/edit or at least to use my new class definition somewhere? In other words what's the use of the [Add Catalog Class] button in General Catalog Management?

Thank you,

[crythias]

Because I'm too lazy to look, what would be examples that you see of other classes?

[Giulio Soleni]

besides the class I wrongly defined (ITSM::ConfigItem::MyClass::MyType) the list of available classess comes from the defaults of the ITSM bundle.
You can see it in the attached pic.

By clicking on each specific class the available submenus specifies the items (I'd say the instances sub-classess) already specified for that class.

What I'd like to know is if behind each one of that entries there is also a configuration file (maybe an xml file or something like that) that is used to specify the possible parameters that may be set for any items of any specific class.
For example, the parameters that have to be defined for a new CI (that is a new item of ITSM::ConfigItem::Class) are Name, Permissions, Valid and Comment, while the parameters that have to be defined for a new item of ITSM::Core::IncidentState are Name, Incident State Type, Valid and Comment ... and so on... generally speaking I see that all the classess let specify items that should be defined by Name, Valid flag and Comment field.

So... even if my test was a complete error... I would like to know what's behind my ITSM::ConfigItem::MyClass::MyType definition and what - in case - should I add to complete the definition of a new class that I simply got by filling up the fields after clicking [Add Catalog Class] button in General Catalog (should I specify a configuration file, a template...)

Edit: I named 'instances' the items that can be specified for each class but I guess they are classess themselves ... so it would be better to call them sub-classes (e.g. "Monitor" is an Item of ITSM::ConfigItem::Hardware::Type and for sure it is not an Instance but a class of objects)

[crythias]

If I recall correctly, and I'm not sure I"m correct, I believe the classes are intended to be "Containers that have a set of fields to fill".

Edit: Note that you created a ConfigItem and not simply a foo widget. Which should mean that the fields attached to the Custom ConfigItem should be available when adding one to your Catalog.

[Giulio Soleni]

Edit: Note that you created a ConfigItem and not simply a foo widget. Which should mean that the fields attached to the Custom ConfigItem should be available when adding one to your Catalog.

well... I *thought* I created a new ConfigItem but I actually created a foo widget that cannot be retrieved among the list of real available CI's.
As I afterwards noticed, the correct way to define a new CI sub-class is to set a new item starting from ITSM::ConfigItem::Class

I mean that by using the [Add Catalog Class] button I probably would have got the same result even if I defined ITSM::MyDummyClass::MyType instead of ITSM::ConfigItem::MyClass::MyType