Enivornment, Used For and Service Instances

[Tone1]

Hi everyone,

I’m currently refining our CSDM 5 implementation and have a conceptual question regarding Service Instances (cmdb_ci_service_auto).

In the Service Instance Wizard, we can only select Production, Test, or Development for the Environment. However, the record itself also has the Used for (used_for) attribute with more granular OOTB choices like QA, Training, and Staging.

I need to create a Service Instance that is technically hosted within our production infrastructure, but its sole purpose is for Training. I’ve read in older posts that used_for is considered legacy and we should focus on the environment attribute.

Could someone clarify if used_for should be completely avoided in CSDM 5? If so, is the best practice to simply add custom dictionary choices (like "Training" or "Staging") to the environment field so they appear in the Service Builder, and how do you generally handle such a "Production-Training" instance in your data model without breaking governance?

Thanks in advance for your insights!

[fknell]

HI @Tone1,

The used_for field is already declared to be deprecated and shouldn't be used anymore. The environment field is the replacement, this explains also why you find it in the Service Instance Wizard.

It was mentioned in the CSDM training, but I try to find you an official statement.

Edit: It's in the slides, that come with the class.

Hope this helps!