Best way to update the Environment in the CMDB CIs

[Deepanshu Grov1]

Hi All, 

There is one challenge I am facing and need experts advises here. 

we have 2 environments lets say PROD and TEST of cloud and discovering both of them and populating the data into ServiceNow Prod... there i want to segregate the CIs coming from PROD and Test cloud platform. 

I am thinking that there is a field in the CIs form "Environment" and this can be used to map as Test or PROD, some conditions can be configured either in the Business Rules or Flow designer to update the field with Test or PROD depending upon from which midserver or user discovery is creating/updating CIs. 

Has anyone done this already and got some best advise/lesson learnt? 

Thanks

Deepanshu Grover

[suvro]

Mostly we can use before/after Business Rule. The point is based on what we can say that a CI is from which environment.

In one of our projects the naming convention of the CIs used to determine the environment. Production CI name used to start with P. 

So we used a before Insert Business Rule to check 

if (current.name 'STARTSWITH' 'P'){

current.environment = 'production';

[Deepanshu Grov1]

I was rather thinking to put a flow, on create and update and restrict the same with Users as I have different user for different environment  🙂 

[Deepanshu Grov1]

I prefer flow designer more, but don't you think either BR or Flows will check millions of CIs and make the instance slow, no matter discovery jobs will run during the odd time, this will still consume a lot of processes.