Difference between Classification, Environment, and Used For

shuchimmishra
Tera Contributor


Could someone please help me understand the differences between the Classification, Environment, and Used For fields in the cmdb_ci table in ServiceNow? Additionally, I’d appreciate guidance on when and how each of these fields should be used.
shuchimmishra_0-1750830588664.png


Thanks in Advance

1 ACCEPTED SOLUTION

Hi @shuchimmishra 

I would say no, and here’s why: the Environment field only has three values (e.g., Dev, QA, Prod), whereas the Used For field has six, serving a different purpose. So, both can be used for distinct needs.

However, if you're just starting out, it's better to begin with the Environment field. Once your process matures, you can introduce the Used For field based on specific use cases.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

View solution in original post

5 REPLIES 5

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @shuchimmishra 

If you look at the Classification value, it indicates whether the server will be designated as a DR server or Production server, and what it's primarily used for — such as QA or Production.

The Environment field typically has three values based on the instance type: Dev, QA, or Prod. It can get confusing when multiple attributes are used to represent similar information. So, based on business needs, it’s recommended to use just one or two of these attributes consistently.

Note that the Environment field is mainly used for change request purposes.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Hi Atul,

Thank you for your response.


Just to clarify—does this mean the Environment and Used For fields are intended to capture the same type of information?

Hi @shuchimmishra 

I would say no, and here’s why: the Environment field only has three values (e.g., Dev, QA, Prod), whereas the Used For field has six, serving a different purpose. So, both can be used for distinct needs.

However, if you're just starting out, it's better to begin with the Environment field. Once your process matures, you can introduce the Used For field based on specific use cases.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************