How can I automate using ServiceNow to Retirement/Decom application/Infrastructure?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-23-2019 12:32 PM
Has anyone leveraged ServiceNow to automate the retirement/decom of configuration items? Can the release module be leveraged and a Retirement Release would be set-up and all the change requests need to retire the application assets would be created against that release? We currently run reports to pull all the CI's but would like to create CR's.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-23-2019 01:26 PM
I feel the best place to start is some of the out of box functionality when it comes to proposing a change to a CI -
https://docs.servicenow.com/bundle/helsinki-servicenow-platform/page/product/configuration-management/task/t_AddAProposedChange.html
We have not done that here yet but it is functionality we're looking at.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-23-2019 01:35 PM
We're going through the process right now. I think we've settled on a record producer that generates a Change. 3 pre-tasks (ie pull the plug) define the planned window, then wait 2 week and then trigger 7 post-tasks. If physical server, 2 more on-site tasks. Since we're not using Discovery yet, just because a CI goes Retired, doesn't mean that's correct.
