Serial number mandatory oob on cmdb_ci? Does anyone actually leave this like this?

[bleedy]

If you do leave it mandatory, what does your health dashboard look like? (Mine's a mess because of it)

If you disable this, what did you do to make it required on child classes? Dictionary overrides?

[boteeuwen]

Hi bleedy,

Serial number isn’t mandatory on the base cmdb_ci class out of the box. I’d check the dictionary entry and any existing overrides to see where that requirement was added. If it’s mandatory on cmdb_ci, classes that don’t have serial numbers can inherit it, which would explain the Completeness results you’re seeing.

I’d remove the requirement from the base class and use dictionary overrides on the specific child classes where a serial number really is required. If your main goal is to spot missing values without stopping Discovery or integrations from creating CIs, you can set serial number as a recommended field for those classes in CI Class Manager under Health and Completeness. For manual entry only, a UI Policy on the relevant forms is another option.

If this helps, could you mark the reply as helpful or as the solution?

[bleedy]

I would beg to differ. It's set to true by system in my instance. That sounds a whole lot like oob to me.

The only overrides are to set it to false on some classes. So, for me, I'll need to think about what should have a serial number and add it to it I guess.

Sounds like you're saying override it at the child class level's dictionary instead of at the base ci. Makes sense.

[bleedy]

We just got this instance a few months ago. All settings on the same date, by System. It's update number 0. Seems like newer instances come with serial number set to mandatory on the base ci, which makes zero sense.

[SGienow]

Do yourself a favor - pull up a PDI etc, and take a look there.  I had one provisioned yesterday and it is not mandatory.