Retire CIs not discovered within the previous 30 days

Mark Weber2
Tera Contributor

How would I write a business rule to set status(hardware_status) to "retired" for CIs not discovered within the previous 30 days?

Thanks

1 ACCEPTED SOLUTION

Chuck Tomasi
Tera Patron

A business rule only runs when the record is updated, so if a CI hasn't been updated, the CI doesn't run.



You might want a scheduled job to do some checking to see if the CI has been discovered/updated in the past 30 days or perhaps just a report would be useful so you can review it.



Reference:


Business Rules - ServiceNow Wiki


Business Rules Best Practices - ServiceNow Wiki


Creating a Scheduled Job - ServiceNow Wiki


http://wiki.servicenow.com/index.php?title=Reporting      


View solution in original post

2 REPLIES 2

Chuck Tomasi
Tera Patron

A business rule only runs when the record is updated, so if a CI hasn't been updated, the CI doesn't run.



You might want a scheduled job to do some checking to see if the CI has been discovered/updated in the past 30 days or perhaps just a report would be useful so you can review it.



Reference:


Business Rules - ServiceNow Wiki


Business Rules Best Practices - ServiceNow Wiki


Creating a Scheduled Job - ServiceNow Wiki


http://wiki.servicenow.com/index.php?title=Reporting      


crc2580
Tera Guru

Hi Mark,


  I would caution you not to automate this process of retirement. If you retire CI's simply due to lack of discovery, you can end up retiring them because of a discovery issue. What if the device is setup to reboot during the discovery window? or a firewall has been setup that blocks scans? or any number of reasons the CI record doesn't get updated?


  I would recommend setting up a report to generate a list of these devices. You can easily setup a series of scheduled reports to hand off to the device owners for them to verify that the CI is no longer present in your environment and enforce your companies retirement procedures.



Regards,


Chase