question Automate and s the operational status of CI's as non-operational if 90 days over and no discovery in CMDB forum

Automate and s the operational status of CI's as non-operational if 90 days over and no discovery

MohammadAmzad — Wed, 25 Jun 2025 14:09:33 GMT

Hi all can you please help me, how to set operational status of Cis as non-operational which are not updated via any Discovery source for 90 days

Re: Automate and s the operational status of CI's as non-operational if 90 days over and no discover

YaswanthKurre — Wed, 25 Jun 2025 15:31:11 GMT

Hi @MohammadAmzad ,

Flow Designer Approach (No-Code/Low-Code)

Steps:

Create a New Flow
- Go to Flow Designer > New
- Name: whatever you want
Trigger
- Use Scheduled Trigger
- Run: Daily or Weekly
Add Action: Lookup Records
- Table: cmdb_ci (or specific CI class like cmdb_ci_server)
- Conditions:
  - sys_updated_on on or before 90 days ago
  - discovery_source is empty (or not in known discovery sources)
Add Action: For Each
- Loop through the records found
Inside Loop: Update Record
- Set operational_status to 2 (Non-Operational)
Save and Activate the Flow.

or you can do scheduled script in the same process.

Please mark this as helpful and correct if this helps.

Thanks,

Yaswanth

Re: Automate and s the operational status of CI's as non-operational if 90 days over and no discover

JobyV — Wed, 25 Jun 2025 15:45:07 GMT

You can easily achieve this through CMDB Data Manager policy, you need to create a Retirement Definition and add the Data Manager Policy with the same.

Re: Automate and s the operational status of CI's as non-operational if 90 days over and no discover

MohammadAmzad — Wed, 25 Jun 2025 15:45:51 GMT

thank you @YaswanthKurre , let me try this one, will update you

Re: Automate and s the operational status of CI's as non-operational if 90 days over and no discover

Pratiksha — Wed, 25 Jun 2025 15:47:47 GMT

You need to create staleness rule for ci classes, once the ci state, on stale task you can trigger flow to mark the ci retire. You can also use data manager policy to create retirement policies.

Re: Automate and s the operational status of CI's as non-operational if 90 days over and no discover

MohammadAmzad — Wed, 25 Jun 2025 17:06:44 GMT

Hi @JobyV here are the OOB retirement custom definitions we have but they are active false, can you please let me know which one i need to make active true

Re: Automate and s the operational status of CI's as non-operational if 90 days over and no discover

MohammadAmzad — Wed, 25 Jun 2025 17:10:50 GMT

Hi Pratiksha, these are the retirement definition available OOB , but all are in active , please refer the Screenshots and let me know which one I need to make active or need to create a new one

Re: Automate and s the operational status of CI's as non-operational if 90 days over and no discover

JobyV — Wed, 25 Jun 2025 17:16:40 GMT

It depends on your business requirements, but I would go with Hardware, if you are mainly concerned about Win/Linux etc. Usually, the retire policy is used to set CI status to retired, but you can create your own definition, if that's more helpful.

Re: Automate and s the operational status of CI's as non-operational if 90 days over and no discover

Pratiksha — Thu, 26 Jun 2025 07:34:51 GMT

https://www.servicenow.com/docs/bundle/xanadu-servicenow-platform/page/product/configuration-management/concept/life-cycle-rules.html

Go through this. You can create new for specific class and if you want it on global level then change the cmdb_ci one.

https://www.youtube.com/watch?v=1p74bg6ZK9E