CMDB Custom Attribute Creation

[sanjeev28 k]

Hi All,

We added all the custom attributes to OOB classes like port, service and circuits.. but there was a comment from servicenow that we should extend these classes as new custom class and then add the custom attributes there.. Ex. create a new class called u_Circuit for circuits which is   a new table and is an extension of cmdb_ci_circuits. The custom attribute that we need will now go into u_circuit instead of cmdb_ci_circuit.

so I just wanted to know what is the best practice for extending the CMDB class and creating custom attribute ...and is there any implications   if we will create custom attributes on OOB cmdb_ci child tables?

[Chuck Tomasi]

Hi Satya,

Yes, you can add fields to the existing table. There are no upgrade issues for doing that. In fact, the system was designed to allow you to create your fields without conflict or impact to future upgrades. Customer fields are prefixed with "u_" in the global scope and the scope name in a scoped app so there's no potential for conflict.

The only decision you need to make is "Is there any value in extending this table?" Do you need to segregate those new fields somehow from the existing table? E.g. is it an entirely new class of business service? If not, then go ahead and put your new fields on cmdb_ci_business service. Pretty simple and straight forward.