New Hardware asset record model category

ncp · ‎05-19-2017

We import hardware records and automatically create hardware assets from Dell's Advanced shipping notice. They have a Asset category defined as Desktop which I was planning on mapping to a model category of Desktops in ServiceNow. The issue with that is, this model category does not have a defined CI Class that maps to the asset class, so what happens is a CI is not created.

1) I looked to see if I could add a cmdb_ci_computer class to the Desktops category and I cannot

2) I would have to map the desktop to computer which already has that the ci class defined, the issue with that is I wont then be able to identify dekstops from notebooks or thin clients

Any ideas on how we can map and automatically create a CI for the Desktop model category?

The other question is why is the model category a mandatory field when creating an asset - the model already maps to the model category and if you go to the model its a slush bucket where you can pick multiple model categories

Thanks

Chandran

Community Alums · ‎05-22-2017

Hi Chandran,

I agree with the idea that these devices should not require their own classes in the CMDB. It can overcomplicate matters.

My recommendation would be similar to Andrew's with regards to using the Form factor, but I would NOT use the one that is available by default on the CI records. The CI record really is not the place for this type of information. It should instead be on the Product Model record (I would add it to cmdb_product_model; this makes it easy to display the value on the Asset and CI records if you want) and input the choices you want.

With this value set on the Model, you should have just a little work to identify the laptops, desktops, and thin client models. This should be pretty quick and painless to do in groups in the list view, especially if you focus on models in your environment.

Without knowing much about how you have the ASN details coming in, I would have these all point to the Computer as it sounds like they are doing. Then you will get your CIs properly.

A couple points about some of the information shared above:

While you cannot add a CI Class after a Model Category is created, you can add an Asset Class later.
Rather than messing around with the Business Rules and Script Includes that create CIs from Assets, use the Model Categories to support your work. If you do not want a CI created for a particular categorization of device, make sure you have a Model Category that has an Asset class defined but no CI class.
There is often confusion about the Model category on the Model records. If you consider it, it is likely that a Model could be associated with multiple Model categories. For example, that new ProLiant could be a Computer or a Server or a Windows Server or a Linux Server. In fact, in the course of its operational lifecycle, the device might go through several different categories. The Model category just helps when you are creating the asset to limit the Model selections. When the Service Catalog is used, the first Model category on the list is selected as the Model category.

I hope this helps,

Ben

View solution in original post

Chad Wilhelm1 · ‎12-09-2017

Hello,

Is there a way to restrict ci creation to only to certain model category on asset? I have tried through mapping and messing with the create ci business rule but no luck.

Thanks,

Chad

Community Alums · ‎12-11-2017

Chad,

Yes. If you use a Model Category that only has an Asset Class associated with it, the system does not create a corresponding CI.

Ben

Chad Wilhelm1 · ‎12-11-2017

Hello,

We were able to resolve this by altering the Create CI on Insert business rule. && current.model_category == 'e01de6b513d7ba80fa7c73076144b061'.

Thanks,

Chad

Community Alums · ‎12-11-2017

Chad,

I highly discourage modifying the Business Rule here. Model Categories were designed for this purpose simply by identifying what CI class and Asset class is associated with the Model Category. Modifying the BR affects upgrades (which is sometimes okay), but this particular adjustment also makes it very difficult for you to see what is going on. If you later want to create a CI for this Asset class, or you look at it and try to figure out why down the line (or someone besides you), it is going to involve a fair amount of research and hunting to figure out what is going on here.

Ben

Chad Wilhelm1 · ‎12-14-2017

Thanks Ben, how do I go about removing the asset from the other model categories since I only want Audio asset to create ci's, the field is not editable?

Chad