Hello all,
I am seeking some best practice guidance and advice. We are considering automating some of our staleness rules for our Configuration Items (CIs). I am currently evaluating the possibility of building a flow or sub-flow to manage this process. The flow would perform a record lookup for the hardware class, log it as a variable, and update the operational status to non-operational, while keeping the hardware status/asset status unchanged until the CI owner can verify the need for retirement or address the issue with discovery.
I am wondering if there is an effective way to integrate this with the newer retirement definitions and data management features from the CMDB Workspace, or if I am overthinking and putting the cart before the horse.
Additionally, I would like to mention that we are in the early stages of our governance process and are still working on gaining buy-in from our teams. As a result, much of this effort is currently one-sided.
