cmdb retirement policies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-16-2024 03:17 PM
Hello all!
recently we have begun turning on retirement polices--- they are very loose
(CI hasnt been updated or discovered in 6 months) just to get a feel of the process.
however, we have run into an issue where the CI is discovered, after its retired/non-operational, and it will not pull the CI out of retirement. I was under the impression that it should automatically, but alas, here i am. My initial thought was to create a business rule to change back to operational-- but i feel like thats too simple?
Can someone please advise?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-17-2024 02:13 AM
OOB the state isn't changed back, so you need to apply that logic (preferably within the discovery part of the platform). But if that's not working for you, you could have a BR or flow on change of the last discovered date/time on non-operational/retired CI's to set it.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-17-2024 07:09 AM
understood---- but what do you mean by "you need to apply that logic (preferably within the discovery part of the platform)"
is there a setting i can adjust?
