CI not created for Model Category "Monitor" and "Docking station"

[Swarnarghya Gho]

1)Can you please explain why  does Model Category "Monitor" does not have a CI class associated with it by default?

2) I have created a new model Category "Docking Station" without filling the CI class.So when I am creating the asset, it is not creating any CI for that. now the field CI Class is not editable.The CI class cannot be added to the model category later.

Can you please let me know how to fix this issue.

[Harshinya1 · Accepted solution]

In many cases, people do not open tasks directly against a monitor, so the default configuration is to not have an associated CI Class. They are often just tracked as Assets. An incident would then be opened against the computer (if anything) and the monitor is described as the issue for an incident.

When an Asset is created, default business rules that trigger would check if the model category allows to create a CI. In your case, Docking station model category does not have a CI class defined and thereby no Ci was created.

There is a write ACL for CI class field on model category record and it is set to nobody role by default. You can edit that ACL to your desired role and edit the CI class

Hope this helps

[sravs3]

Hi, The scenario above worked as I am able to edit the CI class but getting the error as the Changing the CI class after creation is not allowed and Invalid update. Do I need to disable the Business rule "Protect cmdb ci class" which is running default as given by servicenow. Please share your inputs. Thanks