Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

CMDB Install state moves to retired or non operational

GopikaP
Mega Sage

Hi Everyone, 

 

What happens to a CI when it is not discovered for 60 days? Any OOB scheduled job will run and change its state? Without any configuration?  Something from OOB?

 

Thanks!

1 ACCEPTED SOLUTION

The staleness rule will simply create a task for someone to take action, it would require manual intervention. 

 

Data Manager Policies can be fully automatic, or require a user to approve the change to the CI data

View solution in original post

3 REPLIES 3

Kieran Anson
Kilo Patron

By default, nothing will happen. 

 

However staleness rules or CMDB Data Manager policies can be configured to create a follow on taks or initiate a retirement process automatically 

Hi @Kieran Anson , thanks for taking the time to review this. I have one more question—The staleness rule is set for a 60-day duration, but there is no data manager policy in place. Will there be any OOB scheduled job running to change the state?

The staleness rule will simply create a task for someone to take action, it would require manual intervention. 

 

Data Manager Policies can be fully automatic, or require a user to approve the change to the CI data