Application Service class: "Used for" vs. "Environment" field?

Jacques Clement · ‎09-09-2021

Hi -

Does anyone know why on Application Service (and other Service tables), we have both Used for and Environment to model the environment. They both seem to represent the same thing - or am I missing something?

Thanks

scott_lemm · ‎09-09-2021

A bit of history here:

1. used_for is a legacy attribute in ServiceNow CMDB and not present on all CMDB classes

2. The used_for label is quite possibly the worst label in all of ServiceNow CMDB. The industry refers to this data as "Environment". Due to the poor name, many customers didn't know this attribute existed. The #1 custom created attribute in ServiceNow CMDB is "Environment".

3. The oob Environment attribute is our effort to right a wrong by providing an object that is available on all CMDB classes and labeled appropriately as "Environment".

Eventually, after customers have migrated from used_for to environment, we will deprecate the legacy used_for object. We recommend you utilize "Environment" in your operations.

Hope this helps in understanding why both objects exist.

View solution in original post

Andy Hopper · ‎02-01-2024

Hi @scott_lemm , sorry to resurrect an old thread but I think @Jim Zeigler1 's question is still relevant - can you provide any insight as to why SNC didn't elect to push users towards the Environment table [cmdb_ci_environment] instead of choice lists? Referencing the table seems like the natural choice. What are SNC's plans for this table going forward?

Daniel O_Reilly · ‎06-12-2025

Hey Scott,

I think the memo may have been missed in here in developing EA Workspace. The insights tab for technology portfolio when you select "Show only production" it sets a filter using the "used_for" field. Looks like this is running off the InsightsUtils script include.

Not a huge deal but has been bugging me, any plan on fixing this.

Jacques Clement · ‎09-09-2021

Very clear, thanks!

Jacques Clement · ‎09-15-2021

Hi. Just realised that some of the use case PDFs still refer to the Used for field. I have not checked them all but e.g. Change Product View for CSDM 3.pdf explains that "The environment maps to the attribute used_for." (page 6).

Maybe something to consider if those papers are reviewed along with the 4.0 version of CSDM.

Thanks!