Inactivate ICs

LucasEduarF
Tera Contributor

Tuesday

I'm creating a script to deactivate configuration items that are outdated, meaning those that haven't been discovered in over a month. The lifecycle stage and lifecycle stage status fields are active, and that's why we decided to use the latter. Is this correct?

0 Helpfuls
  • 100 Views
1 REPLY 1

Pratiksha
Mega Sage

Tuesday

the first step should be to configure staleness rules correctly.

Staleness configuration allows you to define what “outdated” means for your organization. For example, you can specify that if a device has not been updated or discovered in the last 30 days, it should be considered stale.

Once this is in place, ServiceNow can automatically:

  • Identify stale CIs

  • Create a Stale CI task for each affected device

These tasks can then be assigned to a support team or CI owner to investigate why the device is no longer being discovered (for example, agent issues, credential problems, or decommissioned systems).

However, if your process does not require investigation—for instance, if you already know that such devices are no longer in use—you can go a step further. Using a Flow or automation, you can:

  • Update the Operational Status to Retired

  • Update the Install Status to Retired

This approach ensures that:

  • CMDB data remains clean and trustworthy

  • Manual effort is reduced

  • CI lifecycle is managed consistently and in alignment with governance practices

In short, staleness is not just a health metric—it is a control mechanism to actively manage CI lifecycle and maintain CMDB accuracy over time.

 

Here is how to guide : https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-manag...

 

Regards,

Pratiksha

0 Helpfuls