Adding custom printer types to the organization's assets

[jeremyduffy]

I'm in IT and we want to add a custom printer type (extend the existing printer CI?). I've been reading how the asset records are supposed to be tied to configuration items so I have some questions:

1. Asset records and printers are 1 to 1 right? So we'd have an asset tag and that would point to a CI and that CI would be an individual printer, yes?
2. Can the existing printer CI record type be extended so we can have custom fields? Does that break everything or does that still work?
3. When we create new instances of printers, does that start as an asset tag or a CI? If you create one, does it create the other automatically?

[k_lutz]

Hi @jeremyduffy 

I would suggest reviewing documentation around configuration items, assets, models, etc. a bit more as some of the terms in your questions don’t align to what I think you may be asking and key functionality depends on the setup of the data, business rules, etc.

1. Asset records and printers are 1 to 1 right? So we'd have an asset tag and that would point to a CI and that CI would be an individual printer, yes? Asset record and configuration item records can be 1:1 but it depends on the model category tied to the model that is associated to the record. You would utilize both for items where there is the need to financially track attributes (asset side) and where you need to populate operation attributes (CI side). I have seen instances where a custom model category is created for a model so it only tracks the asset side and not both. The out-of-the-box (OOTB) model category for “printer” does both the asset and CI classes.
2. Can the existing printer CI record type be extended so we can have custom fields? Does that break everything or does that still work? There is a current extended class for printers related to multi-function. There is no OOTB model category for this class, but you could create one and associate it to the multi-functional one or you could create another extended class. Typically, my experiences has been if it is just an attribute that might be used by any sub-class it should go on the parent. For example…let’s say operating system is on the “server” class as any type of server would use that but if there is an attribute that is specific to a windows server; then it should live on the windows class. Now the decision to create a new extended class depends on how different it really is from the parent. Again, I would look to see what SN does in terms of doing this for other classes like server, network gear, etc. Compare why they have extended classes for those main classes and does your situation match or is it maybe one attribute you want to populate.
3. When we create new instances of printers, does that start as an asset tag or a CI? If you create one, does it create the other automatically? Again, this depends on the model category tied to the model. It can also be impacted by settings on the model as there is a value on there for “not creating an asset.” There is a setting in the model category for “enforcing CI verification” that can stop the asset from being created. But “typically” if you create an asset that has a model that has a model category that says to create an CI; it will create the CI. If you have a CI with a model that has a model category to create an asset; it will create the asset. Also, not all attributes replicate. There is a defined list of attributes that will sync between the two records.